What was it like to be a software engineer at NeXT?

Re:What was it like to be a software engineer at NeXT? by anonymouse008 on Tuesday November 24, 2020 @10:40AM (#25199405)

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.

[ Parent | on HN ]

Re:What was it like to be a software engineer at NeXT? by grecy on Tuesday November 24, 2020 @02:38PM (#25202166)

I 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.

[ Parent | on HN ]

Re:What was it like to be a software engineer at NeXT? by sjg007 on Tuesday November 24, 2020 @10:58AM (#25199572)

Seems like some demos around 2019 are still available: http://www.alwaysrightinstitute.com/wo-intro/

[ Parent | on HN ]

Re:What was it like to be a software engineer at NeXT? by pjmlp on Wednesday November 25, 2020 @02:06AM (#25206650)

It 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

[ Parent | on HN ]

Re:What was it like to be a software engineer at NeXT? by artificial on Wednesday November 25, 2020 @12:45PM (#25211917)

Here's an experiment to that end: https://github.com/SwiftObjects/SwiftObjects

[ Parent | on HN ]