131–140 of 142 posts
After being burned really badly by Ember and Meteor, I'm probably never going to use tools that are all-in-ones ever again. With React I get something laser-focused, just does 1 thing well and that's it. With Vue, I have to buy into the entire ecosystem. I don't want to experience what I did with ember and meteor ever again in my professional life. I think about all the great developers I've worked with and I looked…
Earlier quoted context omitted.
What drives me insane about Angular, both 1.x and 2.x, is the sheer amount of idiosyncratic boilerplate required to merely get started and do things the "framework way". It's unreal, though of course Angular 2.x takes that to a whole new level. AngularJS could at least be written in vim without boilerplate generators and meta-meta-meta tooling. I suppose the thinking behind all these services, providers and factories…
So ... actual developers are people who don't work on teams for large scale applications? Because what you call "childproofing" is basically the most obvious tenets of a shared codebase.
Don't forget about others, such as Preact [1] [1] https://github.com/developit/preact
The thing that sold me on Preact is its compatibility layer with React, which provides a kind of de facto standard API for components. One day I just replaced React with Preact, with the only difference being a happily reduced app size - and have been using it since. I don't plan to keep up with React's latest developments - I'm satisfied with the rendering performance of Preact, and want to stick to a stable API which lets me focus on actually building things with it.
I feel the same about client-side routers, the build process with Webpack, etc. - I'm fatigued of keeping up with breaking changes, and have started transitioning to smaller, individual libraries that just do their modular jobs, with minimum API surfaces that are reliable over long-term.
[0] https://github.com/maxogden/yo-yo [1] https://github.com/WebReflection/hyperHTML
Upvote if you're still using Vue in 2017! /s
It's a bit disingenuous to say that Facebook uses Vue for Newsfeed. It's on a marketing site, not on a performance and business critical part of the site. These marketing sites are very often built by contractors, not FB engineers, and tend to be one off efforts. Not to knock Vue, but it weakens the message when deliberately misleading info like this is used
I've seen the word "disingenuous" used many, many ways over the internet. People keep using this word, I don't think it means what most people think it means. Because it doesn't: "not candid or sincere, typically by pretending that one knows less about something than one really does." There's nothing insincere about saying that newsfeed.fb.com uses vue because it does. It isn't pretending to know less, if it were fal…
I think there's merit on staying small-ish. Not every framework has to be a giant that dominates the industry. Having a small community means the potential for focus and strong canonical learning resources, as opposed to the mess of poorly written React and Angular posts/"guides" we get every week. The community feels tighter and it may be easier for the maintainer(s) to manage it and the codebase. Ember is a good ex…
Earlier quoted context omitted.
You don't understand? Just read the thousands, probably millions, of explanations on that and other advantages and disadvantages of both dynamic and static languages in the thousands, probably millions, of discussions that have been about it for the past sixty years. What? You thought dynamic languages were a new fad? They have existed as long as computer science has, exactly like static languages. For what it's wort…
> You don't understand? Just read the thousands, probably millions, of explanations on that and other advantages and disadvantages of both dynamic and static languages in the thousands, probably millions, of discussions that have been about it for the past sixty years. I've worked a lot with static and dynamic types, read a lot about both and in my opinion static typing has clear and obvious advantages. > For what it…
You can read on advantages of dynamic languages everywhere, I was just pointing out that your point of view, and the point of view disagreeing with you, isn't anything close to new, making the attempt to start a flamewar in your first post, and trying to continue it here, all the more pointless.
BTW: Good coders are factor because no amount of "you have to write 'string' or 'int' before the name of the variable" is going to save a bad coder from producing bad code.
Earlier quoted context omitted.
I'm going to go out on a limb here and say "Never attribute to malice what can easily be attributed to ignorance". I have a feeling the author did not intend to mislead their readers. I feel that it is more likely that they didn't look too deeply into the subject. It's fairly simple to attribute some piece of work to Facebook when Facebook's branding is plastered all over it.
Fair comment. However it's fairly clear that there's a difference between a complex web application which pushes a library to its limits, and a page describing that application. The author must have known this and thought it'd be funny to be able to say that Facebook uses Vue in their flagship product. They really didn't need this to sell their point and should have just left it out. While it makes a humorous point,…
It's the best parts of Angular and React in one framework. I don't know why you'd want to use anything else.
What are the good parts of Angular that are in Vue?