Fascinating stuff, I've never really thought about what problem e.g. frameworks are solving. It's kind of too bad that in my day job my head's in the clouds and usually somewhat removed from most of these system level details.
inb4 it's just someone else's computer -- trust me I know
What they solve is that they are not just shared libraries, they include any other resources the library needs like translations, images, other data etc and for developers any header files.
But it works if you just treat them as shared libraied - just use -F on the compiler anlink rather than -l and the headers are not needed in /usr/include etc.
The are also versioned so easy for two apps to have different versions of the Framework.
Minor clarification: two apps can embed different, incompatible versions of the same framework without versioning — the versioning is a NeXTism that allows the system vendor to ship a newer, binary incompatible version of the framework.
NeXT used it with AppKit for a few releases, but when they came to Apple they realized it would be impossible to support something like Aqua with the desired UX without having to update all the versions of the framework every release, which would defeat some of the purpose, not to mention exploding the QA matrix.
True for Apple/NeXT Frameworks or others used by a lot.
I think versioning could work if your framework is not used by many apps - the link structure and version number is still there but I have not tried for 20 years.
The correct current practice is as you say to embed the framework in the app at build time so you don't link to outside non Apple Frameworks.
Primary cooling could be molten salt or liquid metal but unless you take the power out through the Seebeck effect like RTG’s on space probes, you still need water to make steam for turbines, I guess.
To me this is the weirdest thing about Pantone the company, their products etc: so much trouble to try to make sure that for a fleeting moment some knick-knack produced half a world away looks like it did on the designer’s expensive monitor. Then, time happens.
Is the world better off than if we just eyeballed it?
I was a consultant working on two Meego projects at the time, fancy mechanics and some pretty interesting ideas about graph data storage and inference. Super talented crew of diverse hackers, kind of a tech head dream project thinking back on it now. This all was such a gut punch. I always thought they should have just rallied behind their own OS, but I don't claim to understand the business all that well.
(edit: a highlight was getting to meet Dan Ingalls once; he was cool)
It is probably caused from postmortem culture not being shared in the community.
"Having problems" in this world (any kind, not only due to the github scale!) is something that happens - we are not perfect and we work on an incredible amount of layers of complexity.
It is sufficient to actually touch production code on a daily basis to see that it can happen to the best, with the best observability systems or processes. The key is avoiding blaming, and understanding iteratively how to fix the problems underneath (faster recovery, detection time, and so on).
Got a big chuckle out of them describing server-side rendering as this new-fangled unproven technical risk of a technology :) I get the context, but it was still funny. Ah, back to editing index.php I guess.
Sorry to be the “actually…” guy here, but actually… what the article describes is ISOMORPHIC server side rendering, which is very different from traditional SSR + client side dynamic behaviors.
The fact that the same code can render the initial static page AND the dynamic client interactive UI is the point here.
Me too. This regularly reminds me that some folks don’t have full stack experience and are coming from a completely different background. I am subsequently much more deliberate in describing architecture these days to front end devs.
It’s certainly nothing new, but the “buzz factor” impresses people who don’t know what it’s for and they implement it everywhere thinking it’s an improvement. The trend/gimmick culture in frontend is a real thing.
inb4 it's just someone else's computer -- trust me I know