Earlier quoted context omitted.
It's TechCrunch... I won't say anymore because I'm also a member of the press... but it took me 3 seconds to find this on Google: https://gist.github.com/duivvv/2ba00d413b8ff7bc1fa5a2e51c61b... Somebody forgot to fact-check his article. That's for sure.
Most reporters these days don't appear to fact check anything anymore. It's too important to get the first story out.
Facebook Announces React Fiber, a Rewrite of Its React Framework
311–320 of 422 posts
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#312Earlier quoted context omitted.
Javascript fatigue is real. Shit in front-end land changes so fast it is impossible to keep up with. We just finished a rewrite from jQuery to Angular 1, with updates to all the tooling that goes along with it. We're now at least three years behind the curve... Hooray! Meanwhile, the backend frameworks we've been using have had one minor version Nuget package release in the same timespan.
Angular 1 is 7 years old. And guess what? It's still a perfectly valid framework to build a web application with. There is no "curve".
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#313Earlier quoted context omitted.
If you're on gradle you're already pretty cutting edge compared to most enterprise java setups. Probably most projects are still using maven. Also there's definitely been some cross pollination of ideas from at least the Ruby world to the Java (Rails inspiring Grails and probably Play too), so it's getting better. Add java8 lambdas, and it's quite nice.
> Probably most projects are still using maven. Aren't you optimistic.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#314Earlier quoted context omitted.
If it wasn't a problem, it wouldn't be upvoted. That is how voting works. I'm not a JavaScript programmer, although I have dabbled extensively in the past. My impression of this thread is that not much has changed in that world. Sencha, titanium, and Phonegap were super hot back in the day, along with jQuery, SproutCore, Knockout and Backbone. Now it is all different for JS. That fuckng sucks.
It's such a dumb argument that boils down to "things are changing and I don't like it!". Javascript fatigue is not real. I am completely convinced anyone who says otherwise has never had to maintain a non-trivial web application in Backbone/jQuery -- meaning they're complaining about frameworks that weren't built for their use cases.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#315Earlier quoted context omitted.
The benefits you acknowledge (distribution) are not because of the tech but in spite of it. At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative. That alternative could be distributed to a large percentage of desktops in a relatively quick manner saving billions if not trillions of dollars in wasted productivity. It will never happen though. * EDIT: This comes from som…
No-one could even agree on making HTML5 valid XML - in order to leverage all the tools and knowledge that exist in that space. Not that I even like XML. But having another XML dialect that's not actual XML shows that the only hope is to build valid tools and abstractions on top of all the crud.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#316Earlier quoted context omitted.
Why is an active ecosystem with healthy competition a bad thing? Personally, I can't stand javascript, and why you'd ever elect to use it for backend/server side code mystifies me. So I don't use it (or work in web development), and couldn't care less about what platform the hip web devs deem acceptable.
I mostly agree, however it does seem to make some sense to dive deep into one ecosystem, instead of learning & keeping up with two. (Let's not pretend that Javascript is the only one advancing--Django of a few years ago is not compatible with Django of today, as one other example). I have always used python/ruby on the backend, and I prefer them, but I recently worked on a couple of javascript backend projects, and I…
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#317Earlier quoted context omitted.
And thus, yet another insipid "hey let's argue about JS fatigue!" comment clobbers another HN comment page, with 100+ replies not one of which has anything to do with TFA .
If it wasn't a problem, it wouldn't be upvoted. That is how voting works. I'm not a JavaScript programmer, although I have dabbled extensively in the past. My impression of this thread is that not much has changed in that world. Sencha, titanium, and Phonegap were super hot back in the day, along with jQuery, SproutCore, Knockout and Backbone. Now it is all different for JS. That fuckng sucks.
It's upvoted because it's HN's current favorite holy war. "Front-end development is out of control" is something everyone has an opinion about, in a way that the announcement of React Fiber isn't.
That doesn't mean the same debate needs to be re-litigated every two days. Occasionally would be fine, but when it happens in every tangentially related thread it sucks the oxygen out of everything else.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#318Lin Clark's talk makes this sound like they implemented a scheduler in React -- basically JS is single-threaded, so they're implementing their own primitives and a scheduler for executing those on that main thread. Sounds neat, but it also seems like an explosion in complexity -- perhaps there will be a bunch of weird scheduler bugs the operating system folks more or less figured out a long time ago?
New code certainly carries risks that old, known code doesn't. And yes, this does carry over towards OS scheduler territory. That said, the early feedback from others in the React community is that the Fiber implementation is simpler overall and easier to work with than the "React Stack" implementation. Fiber is also explicitly built to support additional renderers on top of the core reconciler, while building render…
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#319http://isfiberreadyyet.com/
Do any of these fancy frameworks actually make a HTML fallback anymore? Most of the web pages I visit still renders fine without javascript.
Re: Facebook Announces React Fiber, a Rewrite of Its React Framework
#320Earlier quoted context omitted.
It's quite possible to use react with nothing else: no build tools, no transpilers, no fancy JSX, so in terms of tooling complexity, it can be as simple as you want or as complex as you want. Regarding the complexity of the underlying system, I think this is not a concern of the typical frontend developer. It has nothing to do with JavaScript or the web. If you are writing a "simple" C program on Linux, would you be…
Any resources you can provide about how to use React without JSX? JSX is a blocker for me.