A whole website in a single JavaScript file

edent wrote: post #2

> rendered dynamically, just in time, at the edge, close to the user. HTML. You're serving HTML. Doesn't really matter that the server-side language is JS, PHP, or BASIC.

Aaron from Deno here. Of course it's producing HTML as an output, but the point is that you can use JSX and familiar technologies like tailwind to dynamically generate that HTML at edge vs client side.

And unlike a pure static site, you can add API or form routes

Re: A whole website in a single JavaScript file

#6

Post by AaronO » Wed, Apr 06, 2022, 6:24 PM UTC

jack_riminton wrote: post #4

I don’t think a simple, static site is a great example for an entire framework

What other kinds of examples would you like to see ?

The goal was to showcase simple yet intuitive JSX + tailwind at edge, we didn't elaborate on more advanced use-cases like authenticated pages, API endpoints/forms, dynamic pages (location, etc...) or parametric routes.

Re: A whole website in a single JavaScript file

#7

Post by lucacasonato » Wed, Apr 06, 2022, 6:26 PM UTC

dmitrygr wrote: post #3

"time to interactive: 1.0s / first content paint 1.0s" My man, let me introduce you to ... HTML. It has "time to interactive" at 0.0 seconds and content paints instantly!

I think you might have misunderstood the blog post. It is server-side rendering on the edge, shipping nothing more than plain HTML/CSS to the browser. There is no client side JS *at all* here.

Re: A whole website in a single JavaScript file

#8

Post by dmitrygr » Wed, Apr 06, 2022, 6:28 PM UTC

lucacasonato wrote: post #7

dmitrygr wrote: post #3

"time to interactive: 1.0s / first content paint 1.0s" My man, let me introduce you to ... HTML. It has "time to interactive" at 0.0 seconds and content paints instantly!

I think you might have misunderstood the blog post. It is server-side rendering on the edge, shipping nothing more than plain HTML/CSS to the browser. There is no client side JS *at all* here.

The shown page could be served on 0.01 seconds if it was...html. Or, if you MUST lob complexity at it, use a static site generator... that generates...HTML

Re: A whole website in a single JavaScript file

#9

Post by tmp_anon_22 » Wed, Apr 06, 2022, 6:31 PM UTC

This starts to make sense when you consider the self-flagellation of a full server-side-rendering production setup that has existed over the past decade, to the point many SPA products completely give up on SSR - or nowadays throw themselves at the walled garden of Vercel/Next.js etc to solve it for them.

Re: A whole website in a single JavaScript file

#10

Post by suprfsat » Wed, Apr 06, 2022, 6:45 PM UTC

dmitrygr wrote: post #3

"time to interactive: 1.0s / first content paint 1.0s" My man, let me introduce you to ... HTML. It has "time to interactive" at 0.0 seconds and content paints instantly!

Report a bug in Lighthouse then.