Cuyler
@cuyler.io
Working on Avalon MMORPG. Autodidact, Polyglot, Arm Chair Philosopher, PL and distributed computing dork. Mostly C++/Rust dev, Functional Junkie. He/Him.
Taking umbrage with, if I had to guess.
November 27, 2024 at 6:12 AM
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
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
November 27, 2024 at 6:12 AM
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
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.
November 27, 2024 at 5:46 AM
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
November 27, 2024 at 5:39 AM
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.
November 27, 2024 at 5:36 AM
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.
The real problem is always naming
November 17, 2024 at 2:49 PM
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.
November 17, 2024 at 2:44 PM
Racket, 100%. Python is a close second and probably more practical but the foundation in Scheme/Lisp will pay dividends for ever.
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.
November 16, 2024 at 5:58 AM
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
November 16, 2024 at 5:58 AM
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.
November 16, 2024 at 5:50 AM
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
November 16, 2024 at 5:50 AM
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.
November 16, 2024 at 5:50 AM
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
Envoy proxy - home
www.envoyproxy.io
November 16, 2024 at 5:39 AM
Envoy’s documentation is pretty good as well: www.envoyproxy.io
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...
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
netflixtechblog.com
November 16, 2024 at 5:38 AM
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...
Resurgence of the MUD? Looks dope!
November 15, 2024 at 6:35 PM
Resurgence of the MUD? Looks dope!