brillout
Joined 13 years ago
Karma
152
Submissions
137
Member since
Sep 7
Recent submissions
Comment · 7 months ago
Comment · 7 months ago
Doesn't seem like it — see VoidZero investors [0].
> Unfortunately for Bun, if they are forced to help Anthropic more than they can focus on OSS
Curious: is that speculation, or based on observation?
Comment · 7 months ago
Vite+, Void Cloud, Void Framework... an epic battle between Vercel and Void is coming.
The PRC (aka server functions) demo [0] is particularly interesting — end-to-end type safety (from DB to UI) is a major milestone for JavaScript. We've been doing a lot of RPC design work in that space with Telefunc (tRPC alternative) [1] — it's a really hard topic, and we're looking forward to collaborating with the Void team. (Also looking forward to contributing as the creators of Vike [2].)
[0]: https://www.youtube.com/watch?v=BX0Xv73kXNk (around the end of the first talk) [1]: https://telefunc.com (see the last PR) [2]: https://vike.dev
Comment · 7 months ago
The Void Framework demo [0] is exciting!
The PRC (aka server functions) demo is particularly interesting — end-to-end typesafety (from DB to UI) is a major milestone for JavaScript.
We've been doing a lot of RPC design work in that space with Telefunc (tRPC alternative) [1] — we're looking forward to collaborating with the Void team. (Also looking forward to contributing as the creator of Vike [2].)
[0] https://www.youtube.com/watch?v=BX0Xv73kXNk (around the end of the first talk)
[1] https://telefunc.com (see the last PR
[2] https://vike.dev
Comment · 1 year ago
Author of Vike (unaffiliated with Vite) here. Questions welcome.
Comment · 2 years ago
Hi, I'm brillout the creator of Vike.
Questions welcome!
Comment · 3 years ago
I agree and, as the author of vite-plugin-ssr[1], that's what I recommend to my users: go for static whenever you can.
I think it's something every web developer should be aware of. Static is indeed a lot simpler than dynamic.
I've wrote more about it over here[2] (SSG = static, SSR = dynamic).
Comment · 3 years ago
Also have a look at https://vite-plugin-ssr.com/ (author here).
VPS is slightly lower level which gives you a lot more control: integrate with your existing Node.js backend (use any backend framework you want), deploy anywhere, use any React alternative (Solid, Preact, ...) and any data fetching tool (e.g. Relay can't really be used with Next.js).
The flip side is that you've to write a little bit more glue code. Although this will be alleviated by a lot with projects such as Bati[0], Stem[1], and vike-react (see Vike Rebranding[2]).
VPS also cares a ton about details, such as hooks for full control over i18n (use any i18n strategy you want), better Base URL support (VPS supports setting a different base for your server and your CDN), automatic deploy synchronisation, domain-driven file structure, polished and helpful error messages (especially the next upcoming release), ...
Detailed comparison with Next.js: [3].
If you run into any blocker then it's quickly fixed (or at least a workaround is proposed).
It supports not only SSR and pre-rendering, but also SPA in case you don't need SSR. It's going to support RSC but doesn't yet (RSC isn't ready for production).
Because it's lower level and because it's decoupled from React everything is designed in an agnostic way and with meticulous care. In other words: vite-plugin-ssr is becoming a robust foundation. There are breaking changes coming for the v1 release but beyond that chances are that there won't be any breaking changes for years in a row.
In a nutshell: vite-plugin-ssr takes care of the frontend and only the frontend. You keep control over your architecture. (Whereas frameworks tend to put themselves right in the middle of your architecture restricting you in fundamental ways.)
Last but not least: it's powered by Vite which means blazing fast HMR.
Comment · 3 years ago
Very nice. Added to https://github.com/brillout/awesome-react-components.
Comment · 3 years ago
Interestingly, Vite itself is written in a slow interpreted language (JavaScript/TypeScript) while using compilers that are written in fast native languages such as ESBuild (written in Go).
It's a nice showcase of successfully applying the strategy of focusing on hotpath performance instead of blindly making every line of code "fast".
Also, Vite being written in JavaScript is much friendlier to the ecosystem. I myself made many PRs to Vite which I would have done much less if it involved a more complex language.
Shameless plug: I'm the author of https://vite-plugin-ssr.com which is a Next.js/Nuxt alternative but with a "do-one-thing-do-it-well architecture"[1].
[1]: https://vite-plugin-ssr.com/architecture#do-one-thing-do-it-...
Comment · 3 years ago
Seems like you may appreciate https://vite-plugin-ssr.com/ (I'm its author).
Not sure whether VoidZero and Vercel sharing the same investor has any sorts of implication.
[0]: https://vercel.com/blog/series-f