CIRCLE WITH A DOT

@0xabad1dea Give it time and they'll get it to nine fives.

@simontatham I've sadly had to delete the bookmarks and history entries for your puzzle collection because that was always something I'd pull up when I was "microbored" without even thinking, and now that's 2–5 minutes wasted.

@cstross @bjn MacOS quality was definitely higher during the Jobs era than before or after.

RE: https://cyberplace.social/@GossiTheDog/116228686072308466

The first highly-visible example of FAFO when it comes to cutting corners with AI has landed:

@cstross If they could also stop with shoving the constant tin-rattling from their cloud services into everything, that'd be wonderful.

I'm a software developer and sysadmin who could really use being #fedihired.

What I'd really like to do is Rust, but once you ignore the dubious crypto and AI stuff, there seems to be nothing out there. Prove me wrong with a counterexample!

I've spent decades fixing Enterprise mudballs mostly written in #Perl. If you've got a crufty legacy system that everybody else is too scared to touch, I'm your man. I love fixing stuff like that.

I've also done commercial #Scala, #Python, #C/#C++, and although I don't usually admit it on my CV but these are now Trying Times when everything is on the table, even #PHP (the longest six months of my life).

Perl naturally leads into Unix system administration and infrastructure. I've built and maintained mail clusters, VoIP systems, network monitoring, DNS management platforms, that sort of thing. If it's non-sexy but something which needs to be done, I'm there.

Available immediately, for contract or permie, onsite in Amsterdam/Randstad or remote to anywhere.

Drop me a private mention or mail peter@mooli.net if you have or know of something.

@arichtman @fasterthanlime In my own hypothetical Rust replacement which I don't expect to write any time soon, I would definitely be stealing quite hard from Scala. Other things: square brackets for trait parameters so we don't get weird parses from angle brackets and generally improving ergonomics, it basically having stable fn_traits so a collection or other container type can just be called directly to perform a lookup without the noise of .get or whatever, implicit parameters so some common parameter (e.g. a database handle) can bubble through the call stack without explicitly adding it to every function call, and perhaps its dependent functions/methods. But those are another three things…

@arichtman @fasterthanlime It's not quite the same thing because the languages approach traits and the problems solved by traits differently, but Scala handles this by (massive handwave over the details) giving the implementations a name, which has to be imported by the code which uses it. That way there doesn't need to be One True Implementation which limits where it can be defined. The flip side is that it needs to be imported by all library users and isn't automatically available, but since Scala code tends to wildcard-import from libraries, this is not particularly onerous.

@fasterthanlime How has nobody else mentioned the orphan rule yet?