533 karma · joined March 1, 2021
That should work as a brute-force method. You could simulate lighting conditions by measuring the reflected spectrum of different materials and multiplying with the spectrum of a light source.
Check out the CIE XYZ color space and its color matching functions. It's the standard for defining/converting color spaces and calibrating displays for accurate color matching. It only models human perception, and contains colors that are physically impossible to reproduce.
Hiring a team of subcontractors carries risks unless you babysit the whole project.
Changing the default demo is a reasonable and actionable suggestion.
"Tony pioneered the famous red-and-green squiggles of Microsoft Word, empowering millions of users with a spell-checking revolution."
Their arguments are mostly addressed by proper, clear attribution. "My sister helped with my homework essay" deserves distrust withour further clarification.
Comparing LLM usage to lying is a fun perspective, but most of the lying happens in attribution. Their moral against lying also seems silly.
Extending applications without having to launch a full agentic IDE. Macos is already very well equipped with GUI automation tools.
You're up to something, maybe they really have a broken pseudo-window with basic UI interaction hacked on top.
Apparently there's a new fancy slider for making it more (but not completely) opaque? Did I miss an option for turning it off?
Searching about common Windows issues results in misleading blogspam. Suggested "solutions" resemble blindly applied folk remedies.
I'm no stranger to breaking my desktop Linux after an hour of misdirected troubleshooting and desperately messing with core libraries. I'm still glad I can quickly find my way to ArchWiki.
Getting indoors from a cold rain is an obvious choice. I can't really decide to stop shivering, but changing my clothes and grabbing a hot chocolate helps. It still takes a while to warm back up, meanwhile I can actively choose not to open windows or go right back in the rain.
I think such forms are a direct downgrade from providing an email address.
- Responding to the submissions likely requires email anyway
- Impersonation/spam is even less difficult
- Sender isn't guaranteed to get a record of sending the message
- A faceless form with unknown machinery feels like sending messages in a bottle
We can't just guess the recipe's teaspoon standard and blindly convert everything to mL.
Why not just offer a monthly subscription "service"?
Logging transactions on the go demands the interface to be rapidly accessible. Touch screen typing is error-prone and slow. I'd prefer a dedicated interface where I could just tap one of the available categories and enter the sum with a large number pad.
It'd make sense to primarily synchronize data from their online bank account and then ask the user to clarify/categorize unknown events. Obviously an online sync is hard to implement for all banks, so a TSV import would be a bare necessity. My bank has integrated financial tracking nicely in their mobile application.
Qalculate handles physical units seamlessly, which makes everyday calculations an absolute breeze. It definitely has an overkill amount of features, but they're not a distraction.
I have a strong dislike against setting the language of my OS, or most applications, to Finnish. Application translations are extremely inconsistent, sometimes even nonsensical. The absolute worst case is seeing only translated error messages without error codes. It's nearly impossible to search help or follow step-by-step guides.
I definitely should improve my knowledge of "proper" Finnish IT terms. Some of them have very intuitive meanings:
- hashing -> hajautus: (chaotically) splitting, scattering things away from each other