21–30 of 34 posts
Earlier quoted context omitted.
What Svelte used to be pre version 5 I think? They now also have a runtime with hooks, etc
Svelte did always have a runtime, they're still doing this from what I understand the major part of Svelte 5 was moving to signals.
Please don't use LLMs for landing pages. Regardless of how long you've been developing the project, many people base their first impressions on whether a real person curated the documentation and website. And if you didn't, then they might never even get to evaluating your code at all.
Thanks. I totally hear you and that makes sense. Content is not my forte and I get lazy when it comes to that. Will improve it.
The way to get good at something is by doing it a lot.
"Four things, running here"
This made me want to close the tab.
Take some time to think about what you've built and explain it in your own words. Get an LLM to help you with content ideas and editing, but write it yourself. It looks like a cool project.
Not sure what this project is for... the only way to statically compile JSX into direct DOM mutations is to either castrate React's dynamic runtime flexibility and closure model, or break its semantics like SolidJS does (in this case worse because the lack of templating/syntax constraints just shifts the burden from the compiler to the developer).
There's ways you can write your code such that you _know_ that certain blocks of code are going to be unaffected by input changes, and you can then use that information to reduce the scope of changes that need to be done, with only minimal costs to expressivity.
I think with a decently smart compiler (and of course the compiler simply treating a lot of stuff in a black box way) you can totally shrink down the amount of work a client needs to do to render React components, all without changing the semantics.
Of course any performance trick might change the actual sequence of events that happen, and in particular for libs doing fancy DOM manipulation, it's easy for those to rely on React's incidental behavior in a non-spec-confirming way.
But the main point her is that you can totally get to useful improvements on a subset of your React, while still leaving the rest of your components intact
Please don't use LLMs for landing pages. Regardless of how long you've been developing the project, many people base their first impressions on whether a real person curated the documentation and website. And if you didn't, then they might never even get to evaluating your code at all.
Airbnb has this project with the same name as well , https://viaduct.airbnb.tech/ , for a second I was confused if that got changed somehow
Please don't use LLMs for landing pages. Regardless of how long you've been developing the project, many people base their first impressions on whether a real person curated the documentation and website. And if you didn't, then they might never even get to evaluating your code at all.
Thanks. I totally hear you and that makes sense. Content is not my forte and I get lazy when it comes to that. Will improve it.
I built a compiler that compiles React code into vanilla JS.
Here are some examples
Vidact Start adds a bunch of server-side features - file routes, server loaders, SSR, hydration, and client navigation.
You can't use class components, createRef, most of the Children helpers, or React DevTools. Or any third-party package that ships precompiled against React's runtime.
React code looks so ugly to my taste. Try reading it: "use state zero". What does it even mean? And why "const" is used for a value that changes? const [count, setCount] = useState(0) I didn't understand how the compiler works completely, but I assume it tries to figure out the dependencies during compilation time ("The text of node Y depends on variable x"). This approach is closer to Vue's approach which uses proxi…
are u being serious rn?