[deleted]
Will Vue.js become a giant like Angular or React?
91–100 of 142 posts
Re: Will Vue.js become a giant like Angular or React?
#92Vue.js is a step backwards, relative to React, in my opinion. What I love about React is JSX (or TSX if using TypeScript). JSX is a combination of JavaScript and HTML syntaxes. You don't need to learn a new syntax in order to incorporate loops and conditionals in the view layer, thanks to JSX: you just use JavaScript. More importantly, you get compile-time verification. If you use a JavaScript variable in JSX and som…
Funny to read this--talk about the benefits of strong-typing, etc. The dynamic nature of JS was once a benefit. Granted, it wasn't initially purposed for full-out browser facing SPAs, etc. Still, strong-typing has been with us forever and, in general, I feel like we've solved this problem. I'd like to see a light-weight VM framework that supports Java code compiled down to JS, with an in-browser Swing-like component…
You can sort of do this with Emscripten + webasm, though I don't think async is supported yet.
Re: Will Vue.js become a giant like Angular or React?
#93React will continue to dominate thanks to react native. Neither Angular or Vue.js has a solution for mobile as nice as react native, at least as far as I know.
You might want to have a look at Weex, aka "vue native": https://weex.incubator.apache.org/
Also nativescript: https://www.nativescript.org/blog/a-new-vue-for-nativescript
Re: Will Vue.js become a giant like Angular or React?
#94I 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…
You may be right about the quality of meetups, but meetup quality is a pretty unusual metric for a JS framework's success.
True. At work we use React for the practical reasons explained by others in the comments.
My point was that Vue doesn't need to be huge. It's fine the way it is and its current size has some benefits.
Re: Will Vue.js become a giant like Angular or React?
#95Earlier quoted context omitted.
> More importantly, you get compile-time verification. If you use a JavaScript variable in JSX and someone deletes that variable you find out about this issue at compile time. This is very important for large projects that multiple developers are working on together. I'm still amazed people argue that statically typed languages don't make you more productive compared to dynamically typed languages.
Vue templates are checked at compile time with the default runtime-only distribution, and the DSL it uses is arguably more checkable than JSX.
Sure, I'm just saying I don't understand how people that like dynamic typing can't see the productivity value in being told e.g. a variable isn't defined or a function call is missing arguments at compile time.
Re: Will Vue.js become a giant like Angular or React?
#96After 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…
This is the philosophy behind why I went with Knockout years ago - and am now helping maintain and write version 4.
Specific, narrow focus and it's served me well. Sensing the innate liability, I've never felt the allure of the full fledged framework.
Re: Will Vue.js become a giant like Angular or React?
#97Tried Angular, ReactJS and VueJS and to me, they have their own strengths, but all are more than capable as frameworks for building large and solid enterprise level apps. IMO, productivity and simplicity has Vue winning my preference.
Reading the article, I was surprised at this part:
"Wait, did I just write Facebook? Check Facebook’s newsfeed."
I did checked facebook's newsfeed and certainly, the Vue Devtools lit up on my Chrome browser, which detected VueJS being used on that page. Given that FB has heavily leaned on React, I wonder why they would be using Vue on one of their premiere pages? Is it because they are also trying to analyze what's being offered by Vue and integrate it with React in the future?
Re: Will Vue.js become a giant like Angular or React?
#98Earlier quoted context omitted.
It's funny: I'm not even a web developer by trade, and perhaps precisely because of that fact, every other day at least I have a conversation with a colleague that goes something like, "Wouldn't it be great if there were Swing for browsers?" The idea of pre-styled and easily laid-out widgets holds a great deal of appeal. Vue and Bootstrap come close to giving me that, but not quite.
Yeah, Swing is actually fun to write. Possibly because its paradigm is elegant and such a natural fit for the problem that you don't spend time fighting to fit a square peg in a round hole. Shame it came with such an unwieldy deployment model that it never gained more traction.
For me personally, the biggest selling point is not having to evolve the skill set of design and layout. I'm a developer, not a designer, and the ROI on me learning the fine points of CSS is very low. I already know the bottom 80% of CSS, but who doesn't? It's the top 20% where the "magic" happens, as with so many things.
Pre-styled, if unremarkable componentry is what I need to deliver business outcomes. Bootstrap is made for people like me, but something like Swing would make it even easier.
Re: Will Vue.js become a giant like Angular or React?
#99Earlier quoted context omitted.
Out of curiosity, how did Ember and Meteor burn you so hard and why are you so averse to "all-in-one" tools as a result?
A typical all-in-one framework is Ruby on Rails. It is great to quickly start a project that does basic things planned for by the framework. But as your project grows, and you start to need special, custom things (and you inevitably do), you understand the "Rails" part. You have to move along the rails. This leads to a growing number of ugly hacks, just to keep the whole thing within one framework. The problem is tha…
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 was that they give mediocre developers that don't really know how to program a more common vocabulary and a set of childproof "design patterns" to grok — that's always easier from a management perspective than giving people who don't really know what they're doing the freedom to architect. But it just frustrates the snot out of actual developers who just want to be left alone and resent having to shoehorn their _entire_ application code base into some framework's mandatory structure, by way of which there are still yet more APIs and conventions to learn and with whose changes it is necessary to keep up ...
In this sense, Vue wins very big. It handles data binding and rendering/UI generally, but in no way premeditates how the rest of my JS is going to work.
Re: Will Vue.js become a giant like Angular or React?
#100Earlier quoted context omitted.
Yeah, Swing is actually fun to write. Possibly because its paradigm is elegant and such a natural fit for the problem that you don't spend time fighting to fit a square peg in a round hole. Shame it came with such an unwieldy deployment model that it never gained more traction.
For me personally, the biggest selling point is not having to evolve the skill set of design and layout. I'm a developer, not a designer, and the ROI on me learning the fine points of CSS is very low. I already know the bottom 80% of CSS, but who doesn't? It's the top 20% where the "magic" happens, as with so many things. Pre-styled, if unremarkable componentry is what I need to deliver business outcomes. Bootstrap i…
Yeah, that's true. Devs spend too much time pixel-wrangling in the minutae of CSS.
But, for me, it's not just the styling, but the architecture and componentry for modeling out async, event-driven web apps in a more natural way. And, I think that's the piece you're referencing that Swing can add to Bootstrap-alone.