We will see ๐
Lichtblitz
joined 2 years ago
Oh, it can be rewritten and it should be. But it's a very time consuming and expensive process. It may take a long time to amortize indirectly though a system that is more stable, easier to maintain, adapt to new laws, and requires less effort to use and operate. It's not a quick win and not a win in the time frame of one administration - which is why it's usually not considered a high priority.
I'm part of a project that does something extremely close to this in Germany. After two or three years we've barely scratched the surface. The complexity of such a system with the wide range of rules, regulations and best practices is mind bogging. Just reverse engineering the legacy system alone takes years.
If you use much of the software that is included in the support package, then the price seems reasonable. No way you could get the same price if you went to each provider individually. If all you use is bare bones openshift, then you're right.
Don't shoot the messenger. The regulations are pretty draconic. I have to ensure the training for that every year.
As a software dev myself: if time in your application's internals jumps on DST, something has been implemented incorrectly. That's what zone information is for, to make times uniquely identifiable and timers run the correct length. Getting the implementation right is hard, though. So, abolishing DST is very well worth it.
Seemingly one of the contributors has visited a disputed region and logged into GitHub from there. By law (export controls) Microsoft must not provide service to that place. So some automatism flagged the account and also the organic maps repo. So far so normal. But either Microsoft dragged it's feet in communicating and resolving the issue or the organic maps team was not doing their part in the process. Doesn't matter, the outcome is still worth it.
The ship is painted red and a few containers are bolted to it, rather than use provided.
Oooh, that explains so much. I had to switch the provider after many happy years with them and found a new home at Hetzner.
It's the same problem as with any other software development: Politics (literally). Some decisions are made by people who are not qualified to make them. Because of the scale of the project, these decisions affect hundreds of devs across dozens of teams with millions of euros swinging one way or the other. Apart from that, when divide and conquer is done properly, the work of each individual team isn't too different compared to software development in commercial companies. Everything is a bit more relaxed, though. That can be a boon but can also be infuriating if you're waiting for licenses, hardware, or some team to act.