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

8

u/CrazedToCraze May 04 '13

Just to nitpick,

or C#

I've started my "main" programming (i.e. university studies) in C# for about 3 years and I haven't really seen any major criticism made against the language as a whole. As someone with limited experience in other languages it's been an absolute pleasure learning C#. I would recommend it based on me experience so far, and from what I've seen and heard there is a good job market for .NET/C#. I know Python is pretty much unanimously agreed upon as the language to start with here at Reddit, but I'd say C# is up there as well and doesn't get suggested enough.

1

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

The issue with C# is that it is not native and therefore needs that shitty .NET framework. And no matter what, you can't statically compile it. The only way to deploy C# applications is through the use of installers that would have to install .NET during the install. It's useless for creating portable applications and creates a barrier for customers that want to use your software.

Also, there is obviously a performance problem (you can't write games for example) and a lack of power when it comes to more low-level stuff.

C++/Qt pretty much does everything C# does and does it better.

5

u/wjbonner May 04 '13

Holy fan boy alert batman. Look, C# does have its cons; no language is perfect. But you are just being ridiculous. First, the .net framework is a great framework. Just because it isn't cross platform doesn't mean it sucks. If you need cross platform use a different tool. Also, you can build perfectly good web platforms off of .net, especially with MVC.

Further, Guild Wars is written in C# and C++. C# is plenty fast for most games, and if you can't get it working than you are probably doing it wrong. And what low level stuff? You mean like memory management? I mean, there are ways to get involved in that stuff in C#, but why would you want to? If you want to worry about memory management, use C, or asm, or a million other low level languages.

I am a long time senior developer, written apps in everything from java, C, C++, natural, cobol, C#, php, etc... C# is a great language. It's not perfect. It's not cross platform for making system apps. But it is pretty darn good. And I was a die hard C and C++ dev for years and only grudgingly started using it. Like any language, it's a tool, and just because you don't know how to use that tool doesn't make it bad.

-2

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

Holy fan boy alert batman. Look, C# does have its cons; no language is perfect. But you are just being ridiculous. First, the .net framework is a great framework. Just because it isn't cross platform doesn't mean it sucks. If you need cross platform use a different tool. Also, you can build perfectly good web platforms off of .net, especially with MVC.

Good framework. Terrible deployment: useless for portable applications + unnecessary barriers due to poor execution on Microsoft's side + no cross-platform support.

Further, Guild Wars is written in C# and C++. C# is plenty fast for most games, and if you can't get it working than you are probably doing it wrong.

You can write games in Java. Or even python. Doesn't mean you should. There is no denying that your game will run slower and be more sluggish.

And what low level stuff? You mean like memory management? I mean, there are ways to get involved in that stuff in C#, but why would you want to? If you want to worry about memory management, use C, or asm, or a million other low level languages.

The point is that if you want to do low-level stuff such as memory management or interacting with the hardware and I/O or other low-level functionalities, you can in C++/Qt. You can't do that in C# afaik.

I am a long time senior developer, written apps in everything from java, C, C++, natural, cobol, C#, php, etc... C# is a great language. It's not perfect. It's not cross platform for making system apps. But it is pretty darn good. And I was a die hard C and C++ dev for years and only grudgingly started using it. Like any language, it's a tool, and just because you don't know how to use that tool doesn't make it bad.

Name one thing that it does better than C++/Qt. C++/Qt has better performance, has cross-platform support, is more native, has better deployment, and supports more low-level functionality and has most of the functionality that the .net framework offers (I'm not 100% sure on this point: can someone that is experienced in both Qt and C# clarify?).

The major criticism to the Qt library is licensing and that it is not as well known as C#.

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.