agrover

This seems to be the growing consensus.

https://en.wikipedia.org/wiki/Inetd came out in 1978, if we're keeping score.

It's not a remake, it's based on the original source code.

> It's not like Toys 'R' Us stores disappearing in 2018. That happened because big-box toy stores were simply no longer viable as a category.

I thought getting bought and pillaged by private equity was the reason.

YES actually, Red Hat bought Cygnus a long time ago, and formerly-Cygnus (now RH) devs are huge GCC contributors.

It was added specifically for c/ffi, so this is cool.

time for the tinfoil!

I doubt it. This is probably talking about early versions of OS/2, like, pre-2.0.

Why wasn't it there already?

I'm a big Bitwig user. This makes me want to get u-he and other CLAP-supporting plugins.

More cowbell.

So, like YouTube? Where only the creator can see dislikes?

And JMAP.

Good news, everyone!

Salk and Polio vaccine.

google Michael Kerrisk.

about:config is not for typical users.

yes

And that can be used to spin up secondary revenue streams more easily than starting from scratch.

agree. Hopefully the seventy megabytes of cache between the two chiplets will help...

The IETF QUIC working is well-aware of this, and is attempting to save design room for future QUIC versions as much as possible. The "QUIC invariants" spec documents everything that is guaranteed not to change, but other than than everything in a future QUICv2 could be updated (e.g. tls version, features, large parts of packet header layout).

Yeah but that's for the insurer. Getting "insurance insurance" would be for the customer, to protect getting screwed over by their original insurer, who has chosen the short-term option of rejecting a valid claim, but which results in long-term loss of trust in the entire industry. The only solution being...more insurance? Crazy.

I thought Trump called him "lyin' Ted" and the zodiac killer thing came from Reddit.

bad reporting.

With Scalia gone you still think it's unlikely?

this is usually not called normalization, it's more commonly called dynamic range compression, or just 'compression', fwiw.

tl;dr vp9 is competitive with h.264 but not h.265

A signed 32 bit "offset" value gives you 2GB in each direction, not 4GB in each direction.

Go only supports static linking. No dynamic linking means no linking issues when deploying the same binary across a billion machines in the Googleplex.

I think just like other languages, writing Rust leads to a familiarity with what the compiler wants. Then you spend more time thinking about design and the problem at hand, and less fighting the compiler. I think Rust will ultimately be easier than C++ to write because while there are tricky concepts to master, there should be much fewer of them than C++ has.