51–57 of 57 posts
Earlier quoted context omitted.
Sounds like your sweet spot is more towards the library end of library/'light weight framework' vs the 'full blown framework' spectrum. I don't believe it has anything to do with age.
Except Vue is a framework but React isn't.
While you can optionally use the official router and state management libraries, these are completely independent and unnecessary.
I don't think this is how how it should be in a tech focussed community. Things should be judged on merit not value added to resume or potenial for well paying jobs.
Earlier quoted context omitted.
Will you explain what you mean a bit more, please? I don't understand your analogies.
Omakase is in reference to http://david.heinemeierhansson.com/2012/rails-is-omakase.htm...
developers should learn X - What you know Y - Technology du jour
It absolutely baffles me that people still like to call React a "Technology du jour". It's ubiquitous today. It's _THE_ go-to front-end web development UI framework.
Earlier quoted context omitted.
It's not quite the (positive) impression I get from react - but then I can't claim to be familiar with the internals. I do think one of the reason I struggle with react is because I still believe the Web is good for REST and Web pages/hypertext - and native is to be preffered for "applications". Conversely I think react is a pretty poor fit for "Web". It still strikes me as crazy complicated compared to say Java SWIN…
the stack has to be backwards crap for GUI programming, right? Right, please dont take my praise for react as an endorment that the state of the industry is where we need to be. Rather I see it was a step forward. For a little background I have been in the business since Tim Lee published his first page of what would become the WWW. I would venture to say the first webpage I wrote was in the first 100 and if not, cer…
Do you really feel the mess of multiple files react seem to dictate is much better? (Honest question, I haven't really used either in anger).
From what I can gather more radical approaches like elm and clojure script - seem promising, but are ultimately (for now) let down by the frameworks doing "too much" - in effect working against the rich vms browsers have become.
I'd like to hear/see more of why you feel vue leads to (demands?) giant controllers as opposed to facilitate real re-usable components?
Earlier quoted context omitted.
Actually for me, React fitted me well as a jacket! Until a friend asked me why there was and advantage to spend an extra minute taking on and off that jacket instead of using a simpler jacket(vanillajs) that fitted just as well but that I could take on and off in seconds. My conclusion today is that the massive hype around React, Angular and so on, is a similar story as The Emperor's new clothes.
> vanillajs Even if you don't need a view framework, do you do serious work with no libraries? What browsers do you support? It'd get really frustrating to support even IE10 with nothing protecting you from random idiosyncrasy
At work we still support IE8 for some clients. VanillaJS? No thanks. I'll take even jQuery 1.X (2.x drops IE8 support) over vanilla.
Earlier quoted context omitted.
Actually for me, React fitted me well as a jacket! Until a friend asked me why there was and advantage to spend an extra minute taking on and off that jacket instead of using a simpler jacket(vanillajs) that fitted just as well but that I could take on and off in seconds. My conclusion today is that the massive hype around React, Angular and so on, is a similar story as The Emperor's new clothes.
> vanillajs Even if you don't need a view framework, do you do serious work with no libraries? What browsers do you support? It'd get really frustrating to support even IE10 with nothing protecting you from random idiosyncrasy