Yes, X11 is a protocol, which is still slowly developed by adding extensions to it. Whether it does or doesn't need to be actively developed is a question of what features you do or don't think it needs.
I used icewm some time ago, and then quite recently when putting together a dashboard of sorts. Configuration you can do in IceWM is amazing, let's you do cool tricks with your window setup.
Also it is my default WM when for some reason I want to run a browser in Xvfb and access it via VNC. Not that I've done it a lot (don't tell anyone). Running an automated browser WM-less gets annoying in certain situations.
DNS caching and thus the load distribution is outside the control of the entity running the servers. You assume you get roughly same traffic on each of the published IP addresses, you even think you can advertise some address twice so that it gets twice the load vs other severs (if you just set up a server capable of serving twice the traffic), but the reality is one of these IP addresses might be used for 90% of the requests (as an example) due to caching and bad luck.
So no, you cannot reliably control load balancing using one domain name pointing to multiple IP addresses. (IP anycast is better suited, but much harder to implement)
This has a big upside: I can now MITM any Android app / IOT device without any suspicious set up on the device? (given it'll run on the unupdated OS and that cert revocation is not ON).
> And for computers, most people could probably make do with machines that are many years old and not feel a difference in their capabilities.
That would be true if not for 50MB-heavy JavaScript webpages.
Same goes for smartphone apps. Facebook app used to be a few megabytes in size and it was already very big compared to other apps you had on the phone.
I bought a refurbished Thinkpad from 2021 to be my daily driver. 32GB RAM. Paid a few hundred bucks for it. I didn't do it for environmental purposes, I just figured that the specs were more than good enough for general use and software development. Has the added benefit of not becoming e-waste.
Works like a charm, does everything I need, just not very good for more demanding games due to lack of a dedicated GPU.
I started wondering if there could be swap-aware GC, like first make the required page swapped in (not that there's any obvious API for that...) and only then pause the world?
You could do lots of interesting things with sufficiently deep inter-layer integration.
For example, why not swap out not by LRU page but by dense node clusters on the heap graph, maintaining in-memory summaries of inbound and outbound edges for liveness? If you do this, you don't have to swap the cluster in to do a GC involving it.
If the whole cluster becomes unreachable, you wouldn't even have to swap it back in to get rid of it: you'd just drop the swap reference and deem the swap space free.
I don't see anything this deeply integrated happening near-term, but it's fun to think about.
Probably more mlock (keep memory area in RAM), mincore just tells you what is or is not in RAM, and madvise is about access patterns.
You could MADV_WILLNEED the GC metadata when you start the GC process hoping they’ll have been paged in by the time you STW, but assuming that area is not massive it’s probably a better idea to just prevent it being paged out.
I was assuming they meant for the heap. Not even executable memory is locked though, so if you mlock too much memory the kernel will page out your executable instead. Something has to give, so it's better to schedule it.
On a lower level, the OCaml and cpython GCs use a prefetch buffer during marking to schedule around the cache.
One can just add APIs to the Linux kernel, and this would be a pretty straightforward one. (though it might be a little more difficult to avoid a syscall here)
I'm sure an agent can work on this and get some numbers with a day's worth of tokens.
I was biten by not understanding madvise(MADV_WILLNEED) semantics fully. It will prefetch, but it will not pre-fault. You still gonna pay minor page fault on every new page access. There is MADV_POPULATE_READ, but it is synchronous.
I think we are not realizing the paradigm shift here. A coding agent can implement this with a modest little day’s worth of tokens. This means that no one needs to read or know the APIs any more. We can just add them to the kernel as we need them. Then when we forget that we needed them we can just rediscover the API idea later and spend a day’s worth of tokens. (But let’s be real here. By then it will probably be just 1/3 worth of tokens with all the model improvements as well as the ample training material.)
Thankfully, we can now use AI to design a test that tests AI. And the AI company can use AI to detect the test and cheat. And we can then use AI to implement anti-cheat.
All that energy wasted... could just drive a big V8 instead and make less money for the big tech
Being a protocol doesn't mean it can't be actively developed (look at HTTP at least), but if it's good it doesn't NEED to
reply