brillout

4 months agodiscuss

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

brillout

4 months agodiscuss

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://voidzero.dev/about

brillout

4 months agodiscuss

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

brillout

4 months agodiscuss

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

brillout

7 years agodiscuss

There are many JS libraries that are wonderfully simple. I think the problem is:

- Too much choice; it's insane how much you have to decide before you get started: React or Vue? SSR or SPA? REST, GraphQL, or RPC? PostCSS or Sass? CSS-in-JS? What router? Redux or stateful components? Axios or Fetch API? Client-side rendering/routing or server-side rendering/routing? Webpack, Parcel, Create-react-app, Next.js, or Gastby? And the list goes on... I mean that's just nuts.

- State management is inherently complicated; people don't realize that 90% of the case you don't need interactive / stateful views to build a product. People implement bunch of useless interactive "niceness" that are overkill because React allows them to. If you use React as an HTML template engine then React is actually super simple and super neat.

How awesome would it be to have a framework that has sensible defaults for all these questions. And that educates how to decide certain crucial aspects.

For example:

- Use plain old HTML instead of interactive views if you can.

- Don't start with Redux. Instead, use Redux only after you know exactly why you need Redux.

- Use a RPC-like API (e.g. https://github.com/reframejs/wildcard-api) and only use REST/GraphQL if you need to expose your data to third parties.

- Use server-side rendering/routing if your app is mainly about content (a blog, a newspaper, a e-commerce shop, ...).

- Use client-side rendering/routing if your app is mainly about user interactions (a music player, an email app, a graphical editor, ...).

That's what I'm trying with Reframe: https://github.com/reframejs/reframe

brillout

7 years agodiscuss

The problem is the enormous amount of choice we have:

- React or Vue?

- Redux or stateful components?

- GraphQL or REST or RPC?

- SSR or SPA?

- ...

We are missing a framework with sensible defaults for all these questions. And that does a good job at explaining what decisions one should take.

I'm trying to build such framework: Reframe (https://github.com/reframejs/reframe).

Submissions

Show HN: Universal Deploy – deploy Vite apps anywhere

comments