31–40 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.
Aren't they? If there are two competing technologies, generally one will dominate, or more likely: both will be replaced by something new. You have to gamble that the technology you pick will stay relevant for long enough to be worth it.
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?
Earlier quoted context omitted.
Aren't they? If there are two competing technologies, generally one will dominate, or more likely: both will be replaced by something new. You have to gamble that the technology you pick will stay relevant for long enough to be worth it.
But if it works, how is it a gamble?
Earlier quoted context omitted.
Aren't they? If there are two competing technologies, generally one will dominate, or more likely: both will be replaced by something new. You have to gamble that the technology you pick will stay relevant for long enough to be worth it.
But if it works, how is it a gamble?
Is this concerning? https://www.google.com/trends/explore?q=ember.js,react.js In any case congrats on the new gig Tom.
For example, ember-redux exists to take the functional centralized state-management of redux that makes react great and ports it to ember. Similarly, react-scripts takes the developer-ease of ember-cli and gives it to react. Everybody uses the DDAU for handling DOM interaction, shadow-dom-tree-diffing (or whatever it's called) for rendering, some sort of declarative remote data-layer in both ember-data and redux-orm (and there's even ember-redux-orm), and junk like animation-handling and whatnot all expose the same change-attribute-yield-block API to the programmer.
If you look beyond the stylistic difference of things like writing jsx v. hbs, there's actually very little philosophical difference between modern 2.x ember and modern react
> LinkedIn has bet big on Ember. I like how as technologists we talk about "betting" on things. As if technology choices are like gambles.
They are bets. In the global market if you pick the wrong tool you severely limit your talent pool and upgrade path. Imagine being stuck on Marionette and Backbone these days. Tough to attract talent with old technology like that. And this is the global market. Imagine how worse it is if you want to hire local. Yikes.
The pool of engineers who are experienced with your stack will be bigger if you pick a "winning" or "popular" stack. But in my experience at Big Co, the stack is as often proprietary as not, yet Big Co can attract talent anyway.
Having lived through transitions from Popular Stack Today to Popular Stack Next more than once, I have yet to go through the experience thinking that the upgrade path is easy.
Proto-jQuery to jQuery, jQuery to Backbone, Backbone to Angular, Angular to React, React to other React-like things... these frameworks were all "winners," but I can't describe the upgrade path without using the word "rewrite."
> LinkedIn has bet big on Ember. I like how as technologists we talk about "betting" on things. As if technology choices are like gambles.
Aren't they? If there are two competing technologies, generally one will dominate, or more likely: both will be replaced by something new. You have to gamble that the technology you pick will stay relevant for long enough to be worth it.
Some leeway could me made around that statement. People who work in fishing and agricultural industries for example could benefit from unique and specially crafted services when it comes to job search and fulfillment. There is a certain effectiveness in the one-size-fits-all approach of applications like Facebook but it could stand to exist within a more diverse ecosystem.
> 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.?
> I'm glad Ember is gaining more traction in enterprise Isn't Ember mostly used in enterprise?
> 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.?
Source: I'm the lead eng for our consumer group