34,207 karma · joined March 2, 2008
http://www.scott-a-s.com
But, in support of your point, it usually does cause the builds to be over-budget and behind schedule.
What I mean is that through training, you learn how to do the sport. That’s table stakes. In order to compete well, you need to learn the skill of competing in that sport. That’s hard, as the practice is competition itself. And it’s a different skill set.
Were you inspired by the Actor model (https://en.wikipedia.org/wiki/Actor_model)? Or am I missing something fundamental?
The top comment links to a bunch of papers.
In my statistical mechanics course, we went through an illuminating exercise where we started by trying to take account of every atom in a gas cloud. We started taking limits and making assumptions. One of them was that all atoms are indistinguishable from each other. This decreases the possible states of the system by N! (factorial, not surprise). After making that assumption, out pops the ideal gas law.
And if they only allow people to compensate artists through cryptocurrency, then it's not viable for artists.
Adjuncts professors teach at American universities on a course-by-course contract basis. These people usually have PhDs. Some would like tenure track positions. But it’s generally a career dead-end.
I suspect your experience is from Europe, and I don’t think it generalizes to the US.
The paper describing my design is "Low-Synchronization, Mostly Lock-Free, Elastic Scheduling for Streaming Runtimes", https://www.scott-a-s.com/files/pldi2017_lf_elastic_scheduli.... The source code for the product implementation is now open source. Most is in https://github.com/IBMStreams/OSStreams/blob/main/src/cpp/SP... and https://github.com/IBMStreams/OSStreams/blob/main/src/cpp/SP....
They won't be mainframes, because as the author does correctly point out, mainframes are unmatched at large-scale, high throughput, resilient, stateful, transaction-heavy workloads. While that is part of what the major cloud providers support, it is not everything. Because it is not everything, the systems the major cloud providers design and build will look different from mainframes, but I think they will have key similarities: virtualization and security features provided by the hardware; high reliability through redundancy and in-hardware error-checking; easy physical maintenance through hot-swappable components.