←back to thread

A standards-first web framework

(nuejs.org)
174 points tipiirai | 4 comments | 16 Jan 25 08:30 UTC | HN request time: 0.21s | source
Show context
tipiirai ◴[17 Jan 25 05:08 UTC] No.42734300[source]▶
I want to address Markdown and it's role in standards first development.

While MD itself isn't a web standard, it's a strategic choice that reinforces standards-first development by generating pure, semantic HTML. This creates a natural separation between content structure and visual presentation.

Consider the impact on CSS development.

In React codebases, engineers spend 90% of their time writing JavaScript - managing state, coordinating effects, optimizing builds. Style sheets become an afterthought, buried under framework patterns and utility classes.

Nue flips this ratio: codebases become 90% CSS, focusing engineering effort on systematic design through web standards. By keeping content in Markdown and presentation in stylesheets, we maximize the power of native CSS features - from custom properties and container queries to mathematical relationships for typography and spacing.

replies(2): >>42734870 #>>42736632 #
1. bitpush ◴[17 Jan 25 07:05 UTC] No.42734870[source]▶
> Nue flips this ratio: codebases become 90% CSS

This shows a lack of understanding of what a modern webapp is meant to be. Again, your framework is a attempt for static blogposts & other non-interactive/minimally intercative sites. Modern javascript developers build complex webapps, whether you like it or not.

You think stripe.com (webapp) engineers are spending 90% of the time tweaking css?

replies(1): >>42734978 #
2. tipiirai ◴[17 Jan 25 07:32 UTC] No.42734978[source]▶
In content-heavy websites, yes. Single-page apps are a different game obviously. this is a real number when comparing Next.js blog starter to Nue's blog starter:

https://nuejs.org/docs/compare.html

replies(2): >>42735206 #>>42737504 #
3. bitpush ◴[17 Jan 25 08:14 UTC] No.42735206[source]▶
If you want to be taken seriously, please do a like-for-like comparison.

Your comparison is between 2 drastically different sites. https://next-blog-starter.vercel.app/ and https://simple-blog.nuejs.org/

4. lelanthran ◴[17 Jan 25 13:53 UTC] No.42737504[source]▶
> In content-heavy websites, yes. Single-page apps are a different game obviously.

Content-heavy websites have (for me anyway) multiple acceptable solutions currently.

I want to see what your DSL looks like for SPAs.

To be clear, I am your target - developer who noped out of JS frameworks and want something better.

But, like I said, I already have multiple options for separation of concerns with content-heavy or mostly-static sites. What I don't have is a decent SPA framework that neatly does separation of concerns.