21–30 of 113 posts
When did Vue hype officially start ? It's funny to see how deeply HN crowd is driven by vouge.
I thought it had more to do with all the noise lately around the React PATENTS, but I could be wrong
Earlier quoted context omitted.
I know this will get downvoted, but here I go anyway: Please stop reinventing the wheels. Just stick to one library/framework whatever crap they are. Why? Because your new shiny wheel will be as crap as the old one very soon. I am myself refusing learning new tools in javascript. I think I have spent enough time learning enough of them. I have a selected set of them, and I turn down projects which fall out of that se…
Webpack came out in 2012, Brunch in 2011. So clearly everyone should stop using Webpack and switch to Brunch, or they're guilty of reinventing wheels.
When did Vue hype officially start ? It's funny to see how deeply HN crowd is driven by vouge.
mainly its the react fatigue, thats finally tipping them over the edge to try something better. vue seems to have come in at the right time for that. and given the momentum, its possible that vue may supercede react at some point if this keeps up.
Also, this endless churning is not how you develop expertise. The way things are at the moment you've just about learned to work with the quirks of one framework and then you have to pick up another one.
It's completely ridiculous, especially when in a lot of cases the benefits of one technology over another similar technology are pretty marginal.
I mean, come on: can you honestly say that Brunch is a quantum leap on from WebPack (or vice versa), or that WebPack is a quantum leap over Gulp (or, again, vice versa)? I don't think so.
By contrast, you become an expert by sticking with things and developing deep understanding. I've therefore reached the point where I'm only interested in the browser APIs and JS libs that are proven, battle-tested, and have stable APIs. I don't want to waste time rewriting code that was working and is now broken just because the previous API version offended the aesthetic sensibilities of some capricious maintainer.
(Sorry, I do tend to get quite grouchy about this stuff.)
If you're looking for alternatives to Webpack, please also check out JSPM (a good short description might be "preprocessing system + package manager + systemjs"): https://jspm.io/ It takes a little more to get it to work with vue (the plugin that makes .vue files work is older and unsupported nowadays), but I use it just fine, with my template, styling and component files separated (I wrote a little thing: https://gi…
Rollup looks pretty good too. It's on my list to play with. https://rollupjs.org/
Earlier quoted context omitted.
mainly its the react fatigue, thats finally tipping them over the edge to try something better. vue seems to have come in at the right time for that. and given the momentum, its possible that vue may supercede react at some point if this keeps up.
I'm getting pretty jaded with the JS ecosystem as a whole. I don't want to have to learn new (effectively throwaway) technologies every few months because, fundamentally, I'm interested in building valuable products, not in learning technologies as an end in itself. Or, in other words, I have better and more interesting things to do. Also, this endless churning is not how you develop expertise. The way things are at…
> The way things are at the moment you've just about learned to work with the quirks of one framework and then you have to pick up another one.
Frameworks shouldn't really have quirks, they should ideally just work with a standard API. Of course, it's never that easy, but we're converging on that with custom elements. This is like switching from MySQL to Postgres. It's 90% the same, the edge cases you can figure out and migrate, and you don't really care about how it's implemented.
It's not like you're trying to learn a new keyboard layout.
Just looking at long chains of mystery-meat that npm imports, and the time it takes Babel to compile the simplest of projects make me just want to say the hell with it all and do everything as GET/POST.
Earlier quoted context omitted.
mainly its the react fatigue, thats finally tipping them over the edge to try something better. vue seems to have come in at the right time for that. and given the momentum, its possible that vue may supercede react at some point if this keeps up.
I'm getting pretty jaded with the JS ecosystem as a whole. I don't want to have to learn new (effectively throwaway) technologies every few months because, fundamentally, I'm interested in building valuable products, not in learning technologies as an end in itself. Or, in other words, I have better and more interesting things to do. Also, this endless churning is not how you develop expertise. The way things are at…
Also incremental improvements are a thing in lots of fields. Science and math make small amounts of progress, build to a critical mass of new theory, and then a new field or concept can be born.
Everytime I search for sites that use frameworks like Vue or React, I came up with mostly empty hands. Except for example pages or pages by coders for coders. Or pages that "use" one of the frameworks but seem to make no use at all of the functionality.
When I ask around people usually tell me "Well, at my company we make a dashboard for another company and it's based on ..."
Any popular public sites (Aka no login needed to access it. So Facebook doesn't count.) for non-coders out there that use these frameworks?