No. In fact we're actually realizing the way we used to ship code was egregiously slow, inaccessible, and no interoperable. Welcome to front end _Engineering_. https://twitter.com/ben_howdle/status/930012526628110337 …
-
-
Not to mention vital tooling and infrastructure like babel webpack lodash, blah blah, and fire catching like vue.
-
Not sure Babel's the best example for you here - the (heroic) maintainers are chronically under-funded and overworked. Its one of the best examples of why I think the OSS model is so profoundly broken and un-maintainable.
-
They are just getting started. Funding and partnerships and relationships take time.
@left_pad drove babel to a better position then it could ever be to continue to drive change and support for babel. -
And in the current broken system and old age where Bazar and legacy OSS support practice break down, the bottom line is: if you want your project funded, it's a shit ton of work.
End of conversation
New conversation -
-
-
The web is so disjointed. I just look at .Net desktop, iOS cocoa touch or Android dev and it's so much more cohesive of an end-to-end developer experience.
-
It's also much, much bigger and covers a much broader set of use cases and environments. Oh, and deprecations don't work that well on the web ;)
-
That's only part of it. Having a rich corporation own the end-to-end experience makes so much difference. The web doesn't even have a word in its vocabulary to describe the stability I enjoyed in my .net days.
-
I'm so sick of the web's lack of stability that honestly having Facebook own React is a huge selling point for me.
-
If only Facebook owning React actually resulted in what you want. Instead, React is less stable than .net and the biggest new tool Facebook wrote advertises the ability to "eject" as a main selling point. Postgres has had a much better run than almost any DB, by analogy.
-
Don't conflate "stability" with "I don't have to learn new things." By stability I mean it works, isn't buggy, etc.
-
I definitely don't mean the latter :) In order to get this kind of stability, a project needs to be serious about owning the primary end to end experience, and "eject" is very corrosive to this goal.
-
I think them owning a lot of the top api stack CRA runs on is enough. I see eject as a blessing not a curse, and that mostly due to the support the community has around the chosen stack.
- 3 more replies
New conversation -
-
-
The reason for a major company is so that it's well supported and an easy-to-make fiducially responsible decision when choosing a toolkit.
-
I think that's an error. Ember, which isn't created by a single company, has remained extremely stable and well-supported during the same time that some toolkits by big companies got total rewrites. Using software built by a broader coalition is more responsible imo.

-
Exactly. What businesses incentive do we have at webpack. None. So far its been a good model ;)
End of conversation
New conversation -
-
-
We're got CRA too, which is pretty close.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.