Yeah as I've dabbled with AI models more and more it's become clear to me how much my mental model is valuable to the programming process. It's easier to debug code I wrote myself then to comb through some AI's mistakes when it eventually gets to a problem too hard for the model to debug.
> Otherwise I’m already freaked out by treating a 32 bit field as a pointer… even if you extend it to first.
The cast from a 32 bit pointer to a 64 bit pointer is in fact an eBPF oddity. So what's happening here is that the virtual machine is just giving us a fake memory address just to use in the program and when the read actually needs to happen the kernel just rewrites the virtual addresses to the real ones. I'm assuming this is just a byproduct of the memory separation that eBPF does to prevent filters from accidentally reading kernel memory.
Also yes the double cast is just to keep the compiler from throwing a warning.
I had not heard of T9 before starting the project and getting interested, I'm too young to have experienced owning a pre-touch screen phone. I don't know if the average HN reader knows what T9 is, so I went with a term that I was fairly certain most people would be familiar with. Is that so people engage with my work? I certainly found the project fascinating, I made the library to share that fascination. If I can get more people to implement and use T9 and alike systems I think my work has has been a success.
Please submit an issue on the Github repo! This is a bug, it should automatically show with words as you type. Include platform details, console logs, etc. I am unable to test every platform alone sadly.
I mean thinking about students as actors of pure bad faith, a student could easily copy and paste any instructions given to them into a LLM and bypass any required training data. Even if an AI company respects the license and the source does not end up in the training set, model knowledge tends to be generalizable to a given area. The only way I could see making a language that is intentionally obtuse to write in (brainfuck or really any other esolang seems to work), but that fails at being a good introductory programming language.
Love this distro, its the only one that loads fast on web x86 emulation. Sad that they're upping the size but 700mb is still leagues smaller then most other distros.
It's odd ICANN has such a control to effect an countries income just by choosing a good abbreviation. I doubt the creators of the DNS system had any idea that domains would arbitrarily give some countries an extra form of income, profiting from people who could care less about the country it was created for. Why didn't ICANN just charge a flat fee for any string to resolve to an IP?
The whole point of the ccTLDs is that ICANN doesn’t really have any control over their contents—they’re “sovereign soil”, so to speak, and each country can do whatever it wants with its namespace. Which brings us to the answer to your question:
> Why didn't ICANN just charge a flat fee for any string to resolve to an IP?
Because ICANN doesn’t control what strings resolve! They delegate to registries (by putting NS records in the root resolvers), and for ccTLDs it’s up to each country to set policy and infrastructure to taste. If anything, the existence of gTLDs (like .com) where policy is set internationally is the unusual aspect of this arrangement.
It's odd ISO has such a control to effect an countries income just by choosing a good abbreviation. I doubt the creators of the DNS system had any idea that domains would arbitrarily give some countries an extra form of income, profiting from people who could care less about the country it was created for. Why didn't ISO just charge a flat fee for any string to resolve to an IP?
Think about the original TLDs, there was value in separating commercial, military, and government content. Unfortunately .gov is US government only and .mil is US military only. So each country would presumably want a .gov.[country-code] and .mil.[country-code] suffixes for those same reasons (and many do).
Opening up registration for non-citizens / non-residents is an option each country has. Some restrict registration more than others.
There's also an important angle that countries can set the terms of service for their ccTLD to match their laws. It's one way to ensure a country has some legislative and enforcement ability over their corner of the web.
