Davidbrcz

The same usual issue with making a tech you do not own a critical element of your workflow

I have not heard about HLA for a looong time !

TIL about Emacs' antinews (what would be new if you were to downgrade to Emacs 30) https://www.gnu.org/software/emacs/manual/html_node/emacs/An...

Tree Style Tab https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...

https://lobste.rs/ feel more like old-HN

This is the 2020s re-enactement of the early 2000 WYSIWYG editors.

The best way to learn a new language is to follow a proper structured resource which would cover syntax, semantic, tooling & ecosystem and best practices.

And that's the usual fallacy (just ignore the bad stuff).

But if you work with C++ in professional context, you will encounter it somewhere (library, teamate's PR, legacy code, LLM output, book / blog / conference ...). |

You actually need to know the bad stuff to be able to judge it and discard it.

Python, Java, Lua, Ruby are ~30 years old, Ada being as old as C++.

Sure, none is perfect and they have cruft and warts, but they are not such a mess as C++ is.

No it's not.

The language keeps growing, with

- new features overlapping old features from previous standards without replacing them or deprecating them (function::copyable_function vs std::function, std::less<> key for transparent lookup in maps)

- new features not usable by the layman (coroutines ...)

- Cryptic syntax (reflection...)

- Stuff you are told not to use because of performance reason and that cant be fixed because of ABI (regex)

- Compile errors that are 1km long (no, concepts are not helping here, the 'nicer' message is still buried into a hot pile of template instantiation callstack).

Except the language keeps growing, with

- new features overlapping old features previous standards without replacing them or deprecating them. - new features not usable by the layman - ...

See function::copyable_function vs std::function, modules, coroutines, Reflection syntax is cryptic at best, ...

I was an intern at CERN in mid 2010s and worked on this !

Concepts have been disappointing for me: what they tell you is still buried in 1000 lines of errors.

We are more likely to have water and food shortages because of resource exhaustion and climate change. Maybe goods shortages because of war or economic depression.

More climate disasters, more wars (water's war), more refugees.

> Dissimilar redundancy eliminates that risk. A completely different OS, different codebase, different development team.

Not entirely true. I've heard during my uni years of a case were two independent teams used the same textbook for implementing a feature, which had an error, and thus resulting in the same failure mode.

They are all the regular software, but with new bugs in it !

I use asio at work for coroutine. It's one of the most opaque library I've ever used. The doc is awful and impenetrable.

The most helpful resource about it is a guy on stackoverflow (sehe). No idea how to get help once SO will have closed

Just need to check if it's plain Ada or one specific profile or SPARK

Refreshing stories between all the AI ones (and crypto/web3 before that)

People manually doing resource cleanup by using goto.

I'm assuming that using defer would have prevented the gotos in the first case, and the bug.

You do a cross analysis.

- Compile it with the maximum number of warnings enabled

- Run linters/analyzers/fuzzers on it

- Ask another LLM to review it

For main it's explicitly allowed by the standard, and no return is equal to return 0

Taxes, that's called taxes.

I'm visually impaired: dark mode is about making the web usable for me

https://drgrizz.xyz/dark-mode.html

Yes, I'm working on FAA SWIM services now. The tech feels old school (UML, XSD...) but having documentation, class generation from XSD is very helpful.

That's some Westworld level of discussion

A goal is what, intent is why. And a same goal could be motivated by different intents.

Don't worry about C or C++, we create the vulnerabilities ourselves !