RandomMarius

Correction, Dear ImGui doesn't count as "zero frameworks"... Let's call it merely a lower-level framework. ;)

I never thought it would come full circle, but here we are. I've helped develop and huge UI application in C/C++ using basically zero frameworks (Used ImGui) and is being used productively by many people and is stable. It runs on Mac, Windows, and Linux. But have also got it fully working on Wasm64. Anything less than WASM and it would have buckled under the load. It's beautiful on Web.

A few years ago one would have thought that it would not be worth the pain to develop it in C, now with AI that is no longer a concern as well, and we're so glad we did not compromise.

But can it run DOOM?

My Pulsar mouse has an OLED display on the underside, DOOM could work... :P But it won't be able to use the firmware, neither would my Gaming Gear OP1.

I already have 2 Keychron HE TKL keyboards, both configured and used under Linux, and it was such a breath of fresh air to configure. I'll definitely consider their mice in the future.

I learnt this distinction only in my 40s. The problem is muscle memory now. But all I do is after I do my first loop, I undo it and undo it again, looping it in the opposite direction. If I untie my shoes I'm less likely to undo that loop. So I can just retie with muscle memory.

I used to hate shoe laces becoming undone multiple times a day... now I tie them and they literally last YEARS.

Running a 3 monitor setup on both Wayland and X11, the displays are wildly different in DPI. In the past I’ve reverted to X11 simply to have Slack screen sharing work, but recently I’m staying on Wayland due to better DPI handling in our production app.

Slack screen sharing works when I share my screen twice, and then Slack sometimes crashes. Google Meet and Zoom screen sharing has always worked well in Wayland, so I imagine they will fix this. I’ve also been able to use OBS to do screen recordings, but the easier default application does not work.

It’s definitely becoming better, and forcing it as the default is what was needed. It took 17 years because nobody used it by default.

"CSV" should die. The linked article makes critical ommisions and is wrong about some points. Goes to show just how awful "CSV" is.

For one thing, it talks about needing only to quote commas and newlines... qotes are usually fine... until they are on either side of the value. then you NEED to quote them as well.

Then there is the question about what exactly "text" is; with all the complications around Unicode, BOM markers, and LTR/RTL text.

People who stress about people who stress about linting… focus on something else. Everyone has their idiosyncrasies.

A lot of great coders have psychological oddities. Some things help them focus. Whether it’s neat environment, listening to music, consistent code formatting.

I listen to them and try and accommodate even if I disagree. I’ve changed my mind about several topics multiple times now. I felt strongly about some at one point over the past few decades as well.

I've mostly been cloud free this way. I do send (sometimes encrypted) backups/copies elsewhere, but those are exceptions. And it works well across many client devices (and remote via DNS/forwarding).