Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:Netbeans is looking just fine (Score 1) 141

I assume that there is some type of application for which NetBeans is as good as (or better than) Eclipse - that application is NOT desktop/standalone Java application.

As someone that maintains a java-based emulator for several years I couldn't disagree more with that.

As a long-time Eclipse user, I moved to NetBeans for just short of two years before the delay when starting an application and the very flaky dependency building (when multiple projects are included in the final application) drove me over the edge and back to Eclipse. In Eclipse you hit "debug" and it starts debugging the application. In NetBeans you hit "debug" and it starts to compile. Change code in Eclipse, hit save, and quite often the application continues with the new code. In NetBeans the on-the-fly debug changes are unreliable and slow (another compile cycle).

Then you are doing it wrong, dude. You should make sure to check "Generate debugging info" under the compile settings for the project, which eliminates the need for the IDE to do it on-demand later. You can connect the debugger to a running instance by clicking "Attach debugger" as long as the process has JPDA enabled already. I do it all the time when I do J2EE or Sling-based dev work since the app servers I run locally have JDPA enabled for that purpose. If you're debugging a desktop app then, yes, you must tweak the parameters ahead of time, or just remember to run with debug instead of clicking "run", but that's minutiae and can be easily resolved by a little self-organization (e.g. decide if you are debugging or not before you launch the app) As for the flaky dependencies, were you using a Netbeans-defined project or a Maven one? If you define your project as a maven project then not only do you get simplified dependency management (which I use without any issue with both large reactor project structures as well as sibling-level dependent ones) but you also get CI support for Hudson/Jenkins. Incidentally, Netbeans can talk to Jenkins directly if you configure it to do so. If you were using a maven project structure and you still couldn't get it to work then you might have been doing something wrong (or just violated the KISS principle somehow.)

Comment Netbeans is looking just fine (Score 4, Insightful) 141

I've been using Netbeans since version 3.6 and am quite pleased with how it works, even in the recently released 8.1 beta. I've tried JetBrains and it seems fine enough for what you pay for (except the maven support feels very clunky and not very seamless, IMHO.) But feature comparison vs. price paid? Netbeans wins, hands down. I've tried Eclipse many times over the years also, but come to the same conclusion: I still don't personally like using Eclipse. Therefore I keep going back to Netbeans because it has 90% of what I need and there's plugins for the other missing 5%. The rest? I have a command line and I'm not afraid to use it. You can use whatever tool(s) you like, but I've been coding in Java professionally since 2000 and you can uninstall my copy of Netbeans when you pry my harddrive from my cold, dead hands.

Comment It's supposed to look that way (Score 3, Interesting) 167

There are a number of titles on NES that I can think of such as Empire Strikes Back which only look correct on CRT or anything that does proper NTSC color artifact emulation. (and actually sonic games on genesis too!) I've written a game editor for Apple // graphics which uses NTSC artifacts as part of the editing experience -- and also part of the image dithering/conversion algorithms -- and believe me: It makes a huge difference when you are designing graphics with a 6-color palette where you actually get an extra handful of extra "fringe" colors when using some combinations. If you are still unsure, use an emulator with NTSC emulation (Blargg's is great) and then switch over to plain RGB. There is a huge difference. Also, a final note on this (Caveat: I am an emulation author and this information is in a very well written wikipedia article on Y'UV if you want to fact check me...) You will NOT EVER get the same colors from RGB than you get from a CRT. The color spaces are different. Emulators can simulate (and in some cases very well) what an analog display does, but it only goes so far. In the NTSC-to-RGB conversion process you wind up having to transform from one color system (Y'UV) to another (RGB) using some rather simple math but then you also have to alias the results to fit the values (which are often outside the 0-255 range). There are colors in the Y'UV spectrum (I'm talking about the Apple colors but there are some on Atari and NES too) that are so saturated that they look completely neon, and those colors actually don't exist in the RGB spectrum at all so you wind up with a rather muted look compared to the real thing. A scan doubler is okay I suppose for this, but really if you want it to look old school nothing beats the real warm glow of a CRT. If you want to play retro games on an RGB screen, just use an emulator. They're cheaper, and if done correctly you're lucky to ever really notice a difference. :-) I think that you can take a Raspberry Pi and make a dedicated emulator solution for 20% the cost of this scan doubler solution and be just as happy if not happier.

Submission OpenShot Video Editor Achieves $35k on Kickstarter, Final Goal in Reach!-> 5

JonOomph writes: The popular open source video editor, OpenShot, has less than 39 hours remaining on popular crowd-funding site, The lead developer, Jonathan Thomas, has proposed a revolutionary new feature, which would allow users to offload CPU, memory, and disk cache to a local server (or multiple local servers), dramatically increasing the speed of previewing and rendering. The more servers added to the pool, the faster the video editing engine becomes (with the primary limitation being network bandwidth). If the final goal of $40k is reached in the remaining hours, this feature will be added to the next version of OpenShot.
Link to Original Source

Comment Re:Low tech solution (Score 1) 301

Linux users could use the Gnome-shell-timer extension, which is perfect for Pomodoro. Of course cell phone timers work well. My most productive weeks look like this: 1) Spend the first hour of the day going through the list of to-dos. If anything is too vague or undefined, I either need to set aside time to research it, or if I break it up into small measurable pieces. These are key because crossing them off later lets me know I'm not a total f**k-up. 2) I keep this to-do list in a very simple editor called "Focus Writer" which occupies the full screen when it is active. This prevents me from getting immediately distracted. 3) Once I get the tasks listed, I prioritize them. Usually the ones that are absolutely important go to the top (criteria: If I skip this will the customer or my boss yell at me?) 4) I stick to the list. I really should try pomodoro because I too get way overly distracted. You're not alone. Damn internet. My core non-web programming tasks get done faster. Why? Because when I'm testing non-web apps, I don't have a browser open. I don't have to google how to solve basic javascript problems. I just get stuff done. But when I'm dealing with a quirky browser behavior with extJS or jQuery.... yeah, where did the time go? And why am I reading TheOatmeal again???

Comment This is old hat (Score 1) 149

I don't see how someone reinventing the wheel should get /. coverage. WorldEdit, a very popular plugin, already has javascript integration. Also, check out GroovyBukkit for groovy integration that is incredibly easy to use. I did one-liners in Groovy to, say, lay rail tracks wherever you're standing if you are holding a rail in your hands -- that way you just walk and the tracks follow you. I have a 100-line bot named "David" (named after the Prometheus character) which helps non-op people obtain things without having to bug me all the time -- it's basically a switch statement and a lot of regex. Anyway, back to the point: It is extremely trivial to write a minecraft mod if you know how to code already. Writing a mod that is actually useful and doesn't crash the server -- that's another story. My only advice is to learn how to manage threads (so that uncaught exceptions don't crash the main server thread) and write watchdogs into your code to avoid infinite loops. :-D -B

The life of a repo man is always intense.