Re:An Object-Oriented Language for the '20s
by protomyth on Saturday March 13, 2021 @09:56AM
(#26446954)
...and steal the Soups from NewtonScript on the way.
[ Parent
| on HN ]
Re:An Object-Oriented Language for the '20s
by mucholove on Saturday March 13, 2021 @10:18AM
(#26447112)
What are the soups?
Both Google and DuckDuckGo give me no results so an example would be appreciated.
(Hope I'm not caught up in a prototype joke :)
Re:An Object-Oriented Language for the '20s
by protomyth on Saturday March 13, 2021 @12:19PM
(#26448017)
Chapter 11-7 of https://www.newted.org/download/manuals/NewtonProgrammerGuid... using the Self influenced language NewtonScript https://www.newted.org/download/manuals/NewtonScriptProgramL...
Re:An Object-Oriented Language for the '20s
by astrange on Saturday March 13, 2021 @05:35PM
(#26450760)
My impression of systems like soups/OpenDoc/component systems/etc is that they're doomed to failure because they don't respect Conway's law. The app model works because each app has its own development team and teams aren't directly editing other teams' data.
They don't have the proper expertise and will break something, because it's not possible to enforce data consistency well enough. (Apple's modern OO database is called CoreData, has a pedigree from WebObjects, and its consistency features are pretty hard to use in practice.)
Re:An Object-Oriented Language for the '20s
by protomyth on Saturday March 13, 2021 @06:05PM
(#26450994)
Soups and OpenDoc have no actual relation. Soups is a object file system and OpenDoc was a component system. CoreData is a poor successor to NeXT's EOF. I so miss EOF.
The only connection to editing someone else's data was the ability to add fields to soups for things like Contacts which allowed an easy expansion. Given how many programs on UNIX can alter each other's data, I don't agree with Conway in the context of the file system or soup.