32 karma · joined August 7, 2019
And aquire/release objects from resource pools that manage themselves. And message queue handlers. And pass-by-reference, and object pools..
Early/mid 19C, with metal-backed currencies, as most of the circulating Silver had ended up there, it was deemed necessary to reverse that flow.
The Opium wars began, to get all the silver back.
I think westerners underappreciate the salience of these events in the chinese worldview.
And which Colony was established by treaty with the chinese defeat ?
Hong Kong.
https://www.bl.uk/learning/histcitizen/trading/story/trade/4...
Just chickens, I hope
To be anti-grandfathered ?
The big iron was a product of large-data-volume business problems - payroll, airline reservations, insurance quotes, credit cards, catalog order stats.
But comp-sci mostly put FLOPS ahead of TPS.
hands up who's heard of data flow programming
Allaire were there with a workable solution, before jsp, php, (?) asp. Iirc only perl was serious competition.
I still sometimes see lotus notes '.nsf' links
that's how you earn your thousand yard stare
now i rent an online service.
the coders behind each of these ventures have different tasks : the first, devising installation and operating manuals for an offline world, the second for a day by day continuous challenge of measuring and updating the service's capabilities and market value
Widget *pw = new Widget(); // heap
Memory is no longer highly constrained
There's a cycle in tool ecology:
- simple useful tool
- adds formats, integrations, config, etc
- codebase is large and change is slow
- the skijump has become an overhang on the learning curve
- a frustrated person writes a simple useful tool
- goto 10
I haven't used k8 but it looks useful for uncommon workloads.
I expect some nu shinyee thing will replace it eventually.