Earlier quoted context omitted.
> I've been observing these trends for years and what I'm seeing is this: ever since these new thick client JS frameworks became so trendy, web performance has dramatically decreased, not increased. I am in the Emberjs community, I do not observe this in that framework.
Well I have observed it. I've worked on many projects that used one of the big frameworks (including Ember.js projects) that would've been better off with vanilla JS and a collection of small JS libraries instead. I'm not going to name names, but they're out there. It's a tool that does get misused, like any other.
I’m Joining LinkedIn
101–110 of 172 posts
Re: I’m Joining LinkedIn
#102Interesting they made that bet on Ember... My only assumption is they made that bet a few years ago and have been working on the refresh that just went live. Seasoned Ember developers are going to be hard to come by not that they couldn't settle for any other JavaScript specialist. I'm debating on an Ember gig this very moment and am slightly bothered by the idea of spending a year on a framework that is on a downwar…
Ember has always dwarfed by Angular and now more recently.. React. They simply have more marketing dollars behind them. That said, it has always had a strong community behind it, and believe it or not it's still growing strong.
Re: I’m Joining LinkedIn
#103Re: I’m Joining LinkedIn
#104Earlier quoted context omitted.
The bandwagoning is disproportionately on the side of those leaning towards big frameworks. Look, I've been on the inside of large companies making framework choices and rarely is the decision rational. Often it's based on what's popular and based on the assumption that popular things are popular for good reasons. Biased metrics get thrown around to justify preconceived notions, and off to the races we go. Years late…
Large companies almost by definition need to hire a lot of developers. Seems to me that it would be an absolutely rational and sensible choice to use popular frameworks keeping those constraints in mind. Google would go bankrupt from a combination of the insane salaries they'd have to pay and the inability to ever fill jobs if its entire stack was based on Haskell.
Re: I’m Joining LinkedIn
#105Is this concerning? https://www.google.com/trends/explore?q=ember.js,react.js In any case congrats on the new gig Tom.
I think a more accurate comparison is this: https://www.google.com/trends/explore?q=ember%20javascript,r... Regardless, I've bet on Ember both at my company and personally because I think they've done a lot of things right and their community process sets them up to continue on that track. As long as the community and innovation continues, I don't think it matters if React keyword searches are 20x Ember's.
It definitely matters, it's a huge deal: popularity > usage > superior ecosystem > jobs > repeat
Re: I’m Joining LinkedIn
#106> Perhaps you can write a tiny web app that loads instantly and still retains a full set of features, but most of the world cannot. I've long been skeptical of this line of thinking emanating from major thick client JS framework authors. I think they underestimate what people are capable of. > Over time, Ember will become like gcc -O3 for web apps, intelligently optimizing them and delivering them as fast as possible…
Re: I’m Joining LinkedIn
#107Earlier quoted context omitted.
Large companies almost by definition need to hire a lot of developers. Seems to me that it would be an absolutely rational and sensible choice to use popular frameworks keeping those constraints in mind. Google would go bankrupt from a combination of the insane salaries they'd have to pay and the inability to ever fill jobs if its entire stack was based on Haskell.
Probably not; people would just learn Haskell.
Re: I’m Joining LinkedIn
#108Earlier quoted context omitted.
Huh? Why would you think that?
I think here we have the "my tooling/programming language is the best, in every situation everytime". I could be wrong. Edit: typos
Re: I’m Joining LinkedIn
#109No one likes it and it takes over 20 minutes to "build" the code from scratch.
We're talking about frontend code, mind you.
At a certain level in LinkedIn, someone decided to standardize on Ember. Fine. But there were many issues, and instead of finding a more suitable and workable pragmatic framework, LinkedIn is instead deciding to hire Ember people to fix up their framework so it's actually useable. We really do work in the only industry where you can get hired to fix a mess you created yourself.
Anyway, besides the recruiter app, is LinkedIn really worthy of a SPA experience? Last time I checked isn't most of the traffic a quick "accept connection" or reply to inmail, or maybe check who viewed your profile bounce? Does the average user actually spend time in it? Probably not.
I'm reminded by a certain quote from a friend: "At a certain level in McDonald's, the managers start thinking of themselves as restaurateurs, and not fast food servants."
Re: I’m Joining LinkedIn
#110> Perhaps you can write a tiny web app that loads instantly and still retains a full set of features, but most of the world cannot. I've long been skeptical of this line of thinking emanating from major thick client JS framework authors. I think they underestimate what people are capable of. > Over time, Ember will become like gcc -O3 for web apps, intelligently optimizing them and delivering them as fast as possible…
It is closer to that. We got a ton of new things, but never the budget nor time to go fix the old thing.