5 ms·
And I'm upset I didn't get an opportunity to properly work with WebObjects. WebObjects with Swift would revolutionize the web - IMHO - it was gone too soon.
by anonymouse008 6y ago
And I'm upset I didn't get an opportunity to properly work with WebObjects. WebObjects with Swift would revolutionize the web - IMHO - it was gone too soon.
- sjg007 6y agoSeems like some demos around 2019 are still available: http://www.alwaysrightinstitute.com/wo-intro/ http://www.alwaysrightinstitute.com/wo-intro/
- grecy 6y agoI coded fulltime in WebObjects from 2006-2008 making webApps in the health care industry. During my Software Engineering degree I learned the difference between a Library and a Framework, but it wasn't until actually using the WebObjects Framework that the light bulb went off in my head. It was a pleasure to work with, and clearly very, VERY well thought out. EOF was great, and every time I made a new NSArray() it brought a smile to my face.
- pjmlp 6y agoIt would hardly do that, in case you aren't aware they were in the genesis of J2EE. > Since the transition of WebObjects to Java in 2000, the functionality of many of Apple's Java Foundation classes is replicated in Sun's own JDK. However, they persist largely for reasons of backwards-compatibility and developers are free to use whichever frameworks they prefer. https://en.wikipedia.org/wiki/WebObjects#Java_compatibility https://en.wikipedia.org/wiki/WebObjects#Java_compatibility
- artificial 6y agoHere's an experiment to that end: https://github.com/SwiftObjects/SwiftObjects https://github.com/SwiftObjects/SwiftObjects