Live data from Hacker News

Vite+ Beta

voidzero.dev

41–50 of 163 posts

Re: Vite+ Beta

#42

Layer on layer on layer on layer on layer.... Web development is just a meme by now

Pretty much all software is built like that.

I think web development does not need that many layers. Usually there is a clear purpose for each layer. I think most problems in web are self-created.

Re: Vite+ Beta

#43

Can it be used for Node builds or browser-only same as Vite?

I'm always curious of the use case when someone proposes Node code bundling. What's the advantage? Obfuscation in SEA?

I’ve found if you want interop ts esm and js cjs you need to compile your code - and then `tsc` doesn’t bundle your dependencies for you and outputs incomplete code.

Re: Vite+ Beta

#44
I appreciate the effort to bring things together in this but…

> Vite+ will manage your global Node.js runtime and package manager.

What? Why?

You’re really going all-in if you adopt this; and… for what? A bit of cozy tooling around existing standard ways of doing things?

Ok, sure; I like tools, like vite.

…but even for an opinionated tool, this is extraordinarily opinionated. Like next.js

Im skeptical.

The pitch of bringing things together seems strong, but did we go too far here?

Reading reviews of people using this didn't really convince me.

It seems to be running on the coat tails of the vite name, rather than its own merit.

Re: Vite+ Beta

#45

Truly have so much trouble keeping up with the frontend (or JavaScript?) ecosystem. I so miss working in laravel. Wish more jobs paid well to use it.

you actually don't have to keep up, whatever you were using still works

Re: Vite+ Beta

#46

Earlier quoted context omitted.

This is just what modern languages have out of box. (Like rust and go.) it’s a true shame that web isn’t actually unified behind a type safe language with a single solid toolchain. It’s a huge pain to manage and I’m curious how much money it’s cost the industry. “Vite+” isn’t a true solution to that. There are many competing toolchains. And no default standardized one.

I'm not very familiar with Rust, but doesn't cargo pull a lot of external dependencies for most projects? I really like how Go can do everything with just the standard library, but I wasn't aware Rust was similar. For typescript we've moved our stuff to bun. It has it's own risk management perspective compared to node, but at least it's now possible to build web services without having to rely on a bunch of external…

> without having to rely on a bunch of external dependencies. Which in our highly regulated business would require security policies for each dependency explaining the risks, why we accept them and how we mitigate them.

How about the dependencies Bun is pulling? How did you ever managed to pass security policies with Bun which has so many segfaults that nobody even bothers to write CVEs for them.

Re: Vite+ Beta

#47

Layer on layer on layer on layer on layer.... Web development is just a meme by now

Vite+ isn't a layer, it's "just" a high-performance suite of excellent tools that work well together to provide a great DX for developers.

Vite+ can improve and simplify what developers are already doing with ad-hoc collections of tools. Vite is already an industry standard, and Vite+ has a good chance of achieving that status as well.

Re: Vite+ Beta

#48

Earlier quoted context omitted.

This is just what modern languages have out of box. (Like rust and go.) it’s a true shame that web isn’t actually unified behind a type safe language with a single solid toolchain. It’s a huge pain to manage and I’m curious how much money it’s cost the industry. “Vite+” isn’t a true solution to that. There are many competing toolchains. And no default standardized one.

I'm not very familiar with Rust, but doesn't cargo pull a lot of external dependencies for most projects? I really like how Go can do everything with just the standard library, but I wasn't aware Rust was similar. For typescript we've moved our stuff to bun. It has it's own risk management perspective compared to node, but at least it's now possible to build web services without having to rely on a bunch of external…

Cargo itself doesn't pull the dependencies, but yes to Rust's standard library being much more lean than Go. Bring your own HTTP, text templating, and such, but core data structures are provided.

Go gives you a bunch of goodies in the standard library.

Rust provides things like your build system, testing, and package management all together, which is what I assume OP meant.

Re: Vite+ Beta

#49
post #35

Layer on layer on layer on layer on layer.... Web development is just a meme by now

Deze vuist op deze vuist. Deze vuist op deze vuist. Deze vuist op deze vuist. En zo klim ik naar boven. You probably need to see a video or gif to get it.

Some barbarian without a grasp of the Dutch language knee-jerked the down-vote button so I'll add a Swedish version which adds an important attribute.

   Imse vimse spindel klättra upp för trå'n.
   Ner faller regnet, spolar spindeln bort.
   Upp stiger solen, torkar bort allt regn.
   Imse vimse spindel klättrar upp igen.
Here's how to interpret this saga of the ever-climbing little spider in the context of web development. It climbs up its tread (klättra upp för trå'n) 'cause that new framework will sure make catching those flies (clicks/jobs/likes/whatevers) easier. And then the rain starts (the CVEs start piling up, the corrupted packages come flooding in) and the hapless spider gets thrown off its web (Pwned!) until the sun comes back and dries away the rain (a new framework, yay, this will solve all problems) upon which the spider climbs up its thread again.

Re: Vite+ Beta

#50

I love Vite, Vitest, Oxlint and Oxfmt and look in their direction for most of my new projects! I hope these folks manage to get a bunch of money and can fund the continued development for at least the next decade. Sure beats opening some ancient project and seeing some mix of Gulp, Grunt, webpack and a bunch of other disjointed stuff (I migrated that one over to also use the newer stack).

> Sure beats opening some ancient project and seeing some mix of Vite, Vitest, Oxlint and Oxfmt and a bunch of other disjointed stuff (I migrated that one over to also use the newer stack).
Post reply on HN