brillout

6 ms·

1.
Show HN: Universal Deploy – deploy Vite apps anywhere(vike.dev)
1 points by brillout 5mo ago|0 comments
2.
by brillout 6mo ago
Indeed Accel is a long-term Vercel investor [0]. Not sure whether VoidZero and Vercel sharing the same investor has any sorts of implication. [0]: https://vercel.com/blog/series-f
3.
by brillout 6mo 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? [0]: https://voidzer
4.
by brillout 6mo 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&#x27
5.
by brillout 6mo 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 spa
6.
Vite 6, a Groundbreaking Release(vike.dev)
1 points by brillout 2y ago|1 comments
7.
by brillout 2y ago
Author of Vike (unaffiliated with Vite) here. Questions welcome.
8.
Vike – June Releases(vike.dev)
1 points by brillout 2y ago|1 comments
9.
by brillout 2y ago
Hi, I'm brillout the creator of Vike. Questions welcome!
10.
by brillout 3y 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&#
11.
by brillout 3y 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 anywh
12.
by brillout 3y ago
Very nice. Added to https://github.com/brillout/awesome-react-components .
13.
Vite 4.3 – Up to 3x faster dev cold starts(vitejs.dev)
4 points by brillout 3y ago|1 comments
14.
by brillout 3y 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 app
15.
by brillout 3y ago
Seems like you may appreciate https://vite-plugin-ssr.com/ (I'm its author).
16.
by brillout 3y ago
I think parent means that both Next.js and vite-plugin-ssr are open source, so "open(-source)" isn't a differentiator. I agree although we think we can keep the word "open" and make it clear that we're takling
17.
by brillout 3y ago
Yea, we've plans to improve communicating that. (Although we do plan to stick to the word "open".)
18.
by brillout 3y ago
Open alternative to Next.js: https://vite-plugin-ssr.com/ (I'm its author). Open: - Choose any UI framework you want (React/Vue/Solid/...) - A lot more flexible than Next.js (e.g. i18n and base assets
19.
by brillout 4y ago
VPS is tailored for users who like/want/need control. If you care about control, Astro isn't a good fit. E.g. you won't be able to use Astro with React Server Components. And many other subtleties that, in the end, sum u
20.
by brillout 4y ago
Astro is a whole different thing really. I don't think vite-plugin-ssr users would want to use Astro and also vice-versa to some degree.
21.
by brillout 4y ago
Yes :sweat_smile:
22.
by brillout 4y ago
I agree and that's why vite-plugin-ssr sponsorship https://github.com/sponsors/brillout plays a central role here: eventually, there will be enough sponsors to make vite-plugin-ssr a self-sustainable project a la
23.
by brillout 4y ago
> I couldn't get it to easily just output an HTML fragment. Feel free to create a GitHub ticket for that. (That's fairly easy to support as the only blocker is vite-plugin-ssr automatically injecting script tags.)
24.
by brillout 4y ago
https://github.com/brillout/vite-plugin-ssr/issues?q=is%3Ais... (it only list recently found bugs - there are plenty of older bugs that aren't labeled)
25.
by brillout 4y ago
What exactly is the problem? A lot of vite-plugin-ssr users are deploying to Vercel - have you seen https://vite-plugin-ssr.com/vercel and https://github.com/brillout/vite-plugin-ssr_vercel ? The recomm
26.
by brillout 4y ago
Comparison table: https://github.com/brillout/vite-plugin-ssr/issues/158#issue...
27.
by brillout 4y ago
> I’ve played with this with Tamagui [...] I’d love to see this stack continue to develop [...] and build the holy grail of universal stacks. Yes! Please let me know about your blockers. Feel free to create a new GitHub ticket "Tama
28.
by brillout 4y ago
Neat indeed :-). Love the Rust + Vite combo. These kind of combos are actually very well on my radar. (Also with Telefunc - a RPC implementation I'm working on.) FYI, in case you missed ViteConf yesterday: Rollup (which Vite uses) is c
29.
Show HN: Vite-plugin-ssr – Do-one-thing-do-it-well alternative to Next.js / Nuxt(vite-plugin-ssr.com)
114 points by brillout 4y ago|35 comments
30.
by brillout 4y ago
It is ironic because AFAICT Zod is actually more boilerplate than `shield()` :-). Although, the Zod familiarity is a clear argument in favor of Zod. Speaking of boilerplate, one Telefunc feature I'm particularly excited about is its ca

More ›