I’m on a call with an extremely large healthcare tech vendor and they’re showing us their internal web app.

It’s written in #WebObjects.

In 2023.

🤯

@chris Maybe it would be OK to say that body returns a list, but even that is not really true, it might return a container.
BTW: As usual it is the same in #WebObjects, it also has the „content“ thing not as an array, but as a single type that can be a container of some form.

Being an old Apple/Mac OS X Server fan and having done web development for quite some time, I always think #Apache #Cayenne and its #CayenneModeler are looking really sexy. I've gotta make a project using it at some point. #ORM #Java #databases #WebObjects #EOF #EOModeler

Hello Mastodon! My name is Fredrik and I'm excited to join this community. I'm interested in Java, Swift, WebObjects, and smart home technology. I'm also a fan of Apple products and electric cars, as well as solar panels. I'm looking forward to participating in discussions and getting to know everyone who shares similar interests. #introduction #Java #Swift #WebObjects #smarthome #Apple #electriccars #solarpanels

Hello Mastodon! My name is Fredrik and I'm excited to join this community. I'm interested in Java, Swift, WebObjects, and smart home technology. I'm also a fan of Apple products and electric cars, as well as solar panels. I'm looking forward to participating in discussions and getting to know everyone who shares similar interests. #introduction #Java #Swift #WebObjects #smarthome #Apple #electriccars #solarpanels

@marcus Also #WebObjects was #ObjC up to version 4.5, only 5.0+ did the full switch to Java. (we didn't use the real WO, way to expensive back then, but SOPE is essentially an API clone w/ many extras)

@paaast I still know people using it every day in production! (which is very weird, because it is so outdated) But then, actual German banks also still use #WebObjects, despite that being officially dead for like 12? years 🙂

Not 100% sure, but I suspect that is also the biggest #WebObjects API application in existence, FOSS or not, (it has a huge number of WOComponents for all the different apps).

Not 100% sure, but I suspect that is also the biggest #WebObjects API application in existence, FOSS or not, (it has a huge number of WOComponents for all the different apps).

#LunchBreakFOSS Today a little obscure project “StaticCMS”. As the name implies this is a static site generator (and pretty old, almost 20y?), still use it for ZeeZide.de. Uses GETobjects, my #Java #WebObjects / #Zope thing at its core.
It is a little outdated (e.g. no Markdown) and finicky, but I still like the overall concept (reusable components). 
Eventually I’d like to build a #SwiftLang version of that, probably has to wait until Swift has proper reflection/FFI.
https://github.com/helje5/StaticCMS

#LunchBreakFOSS Today a little obscure project “StaticCMS”. As the name implies this is a static site generator (and pretty old, almost 20y?), still use it for ZeeZide.de. Uses GETobjects, my #Java #WebObjects / #Zope thing at its core.
It is a little outdated (e.g. no Markdown) and finicky, but I still like the overall concept (reusable components). 
Eventually I’d like to build a #SwiftLang version of that, probably has to wait until Swift has proper reflection/FFI.
https://github.com/helje5/StaticCMS

Late #LunchBreakFOSS, The "SwiftUIRules" project from Sat provides a declarative rule system for #SwiftUI env keys. It can be used on its own but I wrote this for another thing called “Direct to SwiftUI” (D2S). Which is a SwiftUI port of another old #WebObjects technology called “Direct to Web” (there was also “Direct to JavaClient” and “Direct to WebServices” 🤓)
So what it is? It connects SwiftUI w/ a database using the rule system. This article has all the details:
http://www.alwaysrightinstitute.com/directtoswiftui/

Late #LunchBreakFOSS, The "SwiftUIRules" project from Sat provides a declarative rule system for #SwiftUI env keys. It can be used on its own but I wrote this for another thing called “Direct to SwiftUI” (D2S). Which is a SwiftUI port of another old #WebObjects technology called “Direct to Web” (there was also “Direct to JavaClient” and “Direct to WebServices” 🤓)
So what it is? It connects SwiftUI w/ a database using the rule system. This article has all the details:
http://www.alwaysrightinstitute.com/directtoswiftui/

#LunchBreakFOSS SwiftObjects, GETobjects … all those are ports of the one, original thing: SOPE. The Skyrix Object Publishing Environment 🤓 This is a proper server-side #ObjectiveC implementation of #WebObjects and Zope. XML, LDAP, iCalendar, IMAP4 - all the tech you love is in there. #Hardcore!
I personally wouldn’t use it anymore, but it is still deployed on a non-negligible scale as part of http://scalableogo.org (and even OGo is still used by some).
http://sope.opengroupware.org

#LunchBreakFOSS On Wed we had “SwiftObjects”, a #WebObjects implementation in #SwiftLang. That was also just a port of another obscure project of mine (from before 2010): “GETobjects”. Actually it isn’t *that* obscure and still used in production by various people!
“GETobjects” is my #Java implementation of WebObjects and actually pretty good, as it incorporates a lot of additional concepts from Zope.org (v2) that workaround some key conceptual deficits in WO.
https://github.com/GETobjects

#LunchBreakFOSS Remember “SwiftWebUI” from Monday? That is essentially a fork of “SwiftObjects”, another obscure project of mine.
SwiftObjects is a #ServerSideSwift implementation of #WebObjects, the old NeXT/Apple application server you love from iTunes Connect 🙈
One problem it has is #SwiftLang lacking a good reflection API (e.g. something like `NSClassFromString` and `perform::`). With the “stable” ABI technically possible now, I think.
http://www.alwaysrightinstitute.com/wo-intro/

#LunchBreakFOSS The project of mine that received most GitHub stars yet is “SwiftWebUI”, a #ServerSideSwift web version of #SwiftUI. IIRC I hacked that up in about a week (reusing a lot of existing code), when during the #WWDC 2019 I realised that SwiftUI is very similar to #WebObjects.
It is (only!) useful for learning purposes, definitely shouldn’t be used in prod. I have some ideas on how a proper web version of SwiftUI would look like, we’ll see.
http://www.alwaysrightinstitute.com/swiftwebui/

I don't have a sound alternative design, but to me it still feels that `@State` and such should simply not exist, they just hack-add object semantics to value types. Instead stateful Views would be objects and only stateless ones structs.
#WebObjects had such a difference between WOComponent's (stateful) and WODynamicElements (stateless). Though both of course have been ObjC/Java classes.