21–30 of 172 posts
> LinkedIn has bet big on Ember. I like how as technologists we talk about "betting" on things. As if technology choices are like gambles.
And this is the global market.
Imagine how worse it is if you want to hire local. Yikes.
In any case congrats on the new gig Tom.
We need specialists too. We need the folks who can tune x86 assembly better than -gcc 03. We need people who can write segfault free C++ code, and we need people to fix the Rust borrow checker bugs http://blog.ezyang.com/2013/12/two-bugs-in-the-borrow-checke... There are plenty of available consumer of good tools, with more coming into the market every day. We need more specialists. Every person has the same capacity…
Is this concerning? https://www.google.com/trends/explore?q=ember.js,react.js In any case congrats on the new gig Tom.
Great, I'm glad Ember is gaining more traction in enterprise... but what does this mean for things like Fastboot, Ember 3.0, glimmer 2.0, ember-cli 3.0, and the whole cast of in-room-elephants such as ember-redux, flexi, ember-data, vr, etc.?
> Joining LinkedIn Great, I'm glad Ember is gaining more traction in enterprise... but what does this mean for things like Fastboot, Ember 3.0, glimmer 2.0, ember-cli 3.0, and the whole cast of in-room-elephants such as ember-redux, flexi, ember-data, vr, etc.?
Isn't Ember mostly used in enterprise?
Is this concerning? https://www.google.com/trends/explore?q=ember.js,react.js In any case congrats on the new gig Tom.
Ember.js had many strong parts, but also had many issues that pulled it down. Documentation overfocused on explaining concepts but not providing examples of how to solve real issues. New release every six weeks bringing painful deprecations and changes. Lack of realworld apps to look up to for examples. Ember-Data that worked out the box... unless you weren't using Rails for your backend, in which case you've needed bridges and drivers for it to work. Rich of resources assuming that your backend is Rails or that you have enough of understaing about it to translate examples for your tech. All of this eventually pushed me away to React.js that seemed less opiniated about your backend and richer in examples and manuals, as well as unopiniated enough to forgive my mistakes and let me lear from them. Since moving I've made a lot of mistakes with my own solution build using React.js and libs from its ecosystem, which eventually made me understand design choices behind Ember.js, but I still preffer to improve on what I have now instead of considering returning to Ember.js.
Lots of flagged comments, I suppose because of short quips related to the sleazy things LinkedIn has done in the past. I'm sure he's not unaware of those things. I wonder if he's thinking he may be able to influence them? Discourage dark patterns? Discourage the current mobile experience that's broken unless you download the app and/or log in?