For sure it’s hard to do without usage analytics (similar to Guess.js) and/or server-side rendering. But maybe there’s middle ground solutions. I don’t know. But on the React side the capability is there.
-
-
I have a requireJS / dojo AMD flashback
.
But if there was an active feedback loop for analysis that could potentially be very interesting -
I mean.. just because something had a bad implementation doesn’t mean the concept is bad
-
Oh sorry, totally didn't want to suggest that
! It was just a funny observation that programming evolution is typically an old pattern in a new and better shape
(async modules by default in this case). I do see the merits! -
In other words, recognizing previous art in an idea is a *good* sign in my book, not a bad one. Even when previous work didn't work out. It means that there is already a bit of knowledge about potential benefits and pitfalls of the new idea.
-
Yeah, I didn’t mean to be defensive — exactly pointing out this observation!
-
In that spirit, the React model is _kinda sorta_ what http://ASP.NET Web Forms tried to do, at a very high level (custom components as markup). The idea is good, but they were way ahead of their time and the tech just wasn't there.
- 6 more replies
New conversation -
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.
