Live data from Hacker News

Vite+ Beta

voidzero.dev

111–120 of 163 posts

Re: Vite+ Beta

#111
post #94

I think they should find a better name for this project. I find it very confusing since it's not really a better Vite. At the time Void Zero was probably looking to monetize the Vite brand but now that they've been acquired by Cloudflare they don't need to do that anymore.

> I think they should find a better name for this project.

Need another plus? Vite++

Re: Vite+ Beta

#112

Earlier quoted context omitted.

Surprised to see this is the only uv reference in the comments! Feels like an obvious comparison to me, and a very welcome development for the JS ecosystem. uv made me actually _enjoy_ working in Python again.

a single tool was the enabler of enjoyment? It seems enjoyment is a fleeting thing these days if that's the case

uv removes all the pain from python packaging. and if you ever used it for anything more than one off scripts you know it used to be a lot of pain.

manually activating venv, inconsistent python and dep versions, duplicate files taking up space, slow and broken tools, fragmented configs, global state, all of that is gone now. if you never experienced it you have no idea how bad it was.

not all of it was uv specifically (pyproject.toml was a proposal for some time before) but they cleaned it up. its the only reason i even think about python as an option for new projects.

Re: Vite+ Beta

#113
post #94

I think they should find a better name for this project. I find it very confusing since it's not really a better Vite. At the time Void Zero was probably looking to monetize the Vite brand but now that they've been acquired by Cloudflare they don't need to do that anymore.

Its vite... plus a bunch of stuff. Plus can mean different things

Re: Vite+ Beta

#114

Earlier quoted context omitted.

This makes absolutely zero sense. If you're going to post cynically, at least try to have some sort of coherent point?

Tooling instability creates the demand for more tooling.

The major change through all of those was solidifying Vite's concepts of "environments" for better SSR support. If you weren't using that, there wasn't much instability.

Surely lacking features also creates demand for more tooling.

Re: Vite+ Beta

#116
post #97

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?

Say this again when you have worked with Jest, one of the worst and slowest pieces of software I've ever worked with.

Re: Vite+ Beta

#117
post #90

Earlier quoted context omitted.

I was excited about Oxfmt until I tried it and found that it's mostly intended to be a Prettier replacement. Ugh.

I'm curious to know what you were hoping for. Are there features you're looking for in a formatter that prettier/oxfmt don't offer?

I was hoping for something more flexible. I suppose the whole point of Prettier is that it's not flexible but I find 90% of the times the code is actually uglier when using it.

Re: Vite+ Beta

#118

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.

Fear not, engineer! Recently some smart folks invented something called BackRub that’ll soon solve all your problems! Soon you’ll be able to find information in even less than time than it takes you to type a comment and out yourself as clueless!

Re: Vite+ Beta

#119
post #98

Earlier quoted context omitted.

This is the latest emerging "boring but works" stack.

"Latest emerging boring but works" sounds like an oxymoron.

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

Re: Vite+ Beta

#120
post #77

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'm currently experimenting with a stack combining assistance, ASP.NET Razor Pages, and htmx, specifically to avoid dealing with the complexities of the modern frontend stack. AI eliminates a lot of the tedium, grinding tasks, while HTML partials and htmx complement each other perfectly. Not having to manage frontend framework, SSR states is incredibly liberating. Sprinkle in some vanillla js and redraw specific part…

Are you open to opportunities?
Post reply on HN