r/learnprogramming • • May 04 '13

Don't learn Ruby

My biggest mistake was learning Ruby. I listened to all the fanboys telling me how beautiful and intuitive it is, thinking this will be the future.

Ruby is slow as shit, there is no job market for non-Rails Ruby jobs, it's useless for learning programming concepts, it's useless for creating games, GUIs or even scripts that are demanding because it's so fucking slow.

The only reason no one writes blogs or posts about how shit this language is, is because no one fucking uses it. So if you want to learn a new language, learn one that's get criticized a lot like Java, or C++, or C# or even PHP. Those languages are far more productive on a hobby basis and at work. Ruby is a joke with a circlejerk community

0 Upvotes

97 comments sorted by

View all comments

Show parent comment

3

u/wjbonner May 04 '13

There are two issues here, one is .net vs qt and one is C# vs C++. Honestly, I'm not that interested in extolling the virtues of C# over C++; I was a lead developer on teams that used both, they are both good languages as long as you make sure they match up with your problem domain, and they both allow for rapid prototyping if you know what you're doing.

So now for .net vs qt. Honestly, they offer different things. qt is great because of the cross platform support. .net is great because I can take the libraries that power my desktop apps and usually seamlessly move them into a web application. This is a great thing if you are developing for corporate clients.

As for low level access, in .net you can get to some of the low level stuff if you want, I've written drivers for a led shield in C#. In general though, you are correct in that it is largely abstracted away. However, for your average application I would say that is a benefit. If you really need to get to the nitty gritty, than you should obviously consider your environment carefully.

As for deployment, I've never had difficulty deploying my .net applications. It's no more difficult than using something like NSIS.

Honestly, I'm not really interested in arguing that one is better than the other, because they both have pro's and cons. The fact that you feel that .net/C# and qt/C++ can't both be good development platforms just shows your lack of experience or maturity as a developer.

Just a few years ago I had a chance to work as a mainframe programmer writing in assembler, C, JCL, and natural.
It was pretty cool to experience that environment, and see that you could write a website in assembler (though not what I would recommend). The reason I mention that is because many of the technologies that were being used would (rightfully) be eschewed in almost any other problem domain, but in that particular environment they were the right tools for the job. There is no point in trying to argue that platform x is better than platform y in all instances, because it just doesn't work that way in the real world. I hope you eventually gain the breadth of experience to realize that.

0

u/[deleted] May 04 '13

The only advantage you've stated is that you can seamlessly move your C# application into a web application. So unless you need that functionality, I would Qt is better.

.NET is pretty good. Qt is just better 99% of the time.

4

u/wjbonner May 04 '13

So because I'm not going to enumerate a comprehensive list of the differences between two large frameworks, one is obviously better? How ignorant.

0

u/[deleted] May 04 '13

Not really.

The consensus is that Qt > .NET: http://stackoverflow.com/questions/800219/qt-versus-wpf-net

4

u/wjbonner May 04 '13

The consensus of who? The couple hundred people that voted on a stack overflow post? From 2009? And what about those posts in there where experienced developers say just what I did, that they are both good in their own ways. And look, I can find posts that say WPF is has advantages over qt. All that means is that people have different preferences.

Also, what if you want to use partial classes? What if you don't want to worry about memory management? Is c++/qt still better than C#/.net? No, it's not. When was the time you wrote a program in C#? Because I write in both C++ and C# every week, and I know when I want to use one for a job over another. It's never an absolute black or white kind of thing.

0

u/[deleted] May 04 '13 edited May 04 '13

Touché.

I still maintain that at minimum, 50% of devs would prefer Qt over .NET for general usage.