chikere232

This works in regular C as sizeof() is a constant expression, but perhaps that was your point?

Very true.

Get backups

If you want to write D, write D.

C is fine without these things

Not to take away from the possible usefulness of constant functions, but it's amusing that the article example of `sum(5,6)` would work great in C if written as 5 + 6, or done as the equivalent macro

You could use whatever preprocessor you like really, just add a make step that translates your template into c. I've seem some crazy person use M4 for example.

It's usually a bad idea, but very feasible

People learn the ordering. If that is their biggest hurdle learning C they have a blessed life

Also, usually it's pretty rare to have things internal to one C file that need explicit prototypes. It's easier to just put things in the right order so the funtion definition etc is before its use.

That's pretty cool, but also, get version control

You might benefit from make, as you wouldn't need a full rebuild every time, or have to spell out every step.

> Makefiles are a good example. Every makefile author must write their own functionally identical "clean" target. Shouldn't there be an implicit default?

At some point you have to give the system something to go on, and the part where it starts deleting files seems like a good one where not to guess.

It's plenty implicit in other places. You can for example, without a Makefile even, just do `make foo` and it will do its best to figure out how to do that. If there's a foo.c you'll get a `foo` executable from that with the default settings.

Let's keep "cmake effect" for "trying your best to not have to touch the language and repeatedly looking for something else whenever you do"

It's a very microsoft feeling pile of crap

Practically it has kinda converged, though not necessarily on a global optimum. Most coding is done in relatively few languages.

This would be an overengineered version of "I set my watch early so I'm not late" except that they argue that all watches should be set early, making it fundamentally pointless

12:00 meetings now start at 11:59:30 and you're still late

Get a seconds precision watch if you care about seconds level accuracy

MS DOS choice of / for commandline arguments and \ for paths always hurts my eyes

The metaverse was obviously worse. It's already proven that you can build bots good enough to keep some people engaged, and keeping people engaged is good for ad-revenue. It's not as likely that people would like to spend most of their day with a VR headset on, working in a cartoon office.

That is very doable as a groupchat or a private mastodon or lemmy instance. Invite your family and friends, don't federate with the wider fediverse.

Control-tab can be set to cycle through tabs in recency order rather than the bad apple default of "go to the next tab to the right".

It has far too much feature bloat though to the point that it's somewhat brittle, and I'd imagine there are many more lurking security issues

it can be a team decision, but it's a bad one

You should worry though if a helpful tool only seems to do a good job in areas you don't know well yourself. It's quite possible that the tool always does a bad job, but you can only tell when you know what a good job looks like.

Local search indexing is somewhat more defendable as a system level service, but yeah, it would be nice if that was also up to me as a user.

Why make it extremely hard to disable? Photos is hardly a system level app

As trivia, on mac os, the photoanalysisd service will run in the background and look through your photos, even if you never open Apple Photos. It can't be disabled unless you disable SIP (system integrity protection) which requires a complicated dance of reboots and warnings. It will reenable if you turn SIP back on.

It seems Apple are very passionate about analysing your photos for some reason, regardless if you yourself are.

To give you feedback in your role as Apple's advocate:

"we had to sneak it out because people wouldn't consent if we told them" isn't the best of arguments

The nearest neighbour search is sharded, which apple's blog admits is a privacy issue, which is why they're running the DP and OHTTP parts.

If apple were to add additional clusters that match "sensitive" content and endeavour to put them in their own shards distinct from landmarks, they defeat the homomorphic encryption part while still technically doing it.

The DP part can be defeated with just statistics over time; someone with any volume of sensitive content will hit these sensitive clusters with a higher likelihood than someone generateing noise injected fake searches.

The OHTTP part can be defeated in several ways, the simplest of which is just having a clause in a non-public contract allowing apple to request logs for some purpose. They're paying them and they can make up the rules as they go.

Oh yeah, the well known "blind trust" model of security. Never verify any claims of any vendor! If you don't trust them, why did you buy from them?!

you're splitting a very fine hair while ignoring the larger privacy implication of the feature. So the timestamp might or might not be delayed a bit from being perfectly accurate? So what? It still is data approximating when the photo was taken, even if the resolution were as bad as "within a few days"

> But renaming symbols throughout large projects without an LSP? Nah, been there, done that, for decades, and I'm glad that's over.

It sounds nice; although even with basic emacs: change the definition, compile, step through the compile errors macro-replacing. It's pretty fast and not really common.

Non-compiled languages suck though, but you shouldn't use those for big things

I tried new languages almost daily for Advent of Code this year, with just syntax highlighting (if it was easily available). Not getting little pop-up suggestions wasn't a blocker.

Some languages like haskell where there's a lot of underlying philosophy different from other languages was hard, but it wasn't hard because of things an IDE would help with.

It's syntax emphasis. When skimming it's easier to find a variable if variables are somewhat distinct in colour and so on.

Besides, things being a bit pretty is nice.

Isn't that you feeling superior because of your tool preference?

It's quite possible to know about a tool and still not like it. Some people liked microsoft's Clippy, and some other people didn't and it's hard to say that either of them were wrong in what made them moste productive, respectively.