Evaluating front end frameworks and not choosing any

Re:Evaluating front end frameworks and not choosing any by darkerside on Thursday January 06, 2022 @10:58PM (#29834644)

> VueJS is smaller, around 30kb, but not that small. Also, it is very opinionated and we don’t want to force people of the future to use VueJS.

I don't understand what the criticism is supposed to be here.

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by rk06 on Thursday January 06, 2022 @11:22PM (#29834799)

They wanted it under 15kb. And for some reason, give future devs ability to not use Vue.

I don’t know how they settled on 15kb, but “don’t want to force people of future” is as stupid of a reason as I have seen. Surely, “people of future” can refactor old code, or have different constraints altogether

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by darkerside on Friday January 07, 2022 @06:49PM (#29846652)

Seems like a tautology. They didn't want Vue because they didn't want Vue.

Whatever your choice is, you're going to have to move off of it one day.

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by outside1234 on Thursday January 06, 2022 @11:21PM (#29834795)

They want to write their own framework and inflict it on the engineering team

Way more fun than actual customer problems

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by snowl on Thursday January 06, 2022 @11:26PM (#29834824)

Instead of learning gzip, now in 2 years everyone will have to learn a library that has been abandoned and has almost no tooling or documentation!

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by eternityforest on Thursday January 06, 2022 @11:55PM (#29835099)

It's like when they didn't want to codify SQLite as Web SQL so they tortured everyone with an extra layer of crap they added on it.

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by human on Thursday January 06, 2022 @11:18PM (#29834764)

They don’t want to emit greenhouse gasses because of a few kbs and they don’t want future people to deal with Vue.js. Talk about first-world problems…

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by pqdbr on Thursday January 06, 2022 @11:09PM (#29834715)

I've never been more productive in my life with a combination of Vue and Rails.

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by cutler on Thursday January 06, 2022 @11:18PM (#29834771)

Curious - did you use Rails in API mode?

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by sadn1ck on Friday January 07, 2022 @12:14AM (#29835253)

ive worked on vue and have been looking to dip my toes into ruby on rails, any tips?

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by temp8964 on Thursday January 06, 2022 @11:01PM (#29834661)

Why does it has to be criticism? They didn't choose it and they did say it's bad. Just it's not what they want.

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by darkerside on Friday January 07, 2022 @01:35PM (#29842875)

The article purports to be a rational comparison. If you just want to write an uncritical opinion piece, do it. If you claim you are working pros and cons, do that.

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by markdown on Thursday January 06, 2022 @11:08PM (#29834711)

30kb is too much for js. A modern website should run fine on half of that.

[ Parent | on HN ]

Re:Evaluating front end frameworks and not choosing any by snowl on Thursday January 06, 2022 @11:24PM (#29834816)

Any _real_ modern website should run fine on under 1Kb, no matter the contained data

[ Parent | on HN ]