dashersw

10 ms·

1.
by dashersw 2mo ago
It is real :)
2.
by dashersw 2mo ago
Here is the author of Gea Stack. There is no browser in the device, none of these devices could run one with 512KB of RAM (+2-8MB of PSRAM). We instead transpile TypeScript and CSS into native code, so the UI you build with web technologies
3.
by dashersw 3mo ago
Yes, exactly. We also have iOS and macOS targets, so a direct competitor to React Native as well.
4.
by dashersw 3mo ago
Thank you! I am the guy on the video. We will be open sourcing Gea Stack next month, and in the meantime I am showcasing the examples we've built so far. The underlying framework, Gea, is already available for the web on https:/&
5.
by dashersw 6mo ago
I am pondering about this, but would love to see an example to make it more concrete. The way I see it is that this reactivity is completely on the compiler's side, and there's no more ambiguity or pitfalls than misrepresenting a
6.
by dashersw 6mo ago
Yeah, sure :)
7.
by dashersw 6mo ago
As an open-source builder and a streamer, I'm afraid I will leak keys on stream any time soon. And fun story—I did leak the API keys to my smart lights once, and the company (Govee) had a 30-day grace period for any revoked keys! It st
8.
by dashersw 6mo ago
Feel free to question anything you like and I'll help you find the answers. This is a well-trodden path. All aspects of object mutation and its effects are obvious and well-known. What is pass by ref and what is pass by val is also pre
9.
by dashersw 6mo ago
I don't want to recurse into philosophy but one could argue an assignment is more declarative than a function call :) Solid is function calls everywhere, and extra code, vs plain objects.
10.
by dashersw 6mo ago
I see your point. I designed Gea to be one-way binding only first, and then decided to add two-way binding for props passed as objects. People can still easily only use one-way binding. Maybe this becomes a preference in the compiler config
11.
by dashersw 6mo ago
Thank you for the discussion, I find it very interesting and I'd love to understand how you think. Why do you think setStore and produce let you model your application more succinctly and efficiently than just a direct assignment? And
12.
by dashersw 6mo ago
It's like get-ah (but without the t).
13.
by dashersw 6mo ago
Gea in fact supports regular HTML strings out of the box—that's what the compiler turns the JSX into anyway. However IDE tooling is still in the works for syntax highlighting regular HTML. What syntax would you prefer from Svelte? Like
14.
by dashersw 6mo ago
Heh, sorry, I (the author) wasn't the one who created the post. But the idea is reactivity in JS shouldn't require new syntax. Gea works best with the compiler, I documented a non-compiled (only compiles JSX) browser usage here:
15.
by dashersw 6mo ago
Very interesting benchmark results... well, I guess that's proxies for you. Getters in Gea are designed to be used as computed properties by the components' rendering cycles, and in that, they don't need explicit memoization.
16.
by dashersw 6mo ago
Thank you! Very interesting insight—I'll have a look.
17.
by dashersw 6mo ago
Thanks for your insights. I was originally hesitant about the performance of proxies, too, but they turned out to be great. The benchmarks ( https://geajs.com/benchmark-report.html ) also show good results. Both in terms of m
18.
by dashersw 6mo ago
Because JavaScript _is_ the language and people know it. I never understood the concept of a "React developer", for example, although I saw many junior devs who were very well-versed in React and didn't completely understand
19.
by dashersw 6mo ago
I wish I could bring it to React! That would save so many developers and so much natural resources! I've been working on the library for 6 months, and it's built upon my previous libraries tartJS (2011), erste (2017) and regie (20
20.
by dashersw 6mo ago
Thank you! And you are right. I hadn't submitted it to the original js-framework-benchmark repo yet, but I just added the benchmark code on gea's repo. You can find it on https://github.com/dashersw/gea/b
21.
by dashersw 6mo ago
I understand this bit. The bit that I don't understand is how you compare the two invented concepts like `setStore` and `produce` to just `state.users[2]?.loggedIn = false`. To me it's very clear Gea's syntax requires you to
22.
by dashersw 6mo ago
Yeah afaik React Compiler doesn't really replace virtual DOM.
23.
by dashersw 6mo ago
In fact the precedent to Gea, my previous framework erste made use of `pug` tagged template literals! I started with that base, but then decided to ship with JSX instead. This would be a great addition to Gea and would love to see it as a c
24.
by dashersw 6mo ago
This is an interesting idea, though, thanks for bringing it up! I will think about it and try to add it to the compiler. Especially native objects like `window` would be great to create handlers for in the compiler. It would make life reall
25.
by dashersw 6mo ago
I'm not following—the `new` keyword has been with us since JavaScript's inception. You might be confusing it with the `class` syntax, but before that we could always `new` functions. And yes, Solid has signals that require you to
26.
by dashersw 6mo ago
Solid stores are a great improvement over raw signals, but they still come with their own gotchas. First off, it's an entirely new syntax. You need to learn its documentation. You always have to use setStore, and it has a weird syntax
27.
by dashersw 6mo ago
Solid is honestly a beast, and I love it! It was a great challenge to even match its performance, let alone beat it. While on several metrics they are within margin of error, select row, swap rows, remove row, and clear rows performances ar
28.
by dashersw 6mo ago
As the author... I somewhat agree :) But I really like synthwave and ever since I came across the design trend I wanted to use it somewhere. And I put twinkling stars on purpose, there's even shooting stars if you wait enough. I unders
29.
by dashersw 6mo ago
Thank you for the thorough comments! I wholeheartedly agree. And while I believe React invented most of its problems (mostly because we've been engineering GUI solutions since mid-70's and, as I always say, Excel, the god of all U
30.
by dashersw 6mo ago
Heh, sorry it comes across as LLM-y, honest and human-written answers here only. I'm tired of AI slop as much as the next guy, but, yes, I _really_ took my time with Gea. I've been working on writing JS frameworks for 15 years, th

More ›