Home > OpenStep, GNUstep > The Road to CoreObject Part 2: Why Bother? The Road to CoreObject Part 2: Why Bother? Thom Holwerda 2007-08-02 OpenStep, GNUstep 4 Comments “Since the last post, a lot of people have asked me ‘why are you doing this? What advantage does it actually give?’ In this post, I’ll try to explain.” About The Author Thom Holwerda Follow me on Mastodon @firstname.lastname@example.org 4 Comments 2007-08-03 9:29 am puenktchen sounds like a combination of the persistent object store of the newton os and the enterprise object framework (eof) of nextstep. interesting, but i don’t really get it. 2007-08-03 9:49 am marafaka for a post-desktop interface one would expect that the desktop paradigm is ditched, right? Concepts like document, folder, button, scroll-bar etc don’t necessarily mean anything to musician, mathematician pilot or a kid, but they all use a computer. People naturally understand language, handling language abstractions is the easiest for us all. I understand there was a need for paper and dashboards as communication means before the invention of the internet, but we should slowly forget about that. No modern interface tries to emulate paper or dashboard any more. 2007-08-03 12:22 pm blablabla That is only true if you consider a document as a static collection of strings. A document can perfectly describe a music composition on which different services can act to actually perform the playing or add effects. 2007-08-03 1:15 pm marafaka I was talking about the interface, not a document. And I see no purpose in calling a MIDI, game binary, registry, mp3, script, database or any other STATE other than document a document.