When you explore a problem, use Python and lists/sets/dictionaries/JSON. Wait with types and specific data structures till you have understanding.
Speed of development over speed of execution.
When you know what and how to build commit to good data structures. Do the types, structs, classes, Trie, CRDTs, XML, Protobuf, Parquet and whatnot where apropriate. Instrument your program.
The efficiency of the final product counts.
If you can do a successful switch to cloud only Entra (aka. AzureAD) first, you are 90% ready for a migration to Open Source. You need Entra for Licensing anyway. Yes, I'm aware that this is hard.
Univention Nubus (Keycloak + OpenLDAP) or FreeIPA as alternatives for Entra come to mind.
You can even leverage your Powershell expertise.
They all have a very solid industrial base, like 30% to 50% of the economy, with ~50% of workers living abroad (not fully part of the welfare state). Comparatively high R&D. Low taxes.
And plain tax evasion is now illegal, but those countries are still an important stop to hide money elsewhere.
But the main secret sauce is a flexible fast legal system. Stability, low crime, and less gridlock in the legislature when the need for change is realized.
It's interesting how STREAMS pervaded everything for a short while (Apple's Open Transport networking stack for System 7.5 and up was also based on STREAMS) but everyone almost immediately wanted to get rid of it and just use Berkley sockets interfaces.
I still don't quite get how you should had communicate with the other systems over the network with STREAMS.
With IP you have an address and the means to route the data to that address and back, with TCP/UDP sockets you have the address:port endpoint so the recipient doesn't need to pass a received packet to the all processes on the system, asking "is that yours".
So if there is already some network stack providing both the addressing and the messaging...
STREAMS isn’t a networking protocol, it’s an internal data routing thing some UNIXes use locally, and amongst other things to implement the network stack in it.
You’d still be talking of stuff like IP addresses and the like with it. Probably with the XTI API instead of BSD sockets, which is a bit more complex but you need the flexibility to handle different network stacks than just TCP/IP, like erm…
ZTE is also under scrutiny. The reason it's only Huawei and ZTE is that other Chinese providers are so insignificant that the telecoms will likely be able to replace the infrastructure themselves with spares or consolidation. However, in an emergency, the government would have to foot the bill for replacing Huawei/ZTE systems quickly, as the telecoms couldn't finance this and lack of capacity would mean very high prices.
When you know what and how to build commit to good data structures. Do the types, structs, classes, Trie, CRDTs, XML, Protobuf, Parquet and whatnot where apropriate. Instrument your program. The efficiency of the final product counts.
reply