Yo momma’s so fat she compresses everything she steps on to its Kolmogorov complexity.

It’s performative self-flagellation, same as you would do in any religious event or office setting. The pink dildo is just for better visibility.

Half of what the LLM did was basically:

git clone https://github.com/servo/servo.git
# todo mess up the code until it no longer compiles

Where are my millions?

-u would give you the space back.
The ransomware doesn’t. There is a block of data, sitting there, taunting you.

Hebrew-based content appears machine-translated

Did they vibe code their false identity as well?

Spectre, because it forces us to acknowledge the abstractions we build upon.

2Gb well spent

You would need to filter by direction, that way it could only be spoofed by aircraft or another satellite. Sadly the only way to archive that, while going through the atmosphere would be with near visible light.
Besides needing a clear night sky and being a danger to everyones eyes, I don’t think having lasers pointing up is very stealthy either.

Because you can stack rectangles into bigger rectangles, can’t really do that with hexagons.

While your partner can’t be found by it, they can be approximated to an arbitrary degree of precision.

The idea with metastatic is, that you can just put a repeater and battery in a box, stick a small solar panel on it and put it somewhere outside.
If it’s found you are losing around 50$ instead of your freedom, as long as you left no evidence it’s yours.

Lure the bugs to your screen and catch them or let them hide in the shade. That’s the choice.

Memory-safe since decades.

It’s just reference counting with some common sense optimisations. From the website I can’t quite make out wether they disallow cyclic data structures or just leek them, but I’m guessing it’s the latter.

Also the only thing worse than one-indexed arrays (the default) is allowing user defined array start.

I feel embarrased to admit that I had been totally unaware of Seed7 until mere two months ago.

Don’t be, there are so many out there, no need to be embarrassed for not knowing a language that prides itself on lot having fortran style line length limit.
After slogging through vhdl, I personally will not voluntarily use a language that forces me to write out stuff like

      end if;
    end for;
  end func;

when three } would work just as well.
Similar deal with

const proc: main is func
  local
    # local variables go here 
  begin
    # finally, the actual code can begin

where proc means func void so essentially const func void main is func begin. Just default to const, remove the redundant funcs and allow locals to go where they are used, not all up front, even when they are only used in one branch.

I came up with a kind of clever data type for storing short strings in a fixed size struct so they can be stored on the stack or inline without any allocations.

C++ already does that for short strings while seamlessly switching to allocation for long strings.

It’s always null-terminated so it can be passed directly as a C-style string, but it also stores the string length without using any additional data (Getting the length would normally have to iterate to find the end).

Also the case in the standard library

The trick is to store the number of unused bytes in the last character of the buffer. When the string is full, there are 0 unused bytes and the size byte overlaps the null terminator.

Iirc, that trick was used in one implementation but discontinued because it was against the standard.

(Only works for strings < 256 chars excluding null byte)

If you need a niche for allocated string you can get to 254 but the typical choice seem to be around 16.

The default configuration in 2017 was public write access, but those databases where taken over long ago.

Where is the source code?
You can’t make any claims about privacy without it.

Rust doesn’t have a scheduler.
The issue is the false assumption, that the remove operation can safely be done without taking a lock. This can be done in some specific data structures using atomic operations, but here the solution was to just take the lock. The same thing could have happened in a C code base but without the unsafe block indicating where to look for the bug.

The commenter must believe forks are magic.

and like half the [rust] devs left for Crab.

Crablang is a joke fork to make fun of a trademark screw up by the rust foundation.

Exactly, you never know when you want to change the base for printing out from under someone.

What unholy mix of languages is that? It is dominated by a blend of javascript and python, but with notes of something exotic. Maybe algol? or vhdl?, there is to little to tell.
Impressive, someone write up a spec and publish it to the esolang wiki.