Building my own network stack
blog.lyc8503.net
Building my own network stack
1–10 of 103 posts
Re: Building my own network stack
#2Good to see that people still have this spirit of rolling their sleeves up and doing something like this for fun. Underneath it there is a very real point about mono-cultures and the increased magnitude of the impact of a risk, although more eyes checking one implementation should reduce the probability.
Re: Building my own network stack
#3Prediction: as agentic code generation gets better, more and more code will be written JIT for it to be executed for security reasons. The engineer of the future is not only the one who uses agents to code, he uses agents to code each time "the" program is ran.
Re: Building my own network stack
#4I disagree
Re: Building my own network stack
#5Prediction: as agentic code generation gets better, more and more code will be written JIT for it to be executed for security reasons. The engineer of the future is not only the one who uses agents to code, he uses agents to code each time "the" program is ran.
I doubt it. It seems far more likely that such code will be written just once by LLMs, but in a way that allows its claimed guarantees to be formally verified (e.g. in Lean). At that point there’s no need to JIT an implementation each time.
Re: Building my own network stack
#6I disagree
So do I. According to today’s prevalent tech/science culture, “everyone” should
- write their own network stack, compiler, text editor, operating system
- learn 3-5 foreign languages
- travel extensively
- learn how computers work from the silicon principles to the userspace
- have a complete understanding of algorithms and data structures before even attempting to build anything, because nothing else will do
- read obscure Russian poetry
- “deeply” engage in 5-10 different philosophical practices and meditation techniques
- work out regularly, but according to strictly scientific principles, which you first have to research by reading a dozen books
- appreciate fine art, homestead food, and family life
Sorry folks, y’all are just Instagrammers with MSc’s. Most people here probably have no idea how ridiculous this world appears once you step out for a year or two and then take a look back in.
Re: Building my own network stack
#7I disagree
So do I. According to today’s prevalent tech/science culture, “everyone” should - write their own network stack, compiler, text editor, operating system - learn 3-5 foreign languages - travel extensively - learn how computers work from the silicon principles to the userspace - have a complete understanding of algorithms and data structures before even attempting to build anything, because nothing else will do - read…
It was a joke if you read the article.
Re: Building my own network stack
#8I disagree
So do I. According to today’s prevalent tech/science culture, “everyone” should - write their own network stack, compiler, text editor, operating system - learn 3-5 foreign languages - travel extensively - learn how computers work from the silicon principles to the userspace - have a complete understanding of algorithms and data structures before even attempting to build anything, because nothing else will do - read…
Glad to see you two read only the title, not the article; that fulfills the cliche.
And in your list you forgot taking a lecture in category theory.
Re: Building my own network stack
#9Prediction: as agentic code generation gets better, more and more code will be written JIT for it to be executed for security reasons. The engineer of the future is not only the one who uses agents to code, he uses agents to code each time "the" program is ran.
What's there to gain security-wise? Nondeterministic generation & then execution of that code without proper verification seems to be the opposite of a good security posture.
Re: Building my own network stack
#10Prediction: as agentic code generation gets better, more and more code will be written JIT for it to be executed for security reasons. The engineer of the future is not only the one who uses agents to code, he uses agents to code each time "the" program is ran.
I doubt it. It seems far more likely that such code will be written just once by LLMs, but in a way that allows its claimed guarantees to be formally verified (e.g. in Lean). At that point there’s no need to JIT an implementation each time.
My bet is one ultra-hardened, minimal, front-facing system which does N-modular redundancy which N systems, each written on a different stack/different language.
The hardened software picks the computation that wins the majority.
It's not an issue to write all the implementations in the various stacks/languages: we'll have better and better LLMs to help us.
This shall bring security and shall allow to detect shitload of bugs (both in the implementation itself but also in the stack).
Heck, this could even be compatible with GP: one of the implementation could be JIT'e by a LLM, others could be written in advance (and Lean formally verified). Not sure which sense it'd make though.
I'm 99.9% sure it's coming for if it's not, I'll make one.