Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)BA
Posts
3
Comments
164
Joined
2 yr. ago

  • It’s the 21st century. Many of us are educated enough and have a strong enough image of what a country is. Any country may try to annex any land, but they’ll almost always face resistance. Even in the event of a full annexation, you can’t stop the people from revolting, essentially making your country look as miserable as possible to everyone. Heck, even the full cleansing of an entire population won’t guarantee you’ll reach long-lasting stability on annexed lands; people will hide, repopulate, teach their descendants about their past and forever torture your nation and its people, however horrifying of a worldview it may sound like.

    I remember reading somewhere that some department in the US gov have a paper on their inability to annex or even control foreign lands and their people. Essentially, it doesn’t matter if the USA has the most powerful military in the history of humanity; it cannot conquer the minds of people today, and will suffer from instability for a very long time.

  • You come from a healthy background is what I’m hearing. And that’s good, and I don’t mean that in a derogatory way. What you have there is absolutely the right mindset to have. These tools are made by humans, who have their own set of problems they want to solve with their tools. It may not be the best tool, but it can work pretty damn well.

    However, it’s also not uncommon to see communities rage and fight over the superiority of their tools, if not just to shun those that they think are inferior. It’s a blatantly childish or tribalistic behaviour, depending on how you look at humanity. And you’ll see this outside of programming too; in the office, in town, on the streets. People engage in this behaviour so that they can show that “I am on your side”, for the side where they think is the right or superior side, based on factors like a perception of group size, a perception of power, a perception of closeness. It appeals to a common human desire to belong to a strong group. It appeals to the human desire to feel safe. And when you start looking at it that way, that’s not too different from how animals behave. It’s important to note that not all humans have the same amount of desire for this sort of tribe, or would give into that desire to engage in such behaviours, but it’s not surprising to see.

    In any case, this article is essentially a callout to the sort of toxic behaviour done for the sake of feeling superior, that exists within the programming community, to a point where some may even say is a major subculture.

  • This. Any time someone’s tries to tell me that AGI will come in the next 5 years given what we’ve seen, I roll my eyes. I don’t see a pathway where LLMs become what’s needed for AGI. It may be a part of it, but it would be non-critical at best. If you can’t reduce hallucinations down to being virtually indistinguishable from misunderstanding a sentence due to vagueness, it’s useless for AGI.

    Our distance from true AGI (not some goalpost moved by corporate interests) has not significantly moved from before LLMs became a thing, in my very harsh opinion, bar the knowledge and research being done by those who are actually working towards AGI. Just like how we’ve always thought AI would come one day, maybe soon, before 2020, it’s no different now. LLMs alone barely closes that gap. It gives us that illusion at best.

  • Is there anyone here who’s familiar with the paper(s) mentioned in the article? I’d actually like to read them, so if you do, it’d be great if you could share it with me. I couldn’t really find it in the article, unless it’s just hidden under one of their links.

    I found the following paper with the authors mentioned:

    https://arxiv.org/abs/2501.11582

    But not sure if that’s it. It does have some semblance to the topic though. My search-fu isn’t really doing me great with just author names though.

  • Most of us can’t help but feel powerless while trying to change the world. That’s normal, because the reality is, no one can change the world as quickly as we can make a turn at the next junction. Not Donald Trump, not Elon Musk, not Vladimir Putin, not Xi JinPing. They’ve spent decades getting to where they are today, but the best they can do is do big strokes to sway the world to some extent. And these people just look so lonely; nobody seems to really understand them, neither do they seem to truly understand people, aside from knowing enough to take advantage of them, and they put up some sort of distance between themselves and others, distance in various ways you can measure. Meanwhile, most of us spend our times to be close to those we love and care, trying to be a part of a larger society in a healthy and responsible way.

    If the alternative is to give up and watch this beautiful world burn and die, watch wonderful people suffer and I turn a blind eye to their pain, I would rather continue trying, and one day die knowing that I tried, instead of regretting alone.

  • The world? Or just many world governments that have the power to do so? There are many people out there doing what they can to dissuade governments from supporting the genocide, and they make up a fair size of “society”. Do you no longer care about them then?

    You care. You’re just tired of seeing that nothing’s changed despite people’s efforts. But that’s totally okay. Great powers don’t and won’t immediately change to what we desire it to be, and there is a vested interest for some to keep the status quo, so it’s hard. We get it, and so do you.

    Go take a rest.

  • Knowing how these people behave, it’s “rules for thee, not for me”, and “yes that’s true but every woman should follow, but I’ll continue to say whatever the fuck I want anyways”. Cognitive dissonance on the surface level does not stop them. It’s always been a “I will say whatever the fuck I want and hide behind some pretty words, and all I have to do is to ignore your criticisms. You can’t touch me.”

  • I understand that. I have coworkers with about 15-20 years in the industry, and they frown whenever I put a bash script out for, say, a purpose that I put in my example: self-contained, clearly defined boundaries, simple, and not mission critical despite handling production data, typically done in less than 100 lines of bash with generous spacing and comments. So I got curious, since I don’t feel like I’ve ever gotten a satisfactory answer.

    Thank you for sharing your opinion!

  • I’ve never had that impression, and I know that even large enterprises have Bash scripts essentially supporting a lot of the work of a lot of their employees. But there are also many very loud voices that seems to like screaming that you shouldn’t use Bash almost at all.

    You can take a look at the other comments to see how some are entirely turned off by even the idea of using bash, and there aren’t just a few of them.

  • Good point. It’s definitely something to keep in mind about. It’s pretty standard procedure to secure your environments and servers, wherever arbitrary code can be ran, lest they become grounds for malicious actors to use your resources for their own gains.

    What could be a non-secure environment where you can run Bash be like? A server with an SSH port exposed to the Internet with just password authentication is one I can think of. Are there any others?

  • Creature comfort is a thing. You’re used to it. Familiarity. You know how something behaves when you interact with it. You feel… safe. Fuck that thing that I haven’t ever seen and don’t yet understand. I don’t wanna be there.

    People who don’t just soak in that are said to be, maybe, adventurous?

    It can also be a “Well, we’ve seen what can work. It ain’t perfect, but it’s pretty good. Now, is there something better we can do?”

  • I’m going to downvote your comment based on that first quote reply, because I think that’s an extreme take that’s unwarranted. You’ve essentially dissed people who use it for CI/CD and suggested that their pipeline is not robust because of their choice of using Bash at all.

    And judging by your second comment, I can see that you have very strong opinions against bash for reasons that I don’t find convincing, other than what seems to me like irrational hatred from being rather uninformed. It’s fine being uninformed, but I suggest you tame your opinions and expectations with that.

    About shared libraries, many popular languages, Python being a pretty good example, do rely on these to get performance that would be really hard to get from their own interpreters / compilers, or if re-implementing it in the language would be pretty pointless given the existence of a shared library, which would be much better scrutinized, is audited, and is battle-tested. libcrypto is one example. Pandas depends on NumPy, which depends on, I believe, libblas and liblapack, both written in C, and I think one if not both of these offer a cli to get answers as well. libssh is depended upon by many programming languages with an ssh library (though there are also people who choose to implement their own libssh in their language of choice). Any vulnerabilities found in these shared libraries would affect all libraries that depend on them, regardless of the programming language you use.

    If production only implies systems in a user’s path and not anything else about production data, then sure, my example is not production. That said though, I wouldn’t use bash for anything that’s in a user’s path. Those need to stay around, possible change frequently, and not go down. Bash is not your language for that and that’s fine. You’re attacking a strawman that you’ve constructed here though.

    If your temporary small script morphs into a monster and you’re still using bash, bash isn’t at fault. You and your team are. You’ve all failed to anticipate that change and misunderstood the “temporary” nature of your script, and allowed your “temporary thing” to become permanent. That’s a management issue, not a language choice. You’ve moved that goalpost and failed to change your strategy to hit that goal.

    You could use Deno, but then my point stands. You have to write a function to handle the case where an env var isn’t provided, that’s boilerplate. You have to get a library for, say, accessing contents in Azure or AWS, set that up, figure out how that api works, etc, while you could already do that with the awscli and probably already did it to check if you could get what you want. What’s the syntax for mkdir? What’s it for mkdir -p? What about other options? If you already use the terminal frequently, some of these are your basic bread and butter and you know them probably by heart. Unless you start doing that with Deno, you won’t reach the level of familiarity you can get with the shell (whichever shell you use ofc).

    And many argue against bash with regards to error handling. You don’t always need something that proper language has. You don’t always need to handle every possible error state differently, assuming you have multiple. Did it fail? Can you tolerate that failure? Yup? Good. No? Can you do something else to get what you want or make it tolerable? Yes? Good. No? Maybe you don’t want to use bash then.

  • But not everything needs to scale, at least, if you don’t buy into the doctrine that everything has to be designed and written to live forever. If robust, scalable solutions is the nature of your work and there’s nothing else that can exist, then yeah, Bash likely have no place in that world. If you need any kind of handling more complicated than just getting an error and doing something else, then Bash is not it.

    Just because Bash isn’t designed for something you want to do, doesn’t mean it sucks. It’s just not the right tool. Just because you don’t practice law, doesn’t mean you suck; you just don’t do law. You can say that you suck at law though.

  • People have really been singing praises of Powershell huh. I should give that a try some time.

    But yeah, we wield tools that each come with their own risks and caveats, and none of them are perfect for everything, but some are easier (including writing it and addressing fallovers for it) to use in certain situations than others.

    It’s just hard to tell if people’s fear/disdain/disgust/insert-negative-reaction towards bash is rational or more… tribal, and why I decided to ask. It’s hard to shake away the feeling of “this shouldn’t just be me, right?”

  • Seems like something that can happen in any languages, though yeah, bash doesn’t make it easier, and it’ll depend on what the cli tool would return given the error (eg does it return some code in stdout or stderr, or some non-zero exit code). Depending on the library (in the language of choice), you may still have to handle such errors manually, eg adding the necessary logic to retry.

    And in such a case, I guess it would be prudent to either make sure that the data can be retrieved again, or push it somewhere a bit more permanent (shared fs, or object storage), sort of in a dead-letter-esque style. Seems like the lesson here is to have a fall over plan. The failure mode is not something a proper language and library would necessarily help discover more easily though.