|
Despite its name, that appears to be a lot more of a language reference than a tutorial. What I'm looking for is more a set of sample programs with explanations of why they're written the way they are. (From peanut gallery comments I've seen elsewhere, The Ruby Way(tm) is often different than the naive approach that someone coming from a member of the C family would choose.)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I have this book[^], and it is a very good reference.
On a side note, I also have this book[^] and this book[^], both about Rails.
Keep Clam And Proofread
--
√(-1) 23 ∑ π...
And it was delicious.
|
|
|
|
|
I believe Marc Clifton is the resident RoR guru, doing a quick search here he's done a couple of related articles and if I remember correctly you might look back on some of his early lounge posts I believe he gave a slew of information pertaining to the subject.
|
|
|
|
|
|
Rubykoans is a great place to start. It's test first learning so you'll fall right in line with the rest of the community's expectations.
|
|
|
|
|
I am currently re-installing Cygwin x64 as a recent crash made it go FUBAR (the crash was caused by VirtualBox. No real surprise there, eh?) I also will be updating a number of packages, such as Git (1.7.9 -> 1.8.4.1), Bash (4.1.something -> 4.2), and so on.
How many people here use Cygwin? How many knew there is now a x64 version? How many have no clue what I am talking about? How many don't care?
Keep Clam And Proofread
--
√(-1) 23 ∑ π...
And it was delicious.
|
|
|
|
|
Cygwin is great! I've been using it for years. I too recently discovered there's a 64-bit version by chance when I went to install it on a machine. I've never had to re-install it though, but I also haven't used it inside a virtualbox guest OS. I wouldn't think that would be a problematic configuration though, VirtualBox seems to work pretty smoothly.
|
|
|
|
|
Actually, VirtualBox caused Windows 8.1 to BSOD, corrupting several HDD sectors. VB also has issues with networking on Windows 8.1, and crashes.
The Cygwin setup encountered an error and failed due to a network issue. All five mirrors I tried gave the same error, so I think a Cygwin package is corrupt. They usually get those fixed quickly, IME.
Keep Clam And Proofread
--
√(-1) 23 ∑ π...
And it was delicious.
|
|
|
|
|
Interesting.... I have one Win8 machine and recently upgraded to 8.1 but haven't yet used VirtualBox on it. I have had issues with installing VirtualBox on a machine which had VPN client software that setup a virtual adapter. The VirtualBox installer would just hang due to that adapter. Scary that virtual box would screw up the drive contents!
So a clean re-install got cygwin working again?
|
|
|
|
|
Still fails. I have no clue what is going on, and I will try redownloading the installer tomorrow. My internet connection is kinda flaky at night.
Keep Clam And Proofread
--
√(-1) 23 ∑ π...
And it was delicious.
|
|
|
|
|
You're supposed to always use the most recent installer anyway. Although your symptoms are really suspicious, I've never seen anything like this.
|
|
|
|
|
I used to love cygwin, I still have it installed but these days I tend to use linux in a vm instead. How on earth do you deal with a 4gb text log file without less, tail and grep?
I had no idea there was a 64bit version though.
|
|
|
|
|
Last time I had a look at it, the 32bit version was pretty broken but at least semi-usable. The 64bit version was completely borken, seemingly beyond repair, but I guess it's been fixed now..
|
|
|
|
|
What are you all talking about? Cygwin is rock-stable. Any time it goes wrong, a simple rebase fixes everything (and it's not Cygwin's fault, it's a sh*tty windows DLL model).
|
|
|
|
|
vl2 wrote: a simple rebase fixes everything
If something requires fixing, that means it's broken.
It's also entirely its own fault - plenty of software works just fine on Windows without periodically using the excuse "yes but DLL model".
vl2 wrote: Cygwin is rock-stable.
Ok. Like I said, I haven't used it in a while. Maybe it got better.
|
|
|
|
|
DLL offsets are broken by Windows and the other windows software. And windows does not support position-independent DLLs (in 21st century! omg!), so the usual Unix model does not map well onto windows practice.
I've been using cygwin since around 1999, and it was pretty solid back then. The only real problem with cygwin (back then, and still affecting) is load times for heavy C++ applications, due to a lack of lazy static initialisation (again, thanks to an outdated and crappy COFF model).
|
|
|
|
|
vl2 wrote: I've been using cygwin since around 1999, and it was pretty solid back then.
Really? Never even a "nope, there's a space in that path so I'm just going to completely freak out"?
The first (and only) time I tried the 64bit version, it just completely refused to work at all. Some arcane error when trying to start that shell thing.
|
|
|
|
|
Unix tools will freak out on spaces in paths anyway, no matter what your underlying platform is. It's not a bug, it's a feature.
But I admit I never tried cygwin on Windows8, and I'm not going to leave 7 any time soon.
|
|
|
|
|
Most paths on Windows have spaces. Refusing to deal with that reality is absolutely not a feature.
|
|
|
|
|
Cygwin feature is to be POSIX-compatible. Introducing incompatibilities for a sake of some stupid spaces is not an option.
|
|
|
|
|
Great, so it's stuck between not working and not working.
|
|
|
|
|
It is working, perfectly. Just not the way windows-minded folk expects it to.
|
|
|
|
|
Ok, try to install it in a directory with a space somewhere in it then. Like "Program Files". That's supposed to work, right? Well it didn't.
That it doesn't like paths with spaces in it internally in its own little world is fine. That's not what I'm talking about.
|
|
|
|
|
Why is it "supposed to work", to start with? Windows mindset is such an amusing, funny little thing!
|
|
|
|
|
When in Rome .. well you know the saying.
Having a limitation "installation directory may not contain spaces" is a bug. There are simply no excuses. Paths contains spaces on Windows. Almost always. That limitation essentially means it can't be installed at all, except in some places that are off-limits like "C:\".
How would you like it if people "ported" things from windows to linux and kept all the windows-quirks?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
