It used to be C++ would be the last choice for embedded...

Modern C++ with constexpr and friends and the massive work and cunning they have put into avoiding template bloat....

...C++ is now my first choice for embedded.

It's part of a compiler ecosystem. ie. The front end is shared.

See clang-tidy and clang analyzer for example.

ps: That's what I like most about the core guidelines, they are trying very hard to stick to guidelines (not rules) that pretty much uncontroversially make things safer _and_ can be checked automatically.

They're explicitly walking away from bikeshed paintings like naming conventions and formatting.

The core guidelines aren't as subjective as other guidelines but they are still subjective. There is plenty of completely sound code out there that violates the core guidelines. Not only are they subjective, but many of them require someone to think about the best way to write the code and whether the unpopular way to write it is actually better.

I know compiler front ends can be and are used to create tooling. The point is, you shouldn't be required to implement some kinds of checking in the course of implementing a compiler. If you use a compiler, you should not be required to do all this analysis every single time you compile (unless it is enforcing an objectively necessary standard, and the cost of running it is negligible).

Skip the "Russian" bit, down rank _all_ sites associated with disinformation.

Can you expand on how you would define disinformation if it were your job to down rank sites associated with disinformation?

It's of course impossible to do that, which is why it's a bad idea to pretend you can.

Nah. Unless it's a social call, the video stays off in our team.

In the Good Old Bad Old Days...

The South African Rand Note had the words, "I promise to pay the bearer, on demand at Pretoria, one Rand" and had the facsimile of the signature of the Governor of the Reserve Bank at the time.

I don't know of anybody who made the trip to exchange one. But by the time I could read that and understand it... you wouldn't of got much gold!

Logs are there for those WTF!? Moments. When something unexpected happen and you don't know what. When you need a clue any clue.

Logs are there for observability, so you can get those, "Oh wow! Cool!" moments when you see something that you never knew.

If you never make a mistake, or if you know your external systems and uses perfectly.... Don't log.

If you're a mortal that gets surprises... log.

Don't care. Want my morning time back.

I hate Morning Losing Time.

I hate 5:30 sunsets. A few hours from here are 4:49 sunsets which I'd super hate.

...the History of the History of Lisp threads.....

The next time someone posts a History of History of Lisp threads[0], we can officially begin tracking the History of History of History of Lisp threads :)

----------------

[0] likely in another History of Lisp thread!

And there is the core difference....

For some socialization is stress relief.... for others, such as myself, it's stress.

Asshat bosses want bums on seats in plague pit openplan offices even if #WFH is eminently possible and as someone over 60 even vaccinated I'm still more at risk than I'd like.

If I was more financially secure I'd resign in a heartbeat, so looking around for a remote job.