Oil and gas products account for 4.2% of Sweden’s exports. The gas exports alone almost rival those of dairy and eggs! Truly a petrostate if I ever saw one

Well the largest category is

• Machinery, Nuclear reactors and boilers. The nuclear part of this in Sweden is quite small so machinery is the big part. 14%. Second is:
• Vechicles, Other than railway, trans. E.g. the later large Car and Lorrie, Truck manufacturers, Volvo, Volvo Cars and Scania. also about 14% The third is:
• Electrical, electronic equipment, with large companies like Ericsson. 8.7% Then on fort place:
• Mineral Fuels, Oils, distillation products, 7.4% Thou there are no internal sources for this is mostly refining of imported gods.

https://tradingeconomics.com/sweden/exports-by-category

Yet, that is the real Linux phone killer move by the former, Microsoft CEO for Nokia. Also the move that killed Nokia phones.

I agree that in most cases it's more of an E2E or integratiuon test, not sure of the need to split into different repo, and well in the end I'm not sure that would have made any big protection anyhow.

Sais no-one that knows vim, thou it have a vi-like mode that is missing most advanced vi-trixs.

Or in the office, the hardware-software relations between the laptop and Windows and in some parts Linux are strained at best, where drivers, power management, and so on get crappy. E.g. after a year or two of updates, it gets out of control and nice things like hibernations don't work. It's usually a driver for some small thing you don't care about that forgot to read the Windows specification change and now it can't do that power handling in a good way. Oops the computer refuses to sleep and your bag is burning, your battery is 1% when picking the computer up again.

LiveNation has fixed the issue that artists got paid for playing live, not the companies can take that cut as well.

Imho on any server today all editors should be removed. You edit on your workstation and provision to the server.

Because of the geneva conventions about protections civilians.

Attacking a hospital is not a warcrime if the hospital is used for military operations.

It is, you have the right to defend yourself if the opponent is attacking from inside. But no even if the enemy is doing a war crime by using non-combatants as protection you are not allowed to engage them in that situation. You are allowed to inspect a hospital or ambulance to make sure the enemy isn't using it to transport or hide munitions. You are not allowed to attack anything marked with protected signs, such as the Red Cross, red crescent, or red diamond. If you as a solder break these rules, even on a direct order you are still personally responsible and might be judged in national or international courts. In practice, it might be hard to get soldiers to stand trial for these crimes. But it has happened. All my education in this has been in Swedish from the Swedish armed forces so some translations might be wrong.

A good IDE also helps you make better refactoring, making the code so much easier to read. The main goal of any code.

I blame the rise of frameworks, libraries, and IDEs

Without good libraries and frameworks, we can hardly get any software working in today's environment. We get stuck with a slow development cycle and have software that doesn't do what the users want of it. A few years ago, I was at a customer using an old Linux distribution at their customer's site. For contractual reasons that was not upgrading to the latest version, they had skipped keeping up to date with changes as they came. Every step of development became a hassle and the good programmers there were not able to deliver features at any predictable rate. There were issues with HTTPS, most webservers of today mandate at least TLS1.2, but when the OS only supports SSLv2 and SSLv3, and TLS1.1, connecting to the internet, well gets hard.

Having to develop all functionality from the ground up, makes no features needed by the customers ever released. With most developers I have worked with using good libraries also makes the implementations less prone to have serious bugs in them.

It seems to me that the author doesn't remember all the struggles we had back then with bugs and features not working. And masses of needed functionality that never got skipped into the hands of users. It also strikes me that maybe there is a bit of nostalgia, just a bit of reluctance to change his ways. He found a workflow around the missing functionality that might be blocking for others and he has a harder time adjusting to the new functionality.

A bit like my father that refused to change his workflow, to make images for webpages (all static) he used for different Amiga programs because one could scale the images, one could edit them add lines and stuff, one for helping him make image maps, and they one so they could be converted to jpg/png as anim files used by everything else on the amiga didn't work well on the internet.

Bug testing back then was awful, we never had time to catch any issues but the biggest. The time plan for the release was fixed years ahead, the functionality that was needed was fixed years ahead. All the needed time for testing was eaten up by the developers working into the final skip to customers, trying to make the software actually run. It wasn't uncommon for test teams trying to cramp months of eating into a weekend to have the software skipped on Monday morning. Well including masses of needed bug fixes during that weekend that no one knew what code each issue was actually tested on. Remember that software version control system was almost not used, there was no CI build system all all software was built on some random developers workstation. Maybe, with some additional changes for his or her convenience. No software development has come a long way since the 90s. A very long way!