3 ms·
I assume that the author means "Framework XYZ in TypeScript running on JS running on V8, which is written in C++, compiled by clang, running on Linux with glibc
by titzer 4y ago
I assume that the author means "Framework XYZ in TypeScript running on JS running on V8, which is written in C++, compiled by clang, running on Linux with glibc N, running on VMWare, running on x86, running on the Rapture Cove microarchitecture." I don't know if there are 10 I could name, but stacks are deep.
- deleted 4y ago[deleted]
- diydsp 4y agoYup, that graphics stacks could easily add a few layers for ya! When I was at a gfx card mfr, there were many compatibility and shim layers :)
- swyx 4y agoi’d honestly love a full accounting of those stacks from browser all the way down to transistor. almost feel like we need to record it for posterity in case anything happens to our civilization
- sva_ 4y agoOSI alone would give you 7 stacks
- samstave 4y agoTrue, but when learning OSI in 90s - they were always refered to as 'layers' of the same protocol. Stacks where completely stand-alone applications connected which were not layers of the same protocol/system. I think that the simple way is to refer to them as stacks now, but if you were raised on LAYERS - refering to OSI as 'stacks' feels foreign. It appearsthat as we atomoze / containerize various teck, we now thing of them as 'stacks' rather than layers. It seems that 'layers' are now 'services' rather.
- swyx 4y agoarent many of the OSI layers effectively collapsed? eg TCP/IP has like 90% market share compared to alternatives and effectively function as a single layer. im not sure about the DNS layer but i think theres a case to be made there too