earenndil

How about 'jug'?

Ironically, a website centred around security doesn't support ed25519 ssh keys.

It is completely arbitrary, yes.

    <link rel='stylesheet' href='res/lettercrap.css' />
    <link rel='stylesheet' href='res/style.css' />

;o

More to the point, it's gray goo https://en.wikipedia.org/wiki/Gray_goo

Good luck using one as a regular workstation (without resorting to classic unix, at which point we're back where we started).

That's a bit of a knee-jerk reaction, IMO.

Problem: the computer systems we use are insufficiently flexible/too flexible, encouraging the use of N different ways of serializing data.

Solution: make a computer system which encourages centralizing the mechanism by which data is serialized.

You don't have to 'mentally substitute' the actual words. PC, SP, A, etc. are the words themselves. StackPointer is a pointless formalism.

Don't you have to destroy the target object, before you move into it?

Oops, I typoed. I said 'new *printf functions'; the example was supposed to be 'printf2("int64: %d64", x)'

GCC supports c17 already. Using c99 is fine, and plenty portable.

What I wonder is, why didn't they add new *printf functions? So you could say 'printf("int64: %d64", x)'

/r/wallstreetbets is a joke...

> first line as the PR title and the rest as description

> exactly the same mechanism as git uses for "git commit"

That's not how git commit works. git commit opens $EDITOR and makes a list of lines (sans commented-out lines) from that. The first line being a title is only convention, whereas in a github PR it's a formal element of the system.

Do we have statistics about how many infected people are showing symptoms?

I believe that's part of what they're trying to point out. That melodies this short should be copyrightable by anyone.

> they apparently do this not to make more money, but just so they can pass the savings on to the consumer

...so that consumers buy more/are more likely to buy, making them more money. Which is kind of the point of the article.

Title taken from the reddit post[1], as the video's title is a bit clickbaity.

1: https://redd.it/f1tuwo

> If he's so unoriginal, you go do what he did

That's nonsense. Most people weren't lucky enough to sell a company for several hundreds of millions of dollars in the dot-com boom.

> If innovation continues to accelerate

It won't; that is a naive view. Innovation can't keep accelerating forever, and I would be surprised if it even keeps up its current pace; far likelier it's a sigmoid curve - https://en.wikipedia.org/wiki/Sigmoid_function

But then you have to call vertical tab VT, and then you have no name for a virtual teletypewriter.

> Also it IS a beginners books because he makes no assumptions about the readers previous experience

I've just started going through it, and it's definitely made some assumptions about prior knowledge; I doubt I would have been able to get through it if I didn't already have some assembly knowledge.

> PSSL doesn't need to be emulated

...which makes the job much harder. Shading languages aren't terribly complicated; implementing a compiler from one to native spir-v/whatever is a reasonable task. Translating from one shader bytecode to another is a more involved operation.

Once freebsd's linux implementation supports io_uring, you'll be able to use that there too. Nothing for macos, though, I'm afraid.

why not add an operator so you can say (x !is null)?

I think the proposal is to solder an entire stick of ram onto the CPU.

Conservative data center managers aren't particularly pissed off. Source: know one.

Yes.

You don't need to (un)marshal necessarily; stuff like strings, or arrays of integers, can go straight across. And if you have to pass large amounts of data, they'll probably take a form that's something like that.