tipiirai

6 ms·

61.
by tipiirai 1y ago
I want the examples to reflect real-world scenarios. Please explain how to simplify the React code. I'll fix it immediately.
62.
by tipiirai 1y ago
I definitely want the examples to be exact. How to fix exactly?
63.
by tipiirai 1y ago
What's the difference? I can easily add the missing peaces.
64.
by tipiirai 1y ago
The core difference here is "reactivity". You cannot build large-scale apps without state management and domdiff.
65.
by tipiirai 1y ago
I sure can. How should I change the code? I'll do it right away.
66.
by tipiirai 1y ago
I see your stance! There are two ways to this: JS-first (React) or HTML- first. Hyper takes the latter: purely focusing on the semantic HTML structure when assembling interfaces. Focusing on pure structure (like React 1.0) and delegating de
67.
by tipiirai 1y ago
There is an offset (depending on the app) where JS crashes with stack overflow exception, and only WASM can continue from there. On the Nue example with user records the treshold was around 150k records (only slightly depending on the brows
68.
by tipiirai 1y ago
This is a prime example of how complexity grows and how simple components remain simple. Just look for the button example: the one button being larger than the entire app. Consider going on from there. Think legos: the 2/4/8 units
69.
by tipiirai 1y ago
Agreed. No reason to show more than 100+ entries on a single table. Event sourcing isn't about UI patterns but rather one level beyond it: the "back of the frontend" [1]: [1]: https://bradfrost.com/blog/
70.
by tipiirai 1y ago
When you go pass 100k-200k records on the client side, typically fetched with event sourcing pattern, you must resort to WASM. Here's a RUST based example with 150k records to tackle the situation: https://mpa.nuejs.org&#x2F
71.
by tipiirai 1y ago
The challenge is that there is a difference. Client is "reactive" and server rendering is static. The SSR output needs to be some sort of hybrid, which Hyper is absolutely going to tackle. This is another area where simplicity shi
72.
by tipiirai 1y ago
Thanks. The utopia is real. React absolutely dominates the market and has a certain, monolithic way of doing things. Hyper attempts to show that timeless software patterns, namely separation of concerns (Remember Gang of Four?), can bring s
73.
by tipiirai 1y ago
You're right. This post has major corrections to the orignal post.
74.
Show HN: Hyper – Standards-first React alternative(nuejs.org)
70 points by tipiirai 1y ago|85 comments
75.
by tipiirai 1y ago
Exactly. Doing it myself would be more dishonest
76.
by tipiirai 1y ago
@isqueiros I certainly can. Tailwind evangelist like you should look closer to web standards. Especially CSS. The points you make are simply absurd: feels like you have only worked with React and never understood the DOM. Time to learn!
77.
by tipiirai 1y ago
I can see that simplicity appears as "stupid" for you
78.
by tipiirai 1y ago
> You made the choices to include these. I did not. ShadCN data table requires these. Check their docs > None of these things are inevitable in React. Hence the "old shchool" example. ps: I have a deep understanding how Reac
79.
by tipiirai 1y ago
Yes. I asked Claude to write the most idiomatic React to implement both the ShadCN and the old school React examples.
80.
by tipiirai 1y ago
Yes. If you are a keen Tailwind user and think "class names is the reason CSS doesn't scale" (as they say)
81.
by tipiirai 1y ago
It's both: having both "sane" syntax and simple mental model is the key.
82.
by tipiirai 1y ago
Hyper demonstrates that simplicity scales. It's easier to construct large-scale apps with simple units rather than cramming complexity together. It's not about the syntax (JS first vs HTML first), but rather how much you have that
83.
by tipiirai 1y ago
Vue is indeed similar, but Hyper is more minimal with fewer special characters and syntax patterns. The key difference is that Hyper strictly separates styling: no CSS-in-JS or class manipulation is allowed. This makes components truly reus
84.
by tipiirai 1y ago
Thank you. Yes. SSR is supported. Look for the docs: https://nuejs.org/hyper/
85.
by tipiirai 1y ago
Author here: This is a developer preview, ultimately replacing the current Nue JS reactive library. There is a FAQ section at the end of the article. Happy to answer any other questions here.
86.
by tipiirai 1y ago
Seems Grok has silently added workspace feature to Grok, similar to Claude's workspaces with attachments, chat instructions, and past conversations. Seems to be available on the free version too.
87.
Grok 3.0 Workspaces(grok.com)
4 points by tipiirai 1y ago|1 comments
88.
by tipiirai 2y ago
A JavaScript framework, built by a person who hates JavaScript doesn’t sound right
89.
by tipiirai 2y ago
This is a great idea!
90.
by tipiirai 2y ago
Is there a full-blown SPA demo made with htmx?

More ›