4 ms·
Random note, i- for no reason- went looking at WebObjects, which hailed from NeXT I understand. I liked the idea of entity based systems. Discovered that Apach
by rektide 6y ago
Random note, i- for no reason- went looking at WebObjects, which hailed from NeXT I understand. I liked the idea of entity based systems.
Discovered that Apache Tapestry, which I used a decade ago, was inspired by WebObjects. It was a very interesting fairly seamless backend centric web development experience, worked quite well, & I say this as someone who loves JS, thick client architectures, client side architecture. I didn't see a ton of objects seeming like generic web objects like ideas though. In WebObjects it seems primarily like there were objects, then different bindings to re-expose and/or convey updates between the object & the various front ends it might show up on. I'm probably over glamorizing how shared, how web, objects in WebObjects really were.