Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:No (Score 2) 180

by jb_nizet (#47419923) Attached to: Will Google's Dart Language Replace Javascript? (Video)
If you can convert C to assembler, I don't get the point of C. If you can convert assembler to machine code, I don't get the point of assembler. The point of Dart is to provide a better, more productive, safer way to develop code. And frankly, I have not written any line of Dart, but JavaScript is so badly designed that it really needs a replacement.

Comment: Here's a free best practice for them (Score 4, Insightful) 138

by jb_nizet (#41590639) Attached to: Apple, Microsoft, Google, Others Join Hands To Form WebPlatform.org

Underline the damn links (which are one of the main reasons why the web was invented). Undecorated links, using a color which is very close to the normal text color, makes them indistinguishible from normal text for even lightly color-blind people like me, and like 10% of the male population.

Comment: The guide is really hard to use (Score 1) 290

by jb_nizet (#39097933) Attached to: Google Chrome: the New Web Platform?

Am I the only one to find it amusing that the field guide for Web applications is itself

        - ugly,
        - impossible to print to read it offline,
        - hard to use and unintuitive (it took me one minute to find how to go to the next page, and even once you know how to do, it's harder than just clicking on a link)?

If this is an example of a great webapp, I'll stick to my way of designing them, thank you.

Comment: Re:This is one of those (Score 1) 548

by jb_nizet (#38011844) Attached to: End Bonuses For Bankers

Exactly. I've never understood why they had bonuses in the first place.

My job is to be a developer, and thus to produce good, maintainable, efficient code. If I fail at this, I'm fired. If I succeed, I just did my job, and thus get a salary for this.

The job of bankers is to produce money from money. It's just their job, and I'm pretty sure it doesn't need more intelligence than to produce great code. But if they fail at doing it, they just ask governments to help them, and still keep their salary. And if they succeed, they get huge bonuses.

Plain stupid.

Comment: Re:Must be controlled with a keyboard... (Score 1) 874

by jb_nizet (#32088264) Attached to: Top 10 Things Hollywood Thinks Computers Can Do

That's nothing : in an episode of NCIS, they have to crack a remote system (or prevent a cracker for cracking their own system, I don't remember), so they employ the usual technique : they type very fast on the keyboard.
But since they're really in a hurry, they enhance this well-known technique : Abby and Mc Gee both type, at the same time, very fast, on the same keyboard. Go beat that!

Comment: Re:Groovy (Score 3, Informative) 667

by jb_nizet (#31713980) Attached to: The Struggle To Keep Java Relevant

Oh - bonus points if you store the Calendar instance in a static variable, and never require the getInstance() call again.

This would introduce a bug in your application, since Calendar.getInstance() always returns a new instance, containing the current time at the moment it is created. Storing it in a static variable and reusing it would return the same time forever.

Moreover, Calendar is not thread-safe and is mutable, so storing it in a shared static variable is a really bad idea.

Comment: Re:Git and Mercurial? (Score 1) 268

by jb_nizet (#29197515) Attached to: Making Sense of Revision-Control Systems

Subversion calls this a feature branch. You branch the trunk, which stays open to the public. You make regular commits to the branch, and when the large refactoring is done in the branch, you reintegrate the branch into the trunk. The trunk remains stable during the whole process.
How is it different with a distributed system?

Comment: Re:mod parent up! (Score 1) 195

by jb_nizet (#28463869) Attached to: Automated Migration From Cobol To Java On Linux

mind you, by default those things allocate in 6-index chunks, so every 6 objects you add it copies the whole ArrayList to a new one, with 6 more spots available. @_@

There's a reason Java got the sluggish reputation, but it's not because the JIT code is slow. It's because the developers can get by with less of an understanding of what goes on behind the scenes, which never turns out good...

Huh. You might well be the one who doesn't understand what goes on behind the scenes. Just read the source code:

        public void ensureCapacity(int minCapacity) { // ...
                int newCapacity = (oldCapacity * 3)/2 + 1; // ...

It thus allocates half the current size of the list each time the capacity is reached, and not just 6 slots.

To communicate is the beginning of understanding. -- AT&T