It's nice to have a few hours of peace and quiet, uninterrupted by dumbfuck whinging. It's certainly not enough time to recover cognitive resources and get into serious work ... but it's good enough to get on track for the same, after previous work sessions have been disrupted and the startup overheads for work amounting to hours and days, have been discarded, then having to be reexecuted from scratch.
Every interruption - a few hours, sometimes days. Very expensive. Must reduce. Note to self.
Why do people who like to pick their terminal year, pick 40? Round number?
40 is like, the end of general education, and the beginning of specialisation for some.
Traditionally, in some circles, the end of youth, and the beginning of adulthood.
Personally, when I had made certain paradigm shifts around the age of 21, I figured it would take me till the age of 40 to contemplate the nature of the idea, as a matter of quality assurance.
40 was the expected lifespan of man in precivilisation, half their expected span in modern times, and a third of the greatest known spans.
As the genome progresses. So it prunes. One day, something else will be the norm. We would not recognise it.
/// Napkin sketch for HATEOAS optimisation ///
1. CDN serves landing site + client-side controllers
2. client-side controllers react to client-side input, by dynamically manipulating views, from client-side data, when available
3. when client-side data is insufficient, client-side controllers make API calls to get additional assets and/or data from servers, subsequently updating client-side models, and then reiterating step 2.
Local Note : steps 1. and 3. can be implemented with or without edge-computing, with or without server-side rendering.
Global Note :
Based on public debates ( such as this one : https://www.reddit.com/r/programming/comments/w2nwyy/how_did_rest_come_to_mean_the_opposite_of_rest/ ) it seems obvious that at least half the participants have no grasp of Fielding's original thesis defining REST. This provides some motivation for me to produce an annotation of Fielding's thesis in the future.
IMLO : At some point in the early 2000s, it became popular to speak of REST as being opposed to RPC, CORBA, and SOAP. (Let's be clear here : RPC is the end-game in ALL physical information transfers.) CORBA and SOAP were just special-cases of RPC, marketed by specific industry groups (OMG and MSFT respectively) to standardise RPC ergonomics between parties. REST is an approach to implementing RPC, CORBA, SOAP, etc. - which is given by example in HTTP. REST provides a protocol infrastructure to bootstrap communications about RPC, beginning with fundamental protocol interfaces, which MAY BE ESCALATED TO MORE COMPLEX REPRESENTATIONS. The concept of protocol tunneling is included in Fielding's thesis ... and if you can tunnel, then you can basically do anything. As long as you do it a certain way.
This has been bugging me for a decade now.
Architectures such as Kubernetes allow for the orchestration of heterogenous hardware to run many types of applications using HTT-Protocol. But there's no common architecture that allows for the orchestration of heterogenous hardware to run Linux desktop applications using the Linux kernel's local machine management protocol. Is there?
Let's say I want to spin up six old laptops, on a W/LAN, and have my local kernel abstract over all their CPUs as if they were running on the same machine. (Nevermind for a second, how slow this would be, due to the memory siloes.)
What's the shortest path to coding this up?
