Do you think it would be audible in the States if all those ants screamed "RAAAIIIDD!!!" at the same time?
It's going to take a big can of Raid(tm) to find out!
P.S. (for those who don't know what Raid is, it is an insect repellent - and I'm referring to an ad campaign of theirs. Now, nobody can complain about me not catering to the non-North Americans. Of course, it kind of takes the fun out of the whole posting when I have to explain the whole thing to the damned foreigners! Oops... Did I say that out loud?)
I've told my employees that if I ever miss a paycheck, they should quit immediately, regardless of what I say at the time.
Did you learn that at the "Fight Club" school of management?
Pretty soon your employees will have you holed up in a room trying to kill you. All the while, they'll be telling you that it was your idea:-)
I completely agree... The settlement for the previous lawsuit dictated that Microsoft is allowed to use JDK 1.1.4 (read: old as time) and nothing further. That is the only version of Java that M$ is allowed to use. Microsoft did not want to offer old technology to people, so they opted not to offer it at all. Odds are that any Java technology that Microsoft is currently allowed to offer wouldn't be able to run any applets or applications written in the last couple of years. Thus, people would just have to go download a new JDK anyway! What's the difference?
Not if the data is encrypted between playback and display
Well, _somewhere_ in there, it obviously comes to a viewable format which, even if it requires ripping open your TV and jumpering a wire, can _always_ be copied.
They can't even get a decent copy-protection scheme to work! Everything seems to be cracked almost immediately after the general public hears about it. Either that, or it breaks playback on too many devices. Never mind that as long as the physical properties of wire remain the same, I can always reproduce a movie or a song.
T
Re:Why porn today sucks, and what to do about it
on
I STILL Want My HDTV
·
· Score: 2
Demand for porn is nearly universal among men, and if they bothered to work on the stories they could make it appealing to women too. One need look no further than the demand for Yaoi Doujinshi among women to see that this is true.
Ummm I've never even heard of Yaoi God-bless-you before... I had to look it up and it has something to do with male homosexual sex... I've only met two women in my life you like this kind of stuff (I'm almost 30 years old). Where is the demand to which you refer? Is it not more in demand in the homosexual community?
That is my point, exactly. I understand the world isn't perfect, but people can cut their teeth on other, simpler languages, but when they want to do some real work, they will tend to use a language suited to it
well, introducing STL allocators.
for any STL container (which should be used by most people), you can pass in your own allocator class. In that class, you handle your own memory management. If you want to reduce fragmentation, you allocate very large blocks of memory and then do "placement new" calls to allocate memory. Problem solved.
The point is that programming languages evolve, with the ultimate goal of making them as close to natural language as possible
Maybe in your world, but I completely disagree with that. We're not living in Star Trek here. "Computer... calculate the area of this circle". While I understand we're trying to make development easier, we must also concentrate on sacrificing as little functionality as we can. Otherwise we wind up with programs that don't _quite_ do what is needed, but we settle on it because that's the language everyone knows now.
If the client is written in Java, you have to worry about GC there too. If the client machine has a bad JVM on it, you have to replace it. It's a nice configuration issue to have to upgrade or switch a JVM out when you install your software... Oops... what about that _other_ app on that machine that worked better with that _other_ JVM?? Oh well, we'll just have to fight it out... Maybe the user will buy two PCs... yeah... that's it...
some people would rather not worry about de-allocating a linked list
#include <list>
There are two kinds of people - those that just sit and take it up the ass repeatedly and those that try to find a better way of doing things. Miguel is one of those latter people.
Some people do things well enough that they don't have to worry about the things other people consider serious flaws. I can't, honestly, remember the last time I chased down a memory leak in my code. My designs always make the implementation concise and simple. It is very easy to code classes with a defined purpose.
Experienced developers who follow good coding practices will not have a problem with memory leaks. Inexperienced developers, or experienced ones that write spaghetti code, frequently have problems of this sort.
Are you implying that C++ has memory management? It doesn't. Everything is still manually done, or have you not had the joy of chasing memory leaks in C++ programs yet? It may be a step-up from C, but it isn't a picnic either.
:-) Yes, I have been developing in C++ for about 9 years now. I also work in Java, Perl, VB and other more obscure stuff (smartcards) sometimes. C++ has no built in memory management, but a good designer and implementer does not need to have good memory management. ONE Smart Pointer class in C++ will cure any problems you have with memory leaks if you choose to standardize on it.
So you worked with who wrote the original finger, that the Internet worm exploited? Or the people who wrote the GNU C library, which had a buffer overflow recently? Or Eric S. Raymond, who wrote Fetchmail, which had a buffer overflow in version 5.33? Or the authors of X? Or the authors of MySQL? And they're all bad programmers?
Maybe you're such a god that you've never done that, but if ESR and the glibc authors have such problems, maybe it's more than just bad programmers.
I'll respond to those pinnacles of perfect software one at a time.
finger: I'm sure that this product was written with amazing attention to detail and security considering it was a hacked up networked version of "hello world"
the GNU C library: I'm not sure if you've seen that code, but it is NOT pretty. It is also not very well designed. I will also postulate that any mission-critical code that has a buffer overflow problem was not properly designed, coded or tested.
Fetchmail: see GNU C library
X: This product has to be one of the most design-flawed pieces of software out there. It is painful to program in and it was written by students who never worked on real software before. Please find a better example
MySQL: I am not particularly aware of problems with MySQL in the past (I do not use it). So, I will defer to someone else to respond to this one.
I must say that _most_ of the problems that I have seen with problems with the minutiae like memory leaks and other such problems have their roots in poor design. Good design is one of the biggest factors that can mitigate risk in development of any software. I believe that most people, especially widely segregated development (as occurs in many Open Sourced projects) focus too little on design and always talk about "coding this" and "hacking that" instead of talking about higher-level design issues that will make the development easier. And, developers always need to be coding for security if they're writing a mission-critical app. Don't hard-code buffer sizes. Jesus christ... they teach you how to deal with buffer overflow problems in school!
Though my initals are not immediately recognizable to the Slashdot Hive Mind, I believe that I am as good or better at designing software than all the people you mentioned.
C++ may be a great language in certain areas, but the memory management sucks ass compared to Java/C# - this is the point Miguel is driving home here.
Automatic garbage collection is here to stay.
Well, no, actually... C++ memory management is much better because it is done by ME. I only say this because java's memory management is not specified. The garbage collection algorithm is left up to the JVM developer. Thus, Java's memory management doesn't really exist. It only dictates that things will be garbage collected, not how efficiently.
Automatic garbage collection is here to stay.
You feel free to use it wherever you like. I, for one, do not trust an arbitrary algorithm to properly handle garbage collecting my mission-critical apps (picturing Emacs in the old days... "Garbage Collecting..." Me saying "why can't I type?"...).
BTW, your "I'm older than HE is" remark irked me. Who cares how old you are?
Well, I'm sorry if I offended your youthful sensibilities, but Miguel states:
"There is a point in your life when you realize that you have written enough destructors, and have spent enough time tracking down a memory leak, and you have spend enough time tracking down memory corruption, and you have spent enough time using low-level insecure functions, and you have implemented way too many linked lists..."
Well, I have been doing this longer than he has... I still haven't come to that "point in my life" yet. That is why I bring up how old I am.
We use APIs to draw our GUI's, so why not let the computer handle the complexity of memory management, too. Or do you reimplement your windowing routines for every project too?:)
Well, if that is your approach, why not do all your Windows development using VB?
I use C++ because I believe it is the most powerful, flexible language out there. Yes, it does require learning more for particular OSes (GUI, mutexing, threads, sockets, etc.), but if I were stranded on a desert island with only one language, there would be no other choice.
This is not to say that I only use C++. I regularly use Perl and Java where I think they are applicable. I don't like garbage collection because of the potential problems with performace that can happen because the GC algorithm is not standardized or configurable in most applications. In Java, for example, I've seen large systems perform like a champ for 1-2 hours and then grind to a halt for 2-3 minutes while garbage collecting! This is because the VM had a bad GC algorithm. It was still within Java's spec. It was good design and good Java code. I've never had that problem with C++. I don't want to have to configure my client machines or my servers and tweak things or run different JVMs just to make sure that my app will perform properly. This is why I still write most number-crunching, mission-critical stuff in C++.
It's great that people can put less effort into knowing what an Operating System does before they know how to program. It's nice that an Accounting major can take a Learning Tree class and start developing Java or VB code. I just don't want those people anywhere near my software. I want to work with people who understand how the machine works too! Having a developer that has no practical knowledge of memory management is like having a mechanic that doesn't know how an engine works! No thank you.
I understand (and anticipated) that people would think this is Flamebait, but being older than he is, and having clearly more experience in C++ than he does, I do not have problems with low-level calls or memory leaks or any of the things that he insuates are problems of an archaic language.
Running into those problems frequently is only a sign of poor design and poor coding, not a language flaw.
Yeah... that one really irked me. I'm older than Miguel is, and (shrugs his asbestos suit on...) I think this remark just demonstrates a serious lack of proper experience with C++.
Come on! Generating C++ classes is NOT a decent way to compile.
I vehemently agree that design is often (not always) the solution for speed issues. PHBs, though, see the possibility of buying a tool for $X that will immediately give the app a Y% increase in speed and they'll jump on it every time
Slashdot Mirror
AFAIK, all Tivo devices use MPEG-2 technology. And, AFAIK, there is _no_ Tivo mode that does lossless compression.
T
plad = plaid...
Next thing you know, they've got the 8 year old girls wearing plad skirts ... :-)
It's going to take a big can of Raid(tm) to find out!
P.S. (for those who don't know what Raid is, it is an insect repellent - and I'm referring to an ad campaign of theirs. Now, nobody can complain about me not catering to the non-North Americans. Of course, it kind of takes the fun out of the whole posting when I have to explain the whole thing to the damned foreigners! Oops... Did I say that out loud?)
returns:
No entry found for purposful.
1 suggestion found:
purposeful
How hard is it to spell check? Editor, Schmeditor!
T
Did you learn that at the "Fight Club" school of management? :-)
Pretty soon your employees will have you holed up in a room trying to kill you. All the while, they'll be telling you that it was your idea
T
The settlement for the previous lawsuit dictated that Microsoft is allowed to use JDK 1.1.4 (read: old as time) and nothing further.
That is the only version of Java that M$ is allowed to use.
Microsoft did not want to offer old technology to people, so they opted not to offer it at all.
Odds are that any Java technology that Microsoft is currently allowed to offer wouldn't be able to run any applets or applications written in the last couple of years. Thus, people would just have to go download a new JDK anyway!
What's the difference?
T
53-13.25 = 39.75%
So, 40% is a 25% decline. I don't see any flaw there.
T
Then your mom would walk in and try to talk to you...
"MO-OO-OO-OOM! I WAS RECORDING SOMETHING!"
:-D
Well, _somewhere_ in there, it obviously comes to a viewable format which, even if it requires ripping open your TV and jumpering a wire, can _always_ be copied.
T
T
Ummm I've never even heard of Yaoi God-bless-you before... I had to look it up and it has something to do with male homosexual sex... I've only met two women in my life you like this kind of stuff (I'm almost 30 years old). Where is the demand to which you refer? Is it not more in demand in the homosexual community?
T
T
for any STL container (which should be used by most people), you can pass in your own allocator class. In that class, you handle your own memory management. If you want to reduce fragmentation, you allocate very large blocks of memory and then do "placement new" calls to allocate memory. Problem solved.
T
Maybe in your world, but I completely disagree with that. We're not living in Star Trek here. "Computer... calculate the area of this circle". While I understand we're trying to make development easier, we must also concentrate on sacrificing as little functionality as we can. Otherwise we wind up with programs that don't _quite_ do what is needed, but we settle on it because that's the language everyone knows now.
My $0.02 on that
T
T
#include <list>
There are two kinds of people - those that just sit and take it up the ass repeatedly and those that try to find a better way of doing things. Miguel is one of those latter people.
Some people do things well enough that they don't have to worry about the things other people consider serious flaws.
I can't, honestly, remember the last time I chased down a memory leak in my code. My designs always make the implementation concise and simple. It is very easy to code classes with a defined purpose.
Experienced developers who follow good coding practices will not have a problem with memory leaks. Inexperienced developers, or experienced ones that write spaghetti code, frequently have problems of this sort.
T
:-) Yes, I have been developing in C++ for about 9 years now. I also work in Java, Perl, VB and other more obscure stuff (smartcards) sometimes. C++ has no built in memory management, but a good designer and implementer does not need to have good memory management. ONE Smart Pointer class in C++ will cure any problems you have with memory leaks if you choose to standardize on it.
T
I'll respond to those pinnacles of perfect software one at a time.
I must say that _most_ of the problems that I have seen with problems with the minutiae like memory leaks and other such problems have their roots in poor design. Good design is one of the biggest factors that can mitigate risk in development of any software. I believe that most people, especially widely segregated development (as occurs in many Open Sourced projects) focus too little on design and always talk about "coding this" and "hacking that" instead of talking about higher-level design issues that will make the development easier. And, developers always need to be coding for security if they're writing a mission-critical app. Don't hard-code buffer sizes. Jesus christ... they teach you how to deal with buffer overflow problems in school!
Though my initals are not immediately recognizable to the Slashdot Hive Mind, I believe that I am as good or better at designing software than all the people you mentioned.
T
Well, no, actually... C++ memory management is much better because it is done by ME. I only say this because java's memory management is not specified. The garbage collection algorithm is left up to the JVM developer. Thus, Java's memory management doesn't really exist. It only dictates that things will be garbage collected, not how efficiently.
Automatic garbage collection is here to stay.
You feel free to use it wherever you like. I, for one, do not trust an arbitrary algorithm to properly handle garbage collecting my mission-critical apps (picturing Emacs in the old days... "Garbage Collecting..." Me saying "why can't I type?"...).
BTW, your "I'm older than HE is" remark irked me. Who cares how old you are?
Well, I'm sorry if I offended your youthful sensibilities, but Miguel states: "There is a point in your life when you realize that you have written enough destructors, and have spent enough time tracking down a memory leak, and you have spend enough time tracking down memory corruption, and you have spent enough time using low-level insecure functions, and you have implemented way too many linked lists..."
Well, I have been doing this longer than he has... I still haven't come to that "point in my life" yet. That is why I bring up how old I am.
T
Well, if that is your approach, why not do all your Windows development using VB?
I use C++ because I believe it is the most powerful, flexible language out there. Yes, it does require learning more for particular OSes (GUI, mutexing, threads, sockets, etc.), but if I were stranded on a desert island with only one language, there would be no other choice.
This is not to say that I only use C++. I regularly use Perl and Java where I think they are applicable. I don't like garbage collection because of the potential problems with performace that can happen because the GC algorithm is not standardized or configurable in most applications. In Java, for example, I've seen large systems perform like a champ for 1-2 hours and then grind to a halt for 2-3 minutes while garbage collecting! This is because the VM had a bad GC algorithm. It was still within Java's spec. It was good design and good Java code. I've never had that problem with C++. I don't want to have to configure my client machines or my servers and tweak things or run different JVMs just to make sure that my app will perform properly. This is why I still write most number-crunching, mission-critical stuff in C++.
It's great that people can put less effort into knowing what an Operating System does before they know how to program. It's nice that an Accounting major can take a Learning Tree class and start developing Java or VB code. I just don't want those people anywhere near my software. I want to work with people who understand how the machine works too! Having a developer that has no practical knowledge of memory management is like having a mechanic that doesn't know how an engine works! No thank you.
T
Because we've worked with them.
T
Running into those problems frequently is only a sign of poor design and poor coding, not a language flaw.
T
T
I vehemently agree that design is often (not always) the solution for speed issues. PHBs, though, see the possibility of buying a tool for $X that will immediately give the app a Y% increase in speed and they'll jump on it every time
T