A bullshit report from commercial CI company peddling AI?!

Yes and no. It depends on how you manage symbol visibility. There is such a thing as a "private" dependency. For example:

• libA uses a patched version of libZ, and breaks ABI compat with the upstream version
• Your program links with libA and upstream libZ dynamically

If LibA links with libZ statically, and doesn't expose any internal libZ structures through its own APIs, then there's absolutely no problem. Your code will never directly interact with the internal libZ of libA.

If LibZ is exposed by LibA, or LibA dynamically links with LibZ, then you have a problem. I'm not an expert on dynamic linkers, but they're might be some platform specific workarounds you can do.

Something else I've seen before is some libraries use preprocessor macros for their namespaces. That way, you can change the namespace (and thus symbol names) at compile time. That way, you can have multiple copies of the same library coexisting, even with type safety at compile time.

He's huge on all the streaming platforms, so you can't really ignore him. Clueless people will have his content force fed to them by the algorithm, and some will end up becoming fans.

Pre-empting that by pointing out how much of a disgusting pathetic loser and worthless piece of shit he is might help someone make an informed choice before watching his content.

This the most logical solution. Python is what you (should) turn to when your Bash scripts start looking like real software. Whenever I see a (non-geriatric) developer with a giant bash script, my first assumption is that this is a junior dev who doesn't know better.

That's how I pronounce it in my head. Spanish J is pronounced with an H sound, and Spanish isn't a fake language like Esperanto.

func get_album_by_id(album_id: int16): Album -> (
  get_albums()
  | find(func (this) -> this.id == album_id)
)

I'll admit I'm not a database guy, but isn't this inefficient? It looks like it's first querying the DB for all albums, then filtering the results in the interpreter. I assume the db engine has a more optimal implementation for when you do SELECT WHERE query, designed for whatever data structures it's using internally.

Also, minor nitpick but why does it have so many different ways to define a function body?

func something() -> { ... }
func something() -> ( ... )
func something() -> ...

I don't know you, but I'll give you an example of someone I do know

• Didn't give a crap about computers throughout highschool. Didn't really know what he wanted to do in general

• Picks computer science last minute because it supposedly makes a lot of money

• Cruised through shitty community college doing the bare minimum, no side projects or any sign he's even interested

• At graduation time, he barely knows how to code. Has a github profile with some homework assignments he was forced to do

• Is part of the job market now, competing against you and me.

I don't know if he's employed as a software engineer right now, but I've worked with people who obviously fit the same profile. People who expect real work to be as simple as submitting a homework assignment last minute using shit you copy pasted from SO (or I guess ChatGPT now), and then fucking off to enjoy life while your coworkers are burdened by your incompetence.

This is a field where actually giving a shit is a requirement.

I don't agree with OSI either, and think their licenses are exploitative. But their definition is useful to call out orgs like FUTO.

The solution to devs being exploited by big tech is the GPL or AGPL, not whatever FUTO is doing. They're trying to have their cake and eat it too: earn the goodwill that comes from claiming you're open source, while keeping the same restrictions in place you'd see in a commercial software package, which keep users locked down to one vendor (aka "free beer" rather than "freedom")

This isn't a new idea invented by FUTO, it's called "source available". Gitlab is another example of this, as is Unreal Engine, and many others.

Not being the language for programming beginners and data scientists, probably aides that impression, though…

I think it was that back when it was relevant (but replace data scientists with web devs)

I never got interested in the ecosystem myself, but I've run into it every now and then. I feel like it's in the same place as PHP today: still used a lot for legacy reasons, but you'll get weird looks if you start a new project with it and you're under the age of 40

Wow I always assumed the same thing lol

Off topic, but is there a name for that grin/facial expression? It's like technically a grin, yet devoid of any real emotion. Feels like it's trying to not commit too much into an emotion, maybe even for calculated social engineering reasons. I see it in the Godot logo as well.

In my head, I've taken to calling it "the autistic stare" due to the confused/vague communication of an emotion, but idk if that's offensive.

being inserted automatically.

Aka the entire point of RAII