The book Building a Debugger, featuring a robot designing a complex debugging machine on a drafting board

The book placed in front of a tortie cat

Building a Debugger is now officially released!

It guides you through building a whole native x64 debugger from scratch, dispelling all the magic and teaching you a ton about operating systems as it goes.

Even if you don't care about building a debugger, you can read it to your cat.

Taking umbrage with, if I had to guess.

conv86 was a transcompiler; cfront from Stroustrup was also a transcompiler (transpiler) and called as such.

A transpiler translated dialects. As I said, transliteration. It doesn’t ’compile’. PL/C was a good early example. Modern usage means, ‘syntactic conversion’, which is probably what you’re

But also (addressed elsewhere ) a transcompiler (transpiler) is a real thing. Not a JS meme.

It’s really great to see productive PLT convos happening. Also, Rachit is 120% wrong. <3

I’m gonna disagree here. A Transcompiler ( Transpiler ) is the industry jargon equivalent to ‘transliteration’ and has been in use for 46 ish years. JS convolution doesn’t change that, at all.

Age yourself with your first computer.

The real problem is always naming

Racket, 100%. Python is a close second and probably more practical but the foundation in Scheme/Lisp will pay dividends for ever.

sexpr

They couldn’t crib on a CDN as easily. The source of the stream was probably also a bottleneck to their ‘recasting’. For a lot of their programming, they embed stream boxes which are basically appliances that live in data centers around the world; many copies of $Show sourced from different locals.

It comes down to two things: switching capacity and yes horizontal scaling. Ironically, they probably have the throughput, but they can’t oversubscribe their ‘grid’ without deleterious effects to other parts of their business. Also, this event was different because it was a live stream so

Basically, everyone refeshing exacerbated the problem.

It’s a little more technical, but essentially the switch operator ‘envoy’ was trying to connect an incoming call but the other side was busy. After a certain amount of time or a certain number of failures it gives up. Cascade failures happen when a bunch of people request the same thing

Netflix uses a mesh compute system, basically a giant grid with CPU allocated to it. For incoming requests, a portion of that grid is allocated to perform whatever ‘task’ is requested. Envoy failures invariably mean that the request couldn’t be mapped to the grid because it has no capacity.

Envoy’s documentation is pretty good as well: www.envoyproxy.io

Zero Configuration Service Mesh with On-Demand Cluster Discovery Netflix’s service mesh adoption: history, motivations, and how we worked with the Envoy community on a feature to streamline mesh adoption

Envoy is a reverse proxy system that Netflix uses to map incoming requests to internal resources. There’s a pretty deep technical article about their stack here: netflixtechblog.com/zero-configu...

Cameras caught Mike Tyson naked in the locker room before his fight

Tasman Road, Figure 2, by Thomas J Price, 2008

🏳️‍⚧️happy trans awareness week🏳️‍⚧️

my first trans marine, pretty proud of it as it was the first time I used brighter colours, and first time using transfers on marine shoulders in close to a decade

also helped me properly come out to a friend of mine

but yeah, I'm planning to make some more

🏳️‍⚧️🏳️‍⚧️🏳️‍⚧️🏳️‍⚧️🏳️‍⚧️🏳️‍⚧️🏳️‍⚧️🏳️‍⚧️🏳️‍⚧️

Resurgence of the MUD? Looks dope!

[oc] natural talent ✨

Starting in under 10 minutes!

twitch.tv/seanicuscode

#elixir #rust

Hello, #Elixir friends! I'm live coding on Twitch tomorrow (Sunday Aug 13) at 3:30PM CDT. We'll continue working on our HTTP client, tweaking macros and looking at timeouts!
Join me tomorrow: https://twitch.tv/seanicuscode https://everytimezone.com/s/9042a8c9 #myelixirstatus #WeBeamTogether