Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue RFC: Expose logic-related component options via function-based APIs instead

github.com

Post reply on HN
Print view View original

81–90 of 253 posts

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#81

Post by AngeloAnolin »

Breaking changes such as this makes me rethink what could be the best approach with regards to front end development.

I can recall the time when I moved past Angular when they introduced so many breaking change on their next version. I started using React but was not comfortable enough to keep pace with its progression. Then I found Vue which was a breath of fresh air as this framework has allowed me to deliver end products faster yet being simple enough to allow for easy scalability & enhancements.

With these upcoming enhancements, I hope that it wouldn’t introduce major changes that would require for me to rewrite large portions of my applications.

I have a lot of trust and confidence with Evan and the Vue Community and I guess all these changes are in line with best practices and better productivity rather than following a path because another framework is doing things like that.

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#82

Post by Sir_Cmpwn »

tannhaeuser wrote: post #77
Sir_Cmpwn wrote: post #51

Quick reminder that you can still write complex and useful form-driven web applications with no JavaScript at all.

This. I've used React and to my surprise even liked it, but if you have to start all over every 3 years, you've got to ask whether pulling your model ... whatever over to the client is actually worth it in the vast majority of cases. What was wrong with SSR and a bit of jquery and Ajax again?

Note that I said "no JavaScript at all", not "a bit of jquery and ajax"

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#83

Post by ng12 »

treelovinhippie wrote: post #47

Well that's enough to reinforce my switch to https://svelte.dev I want a JS framework simple enough that even hobbyist devs can understand in an afternoon. React syntax is an overly complicated mess; like reactivity forcing itself onto HTML. Current Vue syntax is neat, simple and clear; like HTML with added reactivity.

> React syntax is an overly complicated mess; like reactivity forcing itself onto HTML.

What now? Are you talking about JSX? If so, it's pretty straightforward (and optional).

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#84

Post by ng12 »

Vinnl wrote: post #55
lucidone wrote: post #4

I haven't done front end work for about one year. Looks like I'll be re-learning everything at some point, because this looks like a fairly major change. I'd strongly prefer backwards compatibility over a breaking change.

I feel like I'm shilling a bit for React over here, but they are nearing two years without major breaking changes, and has been the de facto framework to go to for quite a while now.

Agreed. I've been using React for 4+ years with only minor changes.

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#85

Post by pier25 »

tnolet wrote: post #16

I might be totally and completely wrong, but changing everything does not help anyone except scratch the itch of the framework's designers. I'm pretty sure this is all with the best intentions, but this would be a disaster similar to how Angular suddenly changed everything . Not against change, but the API is fine. Just iterate and evolve it. disclaimer: Big fan of Vue, early user and conference attender..

Totally agree. Once you have millions of users you have a great responsibility since they depend on you.

jQuery did it right. They decided on a methodology and stick with it changing the internals and gradually adding features.

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#86

Post by lwansbrough »

samhh wrote: post #79
_sbxe wrote: post #36

FINALLY. What took so long? Seemed like we're long overdo for a big syntax change to take up engineering time with no real gain. I should have never left C.

> with no real gain Did you read the linked motivations?

Nobody cares what the motivations are if they can’t update their code base without thousands of hours of work.

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#87

Post by stupidcar »

the-pigeon wrote: post #54
Vinnl wrote: post #46

Earlier quoted context omitted.

> this would be a disaster similar to how Angular suddenly changed everything. To be fair to Angular, if they'd stuck with what they had, it'd have faded into obscurity far more than the current version has. Angular.js was great for its time, but lost most of its advantages as the web caught up, and what used to be its advantages started to become kludges.

I don't know. I prototyped with Angular and it just seemed like one of those approaches that sorta made sense verbally but not at all on paper. Like trying to take jQuery and make it a framework like React. But in their attempt to make it "simple" they made it useless. And then the next generation of frameworks like React came out and basically killed it.

You may not like it as a technology, but one search on recruitment sites will show you that it's far from dead.

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#88

Post by pier25 »

Vinnl wrote: post #46
tnolet wrote: post #16

I might be totally and completely wrong, but changing everything does not help anyone except scratch the itch of the framework's designers. I'm pretty sure this is all with the best intentions, but this would be a disaster similar to how Angular suddenly changed everything . Not against change, but the API is fine. Just iterate and evolve it. disclaimer: Big fan of Vue, early user and conference attender..

> this would be a disaster similar to how Angular suddenly changed everything. To be fair to Angular, if they'd stuck with what they had, it'd have faded into obscurity far more than the current version has. Angular.js was great for its time, but lost most of its advantages as the web caught up, and what used to be its advantages started to become kludges.

The problem with Angular 1 is that it was slow and bloated, relatively speaking. Google could have improved on that instead of starting from scratch, or ok, start from scratch but use a different name.

Re: Vue RFC: Expose logic-related component options via function-based APIs instead

#89

Post by superasn »

Hopefully history will repeat itself and some clever dev will fork Vue 2.0 and create a new framework which has all the good parts of Vue 2 and nothing from this react inspired Vue 3 and all would be good again

(just like Evan did when Angular went rogue)

Post reply on HN