750 karma · joined September 11, 2015
var source = new EventSource('pull?name=one');
source.onmessage = function (event) {
document.getElementById('events').innerHTML += event.data;
};
http://talk.rupy.se/event.html> If you need bi-directional communication, then you should consider using WebSockets instead.
Or you just do a HTTP request?
Don' let the voltage go to far below 3.7V and don't over charge above ~4-4.2V.
Pi4: 20 FPS same when using ffmpeg to stream to twitch. 5W
Pi5: 40 FPS idem as above. 10W
3588: 300+ FPS and rock solid 60 FPS streaming to twitch. 15W
So 5090 is not even interesting for gameplay. More polygons and larger textures do not make games more fun to play.
AAA has peaked and C++ does not even deliver interesting games any more. C#/Java are way better alternatives for modding.
It's usable as is.
By the time linux catches up hardware might be very expensive or missing completely.
So my thinking is buy now, use as is, and maybe later we get better software... The point is the 3588 can actually replace my X86 desktop for ALL purposes except Unity/Unreal which I am glad to not run.
Pi 5 and N150 are completely meaningless since before they came into existence.
Also the price of 3588 increases by batch so you can still get them at almost launch price (4GB was $70 now $110, next batch probably ~$150 by now if nothing improves)
We need to be able to set it to -1 to tell the OS that no acks should be used at all, effectively turning that socket into UDP but with a TCP API!
That way we only have one protocol for ALL internet traffic.
I made a RFC about this a decade ago that was ignored.
Then we can make TCP become UDP.
And then we solved everything.
Both linux and Windows have this config but it's buggy so we're back to TCP and UDP.
Edit: TWM is less cluttered and less features is actually more here...
RAM maybe wears quicker if compressed?
NVMe will break long before a good old SATA drive.
WSL... lol
ISO you can do with daemon tools for free...
Displays are good enough at 60Hz 5:4 matte.
I'm going linux with TWM (desktop with design look from the 70s) on ARM because M$ is clearly not thinking about the long perspective.
We need a stable platform to build quality software.
And that's saying alot seen how linux is deprecating libc after very short time and the legacy joystick API is not being compiled into modern kernels anymore.
Stability is way more important than bells and whistles.
But with a 3050 upgrade from the 1050 and later 1030 (best GPU for eternity if you discount VR) I had in it it's good for another decade. If a game comes out that does not run on it I wont play it... simple as that... 150W is enough. So far only PUBG stutters, what a joke of bloat and poor engineering that game has become...
Win 10 improved NOTHING over 7. Win 11 improves NOTHING over 10.
YMMV but recommendation is still: do not buy new X86 hardware; do not use new OS/languages.
Build something good with what you have right now.
Make it so good it's still in use after 100 years.
Maybe 120Hz if they come in 4:3/5:4 with matte low res panel.
But that's enough for VR which needs 2x because two eyes.
So progress ends there.
16 cores can't share memory well.
Also 15W is peak because more is hard to passively cool in a small space. So 120Hz x 2 eyes at ~1080 is limit what we can do anyways... with $1/KWh!
The limits are physical.
VAO is the last feature I was missing prior.
Also the other cores will do useful gameplay work so one CPU core for the GPU is ok.
4 CPU cores is also enough for eternity. 1GB shared RAM/VRAM too.
Let's build something good on top of the hardware/OSes/APIs/languages we have now? 3588/linux/OpenGL/C+Java specifically!
Hardware has permanently peaked in many ways, only soft internal protocols can now evolve, I write mine inside TCP/HTTP.
3588 (10W) plays HL2 at 300 FPS and streams it at 60 FPS to twitch.
Turns out 2025 was the year of the ARM linux desktop after all!
TWM + emacs + irssi + mpv(ytdl)
Some say they have the opposite experience, mine is ONLY Intel drives, maybe that is why.
X25-E is the diamond peak of SSDs probably forever since the machines to make 45nm SLC are gone.
Bandwith increases, but if you only need a few bytes DDR3 is faster.
Also slower speed means less heat and longer life.
You can feel the speed advantage by just moving the mouse on a DDR3 PC...
Just like SSDs from 2010 have 100.000 writes per bit instead of below 10.000.
CPUs might even follow the same durability pattern but that remains to be seen.
Keep your old machines alive and backed up!
Edit: found this below: "Powering the SSD on isn't enough. You need to read every bit occasionally in order to recharge the cell."
Hm, so does the firmware have a "read bits to refersh them" logic?
The only MLC I use today are Samsungs best industrial drives and they work sort of... but no promises. And SanDisc SD cards that if you buy the cheapest ones last a surprising amount of time. 32GB lasted 11-12 years for me. Now I mostly install 500GB-1TB ones (recently = only been running for 2-3 years) after installing some 200-400GB ones that work still after 7 years.
I much rather have 64GB of SLC at 100K WpB than 4TB of MLC at less than 10K WpB.
The spread functions that move bits around to even the writes or caches will also fail.
The best compromise is of course to use both kinds for different purposes: SLC for small main OS (that will inevitably have logs and other writes) and MLC for slowly changing large data like a user database or files.
The problem is now you cannot choose because the factories/machines that make SLC are all gone.
Also about cross compiling that is meaningless as you need hardware to test on and then you should be able to compile on the device you are using to test. Alteast that is what I want, make devices that cannot compile illegal.