News for hackers. Stuff that matters.
Re:Signs You’re in a Dead-End Job by dschiptsov on Friday July 26, 2013 @09:01AM (#6107954)
Oh, that's simple - you are 9-to-5 coder in a language which name begins with J or ends with #.
Re:Signs You’re in a Dead-End Job by mironathetin on Friday July 26, 2013 @09:25AM (#6108051)
In what kind of mind distortion field are you living? I used to write code in Java and Jython for a big science project. Now I switched (avoid the word advanced) to a new big science project, where we use c, c++ and python.

This is a nightmare compared to everything we did before. I always liked to work in Java, but I never realized how powerful it is compared to the other stuff. We as a team are close to switching languages and starting from scratch, its so bad.

Re:Signs You’re in a Dead-End Job by vonmoltke on Friday July 26, 2013 @09:52AM (#6108179)
A significant portion of the ML/NLP world runs on Java. Its the worst language for the job, except for all the others.
Re:Signs You’re in a Dead-End Job by yummyfajitas on Friday July 26, 2013 @10:48AM (#6108488)
Re:Signs You’re in a Dead-End Job by jbooth on Friday July 26, 2013 @12:06PM (#6108909)
A lot of people (myself included) see Scala as being one step forward, two steps back. Some good features, and then a whole bunch of poorly thought out, wankerish features that can only serve to screw up your code base if some developer gets bored and makes the mistake of using them.
Re:Signs You’re in a Dead-End Job by happy_dino on Friday July 26, 2013 @08:04PM (#6111237)
> and then a whole bunch of poorly thought out, wankerish features that can only serve to screw up your code base if some developer gets bored and makes the mistake of using them.

I'd love to see an example of that!

Re:Signs You’re in a Dead-End Job by jbooth on Saturday July 27, 2013 @01:12AM (#6111955)
Sure, the crazy symbolic operator overloading and a bunch of libraries that encourage you do do things like a :=: b and have it mean something.

Also, there's something about the net sum of the type system where it feels like there are a lot of concepts at work and it's easy to get lots with what type something is, exactly, especially if you didn't write the code and you're just skimming it.

Re:Signs You’re in a Dead-End Job by happy_dino on Sunday July 28, 2013 @05:14PM (#6118118)
Scala has neither operators nor operator overloading and I don't know any library which "encourages" doing those crazy things.

There are a few places where symbolic method names are used, and in pretty much every case, it is well-established prior art: +, -, *, /, etc for math operations, ! for sending actor messages (Erlang), &, | ,^ for bit operations (C and friends).

Regarding the type system ... well, the alternative is stuff like reflection and casting. Both introduce the possibility of runtime failures and make refactoring and reasoning a lot harder.

Sure, sometimes a well-placed I-assume-this-can-never-fail cast is exactly what one needs, but I'm happy that Scala gives developers another, safer option here.

Re:Signs You’re in a Dead-End Job by mironathetin on Friday July 26, 2013 @10:25AM (#6108362)
well said.
Re:Signs You’re in a Dead-End Job by Roboprog on Friday July 26, 2013 @09:58AM (#6108211)
Of those 3 languages, I would blame C++ for laying out a minefield.

Considered FreePascal or Go, maybe? Pascal doesn't have a garbage collecter, but it's not "pointers everywhere" like C, and string values are reference counted. Having done a lot of C, I really miss function pointers when working in Java. (Pascal calls them procedural types instead of func ptrs)

Re:Signs You’re in a Dead-End Job by ihnorton on Friday July 26, 2013 @10:14AM (#6108295)
What field are you in, and what are your biggest pain points with that stack? (I have a long list of issues in "small" science, curious how they compare)
Re:Signs You’re in a Dead-End Job by mironathetin on Friday July 26, 2013 @10:21AM (#6108335)
I am in astrophysics (lots of telescope and satellite data). Our main point is that Java provides a complete environment: no shared libraries, no compilation problems when moving to other machines.

The next is productivity. In java, I could focus on the problem. In c/c++ it takes only minutes, until I have to think about why my code doesn't compile. That can easily take me away for hours, sometimes longer.

The most significant downside of java is for me memory consumption. It needs a lot of care and experience to get that right.

Python on the other hand is nice. Although it does not integrate with c++ as nicely as jython integrates with java.

Re:Signs You’re in a Dead-End Job by ihnorton on Friday July 26, 2013 @10:57AM (#6108546)
Thanks for the perspective. Sounds pretty familiar. Aside from missing math syntax, Python by itself/packaged can be great -- until it's slow, which leads to the real problem for me, that compiling mixed Python/C[++] and dependent libraries is just absolutely horrendous on Windows. Unfortunately, Windows is where my users are.
Re:Signs You’re in a Dead-End Job by dschiptsov on Friday July 26, 2013 @10:10PM (#6111603)
Here is a glimpse of that reality distortion field on this site: http://talks.golang.org/2013/oscon-dl.slide

And this very site itself is another reality distortion.

Re:Signs You’re in a Dead-End Job by voltagex_ on Friday July 26, 2013 @11:23AM (#6108692)
What are your particular problems with C#/F#? Honestly interested.
Re:Signs You’re in a Dead-End Job by UK-AL on Friday July 26, 2013 @11:55AM (#6108850)
They probably get paid more than him ;)
Re:Signs You’re in a Dead-End Job by umsm on Friday July 26, 2013 @03:30PM (#6110018)
There is a lot of truth to this statement. I've seen so many jobs that are looking for .NET coders that pay so much more than most other languages...
Re:Signs You’re in a Dead-End Job by Jimmy on Friday July 26, 2013 @10:40AM (#6108450)
So everyone working in J or F# has a dead-end job?