writing this was partly a byproduct of thinking a lot about how applications interface with OS.
Uncategorized
4
Posts
2
Posters
2
Views
-
writing this was partly a byproduct of thinking a lot about how applications interface with OS.
i like the fact that Linux syscall abi is stable. Kernel's good, but userland shits the bed: libc, dynamic linker and threading are all interdependent. you can talk to the kernel directly but the second you need a dynamic library it's game over. libc infects everything, and is the reason that being able to run the same Linux binary on two different computers is not a given.
-
writing this was partly a byproduct of thinking a lot about how applications interface with OS.
i like the fact that Linux syscall abi is stable. Kernel's good, but userland shits the bed: libc, dynamic linker and threading are all interdependent. you can talk to the kernel directly but the second you need a dynamic library it's game over. libc infects everything, and is the reason that being able to run the same Linux binary on two different computers is not a given.
@nicebyte Which leads us to this classic:
-
writing this was partly a byproduct of thinking a lot about how applications interface with OS.
i like the fact that Linux syscall abi is stable. Kernel's good, but userland shits the bed: libc, dynamic linker and threading are all interdependent. you can talk to the kernel directly but the second you need a dynamic library it's game over. libc infects everything, and is the reason that being able to run the same Linux binary on two different computers is not a given.
It's such an annoying design, and the worst part is - what on earth does C have to do with it? The language runtime should be completely separate from bits that actually talk to the OS. Kernel should come with some userland libs that wrap syscalls - kind of like windows. And as an extra bonus it makes things like wine possible!
-
writing this was partly a byproduct of thinking a lot about how applications interface with OS.
i like the fact that Linux syscall abi is stable. Kernel's good, but userland shits the bed: libc, dynamic linker and threading are all interdependent. you can talk to the kernel directly but the second you need a dynamic library it's game over. libc infects everything, and is the reason that being able to run the same Linux binary on two different computers is not a given.
Note you can do amazing heroics like this but in a better world the problem that requires this solution wouldn't exist https://github.com/graphitemaster/detour
-
undefined aeva@mastodon.gamedev.place shared this topic
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
La formula più bella del mondo (libro)
@libri - Un approccio umanistico alla famosa formula di Eulero
-
The only other thing I can think of are forced anti-features, like mandatory advertising, mandatory algorithmic feeds, or forced participation in LLM training.
Are there other things I'm missing?
-
@julian @silverpill @slyborg I wonder, though: what would be some changes that would worry you, though? I'm having a hard time imagining what they would be.
The best I can come up with are features that are too complex for small development teams (e.g. oodles of mandatory APIs), or too resource intensive for small instances to support (e.g. required to handle terabytes of big data).
-
@julian @silverpill @slyborg the changes I have marked for the next version are here.
https://github.com/w3c/activitypub/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Next%20version%22
I know there are some on there that Silverpill won't like, such as supporting IRIs for object IDs. I think it's worth having that conversation.
-
@julian @silverpill @slyborg most importantly: no protocol is mandatory. No protocol revision is mandatory. If the work the WG does isn't useful, nobody has to implement it.
-
@julian @silverpill @slyborg it's also worth noting that all discussions of the WG will be on a public mailing list. People can join the meetings, comment on drafts on GitHub. People interested in making more substantive contributions can become invited experts, even if they're not from a member organization.
-
@julian @silverpill @slyborg I will fight pretty hard against breaking changes in ActivityPub. We have an active network with tens of millions of people and tens of thousands of servers. It's too late for breaking changes and it has been for a really long time. Expect changes like: describing required properties of activities better. How `replies` (and maybe `context`) work. References to OAuth, Webfinger and HTTP Signature.
-
Oltre le macerie
@anarchia
Eccoci di nuovo qui. Riprendiamo le pubblicazioni dopo le consuete settimane di pausa, ma per le lotte non c’è stata sosta nella crescente stretta autoritaria e militarista. Multe, denunce, sgomberi. Questi sono i regali che si sono scambiati governo e...Vedi l'articolo
https://www.rivoluzioneanarchica.it/oltre-le-macerie/
