Please create an account to participate in the Slashdot moderation system


Forgot your password?
Slashdot Deals: Deal of the Day - 6 month subscription of Pandora One at 46% off. ×

Comment apache commons (Score 1) 115

"Commons"? Fortunately, not universal. Naming a library "commons" does not make it part of the language. All those Apache Commons libraries share one thing: they are mostly collections of anti-patterns. Stuff that can often be done better without dependencies, with real standard libraries (part of the platform) instead of collections of trees of mutually-incompatible libraries that look as written by a lazy first-year student. They feature null checks that make it obvious that the lazy programmer that use them consider null and empty as equivalent, which should in itself raise red lights. At best, they reinvent the wheel, quite often in a bad way. Those dependencies are something you won't find in my projects, and the first thing I remove from projects that I have to take over. Whoever depends on this deserved those things. I'd need to read TFA more extensively, but is there any bug report open for the concerned app servers?

Comment Re:If there are patent issues (Score 1) 355

Same thing, really. You can still run some DOS binaries from the 80s in latest windows, even if that's anecdotal. Nowadays, I wouldn't know which platform I could trust (= not just OS) to stay unchanged / compatible for years. Linux isn't a good example for that. BTW, I'm not on MS stack. Just wanted to be fair.

Comment Re: Ummmm.... (Score 1) 319

Java in the browser (applets) is a problem, as any untrusted code with that level of access. Java-generated pages isn't (JSP, JSF...), and can even be more secure out of the box. When we speak of Java web applications, most people mean java-generated pages on the browser. Applets are mostly gone, as they should.

Comment Re:Ummmm.... (Score 1) 319

> Since each supposed "security update" actually deprecates features and adds new ones, Not true. It's been backwards compatible since the beginning. Some very low-level tools can break on major jvm versions (mainly byte-code manipulation tools, which are common for example in servers), but it's mainly a question of upgrading them at the same time. Your code from 15 year ago will still work in 99% of cases, the remaining 1% being basically your fault.

Comment Just steal the damn drive (Score 1) 547

I just had the same problem a couple of months ago. I had planned to copy my data and wipe the disk before leaving. Unfortunately, as I was still working with a colleague 5 minutes before my finally leave, there was no time for that. I just took the hard disk with me. I just didn't want anyone to read occasionnal personal emails or such. There was no backup of my personal stuff, as all important things where under centrally backuped version control anyway. I heard from my ex-colleague that the project manager and the boss (with which I had some bad last days), came multiple times to try to start the (diskless) pc. They were clueless at the fact that it didn't boot. Just the fact that the pc didn't return to the dedicated it team comforted me in picking the damn drive. Management isn't supposed to bypass privacy policies. As it was a big public institution, they had them in place but I suspected they would be circumvented. Had they said anything, I'd have returned the 20$ (then wiped) drive without any problem. It's been in a drawer since then.

Comment Re:Java EE 6 (Score 1) 519

I fully agree with that. I do lot of projects with just about the same technologies. The learning curve is there, but it's worth it. Java EE has one killer thing that I never saw in other platforms: standards, with multiple implementations. JSF might have a bad reputation due to it's past, JSF 2 manages to provide a cool, efficient tool for quick development. Same for EJB, JPA, etc. Plus, they all have multiple implementations. Nowadays, you can switch application server or JSF implementation quite easily, without having to touch the code. This makes things better than with any random framework: you will have years of backwards compatibility, you can evolve your application without rewriting everything if some implementation disappears, bugs aren't marked as "not a bug" (if it's a deviation from the JSR, it's a bug), etc. To answer the OP's question: if you need something simple to see how programming works, pick anything and try, the only thing you can lose is time. If you want something strong, strict, robust etc., pick up Java or .net. In my opinion, .net is technically better, but lacks the standardization and the multi-platform aspects.

Collision of Two Asteroids Spotted For the First Time 31

sciencehabit writes "Astronomers report that a small asteroid located in the inner asteroid belt between Mars and Jupiter took a major hit early last year. Previously rendered only in artists' conceptions, the first asteroid collision known in modern times revealed itself in a tail of debris streaming from what astronomers at first assumed was a comet. Instead of a steady stream of dust, however, they found boulders near the object with dust moving away from them."

Honesty is for the most part less profitable than dishonesty. -- Plato