http://www.winestockwebdesign.com/Essays/Eternal_Mainframe.h...
Long story, short: We will really have to watch out for our privacy because those two remaining platforms give The Management(tm) an irresistible temptation to stomp on us.
It seems to me if desktop general purpose computing becomes a distinctly minority need, then the future of hardware design will bend towards that article's view. Large scale design and manufacturer of hardware platforms will be (mostly) exclusively towards central servers and to specialized devices on the edge. I expect there's an awful lot of legacy desktop design that will disappear.
Evidence of the demise of desktop computing abounds, but I do hope you're merely being alarmist, not prescient.
Great essay. Please write more.
We're starting to see borderline-draconian privacy and data protection laws such as the GDPR in Europe, and while I question the implementation of that law and how effective it will be, the very fact that a group of politicians covering all of Europe managed to identify a risk and make actual law to try to deal with it is noteworthy in itself.
I suspect what will really make a difference in the near future though is that now social media and "fake news" and other consequences of the centralisation and commoditisation of online communications are messing with elections and our democratic systems. Politicians, even those who might otherwise give big businesses a pass on questionable ethical behaviour, do care about the systems that get them into positions of power, and they care very much about attempts to compromise those systems in ways that might remove them from power. If there's one thing in life that I have found quite reliable under all circumstances, it is the ability of a class of people in power to recognise threats and take steps to protect itself.
I also take some comfort in a few conversations I've had with non-techie friends in recent years, particularly those who are of the younger, digital native generations. It's become very clear to me that while my slightly older generation have sometimes been quite naive about the implications of new technologies, those behind us are much less so. Things like basic steps to stay safer online are taught in schools now. Social media accounts are ephemeral and kids switch to different networks in a way that would make it very difficult for the likes of Facebook to reach critical mass as it has with the older generations. The constant updates and sometimes breakages of software or access to multimedia content are getting old. And again, perhaps most heartening of all, while the younger generations consider these technologies an integral part of their lives and accept to some extent that there are compromises made in order to use them, that doesn't mean they like those compromises, and they will switch away if better options become available.
All of this is probably bad news for the long term prospects of businesses like Facebook and Google (and all the other big data hoarders we don't see because they run their marketplaces discreetly behind the scenes instead of with big public websites on the front). But it's probably good news for those of us hoping the centralised/distributed pendulum for computing is starting to swing back towards the distributed side again, in part driven by privacy, reliability and longevity concerns. The biggest weakness I saw in the article was quite a big jump to the conclusion that embedded and mainframe are the only two natural kinds of computing. I don't see why personal devices -- or rather, running substantial software and doing substantial data processing locally on those devices instead of just using them as essentially thin clients -- shouldn't be on that list as well. The form factors might change, but I don't see it as inevitable that personal computing will revert to being primarily a hobbyist's endeavour. There are some very good reasons it should not.
If the language runtime supports the platform (even bare metal), the AOT/JIT does a good enough job even exploring some vectorization and the large majority of the standard library is available, then it is just an instance of cattle OS.
Which by way, has been the way that those hyper engineered mainframes from IBM (and Unisys) are designed, with their "language environments".
Has this really been the case though? Apps are still very much OS specific. Even Web Apps in Backend are also OS specific ( Linux Specfic ). I just don't see any "mainstream" adoption of high level languages that does this.
With a large enough codebase you'll accumulate some unix-specific logic where it'll be less painful to just develop under linux rather than trying to keep it running on windows.
Of course those pain points are minor and you could write some fallback code for windows, but that code would only ever be exercised on developer machines.
All data should come from databases, which also don't matter on which OSes they're running on.
The web app may be OS specific, but does the OS really matter? Any unixy thing would probably work fine with at most mild effort for almost all backend apps.
Microsoft (Azure) is investing heavily in FPGA based configurable cloud
https://www.micron.com/products/advanced-solutions/advanced-...
One could get a lot of mileage in many areas out of a desktop with a good CPU, lots of RAM, a graphics card for general-purpose use, and one or more FPGA's w/ HLS tooling (or just buy the modules). Especially if the basic components were standardized like the PC with minimum requirements on cores, slices, etc on each version of the platform. An app ecosystem could be developed or emerge with capabilities regular desktops couldn't match.
Basically real time capable microcontrollers that share memory with the mainstream CPU that is probably running Linux.
Allows for interesting use cases, like high speed data in or out to drive LED displays, sample signals, generate audio, etc.
Project that uses PRUs for audio: https://bela.io and how it works: https://hackaday.com/2016/04/13/bela-real-time-beaglebone-au...
Driving an LED matrix display: https://trmm.net/Category:LEDscape
Emulating an old Macintosh SE video board: https://trmm.net/Mac-SE_video
Another sort of "minion core" in Allwinner ARM boards: http://linux-sunxi.org/AR100
Post:- https://news.ycombinator.com/item?id=20766283
Tech use cases :- https://www.upmem.com/use-cases/
POWER is also known for being highly SMT, which could lead to them being even more prone to the issues that plagued Intel's implementation of hyperthreading. A single POWER9 core has 4 to 8 threads.
Or maybe POWER9 is completely secure.
My main point was that Epyc has already proven to be much more resistant to these attacks than Intel’s architecture, and it wouldn’t require dealing with porting your applications to run on a niche ISA, with very limited options to buy server hardware, and very few (if any) options to rent cloud instances on POWER9.
Which SMT issues are you referring to here on Intels?