Naked objects
by Richard Pawson, Robert Matthews · first published 2002
8mentions
3recommended by
8HN commenters
2008–2022first – last mentioned
38% recommend50% neutral13% critical
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Pawson's Naked Objects thesis is absolutely brilliant. It proposes a complete approach of which not all of the parts will be useful for any given project, but it is -very- much worth reading even so.
on “Why I don't miss React: a story about using the platform” ↗…web apps, where you may want to re-use business logic for mobile apps, which becomes very difficult when they're tied to a react component. Also makes it harder to test. There's a great paper called "Naked Objects" which I'd recommend for anyone doing GUIs, but powerful idea I got from it is make your presentation code so immediately obvious from your business objects that you can practically generate it automatically.
on “Why I don't miss React: a story about using the platform” ↗Naked Objects is a fascinating idea that seems to have mostly disappeared from view. From my reading on it the UI basically falls out of the domain model fully formed, and that was what end users work with exclusively.…
on “A Pure Types-Driven real-world apps development approach” ↗…way to predict how software will be written in the future. First off read a couple of books to understand better where I'm coming from :- Necessary But Not Sufficient by Eliyahu M. Goldratt Naked Objects by Richard Pawson From a business perspective I want a group of classes that mirror real world items e.g. Order, Invoice, Address, Amount, Price, Date etc. Then I want another group of classes that…
on “Followup on ERP Thread: How I Plan To Do ERP” ↗There is also the idea of Naked Objects [1] based on a thesis from 2004 [2]. [1] http://nakedobjects.org/ [2] http://downloads.nakedobjects.net/resources/Pawson%20thesis....
on “Show HN: ESQLate – Build minimum viable admin panels with just SQL” ↗I think the author is basically describing the Naked Objects pattern, i.e. deriving the full stack of your application, from storage layer, to internal logic layer, to presentation layer, from one single domain layer. The problem with this pattern is that it makes…
on “A Pure Types-Driven real-world apps development approach” ↗…etc.) are separate to the "model objects". Self was inspired by Smalltalk, and its Morphic UI seems to be immediate-mode: the UI objects often are the model objects. This idea is more explicit in the "Naked Objects" approach. Squeak Smalltalk uses Morphic, although its descendents (e.g. Pharo and Newspeak) seem to have replaced it (I'm not sure of their paradigm though) Denotative, Continuous-Time Programming (DCTP):…
on “Immediate Mode GUI” ↗That talk knocked my socks off and pretty much drove me to my own bastardized version of "Naked Objects" http://en.wikipedia.org/wiki/Naked_objects [Edit: upon re-reading it again: in P006 he says blackboxes are hard to reuse because they hide performance characteristics? I can think of a better reason,…
on “Why are Black Boxes so Hard to Reuse? (OOPSLA ’94)” ↗