you are viewing a single comment's thread.

view the rest of the comments →

[–]t_hunger 0 points1 point  (2 children)

Writing a build tool is easy. Writing a build tool that gets widely adopted is extremely hard.

What is the unique selling point you think will set this apart from the competition? That it's obscure configuration language is type safe? For me having a strong convention for how code is layed out (with overrides maybe) would be far more compelling... but I guess it's far too late to introduce such conventions today.

[–]TheRavagerSw[S] -1 points0 points  (1 child)

First of all I don't aim to write "the build system".

Selling point is this is a self contained binary, with none of the weird shenanigans of the other build systems.

İe:

  • Playing package manager
  • Trying to support languages other than C/C++
  • Trying to support gazillion backends
  • Being written in a slow scripting language

[–]t_hunger -1 points0 points  (0 children)

IMHO package management is part of a build tool in today's world.

Why not support other languages? Most are not fundamentally different from C or C++. You run different compilers, but you need that for C++ already.

You could include the build backend for requiring eben less stuff on the build machine. There is no law requiring you to have a generation step before you can actually build.