5 ms·
@Vue team if anyone should read this: I'd recommend to rename vue in the process (for example vueNG or whatever) in order to reduce the amount of false/outdated
by chupa-chups 7y ago
@Vue team if anyone should read this:
I'd recommend to rename vue in the process (for example vueNG or whatever) in order to reduce the amount of false/outdated information when searching for a topic.
- stesch 7y agoIsn't this half the fun of using JavaScript frameworks?
- jspash 7y agoNo, this is the OTHER half of using them. :/
- IggleSniggle 7y agoAngularJS/Angular split community still have this problem, although less so this year than last.
- julvo 7y agoThis. I like that the Vue team thinks of ways to improve on the current state of the art and welcome new ideas, but please under a different name. It needs to be succinct enough so that search engines can distinguish the two. Otherwise, there is a big risk of things becoming confusing and frustrating quickly.
- pier25 7y agoYes, that's what the React team should have done when they implemented hooks.
- zwily 7y agoWhy? Hooks are completely backwards compatible.
- pier25 7y agoWhat about books, talks, blog posts, SO answers, etc? Is everyone going to rewrite all React literature with hooks?
- pests 7y agoNo rewriting needed. Hooks are just another way to do what was already possible in a more well-defined way. All the content written is still applicable. Now there is just a new way to do things too. The developers and documentation even advises against rewriting old components with hooks unless you need to.
- pier25 7y ago> All the content written is still applicable. Technically yes, but what if someone only uses hooks and has never used classes? And, viceversa, since there is now a lot of people moving to hooks and producing React literature for hooks what if you only have used classes? So now, to be able to read all the React literature one has to understand both methodologies. > The developers and documentation even advises against rewriting old components with hooks unless you need to. It doesn't matter. A big chunk of the JS community is hype-based.
- ng12 7y agoHooks are additive.
- NewsAware 7y agoWell, with React you can "opt in" when searching by simply adding "hooks" to the search term. Such wasn't possible with Angular back then
- pier25 7y agoSince the majority of the community will probably be using hooks from now on it will be assumed that is the default React methodology which will break books, talks, blog posts, SO answers, etc.
- ng12 7y agoYou can mix-and-match. If you want to write an individual component as a class you can, and if you want to later convert it to using hooks there's nothing stopping you.
- superasn 7y agoYes it becomes a nightmare to search Stackoverflow too. I still get answers for Vuejs 1.0, with suggestions to use 'partials' for example, only to find out that there exists no such thing in Vue 2.0. This would be very bad for developers if they still call it Vue with another version number. Even if they call it VueThree, VueNext or similar then the problem can be easily mitigated I think.
- tmaly 7y agoIf they won't, the community could always decide to adopt a tagging or naming standard. Being able to find answers quickly is a big win for beginners.
- luismartinezs 7y agoHow about Vue 3.0?