News for hackers. Stuff that matters.
Re:Write Libraries, Not Frameworks by infogulch on Saturday May 09, 2020 @01:34AM (#23122563)
All of which end up getting allocated to a single 56 core cpu.
Re:Write Libraries, Not Frameworks by keanebean86 on Saturday May 09, 2020 @02:39AM (#23122779)
Even the CPU adds at least one layer of abstraction.

Spring

JVM

Container

OS

hypervisor

x86

Real CPU instructions

Electrons

Unknown

EDIT: formatting

Re:Write Libraries, Not Frameworks by dmitriid on Saturday May 09, 2020 @06:03AM (#23123451)
And "EDIT: formatting" is now an additional layer, too :)
Re:Write Libraries, Not Frameworks by majewsky on Saturday May 09, 2020 @10:09AM (#23124810)
That's the layer that's argued about the most. :)
Re:Write Libraries, Not Frameworks by inopinatus on Saturday May 09, 2020 @07:05PM (#23128965)
This process is called “Devops”
Re:Write Libraries, Not Frameworks by gruez on Saturday May 09, 2020 @09:04AM (#23124388)
Are hypervisors and containers really abstractions though? All they do is manage access to the underlying resource.
Re:Write Libraries, Not Frameworks by catern on Saturday May 09, 2020 @09:35AM (#23124573)
A hypervisor definitely is; the "hardware" interface for a kernel running as a (performant) VM is different from the hardware interface for real hardware.

I think one could argue that containers aren't much of an abstraction for the running program itself, though, as you say. The place where containers provide an abstraction is at deployment time/process management time; the program itself has (essentially) the same API whether it's running in a container or not.