While this might work in a country that still has some modicum of work-ethic, I don't believe it would work in the US. A few years ago I had a client that had 100's of people on payroll that were mostly just above minimum wage. When they received their Earned Income Credit rebates annually, most of them wouldn't show up for work. Their reasoning was they had money so there wasn't any incentive to work. Company had to change to policy so that they could only receive EIC monthly, so the amount was too small to trigger them to no show up for work. Real world example.

Governments are not going to adopt any currency that has any limit to the amount that they can "manufacture" out of thin air. That's why we jettisoned the gold standard. Bitcoin is limited and it doesn't do small rapid transactions well. Not going to happen.

Rotting DVDs/CDs, LED lightbulbs that don't last, there are probably others. When a company promises something will last X years, why isn't it fraud when that turns out to be untrue?

Or to delete any communications to hide them from FOIA requests.

Use Pumped Storage Hydropower. Excess electricity to pump water uphill during production hours, use water running downhill to power hydroelectric generators during no-production hours. It's proven, clean, and reliable: https://www.science.org/conten....

Just about any time I contact technical support for help on a piece of networking hardware the first thing they ask me to do is to disable IPV6 to see if that fixes the problem. Until many hardware vendors get fully on board with IPV6 this is going to be an issue.

Trees are good carbon capture devices and can produce lumber in the future.

Agreed. It is time to use RICO to go after these people. They are modern day gangsters and that is what RICO was created to go after.

Big brother wants to know where you are at all times and will monetize this data by selling your data to anyone that will pay them.

My post was supposed to be sarcastic, but I don't know where you are getting your numbers: In 2020, greenhouse gas emissions from transportation accounted for about 27% of total U.S. greenhouse gas emissions, making it the largest contributor of U.S. greenhouse gas emissions. https://www.epa.gov/greenvehic....

I should have marked my post as "sarchasm", apologies.

I'm sure that this problem can easily be solved if everyone would just buy one (or even better two) electric vehicles.

If they had immutable cloud backups that were taken hourly even though this person had administrative rights the backups could quickly and easily be restored. Not quite certain where the $30K cost came from.

I learned a LONG time ago that reusing well written and debugged pieces of code accelerates development DRAMATICALLY. Additionally it provides code with less bugs as the building blocks are refined over time. When I can include/import code blocks that have thousands of lines of code into a new application I know that I'm being efficient and my code will benefit greatly. Unless there is a good reason to "rewrite from the ground up" (programming language obsolescence or complete lack of talent in a language) it is best to leave running applications alone. Now refactoring "spaghetti" code can be beneficial, but unit testing and proper logging is a must.

There have been several attempts, but like Java some of the power of Python lies in the fact that it runs as byte code and is not compiled in the traditional sense. If you want you can always isolate routines that would benefit from running as compiled code and call them from Python. Many of the add-on libraries are done this way. If you haven't used Python you will be surprised at how well it runs without compiling.