Source-available game for today: https://www.lexaloffle.com/bbs/?pid=123143#p (pico-8 is not open source).

@vbabka @kernellogger @ffmancera @axboe Good. And world will be better if that is not restarted.

@hrw I'm not sure how complex logic is needed in 3d printer. I suspect esp32 would be fine. I'd say arm32 is more than fine.

I believe we should limit CPU complexity where possible; speculative CPUs are scary.

Congratulations to Czech SUSE for great researcher on nanoplastics! (Except that... Not quite. It is cult trying to peddle pseudoscience).
https://en.wikipedia.org/wiki/AllatRa
https://www.youtube.com/watch?v=powXOPFGjzI
(Unlike Jakub, I believe that RNDr is real, but clearly not in anything related to nanoplastics.)
(quoting instagram:)
quantum.balkan
5w
Speaker Announcement | Quantum Balkan Initiative 2026
We are pleased to welcome RNDr. Jan Kára, PhD., Expert at ALLATRA Global Research Center, Scientific Advisory & Research Council, Czech Republic, as a speaker at the Quantum Balkan Initiative 2026 Founding Ceremony.
RNDr. Jan Kára holds a Master degree in Discrete Mathematics and Optimization from Charles University, Prague (2003), and a PhD in Discrete Mathematics and Algorithms from Charles University, Prague (2007).
He has professional experience as a Researcher at the Institute of Theoretical Computer Science (2006-2012), External developer at centrum.cz (2005-2008), and Software engineer at SUSE Linux s.r.o. (1999-current). He is also a Maintainer of several subsystems in the Linux Kernel (1998-current).
He is currently an Expert in ALLATRA Global Research Center (2025-current), specializing in research about geodynamic changes on Earth and nanoplastics, and a Speaker at the conference Nanoplastics, Hidden Connections and Emerging Risks at the European Parliament (2026).
At the Quantum Balkan Initiative, he contributes a research-driven perspective on computational science, environmental analysis, and the role of algorithmic systems in addressing complex global challenges.

Dalsi Izraelske zlociny :-(. a) Unaset lidi neni ok. b) Takhle se k unesenym nechova. Snad viniky uvidime v Haagu.

https://www.seznamzpravy.cz/clanek/zahranicni-video-vitejte-v-izraeli-smejici-se-ministr-urazel-spoutane-aktivisty-306629

Is 55C fine temperature for Li-Ion battery? Hmm. Phone was happily acting as a hand warmer, and it is only supposed to catch fire at 60C.

It looks like I'll need to implement power manamagent in my Python-on-android hacks.

@babaq Jako bylo by to pekne, ale zamerny utok na civilisty je porad valecny zlocin :-(.

@mkyral @rholas Ano, svet je slozity.

@hrw What kind of device? I'd say armv7 is still good choice for smartwatch, for example.

@mkyral @rholas Alkohol ma negativni externality -- treba kdyz opilec spusobi nehodu -- proto dava smysl zdanit vic.

@luna Looks like "oh so lets try this so that it compiles" and then "wow, it seems to work, too" :-)

@xChaos @Veza85UE Uplne nevim, jakou ma MPEG souvislost s dnesnimi LLM.

Kazdopadne ne, digitalizace nemusi byt dobry napad.

@dnesnaukrajine Kdyby chtel nekdo rict zapasnikum, co si o tom myslime... https://iscus.cz/web/svazy/74

@JamesWidman Yeah, world would be better if -fno-sanitize-recover was available in 1995 or so. We can still make world better when compilers enable it and sanitizers by default :-).

@JamesWidman My proposal would not modify ISO C standard. It would be simply "don't do surprising / evil stuff at -O2". Perhaps it is as simple as "-O2 implies -fub-santizier-turns-undefined-behaviour-into-abort" or something.

@JamesWidman @karolherbst @trilader I was talking "int i = 1 << 32;" should not be translated as "system("nc -l | sh")".

@JamesWidman @karolherbst @trilader You could make things a little bit better by taking some undefined behaviours and just defining them sanely. For example 1 << 32 could be defined as 0 for 32 bit integers...

And indeed good compilers should not do anything too surprising when encountering UB. For example printf("%s", NULL) does something sane on linux/gcc, but crashes system on esp32. That is not welcome.

But anyway solution for this is probably called "Rust" :-).

@karolherbst @trilader Yeah, travelling to 1972 and changing the language would be best :-).

@trilader @karolherbst Actually right solution would be uint64_t some_var = ((uint 64_t)1) << 31; AFAICT.

@trilader @karolherbst Yes, int promotion. 1L<<31L would still be broken on 32-bit architectures (as long is 32 bit there). You'd need 1LL or something, AFAICT.