131–140 of 422 posts
http://isfiberreadyyet.com/
I love the way the graph shows they actually broke some tests recently
This is exactly the type of openness you want to see for such a widely used project like React
Great. I was waiting for React to stabilize before I learned it. I've been cleverly waiting since 2006 to learn jquery. Will start next year.
Earlier 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…
>"At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative." You mean like Dart? Besides, languages that target WebAssembly are almost certainly going to evolve to fit that space.
And are already but now targeting JS. Like PureScript, ReasonML, Elm and even TypeScipt to some extend.
Earlier quoted context omitted.
There is clearly some sort of mapping available to a JavaScript FFI for doing I/O, as both the Unreal engine and Unity have been ported to WebAssembly. If you can run a video game engine in the browser you can run anything. I believe there are proposals in place as well to add opcodes to directly interface with browser capabilities rather than going through a JS FFI.
> If you can run a video game engine in the browser you can run anything no
Earlier quoted context omitted.
> This page is rendered with it. Yep, I can tell from the 5 seconds of blank screen while my phone browser loads all that JS.
I think it runs the test suite live... It's not meant to be fast, but to demonstrate compatibility.
Edit: Found the github repo - https://github.com/tomocchino/isfiberreadyyet
Looks like it fetches from the umbrella issue[1]
> It’s already in use on Facebook.com today What's preventing us from using it in our apps then ? Do they limit the use of the API to what's implemented in Fiber in some parts of the website ?
Earlier quoted context omitted.
Browsers and JavaScript are what we have, we can't magically replace every browser and JS implementation in the world. We have to figure out where we want to go and slowly get there. That is exactly what is happening in the frontend world and that is why there is so much churn. Browser apps have to work across 4 major browsers with versions going back almost 10 years, an infinite amount of screen sizes, and a near in…
> And the other great thing about these tools is you can add/remove them as needed. In order to get that freedom, you need to build the tooling in such a way that it aligns with the web standards, so that when the standards catch up you can drop what you don't actually need anymore. We all switched from coffescript to ES6 and Babel because ES6, being standards-based, will eventually be supported in browsers, right? A…
Earlier quoted context omitted.
Not the OP, but I expect the web to be a thing where documents (i.e. mainly text) don't have any issues rendering on my 5-year old phone or on my 8-year laptop (both of which work very well, still, and which I don't plan to replace anytime soon). The recent web practices (I'm talking mostly of the last 2-3 years, since more and more people have started copying Twitter with its launch of its "every website needs to be…
Well what's unique about HN and Wikipedia? They're largely non-monezited. If Buzzfeed can make more money off of a flashy website it's hard to argue with.
Earlier quoted context omitted.
Any resources you can provide about how to use React without JSX? JSX is a blocker for me.
It's basically just to use the React.createElement API that JSX transpiles to. I say give JSX a chance though.