So in your opinion, monochrome icons are a sign of laziness, rather than an aesthetic choice. Got it.
I never said that. However, I think the entire industry ended up using monochrome icons due to aesthetic, and many practical reasons.
Readit Newswolpoli commented on Icons in Menus Everywhere – Send Help blog.jim-nielsen.com/2025... · Posted by u/ArmageddonIt
wolpoli commented on CM0 – A new Raspberry Pi you can't buy jeffgeerling.com/blog/202... · Posted by u/speckx
In short, it's a Raspberry Pi Zero 2 designed to be embedded into a finished device.
wolpoli commented on Icons in Menus Everywhere – Send Help blog.jim-nielsen.com/2025... · Posted by u/ArmageddonIt
Flat, monochrome icons might look nice, but they are only useful if used sparingly.
If you're going to use many icons, then they need to be visually distinctive. That means ditching the flat designs, and embracing colour again.
Color icons needs to done twice - once for light mode and again for dark mode.
It is the reason for removing colors and shadings from all icons.
wolpoli commented on After Windows Update, Password icon invisible, click where it used to be support.microsoft.com/en-... · Posted by u/zdw
wolpoli commented on Reinventing how .NET builds and ships (again) devblogs.microsoft.com/do... · Posted by u/IcyWindows
> if your source code is based on newer .NET you have to update to a new version each year
.NET has a really refreshingly sane release life cycle, similar to nodejs:
- There's a new major release every year (in November)
- Even numbers are LTS releases, and get 3 years of support/patches
- Odd numbers get 18 months of support/patches
This means if you target LTS, you have 2 years of support before the next LTS, and a full year overlap where both are supported. If you upgrade every release, you have at least 6 months of overlap
There's very few breaking changes between releases anyway, and it's often in infrastructure stuff (config, startup, project structure) as opposed to actual application code.
> Odd numbers get 18 months of support/patches
The recently fixed the friction with odd number releases by providing 24 months of support.
Hacker solution: open/crowd source a pirate camera network. People submit feeds of traffic from whatever camera they have. We build tiny/concealable cameras to plant all over state capitals. Client-side software detects plates and reports only those on the target list. That list: every elected leader. The next time they hold a privacy-related hearing, we read out the committee chairperson's daily movements for the last month.
Other idea: AI-enabled dashcam detects and automatically reports "emergency vehicles" to google maps hands free. Goodbye speed traps.
They just might write a law that makes the act of publicly disseminating travel data for future and past official's illegal.
Video Game asset and source control retention was _terrible_. Hell, it's still terrible.
Prior to ~2010 we were simply deleting source code and assets for finished projects; either because they weren't owned by the developer due to a publishing deal, or because the developers didn't want to reuse their garbage code. Same follows for assets, often they were owned by the publisher and not the developer, but if the developer did happen to own them they'd rarely see reuse in future projects. And publishers didn't catch on to the value of data retention until remakes started to make serious money.
There were a few patches to RA2 through, so the code clearly exists for a bit of time post completion.
wolpoli commented on AirPods libreated from Apple's ecosystem github.com/kavishdevar/li... · Posted by u/moonleay
is there evidence it’s for vendor lock in purposes? airpods have a pretty stellar connection for bluetooth, wouldn’t be surprised if there were performance reasons for them going off spec
Apple is a promoter member of the Bluetooth standard organization for a while now, so it could submit that as an enhancement.
> I look forward to the "personal computing" period, with small models distributed everywhere...
One could argue that this period was just a brief fluke. Personal computers really took off only in the 1990s, web 2.0 happened in the mid-2000s. Now, for the average person, 95%+ of screen time boils down to using the computer as a dumb terminal to access centralized services "in the cloud".
The personal computing era happened partly because, while there were demands for computing, users' connectivity to the internet were poor or limited and so they couldn't just connect to the mainframe. We now have high speed internet access everywhere - I don't know what would drive the equivalent of the era of personal computing this time.