@gsuberland you inspired me to make a quick character alignment chart of „adherence to protocol spec“ vs „adoption defines standard“, hastily made before I lose the momentum 😇
Hobby Embedded Developer, System admin, Cloud operations, Orchestration and such...
@gsuberland you inspired me to make a quick character alignment chart of „adherence to protocol spec“ vs „adoption defines standard“, hastily made before I lose the momentum 😇
Just remembered for no particular reason that a subtle message in „Idiocracy“ was that „the computer“ was deciding on everything business, including firing half the country from Brawndo, and the CEO had no idea why…
Why have Apple and Windows OS upgrades become :
- "You get two new emoticons"
- "You can now make gifs"
- "The mouse pointer is pointier"
- "You can subscribe to get a spell checker"
- "You can ask an AI to do all the above"
Is this list really that much more interesting to people compared to actual OS changes ? Is there some conspiracy to move to a continuous upgrade model by downplaying all core OS upgrades to theme and emoticons ?
I honestly ask because there is literally nothing on mainsteam news sites that can be considered technical excellence.
I have not checked myself into API, ABI, BUS/Memory/Process Management changes as my point is that those parts seem to be completely unmentioned, and this clear focus on things that don't matter is baffling.
ok, I finally watched "Don't Look Up", It is scary how close to reality the chain of events happened in that movie 😅
@grawity as many of all those new terms, these are internal communication meanings… the simplest explanation is the most likely, and the red button means something much less like a feature flag and more a feature removal. As in „we allow to remove the offending feature and we now need to build a new version to see that“
https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW
How to say that you phased rolled out untested, null pointer exception causing codebase, in a vital and global policy system that has also obviously never been benchmarked for time to full recovery - the initial updates had no ETA even though the root cause was apparently known from the first 10 mins - in 5 paragraphs.
And the scary part ? no mention of violations of any coding practices and code reviews, nothing to base a policy system on policy schemata or versions, nor unit tests that would have stopped a phased rollout.
For some reason they picked to announce static analysis improvements ( to avoid null pointer exceptions ), mandatory feature flags ( in order to not have to wait 20-30 minutes for CI/CD ) and modularization ( blast radius control ), which should have been the baseline anyway, no process changes.
Very embarrassing, I hope whoever decided to remove guardrails and took actions to eventually effectively nullify the phased roll out process, presses on the brakes and starts realizing that they need to push for the stability/credibility currency increase once again...
"Successful null release"
TIL that GRUB will freeze if "sysrq" seq is being spammed...
due to some mishandling liquids in a glass based chain of events, my keyboard's ( matt3o's Whitefox - Nightfox Edition ) Alt and Print-screen buttons got stuck, which blocked me from booting my main PC until I disconnected it.
oh well, you live and learn....
@root42 just for your sanity, keep that „Simon says“ tree solution order in a piece of paper ( no spoiler, just something I wished someone had told me back then )
@gsuberland I had a similar case in EU, the seller chose to use DHL instead of normal post ( even though I explicitly selected and noted that on the order ), and as planned DHL wanted to charge me with twice the product value as "customs processing fees" on top of correct tax calculation.
After getting in touch legal support, I contacted DHL and told them I would be the one doing the process in the customs, which they denied due to them "handling the package", I went and did it anyway, paid the equivalent of 12 euro in local currency.
That was a long time ago - more than 20 years ago, and those times personal touch and discussion worked. Since then neither DHL has a contact point that you can figure things out with anymore ( especially these kinds of things ) nor processing things in customs alone after the fact is an option.
I hope all goes well
Some, but not a priority, I am working on a Rust based Atari 2600 emulator for embedded ARM that could be useful but I never found myself at a point that I could not live without SWO.
On the other hand... my toolset is pretty archaic... qemu mainly and only testing sporadically on a real device, but still SWD is good enough for everything I worked until now, promise to ping you if I find a SWO use case.
@whitequark works like a charm, SWD is pretty much what I work with 90% of the time.
Pretty much removed 3 devices from my desk, but most importantly... de-cluttered my tooling config on VSCodium 😍
I just had to configure SWD and the probe on #probe-rs cargo runner config and it happily run a Rust based blinky example on a STM32F411CEU6 ( Black pill ) board.
Thanks again for the hard work ❤️
Having this + uart on #glasgowinterfaceexplorer 's portB as the second applet is such a quality of life improvement.
@whitequark I was using this one until now https://github.com/probe-rs/hs-probe ( STM32F723 based ) just for the sake of principle for supporting the devs.
Unfortunately it never caught on ( is now 4y since their last commit ), and I still run it with some patches that I never bothered upstreaming ( unseting 5V output pin on main loop bug, default gpio states unsafe, and some config issues ).
Time for a change 🙂
Glasgow packs some majestic HW design, and I feel so motivated seeing what such talents of yours can achieve/unlock while using it. 💪
Had some fun fixing a Sony #Minidisk MZ-R70. Apparently it got damaged internally and someone tried to repair the "leg" that keeps the main cartridge holder connected to the door with medical tape.
Unfortunately this seized the door closed but also didn't fix the real issue, which was that the door closed button sensor was not anymore pressed due to the damaged piece missing, keeping the device in a perpetual off state..
I removed the tape + cleaned up, fixed the bends on the magnetic head and bypassed the sensor to bring the MD back to life, works for reading MDs but need to test recording.
Seems like it had a long life and was used a lot, structural fatigue on the corners and the battery holder clips are making it flimsy to open/close + the battery pops out sometimes, but hey, why should I complain ? i can fix those later, it is a working Minidisk 🙂
😍 Supports different voltages as well 💪
The #glasgowinterfaceexplorer is the best tooling impulsive purchase I ever did, thanks for making and maintaining such a cool device !!!
Discovery: The "copilot" bot user that Microsoft will soon be flooding your github repos with garbage content from is implemented in some sort of special way that exempts it from the "block" feature you would normally be able to block other users/bots with
@bagder @thomas thanks for making me aware about https://ieeexplore.ieee.org/document/1702388, very nice read !
Finally had some time to clean up and upload my code for the Micropython + rp2040 Super Famicom/ SNES cartridge reader 😇
https://codeberg.org/xsk/sfc-cartridge-pico
Even though it might not be a problem you have, it definitely worth checking the optimizations micropython can do in order to make things run fast.
Definitely learned a lot, and I can use these learnings on the ZXSpectrum ULA Project 😈