Everytime I see a language creating their own package system, all I can think of it how much we've missed here.

The only exception is C/C++, where there is none established that well, for good or bad.

These choices may create later super-convoluted processes when you have to mix more than one language together.

Packaging systems makes thing easy, but complicate further the line if another language needs to be used.

afdbcreid 5 hours ago | parent | next [-]

What do you think we've missed? Do you want one build systems for all languages? There are such systems (e.g. Bazel) and they're often used for multi-languages projects, but I think reality has proven that build systems with language-specific knowledge are much easier to navigate.

	▲	__float 2 hours ago \| parent [-]
		I'm not sure how outlandish we're allowed to get here, but IMO we have a fundamental mismatch between application <> operating system <> CPU in terms of dependencies and trust. Fixing this is beyond any one tool, of course :)

▲

small_model 3 hours ago | parent | prev | next [-]

C should have fixed its various issues and added a package manager (or blessed one), Zig is filling that gap.

▲

forrestthewoods 6 hours ago | parent | prev [-]

The world has yet to standardize on a good crossplatform polyglot build system.

The only real such build systems are Buck and Bazel. But they have way too much baggage from their overlords.

It’s a shame.

	▲	himata4113 5 hours ago \| parent \| next [-]
		build systems using llvm as the backend are getting there, but zig is making their own compiler too.
	▲	arikrahman 5 hours ago \| parent \| prev [-]
		Zig is pretty good for my use case. It may not be fully pollyglot at a technical level, but I can use it for my embedded C use case, for Jank to export the .cpp to other platforms, and thereby Clojure.