To compile or not to compile?

That is the question... I had a conversation with a few guys from our local Java Users Group about PHP, Ruby, (scripting languages in general) vs. compiled languages. I have a background in both so I had some strong opinions and thought I'd jot some of them down.

First off, I am of the opinion that scripting (dynamic) languages and compiled languages have their own respective places in programming. There are good and bad languages out there and whether or not they are compiled doesn't enter that argument. People calling scripting language users "hacks" is ridiculous. This is most likely coming from someone having done compiled language development all their career. The one time they tried scripting something, they got bit by the loss of type safety or could not "refactor" or something along those lines. We mock that which we don't understand...

The fact is, scripting languages give you more flexibility, but with that comes responsibility. I worked in a group that did scripting for Web stuff and we had TONS of code, no IDE (just vi) and had successful "deployments" all the time. You have to know what you are doing when you start messing with a scripting language code base. Now if you start mucking with some code written in Java, you can use an IDE to help you along the way. I think it much easier to get your feet wet in Java once you understand OO due to the great IDE's out there that will help you. But once you get going with PHP or Ruby... you can fly, and your development becomes more agile due to the flexibility an interpreted language gives you.

I write code in a few languages, compiled and dynamic... and the bottom line is: the code you write is really just a dumbed down human version of instructions, it's documentation. A compiler (at some point) interprets your mess and sometimes through more conversions finally makes something the computer can understand. You can't argue which is better unless you are talking about a specific problem domain with all else equal.

Happy coding!

Trying new setup…

So I heard about NginX and figured I'd give it a try. The setup for NginX (pronouced engine X) was a breeze. I have a few Mongrels running behind it and things seem to be going pretty well at the moment. I still would soo much like to see a nice packaged server solution for Rails running in a multi-threaded environment. YARV, hurry up! :)

Benefits of Ruby

For me, one of the real benefits so far is getting me back into the C world... I've been away for some time doing Java mostly so it's fun to get back into the swing of things.

I've just recently found the YARV project. From what I have seen so far, it appears to be working toward a multi-threaded version of Ruby which makes me very happy! Ruby is a very cool language and serves a good purpose. Rails is wonderful for getting things off the ground soo quickly... but in today's web world, non-thread safe languages pose a few barriers.

These barriers can definately be overcome (and are everyday) but the web is a multi-threaded world... if YARV does push Ruby into the MT way of things, I think it will only serve to boost the already crazy swirl surrounding the Ruby/Rails phenomenon.