Off topic: The pandemic has been wonderful for my gi tract.
Constipation driven by office bathrooms problems where a regular concern. I would really try to time bowel movements so that they would happen at home. And would get constipated if I missed my window.
Not having to worry about this has been a huge quality of life improvement.
I picture the peak when the moons of Jupiter are full with a thriving civilization. One trillion strong under one government. Building the ships that take humanity to other stars.
I can't see the US ever adopting a single payer health care system. However I do think they could adopt a health care justice system.
The US cares a lot about justice, and free markets. Some kind of well funded, and empowered FBI system for ensuring citizens get fair value for the money spent.
The quote here is the main point. "But if you want to engage with 20+ exchanges, to go to market quickly, and implement continuous performance tuning, you'll choose Java."
The amount of changes you need to make due to customer preferences and regulations is continuous. If it's ok for your system to run in the 100 microsecond range then Java is a clear winner. If you are just focused on a single exchange, running in the same rack as the exchange then of course C or lower is what you will want.
I just wanted to add an another perspective. I had a great private office with a door that closed, and a quiet work environment. My home office is also a nice dedicated room and well equipped.
Even in the quietest office noises would get to me. I would always have to fight to focus on work. At the end of the day I was spent.
Working from home full time, even with my family here 24/7 has been incredibly relaxing. I really, really don't want to ever go back.
I'm amazed at the number of developers who can't seem to cope with working with custom in house frameworks. I'm talking about fully working systems, with full source code and being walked through the code by the author / maintainer.
They fall apart, constantly complaining that the approach is non standard, deprecated, dangerous, unprofessional, untestable.
So we are trying more and more to use frameworks, just to be able to hire more easily.
It's more back to the mainframe model of software development. I did this back in the 90s and I never had to think about scaling. Granted these were just simple crud / back-office apps.
But I can see how it would work for most modern software.
After writing any code I run the program to test the change I have made. I make sure the code is exercised either by logging, debugger, or clear UI change. If it's a browser app I use multiple browsers, if it's a rest service I make the rest call.
But I have known some developers that write a unit test, but never test the actual change! And without fail serious bugs appear. Like the application fails to start, or crashes when the new feature is invoked for the first time.
I feel the change that has happened is that managers _had to_ figure out managing remote workers.
Before when remote work was not 'working' you could fall back to in person. That is not currently an option. So management has been forced to figure it out.
To me I simply have never seen this before. I remember SARS, and H1N1. There was a big media blitz about both, but that was it.
With this I am seeing cities / countries on lockdown. I have friends that can't go home in Italy because of the lockdown. My own government (Canada) has asked us to prepare for pandemic, and we only have a handful of cases ?!?
We worked in offices because it's the way we always did it. But we now know we don't have to.
It reminds me of post World War 2, where women were expected to just return to their previous lives.
There will be a big push to get people back in the office. But companies that embrace remote work will be more profitable.