141–150 of 244 posts
It doesn't make sense :-/
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
I'm still using Jquery and some of the millions js libraries available only when you do not bind yourself to a SPA framework taking control of the DOM. And it work pretty well I must say! My opinion is that for 80% of the websites out there, a SPA framework is not only overkill, but is also a bad choice. Your website is probably not Gmail or Facebook. Server side rendering is perfectly fine. We should start a competi…
...and yeah - most likely you don't need React+Rxjs+Redux for a wizard-like prev/next multi-select online-quiz, but it's me looking for a job so you're right. Hell - let's throw in async/await as well. You'll need a space shuttle to debug this thing.
Earlier quoted context omitted.
Funny, I've worked with multiple companies and their lawyers who were very serious about license compliance and what not. It took all of fifteen minutes to prepare a spreadsheet of our licenses (planned, anyway). Not a complaint from any of them, other than an "oh, that's more than I'm used to seeing." The one sticking point was webpack 1; they had some dependencies with unlicensed dependencies. Fortunately, we were…
Fair enough. Now imagine that your product or service is gaining popularity on the market where Google or Facebook consider you a competition.
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
I'm coming from a similar background and mindset but over the past few months I've been doing a lot of prototyping and some production using Vue without the build tools. I just include vue.js and use x/template scripts for the templates. It's definitley saved me hundreds of hours already.
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
https://reactjs.org/tutorial/tutorial.html
This allow you to start off with a great setup and skip the configuration so you can get started with just writing React. I highly suggest starting with official docs before writing these off. A lot of other tutorials are of varying quality but you can trust the official docs for sure until you learn more about the community and which resources are worth it (or just use this https://github.com/markerikson/react-redux-links). It can be overwhelming if you aren't actively following the front-end world but the reality is that you need very little node knowledge and can go a very long way without ever touching webpack + babel. Even then, once you get to the point, learning to configure those things won't take much time and to me, it's worth it for the developer experience.
If you really want to dabble in just writing React code, you can also try these browser IDEs if they float your boat.
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
It discourages us full time FEs too. Webpack and a full transpile pipeline is still relatively new to JavaScript but it seems like we’re starting to land on some assumptions (and thus making this a more turnkey process) ES6 Route based lazy loading Some sort of typing (TypeScript or FlowType) CSSModules React with JSX Redux The reason it’s been so difficult is because we’ve had a sort of Wild West mentality where we…
Earlier quoted context omitted.
I don't know... not all web standards worked well in the past: xhtml, appcache, etc. I wouldn't be surprised if web components never got success. Why should anyone use this standard when a library is 10 times better? Being the standard is not enough.
You're just assumming the library is 10x better. One reason to use web components would be it allows for a much more lightweight abstraction over DOM.
Earlier quoted context omitted.
If you think Facebook will still be there in 10 years, then you can safely pick React.
> If you think Facebook will still be there in 10 years, then you can safely pick React. At the same time, you could've made that same argument at some point with Google and AngularJS, Dart, Polymer, etc. Not necessarily a safe bet.