× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Adam,

I won't disagree that google (among many others) have done amazing things in
the browser, but we need to look at what they *could* have done if not
limited by standards organizations. How long have we had
HTML/CSS/Javascript in semi reliable form? 10 years? We haven't moved very
far in those 10 years if you ask me.

The way I see it is the IT communitee is doing as good as it can within the
confines of what we have been given.

I have been doing EDI (Electronic Data Interchange) in one form or another
for about 10 years now. When I quote out projects, I have learned that
testing and project management takes considerably more time when I don't
have control of both ends. This is because I have to figure out how
somebody else is attempting to use a technology which heavily relies on
their interpretation of it. For example, there were so many interpretation
issues with XML web services that they had to start a whole new governing
body with the WSI profiles (http://www.ws-i.org/) to get everybody on the
same page.

Another example of this is in a new product I am going to be releasing
shortly. I was originally going to use WSDL's to describe a RPG web service
residing on the iSeries, but I have found that even within .NET, different
versions can behave differently when interpreting a WSDL (in my particular
case, I couldn't get .NET to recognize the XSD "anyType"). Instead, I still
use XML to transfer the data, but I trim it down considerably to take out
features that aren't needed (soap, schema validation, etc). And then to
round it out I provide a fully functional .NET API so the C# programmer
doesn't even necessarily know what is going on under the covers. Obviously
I have just created a "porting" issue as now my new tool can only be used
for .NET languages, but I will have Java done soon and mostly likely PHP.
In the end it is a business decision that requires a lot of thought as to
how a business should proceed with it's infrastructure, and it isn't black
and white but instead will nearly always include a mixture of directions.
By making some business decisions I took out a whole lot of XML (and related
technologies) out of the mix of potential issues. Going back to my original
assesment, that is what companies like Adobe/Microsoft/Sun are doing also
with their next generation "thick clients" (using term loosly).

What are you thoughts based on my response?

Aaron Bartell
http://mowyourlawn.com


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Adam Glauser
Sent: Friday, January 04, 2008 9:53 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: And so it continues...

Aaron Bartell wrote:
It will be interesting to see the IT landscape in 20 years. Having
standards committees is great for moving forward interoperation at a fast
pace, but it slows individual companies down to a crawl concerning
innovation as they have to wait for standards committees to come up with
next versions instead of developing them in-house.

What we are seeing in the Silverlight/AdobeFlex/JavaFX space is a nice
medium I think, because it gets away from so much reliance on browsers and
their adherance to specifications (i.e. HTML, CSS, Javascript, etc)

I have to disagree with your opinion that standards stifle innovation.
Look at Google, they've done some pretty darn innovative things IMHO,
using just those web standards you mention above.

I think this might be getting rather off-topic, shall we take this
somewhere else? (I'm not really sure where though :)



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.