[HN Gopher] Vue.js is Wikimedia Foundation's future JavaScript f...
___________________________________________________________________
Vue.js is Wikimedia Foundation's future JavaScript framework
Author : Volker-E
Score : 101 points
Date : 2021-08-02 21:16 UTC (1 hours ago)
(HTM) web link (lists.wikimedia.org)
(TXT) w3m dump (lists.wikimedia.org)
| ggregoire wrote:
| Can I see the code for the TypeaheadSearch component somewhere?
| (I followed some links but didn't find it)
| katabasis wrote:
| That currently lives here: https://github.com/wikimedia/wvui/tr
| ee/master/src/components.... This is WVUI, the component
| library created to serve the needs of the Desktop Improvements
| case study mentioned in the post here.
|
| Some of this code may change or get moved around based on the
| outcome of these tasks:
| https://phabricator.wikimedia.org/T286946
| timdorr wrote:
| Most of the discussion behind this decision, including feedback
| directly from Evan You (author of Vue), is here:
| https://phabricator.wikimedia.org/T241180
|
| It's pretty interesting to read through.
| skybrian wrote:
| This discussion is from early 2020 and the decision seems to
| have been mostly made by then, but they're announcing it now.
|
| I guess everyone's been busy, what with a pandemic and all. :)
| katabasis wrote:
| Various teams have been using Vue on a more experimental
| basis over the last year. The new Media Search tool on
| Commons is Vue.js-based, for example:
| https://commons.wikimedia.org/wiki/Special:MediaSearch
|
| But this announcement makes things more official.
| [deleted]
| gherkinnn wrote:
| A solid choice and well reasoned. It was a joy to read all of the
| discussions.
|
| Been following Vue and Evan's work since 2015, before it even
| reached 1.0. I think it strikes a good balance between the
| freedom of React and the rigidity if Angular. (Interpret the
| terms "freedom" and "rigidity" as you please.)
|
| My only problem with Vue 2.x was the bad TS support, but I trust
| 3.x solves that.
| seph-reed wrote:
| "The freedom of React" is a hard statement for me to digest.
|
| I stopped using React specifically because it was so incredibly
| limiting. And my life has been a lot better without it.
| Spartan-S63 wrote:
| In my experience, React is very particular at how you present
| your view logic. For state management, though, it has very
| few opinions and that freedom can be paralyzing. Do you use
| Redux? Do you just use built-in component state and props? Do
| you use the Hooks API? React solves one slice of problems in
| front-end development, but has few opinions outside of the
| view layer.
| seph-reed wrote:
| I stopped using it a while ago. I had central state
| management, and a few other bells and whistles.
|
| I was the "go to" guy for when React didn't want to do
| something.
|
| Most of my wrestling came in the form of:
|
| - recycling html-elements
|
| - "tweening" state. a friggin nightmare to have inbetween
| states
|
| - performant animation stuff
|
| - stateless node-to-node communication for stuff that would
| have not fit well in state
|
| - keyboard navigation
|
| Ugh. The more I learned about how it actually works, the
| more I came to hate it. And it kills me to see so many
| people who love it... like I'm an alien amongst the people
| (developers) who I once felt understood me.
| threatofrain wrote:
| Previous big discussion:
|
| https://news.ycombinator.com/item?id=22625556 (March 2020)
| the__alchemist wrote:
| For anyone alarmed about moving towards a SPA, and potential
| performance impacts etc, read the comments towards the top of
| this link from the Vue Team Lead and proposal co-author. They
| address the most obvious concerns.
| seumars wrote:
| Thanks for the link. A lot of people went out of their way to
| criticise Vue which makes me wonder how the general opinion of
| Vue has changed in the last year.
| wolverine876 wrote:
| > A lot of people went out of their way to criticise Vue ...
|
| For almost every topic on HN, a lot of people will go out of
| their way to criticize it.
| ferdowsi wrote:
| Congratulations to the Vue team, this is definitely a big win for
| them.
|
| Reading through the RFC is really interesting. They specifically
| call out the dependency on Facebook as effectively being React's
| Single Point of Failure, citing their negative experiences with
| HHVM.
|
| And for all of the love that people give React's big shifts (like
| hooks), the RFC specifically counts this against them, given that
| best practices have shifted so drastically in the last few years.
| vmception wrote:
| I agree with that. Its been like a twilight zone interviewing
| for anything frontend in Silicon Valley the last couple years
| as they "me too" for React, while I use Vue on my own projects.
|
| Now, the original reason I chose Vue was mostly around a small
| client side package size, but all the SPA frameworks have some
| version that prides itself in small client side package side
| now, and they mostly reach parity on similar concepts.
| huuggjkkkk wrote:
| Good luck getting any libraries working. Good luck using graphql.
| Good luck getting the tooling stable. Good luck getting a PR on
| the main code base done. Vue in production is a minefield of
| nightmares.
|
| Rather have Facebook as a single point of failure than some
| random dude who has other things that consume his interest.
___________________________________________________________________
(page generated 2021-08-02 23:00 UTC)