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

Plans for the Next Iteration of Vue.js

medium.com

Post reply on HN
Print view View original

71–80 of 152 posts

Re: Plans for the Next Iteration of Vue.js

#71

Post by honopu »

no1youknowz wrote: post #4

As someone who writes complex applications on the client side, I welcome a lot of the changes coming up for the next release and they are seriously anticipated. Anything that positions JSX for Vue to be similar to that of React would be awesome for me. I have some issues with relativity with deeply nested JSX templates. Unfortunately I wasn't able to get any help from the discord channel as most are opposed to JSX, c…

That's a lot of sets. I've have you tried out deep-model? I've had varying success with this, essentially it creates a proxy object that wraps, its a computed property on your component. If vuex is too much for your application, but you're using that many $sets for whatever reason, maybe it would help?

Re: Plans for the Next Iteration of Vue.js

#72

Post by honopu »

spiffytech wrote: post #54
enraged_camel wrote: post #25

Earlier quoted context omitted.

Eh, debugging experience is already great. Vue Dev Tools is just phenomenal. Is there something specific you are looking for that is not addressed in the article? (e.g. they are adding render tracking)

My stack traces for JS errors inside component methods often stop at "This component had an error", with no line numbers or context to indicate which method had the error.

I also have the same issue. I don't know what to do to resolve it. It's not a deal breaker but it would be nice to have it unwind the stack a little bit.

Re: Plans for the Next Iteration of Vue.js

#73

Post by rhengles »

another-cuppa wrote: post #37
mlevental wrote: post #17

Earlier quoted context omitted.

>At no point did I feel I had the slightest clue what was going on and it felt like I wasn't supposed to ask what exactly do you mean? you didn't understand the templating language? you didn't understand the data model? you didn't understand webpack? what does "i didn't have the slightest clue what was going on" even mean? do you know what gcc does when it compiles your C code to assembly? is that the resolution at w…

It's hard to explain. I know how the web works. I used to write HTML in Notepad many years ago. With Vue I just didn't know how the stuff I was writing was turning into the stuff that the web browser actually sees. React is just a JS library that you can add on to your HTML and CSS and makes sense in the standard model. I guess with Vue I just don't feel in control any more, and that's a big no for me.

I understand that because of some of Vue default conventions (like webpack and single file components). But i'm building a simple architecture to build Vue apps without the need to compile your scripts, you can check it out here:

https://unpkg.com/@arijs/vue-generator/outra/pagina/index.ht...

https://github.com/arijs/VueGenerator

Re: Plans for the Next Iteration of Vue.js

#74

Post by tinyvm »

Wow , reading comments was quite interesting.

I didn't thought so much people got "exhausted" by Angular. I personally tried it ( v2 , v4 , v5 , v6) and i really fell in love with it.

I use mostly Vue and Angular they complete each others very well , i prefer NGRX over Vuex and Angular native support for Typescript.

Typescript with Vue is a bit of hassle to set up and maintain, but with this new update this a bit of a game changer.

It appeals to a larger audience , especially those looking to build large scale project , while keeping the core of the community.

Really great news.

Re: Plans for the Next Iteration of Vue.js

#75

Post by rhengles »

another-cuppa wrote: post #43
vezycash wrote: post #38

Earlier quoted context omitted.

It's usually React that people complain about. If you like jQuery, you should like vue. Cause, you can use vue just by adding a script tag in your web page. You don't need command line, web pack or any other tool to use most of vue.

You can do that with React too.

React is a great framework, the only thing I couldn't find is a great solution to have runtime templates. I know they're not optimal but for some small projects it's better to eliminate the build step. Of course no one in the right mind would manually write render functions.

Re: Plans for the Next Iteration of Vue.js

#76

Post by mlsarecmg »

another-cuppa wrote: post #15

I'd been out of the loop of frontend Web stuff for several years but I tried Vue.js because I read here and elsewhere that Angular was a mess. I just couldn't stand the weird hybrid html/css/js editing. At no point did I feel I had the slightest clue what was going on and it felt like I wasn't supposed to ask. React felt much more natural to me. Is there any way to do stuff differently with Vue or should I just stick…

This one was pretty good and goes into deeper details instead of just claiming x is better than y: https://medium.com/@swizec/some-thoughts-on-vue-after-deploy...

The fundamental difference between React and Vue is vision. React bets on functional programming and moves closer to reaching its goal, perhaps shedding the last OOP parts some day.

Vue follows an older paradigm, Angulars basically, but with React underpinnings. It's heavily inspired by OO templating, pseudo code mixed into html. Perhaps the gravest difference if you come from React is that it encourages mutation, to an extent that now forces it to maintain two incompatible versions going forward due to IE11's lack of proxies.

Re: Plans for the Next Iteration of Vue.js

#77

Post by rhengles »

petepete wrote: post #18

The ability to split Vue components into multiple (html, ts, scss) files in a single directory would be nice. I dislike the single file approach and it makes things like having nice syntax highlighting and completion more complex than it should be.

Another one here building a simple architecture to build Vue components in a folder instead of a file, you can check it out here:

https://unpkg.com/@arijs/vue-generator/outra/pagina/index.ht...

https://github.com/arijs/VueGenerator

Re: Plans for the Next Iteration of Vue.js

#78

Post by avip »

another-cuppa wrote: post #15

I'd been out of the loop of frontend Web stuff for several years but I tried Vue.js because I read here and elsewhere that Angular was a mess. I just couldn't stand the weird hybrid html/css/js editing. At no point did I feel I had the slightest clue what was going on and it felt like I wasn't supposed to ask. React felt much more natural to me. Is there any way to do stuff differently with Vue or should I just stick…

I'm not sure what you call "hybrid html/css/js editing". Vue components are stored in single .vue file (newer angular versions also default to SFC). Within said .vue file, HTML/CSS/JS are very obviously separated. Scoped style and templates are very easy to reason about and manage, IMHO, as an underqualified front-end developer.

Re: Plans for the Next Iteration of Vue.js

#79

Post by rhengles »

atentaten wrote: post #27
petepete wrote: post #18

The ability to split Vue components into multiple (html, ts, scss) files in a single directory would be nice. I dislike the single file approach and it makes things like having nice syntax highlighting and completion more complex than it should be.

https://vuejs.org/v2/guide/single-file-components.html#What-...

Having to repeat the component name in the "src" is less than ideal, IMO.

Re: Plans for the Next Iteration of Vue.js

#80

Post by no1youknowz »

honopu wrote: post #71
no1youknowz wrote: post #4

As someone who writes complex applications on the client side, I welcome a lot of the changes coming up for the next release and they are seriously anticipated. Anything that positions JSX for Vue to be similar to that of React would be awesome for me. I have some issues with relativity with deeply nested JSX templates. Unfortunately I wasn't able to get any help from the discord channel as most are opposed to JSX, c…

That's a lot of sets. I've have you tried out deep-model? I've had varying success with this, essentially it creates a proxy object that wraps, its a computed property on your component. If vuex is too much for your application, but you're using that many $sets for whatever reason, maybe it would help?

I havent tried deep-model. To be honest, knowing about 2.6-next/3.0 on it's way. I can let it be for now and then refactor when the new version hits in 2019.

I'm not quite sure about VueX. There's this [0]. Which I'm going to attempt soon. Would be nice if VueX could help. Would solve the UX and postMessage issue that I have.

For context. It's a page builder like leadpages, elementor for wordpress, unbounce, etc. It's one big array which then gets parsed as JSX and then rendered out to the vDom.

[0]: https://forum.vuejs.org/t/share-vuex-store-with-vue-app-in-i...

Post reply on HN