Jajcus

My experience with C++ was when C++ was a relatively new thing. Practically the only notable feature provided by the standard library, was that unholy abuse of bit shift operators for I/O. No standard collections or any other data types.

And every compiler would consider something else a valid C++ code or interpret the same code differently.

I am little bit prejudiced since then… and that is probably where the author is coming from too.

Then things were just getting more complicated (templates and other new syntax quirks), to fill the holes in attempts to make C a ‘high level language’.

Poland and probably most of Europe. You don’t need a car here for everyday living, so there is no point in giving licenses and care to kids.

Not that easily and cheaply as they used to be.

Doesn’t sound like the ‘cheap small computer you can run your hobby electronics project on’ that the original Pi used to be. It is not as cheap and a power hungry beast, still small, though. More and more like a PC and less and less a small cheap embedded platform. For some people it is a plus (I guess for most people here), for some not so much.

I tend to build my projects on Raspberry Pi Pico now, but sometimes I would need something more powerful and Raspberry Pi 5 will be too much.

If working with currency use types and formating functions appropriate for currency. Not float.

Jira was ok until they dropped self-hosting option. Why should I keep internal development data at third party server?

Other Atlassian software, though… oh, what a mess. And it only was getting worse with any new release. I am glad we have dumped it all.

And a lot of users’ frustration, especially on more niche platforms (Linux, ARM, etc.) - things look much better on release when the code have been regularly compiled and, hopefully tested, on all platforms, not just the one the lead developer uses.

I know Restic before Kopia and made a set of systemd units to run Restic backups on my home server and office workstation (both online 24/7).

Kopia seems much nicer for a regular user, so I use it on my and family laptops. I used to use Duplicati there, but that project seems dead.

Restic or Kopia, both to Backblaze.

Raspberry Pi is based on smart phone chips, very specific chips from one manufacturer. Raspberry Pi Foundation is not the main customer for this manufacturer and chips used for Raspberry Pi are not their only product – and now, during the big ‘chip shortages’ and supply chain problems other customers and other chips are given priority. There are no (or not enough) new chips for Raspberry Pis so there are no new Raspberries, so availability is dropping and prices are soaring.

I guess the same is true for most other SBCs.

For my hobby projects I switched to Raspberry Pi Pico. It is not a SBC, you won’t run Linux on that, but it is a very capable microcontroller board which is enough for my needs. It is way cheaper much more available. And I won’t look back – it occurred to me that things are much simpler when there is no whole OS on my devices and everything the device does is in my own code.

There are no problems with Pico availability, as it is based on a simpler, custom chip, designed by Raspberry Pi Foundation and manufactured for Raspberry Pi Foundation – they are no longer dependent on a single supplier.

I think Java ecosystem is more about ‘best practices’ (in the most enterprisey meaning) than common sense and good coding. That is why everything in Java gets so over-enigeered. Abstraction over abstraction. XML, SOAP, beans, factories of factories at every corner.

At least that is my feeling, as an sysadmin (fluent in some other programming languages) who occasionally deploys those monstrosities.

Compare that to PHP apps. They also tend to be a mess, but in a completely different way. No ‘best practices’ are common here. Just a pile of spaghetti code, that does the thing it is meant to (until it doesn’t).