The summary is misleading. The custom HW (Yellow, Blue and Green) aren't Raspberry Pi's. Yellow is built around a Raspberry Pi Compute module and Blue/Green is bespoke HW (form factor) and has nothing to do with the Raspberry Pi Foundation.
Home Assistant is just a python app, that can be run on any suitable platform, including Raspberry Pi's.
Couldn't agree more. It's got fat and lazy, plagued by career seekers stopping by to pad their CV. There is no long term vision. Tech champions that once led the charge, are hesitant invest in Google platforms due to their volatility, which is a problem given Google propensity to bin platforms that don't exhibit exponential growth after a few months. Likewise it's rare to see a Google product manager who is really invested in the app/service for more than a handful of years and the ecosystem is littered with half baked services, and acquisition integration. Nest, Fitbit are classic examples.
Google Workspace evolution pretty much encapsulates Google's journey into mediocrity. Started off as a revolutionary product but has largely been allowed to wither on the vine since it was pushed under GCP umbrella. Google bolts on various services from time to time, without any real support or admin. The ecosystem is disjointed and clunky with paid subscribers unable to access consumer services for unknown or illogical reasons. Consumer product teams can't be bothered supporting Workspace accounts or block features. (Google Family sharing, Nest, YouTube Family plans). And to top it off paid support is useless, having to battle for days through L1/L2 just to get the reps to understand the problem.
Vids will be another failed experiment, for all the above reasons.
System # never featured any memory protection, even with later 680X0 processors with MMU's
It also lacked preemptive multitasking, instead featuring cooperative multitasking.
Logical separation of OS and Application only occured in the filesystem. I was always fond of System # FS simplicity and neatness. The resource and data forks file model greatly simplified the OS. An application would be a single file, containing code, configuration, and dependencies.
A bootable OS consisted of handful of files in a System directory. One could achieve OS upgrades or enhancements by simply dropping a single file. No dependency nightmares.
Applications could be copied or move freely between folders, allowing groups of applications and documents/files to be arranged logically in the Finder, bypassing the need for shortcuts or startmenus. You could insert a disk and just run an application from it.
Sadly that all ended with the arrival of PPC architecture, mac clones and ports of Windows apps.
"Microsoft introduced preemptive multitasking to the "first popular personal computer" in 1987"
You may have overlooked The Amiga 1000 and 500 (AmigaOS/Exec) that featured "preemptive" multitasking, not the "cooperative" multitasking that earlier version of Windows and Apple's "System" OS provided.
As any Amiga user would remember getting frustrated with a buggy apps in Windows or Apple's "System" OS rendering the system unusable with their inferior cooperative multitasking.
Jobs could have technically achieved the same with System #, but his obsession with form over function, missed an opportunity to better Windows IMO.
Glass Windows/walls will typically shatter or deform. This aint going to work reliably, if at all.
What's clear is Google have no further plans in this space. Google obviously doesn't think there's value in a one stop shop.
Google was an accredited ICANN registrar some 10 years before launching Google Domains in 2015, and this acquisition includes the IANA accreditation, not just the service and customers. If you look on the IANA list, Google's registration (895) is now Squarespace, albeit with Google's RDAP base URL.
This was probably on the cards for some time. The service was stale. Not much in the way of new features and long-term annoying issues persisted.
Google has high standards. Where product revenue, value or user engagement plateaus, it's up for sale or retired. Just have a look at https://killedbygoogle.com/
Minimum card spend was a thing. You tended to see it in smaller business rather than larger chains. It's pretty much disappeared completely since Covid.
This move does undermine Google's BeyondCorp mantra to a degree.
The type of consumers who buy Belkin products, care little about security. They walk into your average technology retailer and buy on impulse, going with the most appealing packaging/display. Belkin know their customer base and their desire for cheap, consumer grade, crap gadgets.
That's a certainty. Okta is used widely in Fortune 500. Getting insight into the code base for possible vulnerabilities is very attractive. Just look at the aftermath with Cisco and MS leaks.
Same issue with the CSE for Google Drive and Google Docs. The inclusion of 3rd party PKI provider gives the perception Google couldn't get access, even if compelled, but that not the case. The private keys are handled in Google managed code (within the browser).
In layman's terms, paying for a Safe deposit box but then handing over your key to the bank for safe storage. In Google's implementation, you are trusting Google managed code to use private key only within the browser, but theoretically they could save the key centrally or forward to a government agency if compelled.
One of the drivers for CSE in Workspace is to address data sovereignty, specifically in some sectors outside the US and EU and unfortunately this is a very poor substitute.
Given it's aimed at large enterprises (SKUs) one would hope those looking at this would be mature enough see the fundamental flaws, even with basic due diligence.
Might be true in this frenzied economy. Not so much when it goes to shit.
There is also John Barilaro (NSW Deputy Premier) suing YouTuber FriendlyJordies for defamation and hiding behind Parliamentary privilege.
Cobol programmers are down in the dumps.
