Could you please reference the UK law stating that questioning the holocaust is not a crime? Even if there is one, I imagine it could get struck down because it contradicts the Human Rights Act.
Yeah, because it's not like I notice it at every film YSC showed last summer. It's not like I noticed it on, say, The Matrix Reloaded the day after it opened worldwide.
While I can understand his motive, I'm not fond of it at all. Abusing an over-abused process to get your way is going to encourage other people to do it if you win. Besides, it gives the IE advocates ammo along the lines of "Mozilla only survived because MS was forced to cripple IE".
Do a search for the definition of a memory leak. You'll find the most common one is the one from "The Jargon File", and that requires the memory be discarded. If your program holds on to the information by still having references to it, it cannot be safely reclaimed since it may still be used, thus it's not a memory leak.
1) If the allocated memory is still referenced by reachable code, then of course it can't be garbage collected. Of course, this problem is just as likely to occur in C, so using a non-garbage-collected language doesn't have an advantage here.
2) This is no worse than the same problem using C. Of course, that's a bug in your program and not a bug related to garbage collection. It's also not a memory leak, at least not according to the jargon file, since it's not discarded memory.
3) That's like saying C is buggy because the m88k backend of GCC doesn't work properly.
4) That's an obscure bug and not really related to memory leaks, since it's not programatic but runtime based.
Tracing algorythms defeat the circular reference problem. Check out http://www.javaworld.com/javaworld/jw-08-1996/jw-0 8-gc.html for information on Java's garbage collection system.
Re:Imagine that you are an alcoholic...
on
The Next Path for Joy
·
· Score: 2, Insightful
Java can't take Ada's place until the Real-Time extensions are mature enough. Currently, implementations are a bit thin on the ground and well enough tested to be entrusted with stuff that Ada is typically used for.
I'm not sure how you'd have memory leaks in Java, since it's a garbage collected language. You claim it's a joke, but if you find leaving the garbage collector to do its own thing isn't working for you, you can call it explicetly. If you have a place where you drop a lot of objects for whatever reason, you can always tell the garbage collector to run then instead of letting things build up. I was recently writing a.Net library and ran into a similar problem to what you were describing, my solution was to run the garbage collector after processing an arbitrary number of files. It pretty much eliminated swapping and barely affected performance (when swapping's not taken into account) at all.
I feel that the problem is that people try to write inappropriate things in C. Unless you absolutely need to have very high performance and you must keep memory usage down, there's little need to use low level languages for desktop applications. Take Something like an instant messenger client. Since they rarely do anything CPU or IO intensive, they wouldn't feel slow if they were written in Python, C# or Java.
Well, Java has to allow that since it doesn't support generics (at the moment). Otherwise, you'd only be able to get Object instances from the data structures and wouldn't be able to do anything useful with them. There's also the problem that designing software that doesn't cast to the extending/implementing class is very difficult.
Having extensively used Windows 95, 98, Me, NT4, 2000 and XP, I can say I still prefer Linux. While I'll agree NT-based Windows has very good stability, I've still had problems like Explorer dying and leaving my desktop unusable.
Besides, I like the flexibility of Linux, and I have used the source code availabilty to fix problems, so don't bother with that shitty "oh, what use is the source code if you never touch it" argument, it doesn't hold water.
With stuff like bpf and Linux QoS, it's possible to not throttle to a certain percentage of the system, but to a certain priority. A friend of mine has written a script to prioritise things so well that you can saturte the connection downloading files, yet a gamer can fire up their game and still play with a ping below 100ms. The major problem at the moment is finding ways to identify the P2P traffic. Programs like Overnet use random ports, so you can't identify by port, so we need to find something else to identify them by, which doesn't seem too easy.
Have you actually tried Jabber? It essentially works like e-mail in terms of addresses. I have my own Jabber server for my domain, whereas a friend of mine uses jabber.earth.li. I can see his presence in real-time and I can send messages to and from.
Jabbers distributed nature doesn't require anything in the form of a supernode at all. There is a central Jabber user directory, but it's by no means required.
OK, I didn't know that. However, my point is still valid in terms of private property such as your house, which is where a telemarketer is most likely to call.
I imagine that would come under fraud laws. After all, they're reading a script, they won't be taking any statistics or using them for anything useful.
Slashdot Mirror
Could you please reference the UK law stating that questioning the holocaust is not a crime? Even if there is one, I imagine it could get struck down because it contradicts the Human Rights Act.
Since when did one dinner time interval become the definition of "persistent"?
Yeah, because it's not like I notice it at every film YSC showed last summer. It's not like I noticed it on, say, The Matrix Reloaded the day after it opened worldwide.
Eh? I highly doubt that somebody e-mailed themselves 100MB of source code.
While I can understand his motive, I'm not fond of it at all. Abusing an over-abused process to get your way is going to encourage other people to do it if you win. Besides, it gives the IE advocates ammo along the lines of "Mozilla only survived because MS was forced to cripple IE".
In the UK, there are cinemas showing new films that use a two-projector system. There, clear enough for you?
Err...I think you'll find there are cinemas that use a two-projector system.
I can easily get 10MB/sec over my 100-BaseT connection, that's 80% right there.
Do a search for the definition of a memory leak. You'll find the most common one is the one from "The Jargon File", and that requires the memory be discarded. If your program holds on to the information by still having references to it, it cannot be safely reclaimed since it may still be used, thus it's not a memory leak.
1) If the allocated memory is still referenced by reachable code, then of course it can't be garbage collected. Of course, this problem is just as likely to occur in C, so using a non-garbage-collected language doesn't have an advantage here.
2) This is no worse than the same problem using C. Of course, that's a bug in your program and not a bug related to garbage collection. It's also not a memory leak, at least not according to the jargon file, since it's not discarded memory.
3) That's like saying C is buggy because the m88k backend of GCC doesn't work properly.
4) That's an obscure bug and not really related to memory leaks, since it's not programatic but runtime based.
Tracing algorythms defeat the circular reference problem. Check out http://www.javaworld.com/javaworld/jw-08-1996/jw-0 8-gc.html for information on Java's garbage collection system.
Java can't take Ada's place until the Real-Time extensions are mature enough. Currently, implementations are a bit thin on the ground and well enough tested to be entrusted with stuff that Ada is typically used for.
I'm not sure how you'd have memory leaks in Java, since it's a garbage collected language. You claim it's a joke, but if you find leaving the garbage collector to do its own thing isn't working for you, you can call it explicetly. If you have a place where you drop a lot of objects for whatever reason, you can always tell the garbage collector to run then instead of letting things build up. I was recently writing a .Net library and ran into a similar problem to what you were describing, my solution was to run the garbage collector after processing an arbitrary number of files. It pretty much eliminated swapping and barely affected performance (when swapping's not taken into account) at all.
I feel that the problem is that people try to write inappropriate things in C. Unless you absolutely need to have very high performance and you must keep memory usage down, there's little need to use low level languages for desktop applications. Take Something like an instant messenger client. Since they rarely do anything CPU or IO intensive, they wouldn't feel slow if they were written in Python, C# or Java.
Well, Java has to allow that since it doesn't support generics (at the moment). Otherwise, you'd only be able to get Object instances from the data structures and wouldn't be able to do anything useful with them. There's also the problem that designing software that doesn't cast to the extending/implementing class is very difficult.
Having extensively used Windows 95, 98, Me, NT4, 2000 and XP, I can say I still prefer Linux. While I'll agree NT-based Windows has very good stability, I've still had problems like Explorer dying and leaving my desktop unusable.
Besides, I like the flexibility of Linux, and I have used the source code availabilty to fix problems, so don't bother with that shitty "oh, what use is the source code if you never touch it" argument, it doesn't hold water.
He said "most", not "all". Pay attention.
With stuff like bpf and Linux QoS, it's possible to not throttle to a certain percentage of the system, but to a certain priority. A friend of mine has written a script to prioritise things so well that you can saturte the connection downloading files, yet a gamer can fire up their game and still play with a ping below 100ms. The major problem at the moment is finding ways to identify the P2P traffic. Programs like Overnet use random ports, so you can't identify by port, so we need to find something else to identify them by, which doesn't seem too easy.
Have you actually tried Jabber? It essentially works like e-mail in terms of addresses. I have my own Jabber server for my domain, whereas a friend of mine uses jabber.earth.li. I can see his presence in real-time and I can send messages to and from.
Jabbers distributed nature doesn't require anything in the form of a supernode at all. There is a central Jabber user directory, but it's by no means required.
I'm not up on US law, but isn't a sign saying "no soliciting" enough to legally require them to not do such things?
OK, I didn't know that. However, my point is still valid in terms of private property such as your house, which is where a telemarketer is most likely to call.
They can't come onto your property to talk to you without your explicit permission. Why should the phone be the same?
No wonder you couldn't find a solution. You couldn't even describe the problem accurately.
For KDE:
KDE Control panel->Appearance & Themes->Fonts. Untick "use anti-aliasing for fonts". Oh, so difficult.
I imagine that would come under fraud laws. After all, they're reading a script, they won't be taking any statistics or using them for anything useful.