Archive for the ‘programminchatter’ Category.

#programminchatter

Fri May 10 22:12:03 2024 (*097dfbf6*):: the level of autism here is stunning https://arstechnica.com/gaming/2024/05/hackers-discover-how-to-reprogram-nes-tetris-from-within-the-game/ +public! *** Hackers discover how to reprogram NES Tetris from within the game *** New method could help high-score chasers trying to avoid game-ending crashes. *** Ars Technica
(*4cfb807c*):: Ya like, hey guys, how about focusing on geopol for 5 min pls (*097dfbf6*):: But I mean, someone has to figure out how to get to level 255 then wrap around back to level 0

#programminchatter

Fri Apr 5 23:37:37 2024 (*097dfbf6*):: https://www.theregister.com/2024/03/31/rust_google_c/ +public! *** Rust developers at Google twice as productive as C++ teams *** Code shines up nicely in production, says Chocolate Factory’s Bergstrom *** theregister.com
(*097dfbf6*)::

“When we’ve rewritten systems from Go into Rust, we’ve found that it takes about the same size team about the same amount of time to build it,” said Bergstrom. “That is, there’s no loss in productivity when moving from Go to Rust. And the interesting thing is we do see some benefits from it. “So we see reduced memory usage in the services that we’ve moved from Go … and we see a decreased defect rate over time in those services that have been rewritten in Rust – so increasing correctness.”

what is this blasphemy *** Rust Nation UK – Track 1 *** Live stream from Track 1 of Rust Nation UK. *** YouTube

(*9f84df6e*):: tranny propaganda (*b05743e5*):: i guess it’s possible, depending on the specifics of the system, both builds, and the dev teams. there are a lot of mediocre Go devs out there (*b05743e5*):: i doubt that Rust can outshine Go in terms of concurrency (*b05743e5*):: but yeah if you don’t know how to write zero- or low-allocation code, then your mem usage and pressure on the GC will be higher than it should be

#programminchatter

Fri Apr 5 23:14:57 2024 (*4cfb807c*):: https://axleos.com/an-irc-client-in-your-motherboard/ *** An IRC client in your motherboard *** I made a graphical IRC client that runs in UEFI. It’s written in Rust and leverages the GUI toolkit and TrueType renderer that I wrote for axle’s userspace. I was able to develop it thanks to the vmnet network backend that I implemented for QEMU. You can connect to an IRC server, chat and read messages, all from the comfort of your motherboard’s pre-boot environment. “Why”? What kind of question is “why”? *** axle OS (*097dfbf6*):: ^ this is so autistic it’s awesome +public!

#programminchatter

Thu Feb 29 20:51:08 2024 (*e065f1ca*):: +public! (*b05743e5*):: typical democrap bs trying to blame the people for any publicized problems (*b05743e5*):: problems which are usually caused by their cronies and/or policies (*b05743e5*):: maybe they are going for the Learn To Code vote lol (*b05743e5*):: (*b05743e5*)::

#programminchatter

Thu Feb 29 14:47:01 2024 (*b05743e5*):: https://atxcf.slack.com/archives/C0129SE0L3W/p1709217878779749 *** Happy 20 Year Anniversary, Peak CPU! *** Happy 20 Year Anniversary, Peak CPU! *** Happy 20 Year Anniversary, Peak CPU! *** Happy 20 Year Anniversary, Peak CPU! (*4297a328*):: Ya I do vaguely remember that the early 00’s is when they were touting the introduction of multicore processors (*b05743e5*):: dual core Pentium marked the peak (*e065f1ca*):: +public! (*b05743e5*):: typical democrap bs trying to blame the people for any publicized problems (*b05743e5*):: problems which are usually caused by their cronies and/or policies (*b05743e5*):: maybe they are going for the Learn To Code vote lol
(*e065f1ca*):: +public! (*b05743e5*):: typical democrap bs trying to blame the people for any publicized problems (*b05743e5*):: problems which are usually caused by their cronies and/or policies (*b05743e5*):: maybe they are going for the Learn To Code vote lol (*b05743e5*)::

#programminchatter

Thu Feb 29 13:54:13 2024 (*e065f1ca*):: +public! (*b05743e5*):: typical democrap bs trying to blame the people for any publicized problems
(*b05743e5*):: problems which are usually caused by their cronies (*e065f1ca*):: +public! (*b05743e5*):: typical democrap bs trying to blame the people for any publicized problems (*b05743e5*):: problems which are usually caused by their cronies

#programminchatter

Wed Feb 28 23:17:02 2024 (*e065f1ca*):: +public!

#programminchatter

Sun Feb 25 23:23:47 2024 (*e065f1ca*):: (*6952cd93*):: +public!

#programminchatter

Sat Feb 24 19:14:36 2024 (*6952cd93*):: damn even Adobe got a version of photoshop running in browser with WASM https://thenewstack.io/webassembly-in-the-browser-matures-and-cool-things-happen/ +public! *** WebAssembly in the Browser Matures and Cool Things Happen *** An anticipated component model will enable WebAssembly to not just see its expanding use beyond web browsers and servers — but will be able to allow users to deploy different applications running inside numerous lightweight modules. *** The New Stack

#programminchatter

Mon Feb 12 02:53:37 2024 (*6952cd93*):: https://www.theregister.com/2024/02/09/it_incident_report_the_clock/ +public! *** IT incident report: The clock that got ahead of itself *** It’s not NTP. There’s no way it’s NTP. It was NTP *** theregister.com
(*6952cd93*):: 2038 will probably genuinely mess some shit up unlike Y2K