@ariel@m.costas.dev
"Fast" is arguably a #BigTech concern, not something Aral (or me) would give a shit.
Simplicity however is very important, in different ways, for both of us.
However when you try to figure out how simple is your software, you cannot ignore the stack you are using.
How many milions of lines of codes are behind those 100 #javascript ones?
This obviously apply to any stack, go, python, perl, lisp... even C!
Hidden complexity is not simplicity.
@minimalprocedure@mastodon.uno La scuola e l'università potrebbero, ma - salvo eccezioni - in Italia sono fra gli enti che aderiscono e favoriscono l'assuefazione agli oligopoli proprietari.
Individualmente tento di farlo https://elearning.sp.unipi.it/course/view.php?id=554 sfruttando l'articolo 33 della costituzione, ma questo significa venir sistematicamente emarginati da coloro che si sono adeguati all'idea che il modello del docente universitario debba essere il ragionier Filini.
Non è impossibile evitare di sottomettersi a GAFAM https://peertube.devol.it/w/89XNjqjPTXaMVdWsoR3ZzN Ma come trasformare le scelte individuali in scelte collettive, soprattutto per chi lavora in istituzioni e aziende che fanno l'opposto?
https://vimuser.org/1337box.html
Completely bloat-free, javascript-free lightbox implementations. Insanely optimized, pure CSS. Makes viewing images on web pages more user-friendly.
The optimized version is currently 140 bytes!
I've had this for a while now, and thought I'd publish it.
Non male! :-)
Eidas has strict requirements/audit/sanctions for CAs that operate in the EU
Todat they are the issuers of digital signatures, which are the basis of all transactions with legal validity in Europe.
Browsers rigid standards = chosen by Google.
Trust a private monopolist more?
---
RT @doctorow
EU's Digital Identity Framework Endangers Browser Security https://www.eff.org/deeplinks/2021/12/eus-digital-identity-framework-endangers-browser-…
https://twitter.com/doctorow/status/1471711109593845760
«Manifest V3 è un dannoso passo indietro per la #privacy su Internet. … Niente che #ManifestV3 introduce nel suo stato attuale può aiutare a proteggere la privacy. Gli sviluppatori e gli utenti di estensioni dovrebbero agire con fermezza contro di essa.»
#Google sta cambiando tutto, rimuovendo le funzionalità nelle API di #Chrome su cui si basano queste estensioni e lo fa in nome della sicurezza, della privacy e delle pprestazioni, ma c'è chi ne dubita
Di Richi #Jennings
https://securityboulevard.com/2021/12/google-nukes-ad-blockers-manifest-v3-is-coming/
(little implicit premise: when I say "fork" I mean Plan9 style rfork, that let you specify what is inherited by the parent process... except for the stack, which is inherited anyway)
The fact is that both inherited memory and `malloc`ed one (and even `mmap` one in linux, afaik!) is just a promise you get from a cheating kernel: the physical memory is NOT assigned to the process until the last possible instant (the memory access fault).
In #Plan9 this is also true for the stack that is handled as copy on write, but I'd guess on #Linux and #BSD, all other segments are CoW too.
Also in a Plan9 system, pages are 4096 bytes chunks, so the CoW is pretty conservative and after a fork only one new physical page is assigned to the new process (the page where the return value of the fork syscall get written).
So, in theory, fork is not that coarse memory hungry faggot.
But AFAIK this happens with malloc too: pages are assigned to processes only on read/write faults. In modern systems memory is always overcommitted.
It is dangerous, but consider the alternative: most allocated memory would stay unused and you could run a fraction of the programs you run on the same hardware.
Well, this is a good answer, but in fact, on plan9 you only get a new process: memory is only copied on write.
So it's not necessarily a malloc.
Also rfork give you a good degree of control on what is copied.
Well, to be precise, you'd need to know it at loading time. In mainstream os this mean you must know it at compile time to save such info in your ELF binary or something.
But could we imagine something more flexible than that?
Pixel density and size of a display can be known in advance.
Windows' max size is that of the (virtual) display and actually, if you properly align your memory buffer, when the actual size is smaller then the available memory, several pages are never faulted.