I don't know what is more painful: bus of php. On a serious note, we use WO for all of our new projects. It is the most efficient platform.
Michael Sent from my iPhone > On Jun 22, 2017, at 6:53 PM, Tim Worman <li...@thetimmy.com> wrote: > > Hello! > > Just answering the initial question re: a place where we can register. I > believe there is a WO LinkedIn group? I’m pretty sure it is part of my > network. Maybe that would be a way to demonstrate an able community. > > David’s points are valid as well. > > Tim > UCLA GSE&IS > >> On Jun 22, 2017, at 3:45 PM, David Black <dbl...@db3.net> wrote: >> >> I was a WO Sr. Consulting Engineer with Apple until 2005 and miss working in >> WO a lot! I just set up a dev environment to work on a new personal project >> to get my head back into it. As someone whose had to manage the development >> of new products, it's probably a mistake business-wise to choose such a >> deprecated platform with such a small knowledge-base. Even getting the >> environment spun up with WOLips and WOnder has required deciphering outdated >> resources. As WO was already a hard platform to learn (conceptually), it's >> difficulty is now compounded by tools that aren't as slick as a >> ProjectBuilder/EOModeler/WOBuilder. So while there's a still a small >> community of people who could support a WO app, the availability of an >> engineer(s) might be challenging, and trying to train new support engineers >> would be painful. This is why the businesses with whom I've been working >> have chosen popular (or more simple script-based) backends like RoR, PHP, >> Python, or more mainstream Java frameworks. Trust me...I'd LOVE to have a >> few companies use WO, and if this was a merit-based competition, WO would be >> a great choice. Your point about getting hit by a bus is valid. A bus could >> mow down the entire PHP staff at a company and they'd be back in business >> the next day. >> >> >> >> >>> On Jun 22, 2017, at 10:25 AM, Robert Hanviriyapunt <roberth...@mac.com> >>> wrote: >>> >>> Hi everyone, >>> >>> I am a total WebObjects fan (a serious fanatic)! And I have the chance to >>> suggest to a new potential client to have me rework the entire A$P/M$$QL >>> system in WebObjects. My worries are that should I get run over by a bus, >>> whom may I get him in contact with to take over and/or support the system. >>> Anybody still out there? I'm building list to give him confidence there >>> will be available support. Is there a nice place all us WebO developers >>> can register? >>> >>> = Robert = >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/dblack%40db3.net >>> >>> This email sent to dbl...@db3.net >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com >> >> This email sent to li...@thetimmy.com > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/michael%40aspireauctions.com > > This email sent to mich...@aspireauctions.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
