new | show | ask | jobs Github

coldtea 4 hours ago

>Can't we just go back to node + npm + vitest + vite?

The mere enumeration shows how bad it is.

▲

mnahkies 4 hours ago | parent | next [-]

I think it's a pretty reasonable split of responsibilities, and not uncommon.

Eg: JDK + maven + junit + tomcat

Making these components pluggable is arguably how we get innovation (eg: yarn/pnpm, jest/vitest, etc)

	▲	all2 an hour ago \| parent [-]
		Is this the old monolith vs micro-services argument? I guess this boils down to 'how granular and function specific are your building blocks?' and where you draw the lines programmatically: library interfaces in a single program/executable, API/ABI between two or more programs/executables, HTTP API/other transport protocol across network boundaries between two or more programs/executables, and so on. I'm not sure I'm slicing this along the correct abstractions, though.

▲

tavavex 2 hours ago | parent | prev | next [-]

Why? Is fewer things always better? How far should it be consolidated? Taking it to an extreme, would having a tool named Everything that does anything you could imagine in relation to web dev be better?

▲

arendtio an hour ago | parent | prev [-]

Well, do one thing an one thing good as in Unix philosophy?

- Runtime

- Package manager

- Test runner

- Build tool