Lewis' Blog Tales from the trenches of information technology

12Dec/110

Egad! Why do people do their own web development?

WordPress 3.3 is now GA. Knowing better than to blindly upgrade without at least having a look at what may be not quite ready for prime time (though WP is quite good about reasonable beta cycles and such), I happened over to the WP fora to see what reports had been made (yes, I should have gone to the bugtracker, but I like to get a view from "on the ground," so to speak).

7Dec/110

CRTs vs LCDs in 2011/2012

An interesting thread cropped up on the eComStation Technical mailing list on Yahoo! in the past few days. One of our list members was inquiring about the ability to set refresh rates in the Panorama video driver. Short answer: you can't (well, at least, not yet). This is covered in the VESA FAQ. Apparently, the original poster has a CRT which requires proper tuning of the driver for his monitor's refresh rate. One of the first responses to come back to him (aside from the correct answer, pointing him to the FAQ) was the obvious question: "Why are you still using a CRT?"

I suppose what has amused me the most about this little exchange was the assumption that by now, CRTs have become yester-tech, and that *all* truly modern systems (this was a fresh install of eComStation 2.1) should be outfitted with LCD monitors.

I was going to jump into the post, but instead, I'll just migrate some excerpts here, and include my own commentary at the end.

7Oct/110

Ramdom thoughts on the 2011 (and beyond?) Firefox release schedule

As I sit here at Panera Bread, catching up on some tech news, an article caught my eye concerning Mozilla's new approach to updates and, tangentially, the (revised) 2011 Firefox release schedule. This started my own wheels turning, as this has been a bit of an annoyance for me, so I thought I'd just jot down a few ideas...

Concerning Firefox's 2011 release schedule:

Why?

We (I say "we" because I do/have contribute(d) from time to time) have some bugs in Bugzilla which date back several years (some to the Netscape Communicator days, inherited by the Mozilla project - no kidding!). These have yet to be quashed, and all the while new "releases" just keep coming down the pike, bringing with them their own share of new insectoids. Wouldn't it make more sense to stay at a reasonable "release" level, and just fix it before adding new features (and after all, isn't the purpose of a new "release" to introduce new features)? We already have a mechanism in place for extending the functionality of the browser through plugins and extensions, anyway, so what's the point? (If Mozilla wants to emulate Redmond, then they should consider that under the hood, Windows 7 is NT 6.1, anyway, and Microsoft got a head start with NT growing out of OS/2 - NT started at version 3.)

26Jan/111

Why the concept of “The Cloud” is as old as dirt, and about as useful

The Cloud

Cloud? Mist? Fog?

I can't stand it.

I have reached the end of my rope with this stupid, stupid buzzword: The Cloud.

Cloud? Does anyone even know from where (or how) this term was derived? Likely from the typical symbol used to indicate the space between networks. This could be the public internet, an intranet, or even the PSTN (for those youngsters who may not be familiar with that acronym, that's the Public Switched Telephone Network, or the "phone system").

So, what the h-ll is it?

In the late 1990's, the big internet acronym was ASP (Application Service Provider). The concept was a good one, though fraught with numerous problems: security, performance, the stability of the provider's network infrastructure, the quality of the connection on the client's side of the link, and of course, the usual customer service issues.

The idea was simple: instead of purchasing your own application and the big iron to run it, you could essentially "rent" the application on someone else's systems (what we now call "hosted") and pay for it based on time, number of concurrent or overall users, volume of data storage, and/or a number of other factors.

Sound familiar? It should. Web hosting has been done like this for ages. In fact, since the internet became a "public" space and smaller companies (and individuals) who did not own their own web servers but who were desirous of maintaining a web presence, web server space has had a market. Likewise, hosted email systems have flourished over the years. YouTube is a major player in this type of space. They host files (audio & video). Their revenue model, however, is to mainly collect from third parties, in the form of advertising, vs charging the hosting clients directly (in most cases). Still, the concept of "your stuff, stored & accessed from somewhere else" is the same.

The security issue becomes the main concern (to me). What is to keep one of these outfits from setting up offshore somewhere (offshore here refers to outside the US - or outside your country, wherever that might be), accessing your data, selling it to some third party/ies, and then just closing up shop? Nothing. Not every country has a treaty with my country. If I am wronged in this manner, I'm pretty much out of luck.

In addition, I have no guaranty that the provider of these so-called "cloud" services has the infrastructure in place to handle my load once he takes on a dozen more clients.

I'm not completely down on the whole IaaS or SaaS ("Infrastructure as a Service" or "Software as a Service") idea. I just think that like most things, it has its uses, and it is not the answer to everyone's problems in all cases, contrary to what the marketing types would like the huddled masses to think.

Web hosting, where data is not particularly private, and where downtime isn't going to cause someone loss of life, liberty, or money (loss of happiness is a bit easier to bear, when compared to the others), makes sense if the cost is commensurate with the risk. Likewise, email hosting works the same way. However, putting my financial data on someone else's server(s), located who-knows-where (and just because the company's website says the facility is located in New Jersey doesn't - and I hate to break this to some of you - necessarily mean that that's really where it is), and with g-d-only-knows who running it, just doesn't sound like the best idea for me, as compared to hosting my own data on a server in the next room, run by me or by someone hired and trained by me (and that's not to say that it is ever entirely safe to trust anyone with your data).

The Cloud is merely the latest marketing hype word for something hosted somewhere else. Whether that something is your website, your email system, your backup (I'll save my rant about offsite backup for another post), or your precious business-critical data, it's exactly the same: you, giving up control over your data to someone else, located somewhere else, and usually replicated across two to two hundred servers, over which the only control you have is the power to withhold payment for services.

Sounds pretty thin to me, more like The Fog than the Cloud.