Thursday, October 1, 2009

Today's links for 9/28/2009 - 10/1/2009

Had a great weekend, now it's back to work.


  • great articles from evan weaver about using REE 1.8.7, and how to fine-tune ruby GC to make it run faster.
  • Here is a good link for learning how to apply your shiny new GC settings to ruby.
  • Java is dead but you'll learn to love it - A good argument for why java's failure to innovate is leading to newer, better languages being built upon the JVM.

Friday, September 25, 2009

Today's links for 9/25/2009

IE 8 Runs 10x faster with google chrome frame, but, of course, M$ is saying GCF is not a risk we would recommend our friends and families take.  Oh please.  However I do enjoy how Google is embarrassing M$ with this plugin.

Comments roundup:


quote>Looks like Google are going to try and beat Microsoft at their own game: Embrace, Extend, Extinguish.
I've seen several people mention this in the last mention of Google's plug-in as well. I don't understand and I have to wonder if the people saying this know what the strategy they're referring to is. The concept of "embrace, extend, extinguish" is to comply with a standard interoperably until you are popular. Then extend the standard in a non-interoperable way, counting on your popularity and the new functionality to drive adoption. Then, extinguish the competition by utilizing the standard ubiquitously and in a non-interoperable fashion so that anyone who does not have access to the proprietary extensions you added, is removed from the market.
So for IE the strategy was to implement HTML and other technologies interoperably until IE was very popular, then extend HTML with nonstandard elements and rendering and add ActiveX for more functionality no one else could use. Then extinguish competition by building lots of tools and that rely upon the proprietary version and relying on Web developers to target IE's broken version of HTML instead of the actual standard.
So I'm trying to understand how people think Google is employing this strategy. They are embracing IE, sort of by implementing Web standards within it. How do people think Google is going to extend those Web standards in a proprietary way? Do they mean by building proprietary Web applications that use the standards? Do people actually think Google's strategy is to make Google apps really popular and then break compatibility with non-chrome browsers by making them no longer use Web standards? Won't that be hard while maintaining backwards compatibility especially since they're using an OSS browser? I suppose this is possible, but I don't see why people would assume it is Google's strategy.
So basically, while I see that Google is extending IE to use Web standards, I don't see this as a likely part of an "embrace, extend, extinguish" strategy. Nothing stops Microsoft from creating a better implementation of Web standards in IE's rendering engine and out competing Google's plug-in and they have a lot of advantages if they do decide to compete. Rather, this is Google managing to chip away at MS's anti-competitive use of IE and make MS actually compete fairly a little more, pretty much the opposite of Google trying to kill fair competition which is what the EEE strategy is all about.

Thursday, September 24, 2009

Today's Links for 9/24/2009

Work emergencies and sick puppies kept me from finding cool links today.

Functional Javascript - A library that allows Javascript to look and behave more purely functional.  (Academic?)

Your wikipedia entry of the day:  Side Effect - A function has them if it modifies some state or has an observable interation with calling functions or the outside world.



Wednesday, September 23, 2009

Today's Links for 9/23/2009

  •  Google Chrome Frame - Google chrome webkit extensions for IE 6, 7, and 8.  I think it opens a chicken vs egg problem though, as users who have the ability to install a plugin would most likely have the ability to install a new browser.
  • Amazon Basics - Amazon branded cables, blank cds, and the like.  I do like the various cables though.  It sure beats spending well over $100 for an HDMI monster cable.
  • Project Euler - Math / Pure CS problems that start easy and gradually increase in complexity.  Good to exercise the algorithm-producing part of your brain.
  • Lessons learned using ruby for high-computational problems - Two word result:  Use Java.
  • Microsoft Tablet - M$ makes yet another foray into the tablet world.  First mover advantage against Apple?  Maybe.
Your wikipedia term of the day: The Diamond Problem

Tuesday, September 22, 2009

Today's Links for 9/22/09

I am currently in the midst of shedding my OOP mindset in exchange for a purely Functional one.  Hence, my links today are FP oriented.
Your software wikipedia entry for today:
Continuation - The abstract control state a language uses to store the state of a running program, so it can return to that state in the future.

Monday, September 21, 2009

Today's links for 9/21/09

  • Is Java dead? - An interesting (and thorough) article about potential successors to Java in the Enterprise.
  • HTTPFox - A sweet HTTP traffic sniffer for firefox. Will grab each request with all request and response headers, and request parameters. Similar to Fiddler for Internet Explorer.
  • jasonkolb.com - This guy has an interesting blog.

Your software wikipeida article for today:
Brownfield - Building new systems around legacy systems. Referenced in the Is Java dead article in the links above.