4 ms·

http://isfiberreadyyet.com/ http://isfiberreadyyet.com/

majewsky 9y ago
> 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.
- pygy_ 9y ago
  I think it runs the test suite live... It's not meant to be fast, but to demonstrate compatibility.
  - ktta 9y ago
    Are you sure? Because that's a waste of resources. I'd imagine they would cache the results, which would make the GP's concerns about speed valid. Edit: Found the github repo - https://github.com/tomocchino/isfiberreadyyet https://github.com/tomocchino/isfiberreadyyet Looks like it fetches from the umbrella issue[1] https://github.com/facebook/react/issues/7925 https://github.com/facebook/react/issues/7925
    - danabramov 9y ago
      It fetches from GitHub. The website was built in a weekend by our manager to make the task of a complete rewrite a little more fun for the team. Sorry it’s not perfect! ;-)
- mambodog 9y ago
  This app was written by a manager, don't read into it too much ;)
dkarl 9y ago
God, that page makes me want to drop everything and work to make tests pass. My team needs that.
- ehnto 9y ago
  Yay my tests pass. Wait, what were we building again?
  - dkarl 9y ago
    A web page to show our unit test results. I forget why.
nkkollaw 9y ago
That must be the slowest-loading page I've visited today, though.
- theWatcher37 9y ago
  I mean, what did you expect? Won't be long until someone upgrades their 16-thread 32GB machine because Facebook was "too slow"? I type this on a dual core phone with 2GB of RAM that's faster than most desktops 15 years ago thinking I need a faster device.
JusticeJuice 9y ago
I love the way the graph shows they actually broke some tests recently
- shaneos 9y ago
  They didn't break tests, instead a whole load of new tests were added, specifically around server side rendering, which exposed some gaps in coverage. This is exactly the type of openness you want to see for such a widely used project like React
tyfon 9y ago
The page is completely blank with javascript disabled (which is how I browse the web). So I guess it's not ready yet. Do any of these fancy frameworks actually make a HTML fallback anymore? Most of the web pages I visit still renders fine without javascript.
- RussianCow 9y ago
  That's the paradigm of single-page apps (SPAs). Rather than the traditional client/server model where the server renders the page and sends it back to you, SPAs do all the rendering on the client-side, and simply pass data back and forth between the server using APIs. It's (in my opinion) a superior model for apps, but has a lot of disadvantage that make it unsuitable for websites—mainly that SPAs take longer to load initially and don't work without JS enabled (which also includes search engine crawlers). Having said that, it's entirely possible (though not easy) to have your React app work without JS enabled by rendering it on the server before sending the page to the client. This way, you get the best of both worlds, but it's a lot of work to implement this properly for a remotely complex app. The answer in the short-term is that you shouldn't be using a "fancy framework" for anything for which the above disadvantages are a deal-breaker (like most public sites) until the server-rendering story matures and becomes more compelling.

> 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.

pygy_ 9y ago
I think it runs the test suite live... It's not meant to be fast, but to demonstrate compatibility.
- ktta 9y ago
  Are you sure? Because that's a waste of resources. I'd imagine they would cache the results, which would make the GP's concerns about speed valid. Edit: Found the github repo - https://github.com/tomocchino/isfiberreadyyet https://github.com/tomocchino/isfiberreadyyet Looks like it fetches from the umbrella issue[1] https://github.com/facebook/react/issues/7925 https://github.com/facebook/react/issues/7925
  - danabramov 9y ago
    It fetches from GitHub. The website was built in a weekend by our manager to make the task of a complete rewrite a little more fun for the team. Sorry it’s not perfect! ;-)
mambodog 9y ago
This app was written by a manager, don't read into it too much ;)

dkarl 9y ago

God, that page makes me want to drop everything and work to make tests pass. My team needs that.

ehnto 9y ago
Yay my tests pass. Wait, what were we building again?
- dkarl 9y ago
  A web page to show our unit test results. I forget why.

nkkollaw 9y ago

That must be the slowest-loading page I've visited today, though.

theWatcher37 9y ago
I mean, what did you expect? Won't be long until someone upgrades their 16-thread 32GB machine because Facebook was "too slow"? I type this on a dual core phone with 2GB of RAM that's faster than most desktops 15 years ago thinking I need a faster device.

JusticeJuice 9y ago

I love the way the graph shows they actually broke some tests recently

shaneos 9y ago
They didn't break tests, instead a whole load of new tests were added, specifically around server side rendering, which exposed some gaps in coverage. This is exactly the type of openness you want to see for such a widely used project like React

tyfon 9y ago

The page is completely blank with javascript disabled (which is how I browse the web). So I guess it's not ready yet. Do any of these fancy frameworks actually make a HTML fallback anymore? Most of the web pages I visit still renders fine without javascript.

RussianCow 9y ago
That's the paradigm of single-page apps (SPAs). Rather than the traditional client/server model where the server renders the page and sends it back to you, SPAs do all the rendering on the client-side, and simply pass data back and forth between the server using APIs. It's (in my opinion) a superior model for apps, but has a lot of disadvantage that make it unsuitable for websites—mainly that SPAs take longer to load initially and don't work without JS enabled (which also includes search engine crawlers). Having said that, it's entirely possible (though not easy) to have your React app work without JS enabled by rendering it on the server before sending the page to the client. This way, you get the best of both worlds, but it's a lot of work to implement this properly for a remotely complex app. The answer in the short-term is that you shouldn't be using a "fancy framework" for anything for which the above disadvantages are a deal-breaker (like most public sites) until the server-rendering story matures and becomes more compelling.