Discussion on: What would the ideal web framework look like?

View post

Replies for: I'll start My "ideal" framework would be a framework which is compiled: it would have components in a file with script and style tags (like Vue/Sv...

Tyler V. (he/him) • Aug 26 '21

and the compiled output will be HTML (Yes, actual HTML, not just a boilerplate)

Can you clarify what you mean by this? I'm not sure I understand it.

Siddharth • Aug 26 '21

Consider this component:

<script>
    let name = 'world';
</script>

<main>
    <h1>Hello {name}!</h1>
</main>

If you run this through Svelte, you get this HTML as output:

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset='utf-8'>
    <meta name='viewport' content='width=device-width,initial-scale=1'>

    <title>Svelte app</title>

    <link rel='icon' type='image/png' href='/favicon.png'>
    <link rel='stylesheet' href='/global.css'>
    <link rel='stylesheet' href='/build/bundle.css'>

    <script defer src='/build/bundle.js'></script>
</head>

<body>
</body>
</html>

It's basically a boilerplate. In my "ideal" framework, the h1 element would be there in the HTML (maybe statically embedded, if the framework is really good). This could speed up a little bit

Tyler V. (he/him) • Aug 26 '21

I see what you mean now - Something that outputs closer to Static Site Generators without being fully static 😊 That would be amazing!

Eckehard • Aug 26 '21

Why not use a function h1("Headline")? This would be even quicker as it create a DOM element without rendering HTML. And as it is a function, it can be part of any algorithm you want.

Siddharth • Aug 27 '21

Yep, it would! I'm actually building a prototype of something like this.

Gerrit Weiermann • Aug 27 '21

What about next.js?

Siddharth • Aug 27 '21

It sounds interesting, but I haven't used it, so I can't say much.