I just gave a presentation in my Programming Languages class about Ruby. Coming from a backgroung in mostly emperitive languages, I've found that Ruby is very easy to understand and work with. Also I like Matz's "Principle of Least Surprise," which in my opinion makes it a lot eaiser to work in. The only severe problem that I ran into in my breif tour of the language was without strong typedefs or compling it down to machine code, it's going to have a harder time competeing with languages like Python.
"If you pick up a starving dog and make him prosperous, he will not bite you. This is the principal difference between a dog and a man." --Mark Twain
Is it me, or if Caldera is still going to call it "OpenLinux" that the license should then still be free, or does that go against the GPL, to require that something have a seperate licensing agreement then the GPL (which virtually all Linux software is distributed under)?
IF IT'S OPEN, WHY ARE WE GETTING CHARGED FOR A LICENCE? Has Caldera spent too much time in Redmond?
I go to a relitivly small college in upstate NY. A Semester before I became a CS major there was a major shift to using Java as the first language encountered. I didn't like this at first, Java is relitivly ugly and the syntax is only slightly less obfuciated then PERL, but after a number of Semesters dealing with Java on a daily basis I understand why the shift was done: Java forces you to code in a fairly specific way, that being OO. Trying to learn adapt to non OOP can be a daunting task, as I have now experianced.
Enforcing good programming habbits early is very important, and without a backbone in Java I'm not certain that I would have recieved this. Since learning the real ins and outs (or should that be System.in and System.out ?) of the language I have come to appreciate it.
There are many positions on this issue to be sure, but the important thing is that people need to learn somewhere. I think that it's better to learn the hardest way of doing something before learning that there is a better way. For example, I work with PERL now on a daily basis, and readablity is one of the things that I spend the most time looking at. The old adage: "Thouugh a program be but one line long, someday it will have to be maintained" is one that I take very seriously (especially since I'm now working as a QE intern).
Slashdot Mirror
I just gave a presentation in my Programming Languages class about Ruby. Coming from a backgroung in mostly emperitive languages, I've found that Ruby is very easy to understand and work with. Also I like Matz's "Principle of Least Surprise," which in my opinion makes it a lot eaiser to work in. The only severe problem that I ran into in my breif tour of the language was without strong typedefs or compling it down to machine code, it's going to have a harder time competeing with languages like Python.
"If you pick up a starving dog and make him prosperous, he will not bite
you. This is the principal difference between a dog and a man." --Mark Twain
Is it me, or if Caldera is still going to call it "OpenLinux" that the license should then still be free, or does that go against the GPL, to require that something have a seperate licensing agreement then the GPL (which virtually all Linux software is distributed under)?
IF IT'S OPEN, WHY ARE WE GETTING CHARGED FOR A LICENCE? Has Caldera spent too much time in Redmond?
I go to a relitivly small college in upstate NY. A Semester before I became a CS major there was a major shift to using Java as the first language encountered. I didn't like this at first, Java is relitivly ugly and the syntax is only slightly less obfuciated then PERL, but after a number of Semesters dealing with Java on a daily basis I understand why the shift was done: Java forces you to code in a fairly specific way, that being OO. Trying to learn adapt to non OOP can be a daunting task, as I have now experianced.
Enforcing good programming habbits early is very important, and without a backbone in Java I'm not certain that I would have recieved this. Since learning the real ins and outs (or should that be System.in and System.out ?) of the language I have come to appreciate it.
There are many positions on this issue to be sure, but the important thing is that people need to learn somewhere. I think that it's better to learn the hardest way of doing something before learning that there is a better way. For example, I work with PERL now on a daily basis, and readablity is one of the things that I spend the most time looking at. The old adage: "Thouugh a program be but one line long, someday it will have to be maintained" is one that I take very seriously (especially since I'm now working as a QE intern).
Why not....