I was assembling by hand as late as 1985 because I didn't have access to an assembler and writing out the code wasn't that hard. And it made you think about what you were doing! https://blog.jgc.org/2013/04/how-i-coded-in-1985.html
And we had/have people at Cloudflare hand writing assembly to get specific performance out of our systems.
Cloudflare always had a pretty strong culture around optimisation. If you go back and read the blog there are a lot of blogs about reducing CPU, latency, RAM, etc. through software. It's one of the key features of how Cloudflare has been successful and an important part of succeeding in today's world.
And Cloudflare is making money on infrastructure margins not eyeballs (ie advertising like Google), so the incentives are well aligned for this to continue.
I was wondering why you were no longer CTO, congrats on the board role (seems that it's been a bit over 18 months).
I don't know you from a grain of salt, but you've seemed to be pretty open and honest on HN about some of the inner workings (technically and politically) of Cloudflare, which is appreciated.
I decided to step down as CTO because I'd been at it for a long time and the board role allowed me to stay involved without being there every single day. I wrote about my "retirement" here: https://blog.cloudflare.com/three-chapters-at-cloudflare-pro...
1) This decision was made pre-AI, where human familiarity mattered. Since the devs that would've used this were familiar with JS, that was what they were stuck with.
2) You're targeting to the wrong person. Blame the managers at Netscape for pushing Brendan Eich into creating JS, rather than letting him use Scheme as the scripting language. From there, it would've made sense to allow Scheme to be compiled into bytecode.
There's a lot of native code at Cloudflare. Just go look up the optimisations we did around crypto or compression in assembly. Or every time we use a compiled language like Go or Rust or C++.
I'd also say that when you look at JITed language like Lua and JavaScript the performance is pretty damn impressive. As with so many things it depends what you're doing.
As mentioned, that had a tough sync problem. SIGSALY changed its key every 50ms. The mechanical synching of two turntables within that range was possible. That worked because the audio was being compressed pretty hard before encryption.
Delilah, which works by using a modular analog adder to add signal and key noise, would need a new analog key value for every audio sample. Probably 3KHz or so, or about 300usec. That's beyond the precision of sync which can be achieved reliably by mechanical means.
A little bit of analog buffer would help.
It wouldn't be a problem for transistor era electronics. You need something like an analog shift register (see "bucket-brigade device"[1]) Those were not developed until the 1970s, and, for a while, appeared in guitar pedals, reverbs, and other simple audio processing devices. If you had to do that with tubes, you'd have a whole rack of tube delay line.
The more we ostracise people doing that now, the less likely it will come up in the future.
In any place of business that I patronize, if I see one, I will request that staff should ask the offender to remove them, or remove themselves from the property.
I think it's like slices of tree trucks to build wall clocks (or whatever) kind of wall art out of: If you know a guy who knows a guy who works with trees, then it's easy to get a rough cut-off slice.
It may even be free. If they're already there cutting the thing with an appropriate saw, then slicing off one more bit and saving it for Bill's friend jgrahamc isn't a big deal.
Everyone in the industry I can find including people who do recycling of submarine cables. It seems that cross sections are sometimes given away as gifts as part of a project but are really hard to find.
And we had/have people at Cloudflare hand writing assembly to get specific performance out of our systems.
reply