Go disliking is due to its syntax not semantics. Go as a dynamic language runtime platform will be interesting; the platform defines the semantics and languages define syntax.
On similar lines, Fable [0] project recently announced rust & dart runtime support making F# a very attractive choice.
Thanks! From the benchmark report [1], it is not clear how much of the baseline wire performance is observed, the numbers in the table are anywhere from 30% to 90% of plain wire bandwidth.
As there are multiple overlay projects popping up - Tailscale, NetMaker, OpenZiti, NetBird, Nebula, ZeroTier, EVPN, etc, we should consider a baseline benchmark index, like [2].
P.S. We have been testing ZeroTier for VPN access and observe ~70% baseline wire bandwidth.
That is the irony. Only pixel hardware provides one step OEM unlocking in US. All other devices are carrier locked and have restrictive unlocking process.
Samsung/Motorola/ etc. should release OEM unlocked devices not just carrier unlocked that can be purchased directly from their online stores.
This will make adoption easy for these open Android projects.
Current reactive code is littered with async/await for every IO function, which feels like they are trying to bolt reactive behavior. Library-based threading model provide the sync thinking with optimized async compute model.
"SE vendors are joining hands with Google to create a set of open-source, validated, and ready-to-use SE Applets."
Is this a Google specific program or part of AOSP ?
For security critical applications, there needs to be a vendor-neutral program build upon open standards. Can another OS vendor provision attestation keys ?
GlobalPlatform [0] has standardized the SE space, general adoption of APIs is the next step.
K8s forced industry to have a consistent open cluster API that will drive innovation and competition.
We can have multiple implementations of the same API, but what I am seeing currently from the "commercial" vendors is the base K8s with UI changes. I hope we will have multiple implementations of the spec. The specs also have to evolve with time.
Last decade, systemd had its fair share of criticism. But it provided a consistent API to run "Compute Units" locally. K8s can benefit from the same principles to manage "Compute Pods" across the cluster. The concepts of promise theory [1] provide interesting control loop co-ordination.
https://www.wordperfect.com/en/
https://www.softmaker.com/en/
https://www.infomaniak.com/en/ksuite
https://www.group-office.com/
https://www.icewarp.com/
https://www.bitrix24.com/
https://fengoffice.com/
https://www.hancomdocs.com/en/
https://www.larksuite.com/en_sg/
https://www.polarisoffice.com/en/