Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vite+ Beta

voidzero.dev

Post reply on HN
Print view View original

141–150 of 163 posts

Re: Vite+ Beta

#141

Post by 1-more »

anon7000 wrote: post #25
overflyer wrote: post #23

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

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.

> a type safe language with a single solid toolchain

Been paying the bills for 5.5 years now writing in one that gets a fair amount of stick for being ~6.7 years with no language version releases (one is planned for this summer though that should make it just under 7). There's one compiler, one standard library, one formatter (with no config options), one linter, and two test runners but one is a rust rewrite of the other one so it's chill. The language being on a timeout has led to all kinds of things like compilers for native (consuming the intermediate representation .o files), fullstack un-forks (no change to syntax of language), fullstack actual forks, really a lot of weird but delightful activity.

It's like me and a few hundred other people, so "unified" is the part that's missing, haha.

Re: Vite+ Beta

#142

Post by CrimsonRain »

christophilus wrote: post #127
hiccuphippo wrote: post #67

Earlier quoted context omitted.

That's what I liked from Bun's proposition. A single binary that just works. Hopefully the others take notice.

Honestly, I hate that Bun is vibe-coded and seems amateurish in many ways, but it’s still an excellent tool.

so instead of looking at the result, you are complaining about (a minor aspect of) the process.

Jarred is an excellent engineer. He'll deliver.

Re: Vite+ Beta

#143

Post by artemave »

mort96 wrote: post #97
bhouston wrote: post #78

Earlier quoted context omitted.

> But I have zero clue what those other tools are. The incorporated tools are actually really amazing: - vitest, an ultra fast test runner. After using a lot of others, including jest and node's built in one, I love vitest. - oxlint, replaces eslint but is compatible with its file format and ultra fast, since it isn't written JavaScript. I tried biome, but I found oxlint to have more rules and the eslint compatibilit…

I don't get how a test runner can be "ultra fast". Surely all the time is taken by the tests, not calling the test functions?

You'd be surprised https://github.com/artemave/node-test-runners-performance-co...

Re: Vite+ Beta

#144

Post by johnny22 »

ramesh31 wrote: post #126

That "+" is making me really nervous. Is this just a naming quirk, or the start of them trying to monetize Vite? If the latter, this is a dark day for frontend dev.

you missed the monetization phase. It was already attempted before they were acquired by cloudflare.

The goal was to sell a tool that integrated all parts of vite and oxc ecosystem (oxlint, oxfmt, vite, vitest, etc) in one place.

That stopped right before official cloudflare acquisition announcement.

Re: Vite+ Beta

#145

Post by ProCodeSoftware »

sailorganymede wrote: post #55

I am a big fan of Vite. But I have zero clue what those other tools are. I swear to God, I just put my head down to do some work and all the sudden, frontend tooling has evolved. I wonder if there is a push towards a "boring but works" stack.

I use oxfmt and oxlint, the first JS linter I've used. For a long time, I avoided Eslint due to how strict it was, but even though oxlint uses eslint, I've been ok using it. I haven't used vitest before though.

And I think Webpack should be discontinued by now, because Vite has replaced it in every way. Maybe to get other projects to switch, they should make a Webpack-to-Vite migration script.

Re: Vite+ Beta

#146

Post by hokkos »

herpdyderp wrote: post #85
bhouston wrote: post #78

Earlier quoted context omitted.

> But I have zero clue what those other tools are. The incorporated tools are actually really amazing: - vitest, an ultra fast test runner. After using a lot of others, including jest and node's built in one, I love vitest. - oxlint, replaces eslint but is compatible with its file format and ultra fast, since it isn't written JavaScript. I tried biome, but I found oxlint to have more rules and the eslint compatibilit…

I wish Oxfmt supported plugins. Prettier's plugin API is one of the worst APIs I've ever worked with. I'm eager to switch to a different formatter with a better plugin API (and I need plugins).

being worked on : https://github.com/oxc-project/oxc/discussions/21936

Re: Vite+ Beta

#147

Post by tshaddox »

mort96 wrote: post #124
tshaddox wrote: post #119

Earlier quoted context omitted.

So something can only be "boring but works" if it was created before today?

Yes, it's not boring if it's the new hotness

Okay, then how can something become boring? It needs to start as the new hotness? Does that imply that the people who use non-boring software are the ones who determine which things get to graduate to being boring?

Re: Vite+ Beta

#148

Post by mort96 »

tshaddox wrote: post #147
mort96 wrote: post #124

Earlier quoted context omitted.

Yes, it's not boring if it's the new hotness

Okay, then how can something become boring? It needs to start as the new hotness? Does that imply that the people who use non-boring software are the ones who determine which things get to graduate to being boring?

More or less, yeah?

Re: Vite+ Beta

#149

Post by montroser »

Tadpole9181 wrote: post #82
montroser wrote: post #61

Vite had five major version in the four years 2022-2026. Version 3 => 4 => 5 => 6 => 7 => 8. Each one of those had breaking changes and required devs to go through a migration. It's too much. And for what? It's not as if it is dramatically better now than it was in version 3. I can't say I would really look forward to bringing this level of needless churn and constant disruption to the rest of my development toolchai…

I went from 4 to 8 in a single step. I had to change 5 lines of config. Can we please stop the incessant belly-aching over problems that don't exist. I have to question if you even use these tools?

I'm glad that your trivial migration was trivial.

All this was a big source of churn for plugins and frameworks: https://github.com/vitejs/vite/discussions/16358

Re: Vite+ Beta

#150

Post by [deleted] »

CrimsonRain wrote: post #142
christophilus wrote: post #127

Earlier quoted context omitted.

Honestly, I hate that Bun is vibe-coded and seems amateurish in many ways, but it’s still an excellent tool.

so instead of looking at the result, you are complaining about (a minor aspect of) the process. Jarred is an excellent engineer. He'll deliver.

[deleted]
Post reply on HN