3 ms·

I remember when I moved from obj-c to java (as WebObjects made the same transition) and being amazed at just how bad the java standard libraries where compared

I remember when I moved from obj-c to java (as WebObjects made the same transition) and being amazed at just how bad the java standard libraries where compared to the obj-c foundation and other nextstep libraries. The obj-c libraries were so nice and clean and focused. Funny to see the 'oak' name reused - it's now an Apache project for a jcr backend.

cturner 11y ago
Do you remember any of the the names of method calls that were created by converting the objective-c libs into java?
- threeseed 11y ago
  If you mean WebObjects its libraries used almost the exact same method names e.g. EOUtilities.objectsMatchingKeyAndValue(key, value); You can still see a lot of the original code in Project Wonder e.g. https://github.com/wocommunity/wonder/blob/master/Frameworks/Core/ERExtensions/Sources/com/webobjects/foundation/NSArray.java https://github.com/wocommunity/wonder/blob/master/Frameworks...
  - cturner 11y ago
    Thanks - found one I was thinking of, addObjectToBothSidesOfRelationshipWithKey
    - hugi 11y ago
      Or EODatabaseContext.qualifierForLockingAttributesPrimaryKeyAttributesEntitySnapshot(). Work with WO made me prefer this style of long, self documenting method/variable names.
protomyth 11y ago
The difference between WebObjects as a obj-c program to java program was just heart breaking. You could further see the pain of transition in the Java bridge for Cocoa. It really showed the mismatch between obj-c and java.