221–230 of 244 posts
Earlier quoted context omitted.
Not to be a jerk, but can you provide any links to large sites or apps that use Ember? Again,this is a serious question, as I like to keep tabs on trends for JS stuff like this.
LinkedIn uses ember, but other than that I have not heard about big examples either.
Reasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is html javascript css - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple…
> - Sane way of scripting puts the script in an object and each component is html javascript css Each component I have in React is script + css. It did require some setup though. > - Don't need to know jsx! Except you need to learn the v- bindings. I prefer JSX and JS here. > - two way data binding with vue-model Two way data binding is a problem, not a feature.
Vue's "two way databinding", i.e. v-model directive, is actually just a syntax sugar that's equivalent to adding an event handler and a dynamic property on the value/text of the element.
Purely from an outsider perspective, it's interesting to see all the different frameworks out there, but for front end devs I can't help but feel that this type of comprehensive list hinders more than it helps. One key thing JS needs less of is fragmentation. If I were in the front end dev community I'd want to see people making the front runners more mature and flexible, not endlessly fragmenting just because they s…
I actually think fragmentation is ideal, it demonstrates the failures in a system more cleanly. For example, I started with Protoype.js many years ago, after a bunch of research at the time. But then later switched to jQuery, because it was simply better in every way. There simply was no fixing the problems with Prototype.js, they were inherent in the system. I think when a fragmentation occurs in every framework, it…
My argument isn't that frameworks do not have any utility (right now), my argument is, if you stick to a smaller selection of frameworks and work on both polish and flexibility, you'll have frameworks that make people want to develop in JS. At the very least it'll mean that the basics would be easy, and design decisions could be deferred until later in the site design.
Earlier quoted context omitted.
Yeah, In my day to day work I do a little bit more than the OP and know some react/webpack and such. But the last time I needed something a little complicated I ended up using VueJS. If you don't want to do it the "right" way (ie, a whole build system and such) you can just toss the file onto the page with a script tag and get to work with your scripting wherever you feel good about doing that.
> If you don't want to do it the "right" way (ie, a whole build system and such) you can just toss the file onto the page with a script tag and get to work with your scripting wherever you feel good about doing that. The "wrong" way, in this case, is not only the "right" way, but the only way. Any javascript framework, no matter how esoteric or abstract, has to wind up generating one or more javascript files to be ca…
And I agree with your assertion that it's nice to be able to shove a pre-built script somewhere... but I've been working on toy react/redux apps and I feel like no, that would miss the point of the tooling and workflow that I want to learn.
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 learnt a lot from the article Modern JavaScript Explained For Dinosaurs [0] (featured on HN recently), which explains the history of developments from vanilla JS to 2017, "a historical context of how JavaScript tools have evolved to what they are today". I thought it was brilliant at making sense of the jungle you describe. I'm pretty sure it will remove the dread. [0] https://medium.com/the-node-js-collection/mode…
I like that the only con for Vue is there's no jobs for it. Having done two major projects in React and Vue, Vue is my preference. While vue is supposedly faster, speed has never been an issue for either. I think the biggest thing for me is it's just easy. While I like React, I think vue is nicer and often more concise, and if you really want jsx, it also supports that. I also use Bulma for the visual side which work…
i mean its also because the author is obviously biased toward vue. see the other comments here for why people actively pick react over vue. dont confuse the printed word for fact.
I built major things with both react and vue, I like both, but I like vue more.
Earlier quoted context omitted.
Don't expect to learn React (or Angular) in an afternoon by reading a couple of tutorials. Go to Udemy.com . Buy a couple of courses for $20 and spend a week following them. After that week, you will be able to start programming in React.
The official React tutorial is excellent and I learned the basics of React from that and was up and programming in a day. It took me a couple of weeks to understand the library in more depth, but there just isn't a whole lot to React. For Angular I agree it takes far longer.
Some people, when they pick a new technology, they choose to spend an afternoon reading half tutorial and then start coding straight away. By the time they finally "get it" and start to write decent code, they already put 5000 lines of spaghetti in production that some other developer will have to cope with in the future.
Earlier quoted context omitted.
The official React tutorial is excellent and I learned the basics of React from that and was up and programming in a day. It took me a couple of weeks to understand the library in more depth, but there just isn't a whole lot to React. For Angular I agree it takes far longer.
You cannot learn React in one day. No matter how clever you are. You can learn enough to start coding but, until you understand Redux, how to use selectors with Reselect, middlewares, async-actions and the component lifecycle, you will be writing awful code. Some people, when they pick a new technology, they choose to spend an afternoon reading half tutorial and then start coding straight away. By the time they final…
Earlier quoted context omitted.
Can you use react without Node or NPM or a compiler/transpiler or build tool?
Of course - just pop it in a script tag and use the React object functions to render your DOM (which is exactly what transpiled code does)