Frequented Links
Stand To Reason
Scripting News
ThoughtsOnFaith
Scobleizer
Joshua Allen
Steven Vore
Evan Williams
Bill Lazar
Steve Pilgrim
Joe Jenett
Ned Batchelder
J.D. Roth
Arnab Nandi
David Rogers
Matt Kennedy
Brian Cantoni
Mike Sax
Michael Geary
Nick Bradbury
Nick Hodges
Tommy Williams
Justin King
MooseNews
Greg Franklin
Family
Kim Fahrni
Jerry 'Jay' Fahrni
Lori Fahrni
Friends
Dan Albertson
Rick Wolf
David P. Cole
David M. Cole
Chris Roth
Richard Caetano
Steve Mitchell
Stuart Rawling
Tom Distler
Fat Penguin
Will Shattuck
Daved Kuns
Cass McNutt
Kevin Medeiros
Chris Edwards
Jon Davis
James Snell
Troy Sandal
S. Douglass Gilman
Tim Torian
Justin Stolle
Jim Hainline
Chris Hopkins
Ben Padilla
Robert A. Dodd
Misc. links
Heart of the Valley
The Great Valley
Downtown Visalia
City of Visalia
Kaweah Oaks Preserve
Movie Times
State of California
ThinkGeek Wish List
Upheaval
Web Dev Stuff
The Web Standards Project
Zeldman
Eric Costello
HTML Validator
CSS Validator
Development Stuff
Central Cal Developer's
Visio on MSDN
MSDN
C/C++ Users Journal
Got Dot Net?
Scripting News
FatBrain
CheezyPing
What I do
Pelco, Endura
I work at Pelco. The opinions expressed here are my own, and neither Pelco nor any other party necessarily agrees with them.
Harry Pierson: "This is a very pretty sight. It’s a screenshot from the IronPython CodePlex home page showing that 2.0 is the 'current release'. Yes that’s right, dear reader, IronPython 2.0 has officially been released!" - The dynamic language guys have been doing a great job, we have IronPython, IronRuby, and the DLR thanks to them. Well done, and congratulations.
Labels: .NET, Development, Microsoft, Python, Ruby
comment
twitter.com/john_lam: "ironruby running unmodified rails!" - That's pretty darned sweet.
Update: John Lam: "IronRuby doesn’t just let you run Rails; it lets you interact with the rich set of libraries provided by .NET. You’ll be able to use IronRuby to build server-based applications that run on top of ASP.NET or ASP.NET MVC. You’ll be able to use IronRuby to build client applications that run on top of WPF or Silverlight. You’ll be able to use IronRuby to test, build and deploy your .NET applications. You’ll be able to run Ruby code in your web browser and have it talk to your Ruby code on your web server. That’s a feature that we feel that many folks will enjoy." - Wow.
comment
Dare Obasanjo: "The problem is that if you naively implement a design that simply reflects the problem statement then you will be in disk I/O hell. It won't matter if you are using Ruby on Rails, Cobol on Cogs, C++ or hand coded assembly, the read & write load will kill you." - Go read it if you're a Twitter user, especially if you've been bashing Ruby on Rails. Their problem goes way beyond their language/platform of choice.
Labels: Applications, Ruby
comment
A List Apart: "ou’ve probably heard about Ruby on Rails by now. Your developer friends are raving about it—talking about how they wrote an application in less than half the time it would have taken using some other technology—how they really enjoyed themselves instead of stressing out, and then spent their extra time on the beach. Rails sure does sound like a pretty compelling technology. But what is it, and how does it fit into the big picture of web development?"
Labels: Development, Ruby
comment
Harry Pierson: "We've hired a few people around here recently (including me obviously). However, if you have a burning desire to work on IronPython (or IronRuby) and Visual Studio, we're still hiring" - This is exactly what's needed to make IronPython and IronRuby really slick! Complete integration into the Visual Studio IDE. Make them first class citizens.
Labels: .NET, DLR, Microsoft, Python, Ruby
comment
rubydoes.net: "There are other people that have blogged about silverlight and IronRuby before, it might be a good idea to check them out as well." - Tagged for later.
Labels: .NET, Development, Python, Ruby
comment
Mike Sax: "For the last two years or so I have really enjoyed Ruby. So much, in fact, that I may have become a Ruby-snob." - It would seem a lot of old curly bracers are beginning to embrace Ruby, and why not. In our ever evolving world of computing the net is where it's at, much to my own chagrin. Ruby seems a perfect fit for the server, even with its' reported performance issues.
Labels: Development, Ruby
comment
The Server Side.NET: "Microsoft is not dead, and it is not dying. Rather, the company's decline in market share is a runny nose." - I can definitely see this happening with the focus clearly on web based stuff. If you're doing client side applications Windows is pretty hard to beat, unless you're doing Mac applications, but the server side has a ton of dynamic language support with frameworks that allow folks to be highly productive and it's all free; Ruby + Rails, Python + Django, etc... On Windows we have those two plus we have ASP.NET and [insert your favorite .NET language here], but is that really an advantage? In short No. The real answer is Yes and No. For me it would be easier to use ASP.NET and C# because I already have experience with ASP.NET and C# is super easy to transition to because of my C/C++ background. Sure I could pickup Ruby and/or Python, but I'd need a bit of time to become as proficient with it as I am with C/C++. Who knows in the end it may be well worth my time to be a Ruby/Python dude, only time will tell.
Hey, have you looked at C#'s upcoming LINQ implementation? Check out Scott Guthrie's series on LINQ; Part 1, Part 2, and Part 3. It's going to make life more productive for the C# developer, that for sure.
Labels: .NET, Microsoft, Python, Ruby, Windows
comment
Copyright © 2001-2008 Rob Fahrni
