On: Show HN: One – A new React framework unifying web,...

[cabalamat]

> Creating websites and apps is simply too complex

And the solution, of course, is a framework on top of a framework on top of JS and the DOM. OK, maybe I'm being too harsh.

[mplewis → cabalamat]

The problem of integrating high-quality modern UI with complex live data is something that is actually complicated! Your choices here are limited:

1. Write lots of code to deal with the complicated problems

2. Use a framework that abstracts around these problems and solves some of them for you

3. Cut features from your app

This framework helps you with approach 2. If you don't want to use it, you are welcome to use approaches 1 or 3.

[breakfastduck → mplewis]

The problem is most people think their app is super complex and requires some mad thing that's actually complicated when actually its a glorified crud.

[nwienert → breakfastduck]

The iPhone is 100x more complex and does 10x more than like 10 separate gadgets from the 90s, and yet is also easier to use and more efficient than them all, broadly.

Your CRUD app could be terrible in pure HTML and amazing in Svelte. Or vice versa. But a competent engineer will make a better version with the more modern tech.

Your OS GUI is an abstraction on an abstraction, it's UI kit is on top of that, the browser is on top of that, React on top of that...

People always draw the ideal line exactly at where they learned things / stopped learning things.

[cabalamat → mplewis]

> high-quality modern UI

I do think that some UIs are more complex than they need to be.

[aatd86 → cabalamat]

Every problem can be solved by adding an extra layer of indirection xD

[lioeters → aatd86]

Except the problem of too many layers of indirection.

[swiftcoder → lioeters]

That's not a problem, it's an opportunity!

(for more layers of indirection)

[lioeters → swiftcoder]

Wait.. It's all layers of indirection?

Always has been.