Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
Check out the brand new SourceForge HTML5 speed test! Test your internet connection now. Works on all devices. ×

Comment Re:Impossibru! (Score 1) 245

If you read what the GP said, it never said it was "all right". In fact, I think it's pretty clear that GP was implying that violating IP rights isn't something to be proud of.

Two wrongs make two wrongs, and it's just fair that both are mentioned.

It seems you're complaining that somebody is presenting the full picture. It might be irrelevant, but hey, you're not complaining about it being offtopic.

Comment Re:All in works (Score 1) 192

I've had my own intensive "eat sleep code repeat" cycles back in high school, which is more than a decade ago. That's probably when I went from being a shitty programmer (by adult standards) to an OK programmer. These days I mostly fool around random things when I'm not working, instead of being a beta tester for some bleeding edge software development stack (that's what I secretly think of developers who use RoR and node...)

The "eat sleep code repeat" cycle is probably quite effective initiallly, I just think there are diminishing returns to this approach. If you've done this thing for (say) 10 years already, you probably don't need another twenty years doing the same thing -- it either gets repetitive (which, especially in this field, isn't exactly a good thing), or you've managed to continue to innovate, but by then you've probably holed yourself into a tiny niche or something.

Not that I disagree with you though, the *intentional* breaks from actually programming, i.e. those that you force on people just because doing something other than coding "makes you a better coder" probably don't really work. I guess you just need to do coding a lot, and also somehow manage to squeeze other stuff into your life as well.

Comment First world problems... (Score 5, Insightful) 227

210k salary and you can't feed a family of 3.

Software engineering jobs are in ever more demand today, and you're talking about bleak prospects in a job which you say isn't going to fire you any time soon.

You talk about stability and jumping ship from a safe job in the same sentence.

Hmm.

Actually, what do you want? Or maybe you just hate software engineering as a job or career?

Comment Re:Proprietary (Score 1) 648

The argument goes both ways -- I've spent hundred hours of my life learning POSIX, and if my boss wants me to run a POSIX program in Windows, I'm pretty much doomed. (I know a bit of Win32 API if that helps...)

"Open" does not mean "supported on all major platforms". It only means "can be supported by other vendors if they choose to". And if you choose a language or technology that is out of fashion, it doesn't really matter whether it is open or not.

And yes, I know Microsoft Windows is POSIX compliant.

Comment Re:OracleVSGoogle: Judge can program, you still fo (Score 1) 187

clean-room reimplementation is legal

Clean room reimplementation is legal as long as the specification used by the implementors is free of copyright (and other I.P.) issues.

I definitely agree that some of the prior cases of clean-room implementation is at odds with the notion that APIs are copyrightable. To be honest, copyright law has never been logically consistent to me -- which is why I don't even pretend to have knowledge of it unless I'm arguing about legal topics on slashdot ...

Comment Re:OracleVSGoogle: Judge can program, you still fo (Score 1) 187

The "wrong decision" referred to the GP isn't about the trivial range check, but rather the notion that APIs are not copyrightable.

It would be really shitty if APIs were copyrightable, but, as the GP said, that has been the conventional understanding of copyright law for a long time.

It would be interesting to see how the story unfolds, but really, there's nothing funny about the notion of APIs being copyrightable.

Comment Re:The FSF overreached with GPL v3 ... (Score 1) 183

It is legal paranoia. Just like how IT-types have network security paranoia and ban a bunch of software/tools that *could* *potentially* introduce security issues to the company network...

I mean, sure, if you spend time looking at an individual license it could be OK. But why spend the time to investigate? Just blanket deny, and if somebody thinks it's worth fighting the bureaucracy to use a damn piece of software, *then* it might be worth looking into making an exception...

Slashdot Top Deals

Theory is gray, but the golden tree of life is green. -- Goethe

Working...