Live data from Hacker News

Configuring My Machines with Bashtard

tyil.nl

21–30 of 59 posts

Re: Configuring My Machines with Bashtard

#21

Earlier quoted context omitted.

Why does it need explaining. Even if it was a play on retard I think it's really none of your business what someone calls their thing. The kneejerk response here to be "you have change its name" is so damn entitled.

It needs to be explained that it's not using ableist language, meaning that every time it's shared a discussion like this one will take place, regardless of what you think about it.

> It needs to be explained that it's not using ableist language

Why? This doesn't logically follow to the author renaming their thing unless you think speech policing on the internet is some kind of valid passtime or has any weight on anything in the real world.

> meaning that every time it's shared a discussion like this one will take place

So it's a good PR move because the PC police can't figure out that just maybe every corner doesn't have a nazi around it and maybe it's just a play on bastard?

Re: Configuring My Machines with Bashtard

#22
Author should have stuck with ansible a bit longer.

It can stream shell commands so you've got all the usual sed awk etc

And has a battle tested OS detection logic built in.

>This value is correct for Debian and derivatives, but not for my Gentoo or FreeBSD systems, so I’ve created OS-specific configuration files for these.

And can copy in different templates depending on OS.

Hell it can even detect whether its in a KVM or LXC or metal environment with right helpers and same for architecture so very useful for building a script that works in a very mixed environment

Still to each their own. I occasionally feel the need to reinvent a specific wheel too.

Re: Configuring My Machines with Bashtard

#23

Regarding the "I wrote it in bash so it doesn't add a dependency". I've been thinking recently that it might make a lot of sense for these kind of tools to be written in a compile-to-native language (e.g. Go or Rust), and embed a lightweight scripting engine (for example quickjs or luajit). That way they could write everything in a much nicer language and still not require a dependency. For such simple scripts the re…

The problem with Lua at least is that in order to do anything remotely useful you will have to pull in a bunch of 3rd party libs from luarocks or somewhere. There's basically nothing in the stdlib at all except primitive functions to build on. At least with bash the host system _is the stdlib_. And you can usually rely on that.

Re: Configuring My Machines with Bashtard

#24

Earlier quoted context omitted.

It needs to be explained that it's not using ableist language, meaning that every time it's shared a discussion like this one will take place, regardless of what you think about it.

> It needs to be explained that it's not using ableist language Why? This doesn't logically follow to the author renaming their thing unless you think speech policing on the internet is some kind of valid passtime or has any weight on anything in the real world. > meaning that every time it's shared a discussion like this one will take place So it's a good PR move because the PC police can't figure out that just mayb…

The author can do what they want, but if they care what associations people have about the name and they didn't consider this, they now have new information.

Re: Configuring My Machines with Bashtard

#25
post #22

Author should have stuck with ansible a bit longer. It can stream shell commands so you've got all the usual sed awk etc And has a battle tested OS detection logic built in. >This value is correct for Debian and derivatives, but not for my Gentoo or FreeBSD systems, so I’ve created OS-specific configuration files for these. And can copy in different templates depending on OS. Hell it can even detect whether its in a…

I didn't look too closely at this but Ansible offers a number of guarantees such as idempotency, locking, etc. If this thing is just people wrapping their shell scripts in on of the functions this thing executes then it's automatically worse than just using Ansible. Because nobody is going to care to make their script...good.

Re: Configuring My Machines with Bashtard

#26
post #2

That name is problematic as it's too close to an abelist slur. You should change it to something like Bashfig, Bashful, etc. to be more inclusive.

Oh, come on. It’s a lot, lot closer to bastard than retard or tard. At some point people have to own their own misperceptions.

Well, it seems to be about 50-50 in this thread alone whether it was "bastard" or "bash tard".

> At some point people have to own their own misperceptions.

I don't have to own shit. I didn't name it.

Re: Configuring My Machines with Bashtard

#27
post #22

Author should have stuck with ansible a bit longer. It can stream shell commands so you've got all the usual sed awk etc And has a battle tested OS detection logic built in. >This value is correct for Debian and derivatives, but not for my Gentoo or FreeBSD systems, so I’ve created OS-specific configuration files for these. And can copy in different templates depending on OS. Hell it can even detect whether its in a…

I didn't look too closely at this but Ansible offers a number of guarantees such as idempotency, locking, etc. If this thing is just people wrapping their shell scripts in on of the functions this thing executes then it's automatically worse than just using Ansible. Because nobody is going to care to make their script...good.

my experience with ansible is that it offers a suggestion of idempotency, but there's always plenty of room to ignore the best practices.

IMHO it's better to have no guarantee than a vague suggestion that you might tend to rely on but then be bitten because there's nothing actually enforcing the guarantee.

Re: Configuring My Machines with Bashtard

#28
post #5

Earlier quoted context omitted.

As an actual living bastard, I endorse the name. So. There.

I'm all for funny names, but giving your project a needlessly inflammatory name, to me signals that the author doesn't have an interest in working with the greater open-source community to develop it further or adopt it.

> signals that the author doesn't have an interest in working with the greater open-source community to develop it further or adopt it.

This reminds me, there's a somewhat inherent affiliation in the flamewar over the branch name master/main.

The people who use "master" clearly don't think it's a bad term to use, and probably think being upset over it is silly. Those who use "main" either think it's (to some extent) racist to use the word master, or don't want to be yelled at.

Whichever word you chose ultimately signals affiliation, and the other group will feel you don't recognise their frustration. -- I think the sensible people just ignore it.

Rather.. I think if you want to have a community where people with different cultural attitudes feel welcome, I think some toe-stepping is inevitable and unavoidable.

Re: Configuring My Machines with Bashtard

#29

Earlier quoted context omitted.

I didn't look too closely at this but Ansible offers a number of guarantees such as idempotency, locking, etc. If this thing is just people wrapping their shell scripts in on of the functions this thing executes then it's automatically worse than just using Ansible. Because nobody is going to care to make their script...good.

my experience with ansible is that it offers a suggestion of idempotency, but there's always plenty of room to ignore the best practices. IMHO it's better to have no guarantee than a vague suggestion that you might tend to rely on but then be bitten because there's nothing actually enforcing the guarantee.

I'm pretty sure that all of Ansible's core builtins guarantee idempotency

Re: Configuring My Machines with Bashtard

#30

Neat concept, cringe inducing name. Could have called it "Baby Got Bash"

Yeah, I was really hoping it was supposed to be pronounced like (and a play on) "bastard", but it seems like it's intended to be a mashing together of "bash" and "retard", which... oof. Maybe I misinterpreted the small note on the pronunciation, though. If so, I'd suggest the author further clarify.
Post reply on HN