1,495 karma · joined March 5, 2013
I want all the colors, including "semantic highlighting", that is, each variable scope getting its own color.
I think the difference between highlighted colors, rather than the specific colors themselves, is what helps me parse code.
I'm glad the wobbly windows desktop effect has stuck around too: absolutely unnecessary, but it's silly and fun.
My biggest complaint has nothing to do with KDE itself, but the fact that GTK apps are so ugly by default. QT apps look fine in GTK desktop environments though. (At least KDE has easy built-in settings for handling GTK theming these days...I remember it being more of an issue a while back)
These being:
- Eddy sensor (for faster bed meshing, eddy-ng addon for Klipper adds auto z-offset)
- Mainline Klipper/Kalico (required for eddy functionality)
- Some motherboard fan replacement mod (the default is tiny, noisy, and always-on)
Of the others listed:
- Bambu printers and the Elegoo Centauri Carbon have locked-down firmware (possibly with hidden license violations).
- I think the only Prusa machine with that build volume is the XL, which is out of the price range
- The Creality Ender 3 V3 KE is okay, but the build volume is 220x220x240mm
I've lately been pretty deep into 3d printing, and basically all the software has Python...and breaks quite easily. Whether because of a new version of Pip with some new packaging rule, forced venvs...I really don't like dealing with Python software.
I bet JSON would allow hanging commas if not for Jscript.
And it seems like the package resolution is finally local by default, although that requires a 'virtualenv', which seems to be a legacy of the global packaging system.
I see the current state of web development as a spiral of complexity with a lot of performance pitfalls. Over-engineering seems to be the default.