We had one who pulled up the pdf of the textbook to read it word by word

1. The skerton was (is?) A good entry level grinder that will give you very decent results especially for immersion-type brews. It’s what I started on and what I still use for on the go use cases. I haven’t looked at entry level hand grinders in a while so I guess some developments have happened since I got mine. (Based on a comparison video from james hoffman at the time)

2. God yes, I tried a friend’s 1zpresso and the difference in both grind speed and effort is noticable.

Nope, IaaS. With a VPS you are in charge of everything except for the hardware. PaaS the only thing you’re in charge of is your code.

I see, so I’m assuming the same goes for regular actors? And musicians? And basically any performer ofcourse? Oh and also anyone who does manual labour because you are literally renting out your body for that. Well, and technically anyone with an office job too because they are still renting out their time.

Don’t you have the code in most cases? Like with e.g. freeRTOS? That’s fully open source

Isn’t that still the same exact process as a normal compiler except in the case of embedded systems your OS is like a couple kilobytes large and just compiled along with the rest of your code?

As in, are those “crazy optimizations” not just standard compiler techniques, except applied to the entire OS+applications?

Regarding your note on quantum secure cryptography: Yes it exists and is a thing, but a lot of the internet still relies on cryptography that is not quantum secure, e.g. TLS for starters.

#1C1C1C

It’s a very calming nice gray

Grandpa knew what he was doing when he called all the pokemen pikachu

Fun fact: lots of those sd cards are actually fake. Have you tried actually putting 128gb of data on it?

It’s pretty easy for them to put a scummy firmware on it that reports having a significantly larger size than they actually have.

Oh yeah, it’s actually pretty extensive and expressive. If you’re interested in this sort of stuff it’s worth checking out the IR language reference a bit. Apparently you can even specify the specific garbage collection strategy on a per-function basis if you want to. They do however specify the following: “Note that LLVM itself does not contain a garbage collector, this functionality is restricted to generating machine code which can interoperate with a collector provided externally” (source: https://llvm.org/docs/LangRef.html#garbage-collector-strategy-names )

If you’re interested in this stuff it’s definitely fun to work through a part of that language reference document. It’s pretty approachable. After going through the first few chapters I had some fun writing some IR manually for some toy programs.

LLVM is designed in a very modular way and the LLVM IR allows you to specify e.g. if memory management should be manual/garbage collected.

You could make a frontend (design a language) for LLVM that exposes those options through some compiler directives.

In general I’d heavily recommend looking into LLVM’s documentation.

Reminds me of the old joke that monads are easy to understand, you just have to realize monads are just monoids in the class of endofunctors.

What study is that? Can you give a reference?

What is this recent trend of saying “batteries included” for literally anything software related?

It feels like it tells you nothing at all about the project except that whoever is talking about it is big into buzzwords

Couldn’t you do something like JWT except allow the client to slap on their credentials to any initial request?

From the backend side that means that if there is no valid token, you can check the request body for the credentials. If they’re not there, then it’s an unauthorized request.

You’re eliminating a singular request in a long period of time at the cost of adding complexity to both client and backend but if the customer wants to be silly that’s their fault

JS was a mistake.

It’s a joy to do async in go IMO

That’s actually a really nice application, in this case to reduce bandwidth constraints as opposed to the usual use case of memory constraints!

Cool, so in this case your filter is basically a classifier ML model. How would you set the hash functions then though?