Lexy 🦕

AI skills repositories are like documentation but worse, full of bullshit ("you are an expert in X, Y, Z..."), just so an algorithm can roleplay with you without having to read documentation, because oh gosh reading documentation is soooooo hard (sarcasm)

So now #bitwarden is enshittifying… Great. I’ve been on a self hosted instance since forever, but if (and when) they pull the plug in their clients on self hosting, that’ll be fun
https://blog.ppb1701.com/the-quiet-renovation-at-bitwarden

I missed it when it was published, apparently gitlab is trying to speed run destroying their product

They’re going full on AI, agents and all that kind of things
I’m glad I set up my own forge with forgejo, instead of using a public gitlab instance or hosting one

Next to go will be GitHub, though for some of my projects replacing the CI will be hard ; I’ve already started moving projects to my own forge, and removing them from GitHub, so the movement has started!

https://about.gitlab.com/blog/gitlab-act-2/

I'm conflicted about how I should implement UTF8 support for strings in my language, #ArkScript

There seem to be two options:
1. Every string is UTF8, thus every access to a char is O(n) and not O(1) anymore (have to decode the codepoints to count them). Length is O(n) too. That pretty much pessimizes all strings, even ASCII ones, but makes working with UTF8 codepoints easier
2. Every string is just a series of bytes, as it is right now, and a (@ string index) returns a potentially invalid character (on 8 bits). Indexing and length are O(1), but we need a function to get the codepoints, like (string:codepoints str) or (string:graphemes str) or something else
3. third hidden option that I want to avoid and that doesn't really count: introduce another string type that's different from normal strings. That's bad because the C++ API will be impacted, and the internals will need to handle all the different string types

At first, I thought option 1 was better because then everything is easy, since the language is high-level. But now I lean toward option 2 because UTF8 support won't hinder the performance of programs that don't need it, and doing such a thing should be intentional

#pldev

Well, #Ubuntu goes down the drain for me (actually, I already had years ago)

They want to add AI and other bullshit machine stuff…

https://www.phoronix.com/news/Ubuntu-AI-Features-2026