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

Switching From React To Vue.js

vuejsdevelopers.com

Post reply on HN
Print view View original

181–186 of 186 posts

Re: Switching From React To Vue.js

#181

Post by voidr »

echaozh wrote: post #176
piva00 wrote: post #172

Earlier quoted context omitted.

That's for sure a minus, even if you speak the language. You are restricted to a smaller subset of developers that can improve the ecosystem (and let's be frank that most good developers should know English but not Chinese, internationally speaking).

The logic may not be sound as you cannot tell for sure if there are more English speaking front end developers or Chinese-only speaking ones, given the population of China.

There could roughly be as many front end developers in India ... which has 23 languages.

China also has multiple languages and dialects, see: https://en.wikipedia.org/wiki/Languages_of_China#/media/File...

English is the lingua franca of software development and I don't see that changing anytime soon.

Re: Switching From React To Vue.js

#182

Post by thibaut_barrere »

vosper wrote: post #77
thibaut_barrere wrote: post #59

Earlier quoted context omitted.

I don't consider the fact that a large company uses something for their main product is enough to actually make it future-proof. Previous instances of that pattern: - three20 (used in FB ios app https://en.wikipedia.org/wiki/Three20 ) - GWT - Angular is actually a similar instance of that problem, to some extent If "large company" switches their goal at some point, then you're still alone. Currently I'm kind of more…

GWT was first released 11 years ago, the most recent update was less than a month ago. If that's not an example of future-proof (for web technologies) I don't know what is. Whether it's kept up with the state of the art I don't know, but I think that's a different thing.

I was referring to http://www.gwtproject.org/release-notes.html - e.g. the release hole that happened between 2.7.0 and 2.8.0 (2 years). Some clients actually decided to stop using GWT at that time, because of that.

Re: Switching From React To Vue.js

#183

Post by thibaut_barrere »

plorkyeran wrote: post #148
thibaut_barrere wrote: post #59

Earlier quoted context omitted.

I don't consider the fact that a large company uses something for their main product is enough to actually make it future-proof. Previous instances of that pattern: - three20 (used in FB ios app https://en.wikipedia.org/wiki/Three20 ) - GWT - Angular is actually a similar instance of that problem, to some extent If "large company" switches their goal at some point, then you're still alone. Currently I'm kind of more…

Three20 was made obsolete by the useful parts of it getting built into the platform SDK, and yet it was still maintained and kept in a working state for longer than it was ever actually useful.

I know that - but the fact is that for one client of mine, the app was initially build on three20, then they had to literally rebuild it from scratch as they realised that three20 was becoming obsolete.

One of the reasons for the choice was the FB branding associated as something that can be trusted!

Re: Switching From React To Vue.js

#184

Post by gustojs »

reaperducer wrote: post #162
mcintyre1994 wrote: post #22

Earlier quoted context omitted.

https://vuejs.org/v2/guide/routing.html For most Single Page Applications, it’s recommended to use the officially-supported vue-router library. For more details, see vue-router’s documentation. https://github.com/vuejs/vue-router -- https://vuejs.org/v2/guide/state-management.html Vue offers vuex: our own Elm-inspired state management library. https://github.com/vuejs/vuex -- Out of the box or not, they're part of th…

The official Vue docs? The ones where half of the useful stuff is either missing, incomplete, or doesn't work because it's information for a deprecated version? Vue has a lot of things going for it. Documentation is not one of them.

Vue is widely praised for its official documentation, often pointed as one of things differing it from React. But if you have other experience, I'd kindly asked you to mention the places you remember were wrong, so that I can submit a PR for them.

Re: Switching From React To Vue.js

#185

Post by gustojs »

dabit3 wrote: post #167
TekMol wrote: post #68

Earlier quoted context omitted.

Options like React-Native When you use React for a web app, how close are you to turn it into a React Native app?

It's less about code reuse across a full featured web application and a mobile application. The value comes in that once you master React or React Native, you can easily switch across platforms and be just as efficient. If you learn the ins and outs of Vue and gain depth of best practices / domain knowledge, you are stuck building only for the web. If you do the same with React, you are then able to take those skills…

I don't see an issue of learning Vue and not being able to write native apps for iOS and Android as a valid one.

Weex quickly gets better and is maintained by Alibaba, a company of the same scale and with development resources comparable to Facebook or Google. NativeScript recently started work on Vue port, the project is already available for testing. That's excluding the Cordova solutions like Onsen and Framework 7 having official Vue ports.

To that, PWA slowly becomes the new trend for mobile development, native apps are not necessarily the optimal solution to every use case.

The "++ many more in the future" is an optimistic assumption. As much as I wish it to be fulfilled, same can be said about any other framework.

Re: Switching From React To Vue.js

#186

Post by gustojs »

__ddd__ wrote: post #90
jorgec wrote: post #44

I don't get it. Lets say that you have a well formed team, then you have a designer. A designer is who does the UI but know or care so little about programming. With React, the UI is practically JSX that very few people know (in comparison with html) and what we will get instead?, the result is the same html that it tries to avoid.

JSX is very close to HTML. Maybe the issue is expecting designers who have zero dev skills to build front ends in a time of responsive design and rich JS interfaces. You wouldn't hire a print designer with no Photoshop experience to design a site, and you shouldn't hire a graphic designer with no web dev skills to build front ends. If you're team is really well formed, you might have an experienced graphic designer,…

Only in the first world clients pay enough for such a team to make a living. Not a case for other countries.
Post reply on HN