Bearded hacker from Sweden. Learned M68k assembly on the Amiga in the late 80s. Compiling C on a 7 MHz CPU was slow. Working as a contracting software developer since almost 10 years, enjoying visiting various parts of the software world.
I hang out a lot on Stack Overflow: http://stackoverflow.com/users/28169/unwind, mainly answering questions about C. I love C.
Submissions
Defrosting using low-energy surface heating
betterfrost.com
2 points·by unwind··0 comments
Soldr, an open-source compact soldering station
soldr.pro
2 points·by unwind··0 comments
Saw-Tooth Roof
en.wikipedia.org
15 points·by unwind··3 comments
NonStop 80s Servers
en.wikipedia.org
8 points·by unwind··2 comments
Airoll
en.wikipedia.org
2 points·by unwind··0 comments
PlotJuggler Time Series Visualization Tool
plotjuggler.io
2 points·by unwind··0 comments
The O'Neill Cylinder Space Settlement Concept (1976)
en.wikipedia.org
2 points·by unwind··0 comments
Festool's ExoActive Exoskeleton
festool.com
3 points·by unwind··0 comments
The Worsening RP2350 E9 Erratum Situation
hackaday.com
7 points·by unwind··0 comments
Microchip's new 5-core 64-bit RISC-V PIC64GX
hackster.io
4 points·by unwind··2 comments
XCB: An XML-backed replacement for Xlib
xcb.freedesktop.org
4 points·by unwind··0 comments
RVPC: The 1-Euro RISC-V computer with VGA and PS/2
olimex.wordpress.com
33 points·by unwind··12 comments
STM32 MCU family goes 64-bit with the STM32MP2x (Cortex-A35)
Epic to see that it has "No Man's Land" [0] and really really weird feeling to read the readme. No idea why it's listed as a "17 Bit" title though, perhaps they distributed it at some point but they certainly were not involved in creating it. Source: I wrote it. Fun times.
It's not 100% better, but it cuts out a few tokens which helps readability and moves the significant asterix further left where I think it's easier to spot.
Can you elaborate on how it detects and signals if it runs out of output buffer space? I couldn't see how the amount of available space was even communicated to `fc_enc()`.
Also there some "C icks" (to me, I'm very picky and used to know the standard awfully well from answering many SO questions) that you might want to look into. The two I remember now are the casting of `void` pointers from allocation functions, and (worse) the assumption that "all bits zero" is how a NULL pointer is represented.
As a ultra noob in the art of knotting, I liked this when I stumbled over it a few weeks back. I agree that for newbies it would be even more instructive with smoother flows, I guess they're held back by the animations being photos and not, well, animations.
I also have read their backstory/naming thing [1] several times but I still don't quite get it. I first thought they were related to the historical Grog, but that was a misunderstanding. I think.
Meta: This is a very messy title, it should just be "The minichord: a pocket-sized musical instrument" or something like that. We have the github info in the auto-generated blurb right after the title, after all. Thanks.
Just a few months back I worked in embedded development on a project and there was a physical dongle to unlock the compiler, which was surprising during on-boarding as I've spent years doing commercial embedded work relying on GCC. :)
“The historical significance of JUMPSEAT cannot be understated,” said Dr. James Outzen, NRO director of the Center for the Study of National Reconnaissance.
I'm no native speaker but that is backwards, right? Shouldn't it be overstated if it was a success?
I love seeing new games for "retro" machines, it's awesome that people keep pouring time and love into them after all these years.
I'm not super familiar with 8-bit Atari machines, and found the designation "classic unmodified 8-bit ATARI XL/XE" a bit imprecise. Tried looking up specs on Wikipedia [1] but was unsure what to settle on. Perhaps the original 1200XL would match? Or the 800XL which seems to improve on the 1200XL even though the naming suggests the opposite ... Or the 65XE, or both then I guess since the latter is compatible with the 800XL, but in an updated case?
If my math is right it seems the cost in material for the printed part is around $5 which seems ridiculously cheap for a custom-designed and adapted solution like this. Nice!
I wish the author had spent a few words extra to motivate why it needs to be in PETG filament for "heat resistance", is the regular PLA limit of ~55 degrees Celsius not okay for a desktop accessory? I guess if it's in direct sunlight that might be exceeded, or perhaps if the laptop runs very hot?
I hang out a lot on Stack Overflow: http://stackoverflow.com/users/28169/unwind, mainly answering questions about C. I love C.