Ok, I am not a coder. I am not an architect... but like most things on the Internet I can express an opinion. Please take the following with a grain of salt the size of Utah.
I was pointed to
David Millers's musings on computer designs and found it an interesting read. It does have a good point of view that a solid teaching can get you a beautiful architecture.. but I think it misses another point in that computer design and real-world architecture are not completely analogous. Architects of the late 19th century had a very fixed set of physics to deal with. Granite, concrete, steel (of various types), and glass. Gravity is the same wherever you build, and you can test and define that you need an iron or steel of this kind of quality. As has been said in many ways, the strict limitations can be very freeing to creativity and design.
Computers do not seem to be so limited. When architecting a design you need to deal with how many bits you have, endianess, registers, stacks, hardware interconnects etc.. that are like telling the 19th century architect that you need to get that design to work with both aluminum, titanium, and mud/wood plus allow for the fact that the building will be built on Mars, Earth, the Moon, and some non-Euclidean space.
Which may explain why this style of teaching is not used everywhere. [And why LISP machine people think like French 19th century designers :)]
2009-05-22
Thankyou MythBusters
I wanted to say thank you to the many people who make MythBusters go. Watching the collections with my family has been fun these last couple of weeks. I think of the two I appreciate Jamie the most... my 'problems' with cleanliness and specific clothings are very similar (I am sorry that he gets so much crap about it.) So anyway, as a fellow clean-a-holic.. thanks for the shows.
2009-05-15
Memories... Spyglass and BLINK
One of those odd memories came up as I was cleaning out some old boxes. I found my Carolina Hurricanes puck that Red Hat people got me in 2001. I found some paperwork for company ideas that other people did a lot better than me. And I found a printout for the most horrible thing mankind could invoke on others. So here is the story of how one could cause mass dangers to the world... embellished and added upon like any good fish story.
Circa 1996. Its near the end of the first browser wars. The company I worked for was Spyglass, makers of Internet Explorer and Red Hat RedBaron! We had an IPO in 1995 that went to $100+ a share.. and then went down into the single digits after Netscape came out and wowed the world. Netscape had a browser that had lots of bling attributes while the Spyglass Enhanced Mosaic was standards bound. We didn't have blink, we didn't have frames, we didn't have javascript because none of those had been through a standards process etc etc. [Plus our core market was going to be Corporate Companies that wanted their own browser to view super-standard HTML/SGML.]
Our big win had been to sell Microsoft Internet Explorer, SpryNet (an ISP that used modems for you kids) a browser, IBM another one, and Oracle another one.. we were going to be big.. well that didn't happen because our license to Microsoft hadn't taken into account that Windows 95 would BE HUGE, and Microsoft had hired 400 engineers to basically make the source code we sent them whatever they wanted. A company of 30 engineers didn't have much to compete with when it doesn't get a percentage of sales :).
Times got tough and the engineers found that instead of making things complaint to the W3C standards.. it was make things compliant to Netscape or whatever Microsoft had added to IE. And beyond that.. if we added stuff make sure we made it bigger and better. So the engineers got Java into the browser and added stuff, they got Microsofts version of Javascript into the browser and made it cross-platform.. they got FRAMES and added stuff and then came the dreaded BLINK tag.
Adding blink was a pretty hard challenge to a static display.. there are various ways of doing it.. but how does one do it and better? I decided that we needed to add a FREQUENCY tag and a ALTCOLOR tag. Yes a frequency tag... why just have BLINK go at all the same time at the same speed? Make it blink at different times on the page! Make it blink two different colors (versus background, foreground.).. have the frequency be in deciseconds so that you could blink from 10 times a second to 1 per second. Some of the developers thought it was great.. I think one of them actually figured out they could do it..
and then it died...
why? well a qa engineer pointed out a very simple issue.. he was an epileptic. "Ok so?" Well blinking lights of certain colors triggers seizures or blankouts in many people even if they are not diagnosed epileptic.
"oooooooooooh"
and so Blue/Red blinking tags at different speeds had to wait until people figured out how to do it in Javascript..
Circa 1996. Its near the end of the first browser wars. The company I worked for was Spyglass, makers of Internet Explorer and Red Hat RedBaron! We had an IPO in 1995 that went to $100+ a share.. and then went down into the single digits after Netscape came out and wowed the world. Netscape had a browser that had lots of bling attributes while the Spyglass Enhanced Mosaic was standards bound. We didn't have blink, we didn't have frames, we didn't have javascript because none of those had been through a standards process etc etc. [Plus our core market was going to be Corporate Companies that wanted their own browser to view super-standard HTML/SGML.]
Our big win had been to sell Microsoft Internet Explorer, SpryNet (an ISP that used modems for you kids) a browser, IBM another one, and Oracle another one.. we were going to be big.. well that didn't happen because our license to Microsoft hadn't taken into account that Windows 95 would BE HUGE, and Microsoft had hired 400 engineers to basically make the source code we sent them whatever they wanted. A company of 30 engineers didn't have much to compete with when it doesn't get a percentage of sales :).
Times got tough and the engineers found that instead of making things complaint to the W3C standards.. it was make things compliant to Netscape or whatever Microsoft had added to IE. And beyond that.. if we added stuff make sure we made it bigger and better. So the engineers got Java into the browser and added stuff, they got Microsofts version of Javascript into the browser and made it cross-platform.. they got FRAMES and added stuff and then came the dreaded BLINK tag.
Adding blink was a pretty hard challenge to a static display.. there are various ways of doing it.. but how does one do it and better? I decided that we needed to add a FREQUENCY tag and a ALTCOLOR tag. Yes a frequency tag... why just have BLINK go at all the same time at the same speed? Make it blink at different times on the page! Make it blink two different colors (versus background, foreground.).. have the frequency be in deciseconds so that you could blink from 10 times a second to 1 per second. Some of the developers thought it was great.. I think one of them actually figured out they could do it..
and then it died...
why? well a qa engineer pointed out a very simple issue.. he was an epileptic. "Ok so?" Well blinking lights of certain colors triggers seizures or blankouts in many people even if they are not diagnosed epileptic.
"oooooooooooh"
and so Blue/Red blinking tags at different speeds had to wait until people figured out how to do it in Javascript..
Subscribe to:
Posts (Atom)
