Greetings Ramsey, You have highlighted why this makes it the compiler guy's dream job. Take a decent size nightmare for the the subject, pile on a deadline, and add on mediocre salary to give us either a government rice bowl and genius grinder. Oops. Sorry, those have been my dreams lately. Since this all hap-hazardly came together in the first place, it is not as though we can question the mind of the person who orchestrated the mess. We could offer them a them a Guinness but I think they were stoned on something far stronger than the glass would hold.
Seriously though, the problem described would keep a compiler team employed for a good sizable amount of time. It would be a wise investment somewhere to have some kind of converter, mobile code generator or something that would generate the right code for the appropriate language and platform pair. V/R, Dan Beatty, Ph.D. Texas Tech University, Alumni dan.bea...@mac.com https://sites.google.com/site/allnightstarparty/home (806)438-6620 On Jul 13, 2012, at 11:48 AM, Ramsey Gurley wrote: > > On Jul 13, 2012, at 2:54 AM, Henrique Gomes wrote: > >> >> On Jul 12, 2012, at 8:06 PM, Chuck Hill wrote: >> >>>> >>>> You want to know the biggest unfixable problem with WO for me? WO apps >>>> can't be deployed on any mobile platform. That really sucks. >>> >>> For that, you need to change the paradigm from interface vending servers to >>> servers that vend data and processing. Use a mobile client technology like >>> Sencha or Montage. Or write D2iOS. :-) >>> >>> (..) >>> Chuck >> >> I actually think that's the way to go. > > > You can do go client, but then you have to build a client for every platform > you support. That's not trivial. > > Deploying to client platforms is quite a bit different from deploying to a > server under your control too. Instead of having a few instances, tended to > by someone who knows what they are doing, on hardware you know everything > about, you have hundreds/thousands/millions of instances on a plethora of > different configurations being run by people who don't have freakin' a clue. > > Supporting users is endless fun! No, really. It's endless. I get one or two > user problems *every* morning. It's so fun. > > 1. Get problem description. (HelpDesk: ZOMG! User is alarmed!! App is not > workings!!11!) > 2. Ask for detailed information (Which user? What client platform? Define > "not working" please.) > 3. Take info and dig for cause. > 4. Find ambiguity. GOTO step 2. Repeat for a while. (Sometimes forever. I > have a bin of unsolved mysteries) > 5. Determine problem. > 6. Apply fix if a bug. Apply cluebat if PEBKAC. > > Going client may free up some server resources, but it will definitely > require more support resources. Guess which is cheaper :-) > > >> You mentioned that switching to Cayenne leaves 1/3 of WO, aka the >> presentation layer, but, really, is there a future on server side interface >> vending? > > The best way to predict the future is to create it. Is anyone cranking out a > client interface faster and more reliably than D2W yet? I'm all ears over > here :-) > > Ramsey > > > _______________________________________________ > 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/danielbeatty%40mac.com > > This email sent to danielbea...@mac.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
