this post was submitted on 25 Jun 2024
27 points (84.6% liked)

Linux

5234 readers
105 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
top 14 comments
sorted by: hot top controversial new old
[–] thesmokingman@programming.dev 7 points 4 months ago (2 children)

The only feature that vanilla Make doesn’t have over this is solid Windows support.

I’ve evaluated a ton of these tools for CI/CD processes and common task management. So far I have found that Make is the best solution for task management unless you need strong Windows support. If you want to go crazy, you can use Autotools but that’s really only for builds not tasks. I get it; it’s cool to reinvent the wheel with a new feature that makes one thing a little bit easier.

[–] nemith@programming.dev 1 points 4 months ago

I agree. The only one that was close for me is Just. It is just Makefiles but without all the baggage.

[–] Ephera@lemmy.ml 1 points 4 months ago

I mean, I doubt the Windows support is particularly solid here either. Using shell commands to formulate tasks will never be great for Windows, because the shell ecosystem is simply Linux.

[–] boredsquirrel@slrpnk.net 5 points 4 months ago* (last edited 4 months ago) (2 children)

What about just, written in Rust?

That is already used in many projects.

[–] sxan@midwest.social 4 points 4 months ago

Because it's written in Rust.

Seriously, though; there are a dozen widely used make systems, most of which are more widely used than just. People have ideas and think they can improve. As far as it goes, having a bunch of different make options is one of the least annoying areas; diversity is mostly hidden from end users, and you only really have to learn it if you plan on becoming a contributor.

However, if you're asking for a comparison table, a "why is this better than make, or ant, or maven, or cmake, or ninja, or just, or rake," then yeah, I agree. Having a brief elevator pitch is appreciated.

[–] Ephera@lemmy.ml 3 points 4 months ago

Your comment is perhaps a bit confusing without a link: https://just.systems/man/en/

[–] aport@programming.dev 5 points 4 months ago (1 children)
[–] ChapulinColorado@lemmy.world 9 points 4 months ago (2 children)

As someone that uses both Java and k8s at work. I’ll take yaml over xml any day of the week. Maven build files are like 50% useless fluff.

[–] Ephera@lemmy.ml 7 points 4 months ago (1 children)

There's not exactly a dichotomy there...

[–] ChapulinColorado@lemmy.world 1 points 4 months ago* (last edited 4 months ago)

Just saying, it could be worse and some of us don’t mind yaml ;)

[–] amanda@aggregatet.org 4 points 4 months ago

It’s also a lot better than doing it in 100% C++ templates!

[–] randomperson@lemmy.today 5 points 4 months ago (1 children)

There's mage which lets you write tasks in go instead of yaml.

[–] z3r0_Geek@lemmy.zip 1 points 4 months ago

I know someone that will find this interesting.

Thanks!

[–] Blaze@lemmy.zip 1 points 4 months ago