chikere232

As a way of life, weighing and counting macros also seems pretty doomed to because it's just so much work, but it's very doable for a few days to realign your view of what an appropriate amount of food is, if you're diligent and mindful enough to not have a soda or a snack without thinking

It's not posix, but it's pretty available

mktime() parses the time string which lacks any information on time zones

then the article uses timegm() to convert it to unixtime on the assumption that it was in UTC

also it's about C

Functional programming just seems harder for people to get into. Perhaps it's bad for everyone that people don't make that effort, but it doesn't seem like a conspiracy

They needed to have a locale matching the language of the localised time string they wanted to parse, they needed to use strptime to parse the string, they needed to use timegm() to convert the result to seconds when seen as UTC. The man pages pretty much describe these things.

The interface or these things could certainly be nicer, but most of the things they bring up as issues aren't even relevant for the task they're trying to do. Why do they talk about daylight savings time being confusing when they're only trying to deal with UTC which doesn't have it?

Isn't that just improving the prompt to the non-learning model?

When they start opting me into photo scanning I lose a bit of trust. The homomorphic encryption makes it less bad. The relative quiet around the rollout of the feature makes it worse. Apple's past attempt to start client side scanning makes it worse. Etc...

The net result is I trust them a bit less. Perhaps not enough to set my apple devices on fire yet, but a bit.

What if you're a user and you don't care about searching for "dog" in your own photos, you might not even use the Photos app, but apple still scans all your photos and sends data off device without asking you?

Perhaps this complicated dance works, perhaps they have made no mistakes, perhaps no one hacks or coerces the relay host providers... they could still have just asked for consent the first time you open Photos (if you ever do) before starting the scan.

My impression so far is that they're already in diminishing returns territory. They might just be puppies learning to walk, in the sense of having a fundamental limit to their potential

Your takeaways are good and fit that model

Isn't the causality inverted here? It's trained on questions people have asked before, so that's what it's better at. New logic puzzles illustrate this flaw

If I want to invest time in fixing some junior developer's probably broken code, I'd much rather do it with a real junior developer who has the potential to learn over time and become a not junior developer

Of course that sometimes needs some kind of feature flags for bigger changes, which is a configuration option too, but at least the stable state of the code is simpler and not a nest of code + config that never really changes.

Switches can't seem to figure out that I have a case for every value of the enum I'm switching on, so I need a pointless default: assert(0);

I didn't check if this also breaks me getting warnings if I add new values to the enum but not the switch, but I imagine it does

It's pretty cool, and also an obviously terrible idea as you leave behind all standard tooling

It won't become D and you can probably be fairly sure it won't grow a standard garbage collector and object system.