←back to thread

174 points tipiirai | 4 comments | | HN request time: 0s | source
Show context
tipiirai ◴[] No.42722858[source]
Author here: this is Nue's new, more natural direction. Our previous focus on design engineers and CSS design systems was accurate, but missed the most important point: the web platform itself has evolved to eliminate the need for most framework abstractions. What began as elegant HTML, CSS, and JavaScript has devolved into build systems demanding hundreds of dependencies just to render a page.

This is a long term, ambitious project to strip away these artificial layers and return web development to its core strengths. Instead of fighting web standards, we're taking them to their absolute peak.

Happy to hear your feedback.

replies(6): >>42732432 #>>42732783 #>>42732807 #>>42736025 #>>42740718 #>>42743512 #
robertoandred ◴[] No.42740718[source]
You seem to have a fundamental misunderstanding of React, Next, etc. They don't stop you from using native CSS or HTML functionality.
replies(1): >>42741690 #
recursive ◴[] No.42741690[source]
Not technically, but they sure don't have to make it easy. Getting an element reference is clearly not the optimized-for use case. The docs even warn against it.

> Refs are an escape hatch. Manually manipulating another component’s DOM nodes can make your code fragile.

https://react.dev/learn/manipulating-the-dom-with-refs

replies(1): >>42743044 #
1. robertoandred ◴[] No.42743044[source]
Using HTML features doesn't have to mean manipulating another component's nodes.
replies(1): >>42743390 #
2. recursive ◴[] No.42743390[source]
But sometimes it does.
replies(1): >>42743719 #
3. robertoandred ◴[] No.42743719[source]
And that’s different from the primary use case of refs
replies(1): >>42744358 #
4. recursive ◴[] No.42744358{3}[source]
Indeed, and it's also the most practical way to use standard DOM operations from inside of react.