companies need to use cooler languages (scala, groovy, clojure)

[brianmanahan]

so that i can go work there -_-

 

[BrightCandle]

I have been using Windows DLL hooking recently for a program and found I basically had to use C++. I considered D but decided against it since the examples I had were in C++ and I have used C++ before. I looked at Go but it didn't support embedded assembler so had to rule it out from a practical point of view.

I would have loved to do it in something a bit more modern than Visual Studio with C++ but in the end it just ended up being the only real option. But I will be using Scala or maybe Go for the launcher program and analysis because I can't stand working in C++.

In the end even with all the choices you may find you aren't using a super cool language because its not practical.

 

[Markbnj]

Most companies stick to the mainstream, but there is commercial work being done in all those languages. If you're good with any of them you should be able to stir something up.

 

[KB]

There are too many programming languages out there. Please eliminate 2. I am not a crackpot.


I haven't even heard of clojure. Had to wikipedia it. I see more and more development moving to javascript. Windows 8 apps, PhoneGap, html5, you can even interface robots with node.js. That being said javascript still isn't the best tool for every job.

 

[purbeast0]

ive been doing groovy for the past year or so. it's neat but there are still a lot of "groovyisms" that i have to lookup when i come across them. i look at it as shorthand java with more flexibility. i've heard of scala and clojure but never used them myself.

i really have absolutely 0 interest in going back to c++. i was doing it for 5 years after i graduated and been on java based stuff since, and just have no interest in going back.

 

[brianmanahan]

There are too many programming languages out there. Please eliminate 2. I am not a crackpot.

nope, you are a fuddy duddy! like the guys at work who think everything should always be written in COBOL, forever

 

[exdeath]

C and assembly. Everything else can go to hell.

These hipster fad languages created every time someone needs to create a language to graduate can DIAF.

 

[tfinch2]

C and assembly. Everything else can go to hell.

These hipster fad languages created every time someone needs to create a language to graduate can DIAF.

Ugh, not this again...

 

[purbeast0]

C and assembly. Everything else can go to hell.

These hipster fad languages created every time someone needs to create a language to graduate can DIAF.

i guess you hate these forums then, since they weren't written in C or assembly.

 

[mjd]

so that i can go work there -_-

Grab a couple friends. Pick an idea, make sure you include a business/entrepreneur major.
And found your own company using the tools languages you love.

You'll enjoy it.
-M

 

[exdeath]

Ugh, not this again...

Well you know... until microprocessor architecture changes... which it hasn't really since 1971. Still have registers, instruction sets, etc. Somebody has to write the VMs and dev tools for the latest fad script toys in some other language that allows it to run on a physical microprocessor...

 

[QuietDad]

25 years in Programming and development, the reason you don't use fad languages the new guy wants to use is because when he leaves because you wont paint his office purple someone else has to maintain it. You stick to mainstream languages that the most people know so business goes on.

 

[tfinch2]

Well you know... until microprocessor architecture changes... which it hasn't really since 1971. Still have registers, instruction sets, etc. Somebody has to write the VMs and dev tools for the latest fad script toys in some other language that allows it to run on a physical microprocessor...

Nobody is arguing that C or assembly does not have a place. The fact that you do not understand that you should use the right tool for the job time and time again shows that you are either trolling or naive.

When you build a deck you could do it with a screwdriver and a handsaw. All other tools can go to hell.

 

[brianmanahan]

i think way too many places get stuck with average programmers who have no interest in improving their skills, learning new languages, etc.

seriously most of the people i work with are ho-hum, clock in clock out people who havent gotten any better at developing software in 10-15 years and are just in it for the money.

it gets depressing at times

 

[beginner99]

i think way too many places get stuck with average programmers who have no interest in improving their skills, learning new languages, etc.

seriously most of the people i work with are ho-hum, clock in clock out people who havent gotten any better at developing software in 10-15 years and are just in it for the money.

it gets depressing at times

And there are the old one sticking to old ways of doing things and spending 50% of their time fighting progress. Albeit that can be said about almost any area not only programming.

 

[Markbnj]

And there are the old one sticking to old ways of doing things and spending 50% of their time fighting progress. Albeit that can be said about almost any area not only programming.

And then there are the young ones, falling in love with every new cool trick they see their friends using, and implementing things in the most complicated way possible because they're fascinated with how smart they are .

 

[mjd]

As one of the uber-experienced old-timers, I have learned repeatedly that learning new programming languages is easy. Solving rewarding, tough, or profitable problems is the fun part. Pick the right tool for the job and move-forward to the fun part!

 

[teb468]

ive been doing groovy for the past year or so. it's neat but there are still a lot of "groovyisms" that i have to lookup when i come across them. i look at it as shorthand java with more flexibility. i've heard of scala and clojure but never used them myself.

i really have absolutely 0 interest in going back to c++. i was doing it for 5 years after i graduated and been on java based stuff since, and just have no interest in going back.

I am the same way except I've been doing it for about five years or so. If I had to go back to programming normal Java, I might want to shoot myself. It spoils you.

 

[LevelSea]

And then there are the young ones, falling in love with every new cool trick they see their friends using, and implementing things in the most complicated way possible because they're fascinated with how smart they are .

Relevant: http://xkcd.com/1270/

 

[Gryz]

Imho, there is only one thing really important when you write software: readability.

Software is written once. And then fixed, improved, upgraded, fixed again a few times. Each lines gets written 1-10 times during its lifetime. But those same lines get read hundreds, if not thousands of times. Before you can write additional code, or fix bugs, you need to read the existing code. Sometimes that is your own code, usually it is someone else's code. Coming up with good solutions, and implementing them, takes a lot of time. But reading and understanding someone elses code takes an aweful lot more time. And often, it will not be trivial to understand your own code that you wrote 5 years earlier.

So anything you do when writing code, readability is the most important factor, imho. Documentation, comments, even picking function-names and variable-names. Even the wrong coding-style can make code unreadable. Picking the right language is a factor too. That's why assembly is hardly ever the best solution.

For the same reason, many of those fancy new languages are useless too. Because most people don't know them. Or because people use heaploads of libraries that you need to plough through before you understand what it does. C++ and Java are OK, because they are well known. Perl is an example of a shitty language, even though well known. Because writing a function takes 1 minute, understanding one function takes an hour.

All those new fancy languages you learned at university ? 99% Of them will not be used. Not in real projects. Not in large projects. Not in projects that have multiple people working in them. Not in projects for software that will stay around for a decade.

 

[QuietDad]

C++ (and it's predecessors C, and C+) have been around since DOS. Fad languages come and go. When you write business code, you want it to still be maintainable next year. It's really that simple. Java makes an interesting web page. Try writing a payroll system or operating system with it.

 

[Puddle Jumper]

When did using fad languages like Scala become good programming?

 

[Ancalagon44]

C++ (and it's predecessors C, and C+) have been around since DOS. Fad languages come and go. When you write business code, you want it to still be maintainable next year. It's really that simple. Java makes an interesting web page. Try writing a payroll system or operating system with it.

Try writing an interactive website with C - including all of the client side bits.

All you need to do is write your own client side C parser/compiler and get all of the major browser manufacturers to include in their browsers. Easy.

 

[uclabachelor]

so that i can go work there -_-

You don't select a language because it's cool. You select a language because the job dictates the need for it.

 

[Leros]

You don't select a language because it's cool. You select a language because the job dictates the need for it.

Imagine if you had to maintain a 10 year old system in whatever the "cool" languages were 10 years ago. It would be awful. The library support would be weak/non-existent. The knowledge on the internet and among peers would be weak/non-existent. I'd much rather use something like Java.