What I wish a Ruby programmer had told me one year ago..
blog.sirupsen.dk
blog.sirupsen.dk
Probably should try longer than a few days, but this is the best/only metric for personal programming language (business/group programming may impose other metrics).
If you don't love the language you're programming with, you should find another.
It's the other way around. If you love a language, you are probably unaware of its flaws or of other languages (It's like the stupidity-confidence correlation). This is one of the reasons fanboys make me want to puke.
The important thing is just to keep quiet during the "best thing EVER!!!" phase. The reason fanboys are so annoying is the combination of enthusiasm and relatively shallow knowledge.
You'll be dragged, but you won't get any perspective if you know only that language.
P.S. I use OpenBSD.
The post in Google's cache, while the site is down.
When you go back to coding in other languages, you approach the same problems in different ways because you were forced to solve them in a strongly typed functional manner.
Also, not to nitpick, but Haskell isn't an ML dialect, and while my experience is with OCaml (not SML or F#), OCaml doesn't force you to do anything in a purely functional manner the way Haskell does - it just makes it an option. (I think this is a good thing, but I guess it's a downside when you're trying to force yourself to try new stuff.)
What's so great about Arch? Why should I waste my time getting the basic functionality working, like X or audio?
If I wanted something that constantly breaks things and then try to get off by looking cute, I'd get a puppy.
EDIT: s/Slackware/& user/
* Customizability. It's very easy to build a system just the way I want it.
* Rolling release. There are no releases every six months, but when a new version of a software is released, I get it after a short testing period.
* Package availability. Everything I need is either in the repositories or easily buildable from AUR. (Using simple recipes called PKGBUILDs).
BUT: This is only great, if you know your way around Linux - I can install and configure Arch in less than 2 hours, but my notebook for instance uses the same install for about 2 years now. The good wiki helps to gain this knowledge, but it's still very unfamiliar for most people.But if you want things to "just work" then Ubuntu is also great.
Learn what? How to get the basic functionality working? So that when when you are installing Arch, you would know how to do it? Sounds perfectly reasonable, I guess.
P.S. I've been using Linux since the '90s. Configured X, etc. a bunch of times. You know what I've learned? That it's stupid when the computer can't do it for you. Not all "learning" is created equal.
If that's your goal, you may be better off learning C or Assembly (since you are coming from PHP)
Honestly, your choice of words is distracting. Your server got "raped"? PHP is "evil?"
What, no Nazis?
I'm not sure why this post is getting votes...
More likely that choice of word comes from online first-person shooter games lingo like "Let's rape the opposing team's base".
Maybe I was translating from my native language.
And of course point them towards Linux:
“Windows is not the best development platform in the
world for Ruby. I recommend you to try out Linux. Start
with a simple distribution, like Ubuntu. And then I
recommend something like Arch Linux whenever you feel
like you are ready for something more advanced!”
Really? In an article about Ruby you feel the need to point people at your personal pet OS? Pointless.The improved flash performance of Ubuntu 10.04 will hopefully be enough to keep me out of Windows entirely from here on.
The maybe a advantage (if you agree with the OP)/maybe a disadvantage(if you like me, don't): Much more manual configuration.
I think it's a pretty good model. For 90% of the installed software there's really no reason to update packages more than every 6 months.