Tuesday, July 31, 2007 |
|
|
I think programming languages need the complement to "deprecated." It's for those moments when "YAGNI" conflicts with "But I just know I will..." Less imperative than a TODO, but more than a mental note. |
Tuesday, July 31, 2007 6:00:11 AM (Hawaiian Standard Time, UTC-10:00) | Disqus link | Knowing
|
|
|
|
Sunday, July 29, 2007 |
|
|
Revell models. With the plastic trees that you twisted every numbered part out of? Rubber glue, Testor paint? If I were to make a reference to this experience as a metaphor, would anyone under the age of 40 know what I was talking about?  |
Sunday, July 29, 2007 10:17:04 PM (Hawaiian Standard Time, UTC-10:00) | Disqus link | Knowing
|
|
|
|
|
Is there any utility that displays on your task bar all the applications running within your Virtual PC / VMWare / Remote Desktop Session? I'd really like such a utility. It ought to be possible, at least if the virtual machine is network-reachable. If I felt that I could sell more than a couple hundred for $30 a throw, I'd probably be willing to spend some time writing it myself, but I don't think Windows users spend money on utilities. Mac people apparently buy 3rd party software and PDA users and cellphone users are friggin' ATMs, but you know any utility for Windows is going to end up on P2P before you sell a hundred copies. Whether that actually zeroes out sales, I dunno'. |
Sunday, July 29, 2007 7:17:31 AM (Hawaiian Standard Time, UTC-10:00) | Disqus link | Knowing
|
|
|
|
Saturday, July 28, 2007 |
|
|
Since I blogged the pause and restart of Pu'u O'o, for completeness I will report that the eruption on The Big Island of Hawai'i has not only returned, it's in probably the most visually exciting phase it's been in in years. After the Father's Day earthquake swarm, the lava being fed to the surface has apparently moved "downrift" of the Pu'u O'o crater and in the past week has found the surface in what's called a "fissure eruption." This morning's update speaks of a 100M-wide flow of lava (the picture is of a flow that was apparently around 10M across). If you want to see lava, you should know: - The hundreds-of-feet tall lava fountains in the advertisements happened for a few days twenty-four years ago,
- From a distance of more than a few dozen yards, during daylight hours, flowing lava doesn't look spectacular (the surface rock's heat-related red component is very largely overwhelmed by the ambient light of the tropics). (Hmmm.... if your camcorder / digital camera has an infrared "night-shot" mode ... )
- Within a few dozen yards, it's about the third-most amazing thing you'll ever see
- At night, even from a distance, flowing lava is probably the second-most amazing thing you'll ever see. The visible red light from the heat is visible from many miles away.
- Being within a few dozen yards of lava entering the ocean at night is the single most amazing thing you'll ever see.
Right now, apparently the fissure eruption is throwing up some 2M high fountains. My guess is that this is among the best stuff you'll ever see from a helicopter. In summary, as of 7/28/2007: - Eruption's back on and vog has returned (bummer)
- You probably can't see any of this from land at the moment, but the lava will very likely eventually find its way off the ridge its on and be visible, at night, from a distance
- There are no legal hikes with a vantage point of the current eruption
- A helicopter tour of the fissure eruption might give you a once-in-a-decade view
All of this will probably change within a week or so. If you're planning on being a lava tourist, absolutely check out the daily eruption report. |
|
|
|
|
|
Kurt Schrader wonders if he's the first person to hit a point in a Rails app where he wonders if he's "finally hit the point where the cost of maintaining our code in Ruby is higher than the savings by writing it in Ruby in the first place?" He says that: - He misses the refactoring tools of IDEA, and
- Although it may have taken longer to reach, he feels he's on "the same old curve to all of the standard problems you run into when programming a webapp in any language."
Of course, he's not the first person to see such problems. As I write about in a forthcoming column in SD Times, basically as soon as you start getting into professional-level complexity in Ruby, you start seeing that it's no silver bullet. A great language, yes, but not a silver bullet. Rails, too, is a very nice framework / DSL, but has huge shortcomings -- contorting it to work with the naming not-quite-conventions of legacy databases is enough to make me consider it a "new projects only" tool. Of course, refactoring IDEs have not been around for very long and it's undoubtedly the case that people are striving to build refactoring Ruby IDEs. The challenge is making refactorings bullet-proof in a language with a dynamic type system. You can't have a "press the button" refactoring that works 95% of the time. This is a mistake that even today's refactoring IDEs make: the "review these changes" dialog they pop up. They're about as useful as "Are you sure you want to delete that?" in file dialogs. No one actually considers the question, they just hit "OK" and see if it breaks. |
|
|
|
|
Friday, July 27, 2007 |
|
|
Huh. I just received a link in email to "my" August issue of Dr. Dobb's Journal. I'm not going to post the link I got, since it's undoubtedly linked to me, but can anyone access http://www.nxtbook.com/nxtbooks/cmp/ddj0807/index.php? It's a Flash-based interface, but even when viewed in profile, full-screen (1050 x 1680), it's annoyingly fuzzy: Which zooms in as: There doesn't appear to be any way to control the antialiasing within the Flash interface. Blech. |
|
|
|
|
|
Google is joining Intel in putting more cash into the kitty for the Turing Award. To me, $250K is nonsensical -- you should either go for the million (Who Wants To Be A CS Millionaire?) or maintain the super-coolness of the Fields Prize (cash value: $15000 Loonies). |
Friday, July 27, 2007 6:00:05 AM (Hawaiian Standard Time, UTC-10:00) | Disqus link | Knowing
|
|
|
|
Wednesday, July 25, 2007 |
|
|
The very good Threading Building Blocks library from Intel, released last year around this time as 1.0 and being updated soon, has been open-sourced by Intel. This is a hardcore C++ template library, but has some great-looking libraries and algorithms (lots of lock-free data structures). I've been unable to actually use the library, as my multicore system is AMD Opteron-based (just because I live in the tropics doesn't mean I can't appreciate an even warmer room). With quad-core systems available under $1000 and the Q6600 now at $375 from Newegg, there's a great temptation, but I'm going to try to resist until I can build an 8-core machine, which to my mind is the inflection point from "multicore" to "manycore." |
|
|
|
|
|
Interesting, my analysis from last November is unchanged other than time-shifting and yet, emotionally, the availability of TiVo makes a huge impact. On the other hand, I am not sure that they would allow me to change my current TiVo lifetime subscription over to the TiVoHD, so I'd be facing another recurring monthly bill. So it's HDTV ~$2500 + Tivo HD $300 + XBox 360 HD DVD Player $200 + monthly fee and neither Comedy Central nor AMC nor TCM broadcast in HD. Mmm.... temptation decreases ... |
Wednesday, July 25, 2007 6:00:05 AM (Hawaiian Standard Time, UTC-10:00) | Disqus link | Offtopic
|
|
|
|
|
We're hiring developers and testers for the Parallel Computing team in Microsoft's Developer Division....[Contact] joedu at microsoft dot com if you are interested. |
|
|
|
|
Tuesday, July 24, 2007 |
|
|
John Lam details the first public availability of IronRuby. Couple reasons why I'm interested in this: - It's Ruby
- It's the CLR
- It's a second data point for how to code for the DLR
I don't think I'm going to be able to resist the temptation to write a compiler for the DLR. I know I should resist, but I spend so many cycles thinking about programming languages and the DLR seems to have so much promise to language implementors. Argh, I can't believe I have such a busy week in front of me. |
|
|
|
|
Monday, July 23, 2007 |
|
|
Joe Gregorio reports the First Public Working Draft of Efficient XML Interchange (EXI) Format 1.0. Even that name stinks of bureaucratic ineptitude. This is my early contender for Worst Idea I've Heard This Year. Or maybe I should save that for this sub-idea: EXI processors MAY provide the capability to specify different built-in types or user-defined encoder/decoders (CODECS) for representing specific schema types. This capability is called Pluggable CODECS. Oh yeah, perfect. Because the only thing that could make a non-human-readable data interchange format more valuable would be to marry it with the robustness, ease-of-use, and interoperability that we associate with video and audio codecs. And the wonderful thing about this is that this will be marketed as having something to do with performance, because, oh yeah, a linear decrease in the size of your messages -- that will solve your architectural problems. So people with performance issues with their Web services will solve them by introducing another layer of complexity, making the data non-readily inspectable, and throwing proprietary codecs into the midst. I can't see why that wouldn't work. |
Monday, July 23, 2007 6:00:12 AM (Hawaiian Standard Time, UTC-10:00) | Disqus link | Knowing
|
|
|
|
Sunday, July 22, 2007 |
|
|
|
Sunday, July 22, 2007 12:00:30 AM (Hawaiian Standard Time, UTC-10:00) | Disqus link |
|
|
|
|
Saturday, July 21, 2007 |
|
|
Wesner Moise's NStatic static-analysis tool for .NET appears to be approaching its initial beta. Moise has made a number of exciting claims for this technology since he began discussing it about 18 months ago. If I understand correctly, NStatic involves considerably "deeper" analysis than most quality-assurance tools; it almost seems it applies the field of constraint-based programming to parsed program structures. At least, that's the only way I can get my head around this post. |
|
|
|
|
|
Wow! Jonathan Schaeffer of the University of Alberta has solved the game of checkers. Games like tic-tac-toe, checkers, chess, and go are all known to have optimal strategies (I don't recall of the exact game-theory restriction that describes such games: "perfect information, sequential"?). That's why tic-tac-toe is boring -- it's always correct to first play to a corner and its always correct to respond by playing to the opposite corner middle . The bigger games like checkers, chess, and go have such huge solution spaces that one wouldn't think their solutions could be discovered by brute force. Schaeffer's calculation has been ongoing for 18 calendar years (no word on total processing time) and involved "just" 10^14 calculations. It seems that he reduced the tree by finding many equivalent positions and then brute-forcing every possible endgame involving fewer than 10 pieces. The conclusion is that perfect play leads to a draw (I believe it's still unknown if perfect play in chess leads to a draw). What I'm impressed by from a software standpoint is that obviously he figured a way to maintain the partial calculations of his system over 18 years, even as he undoubtedly brought newer generations of hardware and software to bear on the problem. Well done! |
Saturday, July 21, 2007 12:00:09 PM (Hawaiian Standard Time, UTC-10:00) | Disqus link |
|
|
|
|
|
A few weeks ago I got an email asking if I was interested in selling one of my idle domain names -- inkpositive.com. "Sure," I said, and named a price that covered the hour of time it would take me to transfer the domain. The subsequent process (contract, escrow.com, "I can't tell you who my associate is...") makes me think I could have asked for a couple more hours worth of revenue... |
|
|
|
|
Thursday, July 19, 2007 |
|
|
I love this prototype / early version by Mitch Barnett of a web-based IDE for distributed programming using IronPython. It reminds me of my last dot-comet system: a Web-based assessment framework (I'd say "testing framework" but you'd think NUnit when you should be thinking certification). You were presented the pre-conditions, post-conditions, and invariants, pasted your code into the text box, your code was compiled, checked for permissions / size constraints, and then executed in a sandbox that was monitored and constrained in various ways (memory, time, resources, etc.). What I like about Mitch's idea (other than that beautiful Smalltalk-like browser) is the idea of using this for pair-programming over the Internet. Mitch tells me that's not yet supported, but could easily be hacked. |
|
|
|
|
|
You know I love my homeys at SD Times, but ought not the headline read: "Study states obvious, costs money"? 
|
|
|
|
|
|
O'Reilly has made the back issues (from 1983 to 2006) of Esther Dyson's "Release 1.0" newsletter available as freely-downloadable PDFs: O'Reilly Radar > Release 1.0 The newsletter was very forward-thinking; I just grabbed the June 1989 issue (the month I was hired at Computer Language) and found a discussion of self-organizing multi-user systems that is pretty darn timely today. |
|
| | |