Until the OS's that you want to virtualize will not operate well in it. Then you will need to switch.
Don't forget the normal voter who just doesn't want to have more taxes. Even if it means that they will pay more for Internet service.
Americans in general, have a distrust of the government. And prefer to have more personal power even if that means they are putting themselves in a disadvantage. But that way it is their mistake in their lives not someone elses.
Are you implying that my Open Source Grammar and Spell checker is faulty?
Most companies don't.
If it gets to a point where your program is changing its programming language for its code, chances are the entire workflow process will be evaluated, and will be coded from the start up. If there isn't a change in workflow, then there isn't a good need to change how the program is written, and they will just code the legacy system, in the style of the time.
However your Old COBOL or Fortran system is being migrated to a newer platform, the new workflow means a lot of these cool tricks back then may be so simplified down to a built in language class, so that module that took weeks to perfect may be just as easy as x.dothis()
Or if you do go back in time, your grandfather will kill you first, so he can tell those tales at nauseum on how he fought off a mad man at nauseum, which enrages you so much that you just want to go back in time and kill him.
Many high end equipment does have fairly large capacitors to allow enough power off time to do a clean power off.
I remember back in the 1990's some PC Centric folks were looking in a Sun Workstation they were surprised about all the large capacitors that were on the motherboard. In short it gives the system enough time finish its final calculation before the power goes out.
In terms of brain implants, we are at the Peg-Leg level of sophistication. We can offer them a solution that will help with some problems, but it isn't a case where we can solve all the problems.
So something that detects that a seizure will happen then does a pulse to stop it. Will help stop the seizure, but not cure all the problems, as well it may bring in some side effects, because the brain so so complicated.
However for some reason we have been polarized to a point that we really can't judge tradeoffs any more. We want a 100% cure. We want our food to be 100% healthy and fill us up, and meet the taste we are craving, we want technology to Run Fast, Use little power, and be tiny. We want our contractors to be Cheap, Fast and Good.
The fact that we live in this imperfect world, seems to have a lot of people paralyzed to the idea of progress where progress will sometimes means there will be a tradeoff.
Perhaps not as well. If people are following the coding standards for the organization then the code for the most part looks far more similar.
When I am working with a development team, I will tend to adjust my unique style to better match what everyone else is doing. Even if it means doing coding methods that I will normally disagree with.
If the code tends to use a bunch of Goto's instead of Procedures or classes. I will use those GOTO not for my benefit, but for people who will maintain my code later on, so they won't have to change their mindset and debugging strategies to see what the program is doing to do future corrections.
I will go full Object Oriented if the group of people that I am working with do their coding full OO.
My personal style would be more procedural, than OO. Not due to lack of knowledge or not realizing OO advantages and disadvantages. But if I am to code on my own, I code in the way that My Mind handles the requirements, and how I feel would be easier for me to change and fix my code in the future.
I think this method is best for ID based on personal code, vs group corporate code, where a lot of your particular style is hidden.
In terms of a server OS, Linux has good security. The lock screen on X11 in order to keep other out of your logged in session, workstation/desktop usage. It isn't ideal.
the NT Alt-Ctrl-Del is a Workstation thing. Its security is low level to prevent applications from accessing it.
Ethics and Morals are based on the cultural norms.
Taking a bribe is consider corruption in our culture. In another it may be considered payment for expedited services. In America we Tip our servers, the size of our tips are based on what we figure was the quality of the service. This motivates the server to try to exceed expectation. The only difference between this and a bribe is payment after service is performed and not before.
There are the obvious fads. But there are plenty of times where a Fad can endure vs just go away, sometimes it could just be something disruptive that changes its path.
We had the rails fad. Ruby on Rails got rather popular in the early 10's then it just kinda faded away. Technically it was fine, however mobile apps development took over which made Web Applications development seem less popular, so the existing Web Apps were just maintained with PHP, JSP or ASP.NET. The need to try to make an ultra rich interface for web applications somewhat paused, when they realize they just need to focus on the PC, and no longer put effort in Mobile HTML with the new input methods.
OS/2 Vs. Windows 95. There was a lot of buzz around OS/2 Warp replacing Windows 3.1... However IBM really bombed its marketing while Microsoft did a stellar job.
During our careers I am sure the best of us, had jumped onto the wrong fad, or made a bad choice. Then the next time you didn't change your criteria and you made a good choice.
However the real question should be. As the parent pointed out What does it do, and will it actually benefit me/my organization.
There is nothing simple about ethics with international business.
Things that ethically right in one culture can be a huge issue in an other.
Many European countries have laws about Hate speech.
The US has against with Pedophilia.
In some countries bribes are just part of doing business. In others it is quite illegal.
Countries will tax you for things that other countries would consider as overstepping bounds.
Some countries lets things go by without legal controls that others find monstrous.
If you are going to be doing international business, you need to be sensitive to your own ideals, as well as the ideals of your new customer base.
Our American Ideals of nearly full freedom of speech, vs. Turkey ideals of limited speech. Are clashing. So if Zuckerberg just said no. They will not operate in Turkey, and the users will be loss of a medium to spread the areas of free speech that they do enjoy. If Zuckerberg agrees then Facebook stays operational, and while taking heat from the culture who doesn't like to see any speech censored, is allowing the culture to have better tools to share the free speech that they are entitled too.
Especially now that most of the data is transmitted digitally. This was a necessary evil before digital distribution, because an analog signal took up a full bandwidth having too much will cause interference. With the data being distributed digitally a lot of competition can go across the same pipeline without affecting the other. TCP/IP is kinda neat that way.
IT security is about tradeoffs.
The idea of 100% security while possible, it impractical.
Your argument about Blackphone is the fact they are not supportive of the OSS mind set, So you judging the quality of the technology based on what type of license it has.
Ok a flaw was found, and they put in a fix for it, what else do you expect from them?
There is an art to programming. However I am more of a visual person I tend to compare it to painting. Where I use Mathematics, Logic, and understanding of the Systems engineering to replace brushes, paint, and understanding of the textures of the material.
When you teach someone to code, (especially from a non-coder) it is like showing them how to hold a pencil, and write some letters, and words. It will take experience and working with real coders to learn the finer arts to programming.
It isn't about knowing how to do the actions... But how to put yourself in the mindset to create.