The Koru is a 416-foot masterpiece with three towering masts, each standing 230 feet tall, that harness kinetic energy to propel the vessel. The yacht is so massive that, for it to leave the shipyard after completion, a historic bridge in Rotterdam had to be dismantled. Bezos even offered to fund the dismantling and reconstruction of the 95-year-old De Hef bridge but later abandoned the plan amid public outcry. Eventually, Koru was towed away without her masts, which were later assembled.

The tone of this article is astonishing. “He even offered to pay to vandalise a historic building”, how selfless…

I use magit in Emacs in a similar sort of way. Bringing up the magit status page instantly presents a list of hunks I can browse and stage. When committing, there is also an option to “instant fixup” into an existing commit, which you can select interactively from the commit log.

Green is my pepper… If you know what I mean… 😏

I can’t imagine that’s any more free than bitwarden?

The big downside is that, for backwards compatibility, the default must still be unsafe code. Ideally this could be toggled with a compiler flag, rather than having to wrap most code in “safe” blocks (like rust, but backwards).

One potential upside that people don’t seem to be discussing is that the safe subset could also be the place to finally start cutting down the bloat of C++. We could encourage most developers to write exclusively in the safe subset, and aim to make that the “much smaller and cleaner language” trying to get out of C++.

Its just the symbol The Register uses at the end of an article. Like how some papers use a filled in square.

How bloody dare you!

Isn’t production JavaScript usually minified/obfuscated to make it hard to read?

Also wasm is actually bytecode, which I believe has a 1:1 conversion into a text-based format called wat.

I agree with your main point though, it’s kinda creepy when you realise just how much we are expected to allow other people’s code to run on our machines.