Why the obsession with programming competitions? If you're smart enough to do well in a competetion, go and join an open source software project and do something that makes a real difference and will look good on your resume. Competitions may offer a learning experience, but they have little other practical value.
The US work week is tied for first as the longest in the industrialized world at an average of 2040 hours. (France is around 1400 by comparison)
A healthy work/life balance makes for healthy and happy people. It's kinda hard to maintain that balance when you're constantly stressed from overwork. Also, you might find that French people are actually *as productive* as Americans despite working 30% less, because they are happier and less stressed.
Fair enough, but hotlinking is not very nice, especially if it uses a lot of bandwidth, and without even asking, that's just bad manners;)
OK so the author didn't have to do what he did, he could have dealt with the situation in a less antagonistic way, but it's his content on his server and he should be able to do whatever he wants with it, as long as it's not breaking the law.
The author chose, instead of the proper thing (contacting these "fuddruckers" people), posting graphic images. The author is now just as guilty as the people doing the hotlinking were, because he mishandled the situation so badly.
Nonsense, the author is in *no way* guilty. He can do whatever the hell he wants with his own content hosted on his own server, as long as he's not breaking any laws.
The web developer at fuddruckers got exactly what he deserved for being such a fool.
Oh yeah and what if you type in ffs_this_is_a_hard_password instead of omg_this_is_a_hard_password? The hint won't help then. Or what if you have been given a password like &^%£&^%£::@@546832420345, how do you write a hint for that?
You have not had the problems he proposes? He said quite simply that the problem is sun took away the destructor. In what way have you not had this problem?
Yes it's interesting but you can sum it up by saying reuse objects instead of creating new ones, minimising the amount of memory used, allocation and GC work. This is plain common sense and there's no need for a 3 page article. That said, it doesn't provide a solution for the problem that there's no way to explicitly delete objects in Java.
The downfall of Java's method is that although they provide a decent solution for the most common resource type, memory, they completely ignore all other resource types, which is fine except for the fact that they took away the most useful and simple method of freeing resources, the destructor.
I think you've hit he nail on the head there. I couldn't have put it better.
Sorry, I perhaps didn't explain myself well because I think you misunderstood my point. Dynamic typing is as you explained, but dynamical typing has no meaning;)
I agree about multiple inheritance. It is messy, never essential and there are ways to work around the lack of it in situations when you would want to use it, like composition, the adapter or aggregate pattern. Regarding operator overloading, it *is* possible to work around the lack of them, even the exponential operator, but if you really must have them you can use C++ instead.
Just a coule of points to add to my previous comments.
Why should you care when the garbage collector runs?
In my previous example I gave the situation that you have several hundreds of flyweight objects. Memory is finite and is very limited on some platforms like mobile phones (cell phones).
Java does not use reference counting to know when to release an object
Just to re-emphasise, it's incorrect to make assuptions about the algorithm used by the garbage collector. I assume this is an oversight on your part;)
For better or worse. Java will never have direct memory control, period. It's the very antithesis of everything that Java stands for. You will have to do with JNI calls to C/C++ code.
I find the lack of deterministic finalisation a huge pain. There is absolutely *no* guarantee that the finalizer will be called, so you have to write a method for freeing resources like file handles and call it explicitly. In C++ you can just do a "delete" and the destructor will be called. Another ball-ache is when you have hundreds of flyweight objects that you want to delete - there's absolutely no way to do it. You can only *suggest* to the garbage that it should run, whether it actually runs and collects your objects is anyone's guess. Another thing that gets on my nerves is that if you forget to call File.close() on Linux, you've got yourself a file handle leak. Was it really too much to ask for Sun to put a call to close() in the finalizer in the File class?
In all, I wish Java was more like D.
You're right of course, but I shalln't lose any sleep over it because I'm fairly convinced that Mensa_Girl is a troll and not necessarily female (Men's a girl?) and quite probably not a member of Mensa. Read his/her journal/comments and posts and you'll see what I mean.
Is that simple enough for you? Of course if you use primitives they already have sane operators. I'm not saying it's not nice to have in some circumstances, but it can easily be abused and lead to programming errors when things don't behave as expected.
Slashdot Mirror
Why the obsession with programming competitions? If you're smart enough to do well in a competetion, go and join an open source software project and do something that makes a real difference and will look good on your resume. Competitions may offer a learning experience, but they have little other practical value.
No idea. It's funny they had to alter the DNS instead of doing an emergency fix :)
If this is true, perhaps he will do the honourable thing and resign, but I doubt it.
Fair enough, but hotlinking is not very nice, especially if it uses a lot of bandwidth, and without even asking, that's just bad manners ;)
OK so the author didn't have to do what he did, he could have dealt with the situation in a less antagonistic way, but it's his content on his server and he should be able to do whatever he wants with it, as long as it's not breaking the law.
The web developer at fuddruckers got exactly what he deserved for being such a fool.
Oh yeah and what if you type in ffs_this_is_a_hard_password instead of omg_this_is_a_hard_password? The hint won't help then. Or what if you have been given a password like &^%£&^%£::@@546832420345, how do you write a hint for that?
You have not had the problems he proposes? He said quite simply that the problem is sun took away the destructor. In what way have you not had this problem?
It would be like C++ but without the backwards compatibility with C, macro system, inline functions, multiple inheritance, inline asm, etc.
Yes it's interesting but you can sum it up by saying reuse objects instead of creating new ones, minimising the amount of memory used, allocation and GC work. This is plain common sense and there's no need for a 3 page article. That said, it doesn't provide a solution for the problem that there's no way to explicitly delete objects in Java.
Sorry, I perhaps didn't explain myself well because I think you misunderstood my point. Dynamic typing is as you explained, but dynamical typing has no meaning ;)
I agree about multiple inheritance. It is messy, never essential and there are ways to work around the lack of it in situations when you would want to use it, like composition, the adapter or aggregate pattern. Regarding operator overloading, it *is* possible to work around the lack of them, even the exponential operator, but if you really must have them you can use C++ instead.
You're right of course, but I shalln't lose any sleep over it because I'm fairly convinced that Mensa_Girl is a troll and not necessarily female (Men's a girl?) and quite probably not a member of Mensa. Read his/her journal/comments and posts and you'll see what I mean.
You've been trolled.
She knows already, it's been pointed out before. Like all trolls, she's probably doing it for the attention.
Let's try:
z = z*z + c
z = z.multipliedBy(z).plus(c);
Is that simple enough for you? Of course if you use primitives they already have sane operators. I'm not saying it's not nice to have in some circumstances, but it can easily be abused and lead to programming errors when things don't behave as expected.