gpderetta

> This is the country that voted to name a research vessel Boaty McBoatFace

And "Killing in the Name" as Christmas song of '09, to spite the usual X-factor shoo-in.

There is a chance that more entertainment is yet to come from Clacton.

It is really the second coming of Excel. And it is a good thing (probably?)

They are just token generators. It is just that 'just' does a lot of lifting!

humanity has been producing useful things from bacteria for thousands of things already.

always was. Still is.

that per-se doesn't mean you are bound by it.

For what is worth, a few years ago, I was able to chargeback a significant furniture order after the company collapsed. It is indeed at the bank's discretion and my bank didn't really advertise the process, but the people in branch pointed me to the right place and the process was no fuss.

So, no, you do not have the same legal protection as Section 75, but it is always worth a try.

froh: your reply was flagged for some reason! I tried to vouch it but it wasn't enough.

x86 32 bit protected mode segments were a very different beast.

You are right of course. But I expect that valve will come up with proton-on-arm with x86 translation very soon (in fact possibly next week-ish when they release the frame).

That's basically a AOS/SOA transformation (then packing the boolean valued array). You can have extremely cheap proxies in C++ so it is not much of an issue. The problem is that this proxy-optional wouldn't immediately interoperate with std::optional, but could interoperate with any generic code taking an optional-like value.

As the government wants to encourage people to be invested and not hold cash, from '27 you'll only be able to add 12k in Cash ISA. They are planning to also change the limit on cash held on S&S ISAs to avoid an easy workaround for this limit

Well, yes, but after maximizing an ISA that's still an option. Also the government is clamping down on cash ISA.

Nice, but the view keeps clipping out to far ahead of the map (but the character seems to still be in its original position as I can die from monsters). It snaps back in place when I shoot.

edit: both on chromium and firefox, desktop linux.

they literally are not.

great coders ship.

I'm often amazed how things do not break more often than they do[1] given how deep a package can alter emacs intenrals.

[1] and they do break!

No, I think that ̶w̶i̶n̶t̶e̶r̶m̶u̶t̶e̶ ̶w̶i̶l̶l̶ ̶m̶e̶r̶g̶e̶ ̶w̶i̶t̶h̶ ̶n̶e̶u̶r̶o̶m̶a̶n̶c̶e̶r̶ emacs will merge with claude instead.

[from the linked article]

> <deque>: Needs a major performance overhaul", acknowledging that the standard's mandated block size is too small and the design needs to be rebuilt at the next ABI break

Except of course the standard does not mandate a block size. That's purely msvc picking a wrong block size and being stuck with it.

The rant about lists is also nonsense.

Which sucks... unless you really need reference stability.

Don't follow dogma.

it starts despairing. Then it gets worse.

Better here is purely in evolutionary terms, i.e. would a sub- or non non-conscious life form out-compete conscious life forms in its niche.

> I'd say the case it was making has only become more relevant with the chatbot age.

Exactly. The central thesis, consciousness not being necessary for intelligence, is very relevant today.

Of course, the existential horror background in the book was also quite well done.

I'm pretty sure GCC has been ABI stable far longer that MSVC which used to break ABI every release.

GCC was forced to break the std::string ABI by the C++11 standard and they have been lobbing ever since against ABI breaks.

Making DoSomething a template because span is a template is a non-sequitur.

If DoSomething works with untyped bytes, it should require a std::span<byte> (or const byte if read only). Incidentally the standard provides a convenient as_bytes(std::span<T>)->std::span<byte>; There isn't an as convenient helper to convert a singular object to a span of bytes, but it is easy to write.

As to why one should use span, is that a) it helps making sure that the size travels together with the pointer for some additional safety, b) it is more convenient to work with byte ranges than void ptrs (which do not support pointer math), c) helps a bit communicating intent: in C++ void* are used more often for type erasure than for byte related things.

it not really an if statement here in a perceptron though. It is more akin a logic gate.

A transistor (driven to saturation) is a much better model.

What a strange argument. People eat food to survive. Petaflops are not very tasty.

> Reality has no distinction between "data" and "code"

yes, yes, ostensibly the universe is built on lisp.

But we all know that it was hacked together with a lot of perl[1].

[1] you all know the reference.

> Accidentally stumbling on a mechanism that is simple enough to be recreated with every human birth might be possible, accidentally stumbling on a mechanism that took evolution billions of years to find and which it has hung onto by copying it and has never recreated it from scratch, could be much less likely, in a much bigger search space.

Maybe, but you could make the same argument about anything artificial.