Unless your competitors use it and have their own changes that they want to make and push up stream, which benefits you as well as them. Everyone is scratching itches, and most of us have overlapping itches and not enough fingers to scratch with.
Yeah, that's exactly the one. I don't think that they worded as they wanted to, or I just changed the meaning around in my (admittedly poor) short term memory. Sorry about all the fuss, this was a case of me being a little too caffeinated and trigger happy with the 'reply' button =). Note to self: Order of operations; think... then post. Or, double check the facts before posting.
My bad. java.io.Serializable is correct. I was misreading this warning from the JButton overview:
Warning: Serialized objects of this class will not be compatible with future Swing releases. The current serialization support is appropriate for short term storage or RMI between applications running the same version of Swing. As of 1.4, support for long term storage of all JavaBeansTM has been added to the java.beans package. Please see XMLEncoder.
I've seen this warning on a few Swing classes. After re-re-reading it, I have no idea what they're trying to say, but I'm assuming its EE related (although in the SE Javadocs?). IIRC, RMI is Remote Method Invocation or something to the effect (affect? Arg!) of RPC... I haven't the foggiest what that has to do with short term storage.
At any rate, I stand corrected. Sorry for that rant. Given the chance, I'd do it again, but talk about the Thread class! =)
Simply put - Microsoft is the new IBM; you won't get fired for choosing Microsoft, even if it doesn't play out so well.
Whenever I put myself on the line for a Linux box (server, desktop or otherwise), I always know it's going to have out-perform (in whatever metric is important to the person considering it) the competing Microsoft option by a factor of two to be considered equal.
Even worse: you're searching for a particular/obscure combination of hardware/software/error/hardhack, knowing that someone before you has scratched that itch before and has surely posted the way they got it to work. You blow off the obvious CXO sites with whitepapers and make a line drive for a geek forum. Luckily you find a forum where someone is discussing the exact model of $hardware that you're trying to get working/break/overclock, only to find out that they've got the piece of hardware as their sig on the forum. Someone else has the other hardware/software/whatever in their sig, and you only had to search through a three year old, five page thread to find this out.
There are plenty of plugins that will let you interface with real mail servers. Citidel, Zimbra, Kolab, they've all got plugins and one click installers; not even your admin has to know. Think of your children, man!
Customize Google is one of my favorites, alongside Goolepedia which gives you a mini-sized frame with the relevant wikipedia entry on your google search. You can click on a link to show or hide the almost seamless frame from your google search.
Interesting idea (I want my coffin to have a satellite uplink, FWIW), but at the same time... that could be a bit creepy. Then again... 100 years from now, someone will probably have our posts on this little thread stored on some storage medium marked 'internet circa 2010', collecting dust with the rest of their backups. In that sense, all of our information will still be here, although no one is going to read what we had to say (except for our relatives or children).
I've been meaning to add a section to my will that I want all of my source code uploaded to sourceforge under GPL when I die. Same kind of idea as you've got, albeit in a different format. Then again, 100 years from now, we'll both be dead^H^H^H^Hasleep;) When I look at it that way, it's not so important.
While I generally agree with you, AKAImBatman, I think you've missed the mark on this one. The Serializable interface has been deprecated and will not be forward compatible. Unfortunately, this affects (effects? I always get them mixed up...) just about everything in the javax.swing package.
Granted, swing is somewhat ugly, single threaded (discounting worker threads - you still only have one dispatcher to do painting, anyways... although I want to choke everyone who tries to do everything on the dispatcher and wonders why nothing is responsive), and a generally over engineered toolkit; but it's also been around since like version 1.0 and is still effective for consistent cross platform GUIs. LookAndFeel aside, Solaris, Windows, Linux (X11R6 and R7) and, I would presume, Macs all render the same under Swing. As a bonus, about five lines of code will make a Swing app an applet in any browser with a java plugin, and it still renders exactly the same.
I have no idea why something so proven would be deprecated after all this time, considering how many legacy apps could break. Unless I'm not understanding the rational, which is more than likely considering I've never bothered to follow up on it after reading the deprecation notice in the JavaDocs. If so, feel free to flame me for being so loud about something I was too lazy to look up before opening my mouth.
[...] Yes, I know programmers love doing all that, but it's a mistake. The design should be left to someone with at least some basic training in psychology and/or ergonomics
Actually, I know that I have no talent for it, and would rather avoid it at all costs... but that doesn't convince the powers that be (or the users themselves) to keep me away from the front ends.
From the other perspective, though, how are you supposed to describe an error in twenty words or less? People at work ask me a question, and I can see them lose interest before I've gotten more than five words out. They don't understand the problem, and they don't care - they just want it fixed, even if they can't tell you what it is that's broken.
I hear "are you doing something with the 'system'? It's really slow" a few times a week, where the system could be: the internet, email server(s) (they refuse to believe we have more than one, so I stopped trying to explain to them that there is a web interface if our desktop email app/server dies... I just placed that webmail link on their desktop to mess with them, really.), our accounting application, our POS app, Windows, or their screensaver. It's all just 'the system', and most users stop caring at that point.
How would you like me explain to them that the desktop email application cannot connect to its pop server, but the webmail server has an imap connection to the primary email server, in ten words or less that they're not going to read anyways? I'm over simplifying the whole thing, but my point is that you can't instruct someone who doesn't have any intention of doing anything other than calling me to say "the system isn't working."
Are we talking by traffic volume, or number of incidents? How large is a WOW patch? I don't believe the number either, but it wasn't quantified in such a way that it can be refuted, either.
Actually, I run my Linux desktop on RAID0 Raptors. As far as WD goes, my numbers are skewed from an obscure bug they had in their firmware on their **KS drives. I've got 4 AAKS' in my storage box at home, and 3 RE2 Y(D?)KS' on a rack at work.
I've found that in reality the sheer number of WDs that I've got in boxes at any given moment. Their Raptors are in an entirely different league than their large capacity drives, though. I've got three of those (2 150 GB, and a 75GB) in boxes without a single hitch.
IMHO, WDs drives are just at the right price/performance/failure rate ratio. They're not as solid as Seagate, but they also cost less per GB. Then there's Maxtor. I've seen 2 of those things go under this year. Which is remarkable when you consider that that covers 2/3 that were being used. Avoid Maxtor like the plague. Finally, nothing is holding a candle to my old 5.25" Quantum Bigfoot 20GB drive that's been running for nearly ten years now.
I run two Raptors in RAID 0 with short stroked partitions. If you keep your partition slices to the outside of the drive, with variable data partitions (/var,/tmp (if you put that to HD instead of tmpfs), and swap) between static partitions (/usr,/usr/local), you can get much better performance than if you glob the whole thing on LVM. Oh, yeah, and write off the last 15% of the drive, the seek time to it doesn't justify the storage space since it's the slowest part of the drive. Use the kernels I/O elevator to your advantage and lay out your partitions accordingly. If/var is at the middle of the disk, you're, at most, half a disks width from it and will be passing over it to get to other static data.
You will never be yelled at for releasing software with a well understood and documented defect, but the shit will hit the fan when you release major defects that are not understood.
This is the most true thing I've read in a long time. I've found that being as up front as possible about bugs and defects is always the best policy.
Yeah, it's the last time I'm going to buy one of those things... until the next sale... or if I need to pick one up at Wal*Mart at 3AM. I've been saying that for three years now. Somehow my drives die just in time for the newest WD's to be on sale.
Slashdot Mirror
Unless your competitors use it and have their own changes that they want to make and push up stream, which benefits you as well as them. Everyone is scratching itches, and most of us have overlapping itches and not enough fingers to scratch with.
Geeky wedding band? Weird Al!
...Huh? Wrong kind of band?
It's all about the Pentiums, baby.
Yeah, that's exactly the one. I don't think that they worded as they wanted to, or I just changed the meaning around in my (admittedly poor) short term memory. Sorry about all the fuss, this was a case of me being a little too caffeinated and trigger happy with the 'reply' button =). Note to self: Order of operations; think... then post. Or, double check the facts before posting.
See my reply to AKAImBatman (this thread); I misunderstood a warning note in the Javadocs.
Warning: Serialized objects of this class will not be compatible with future Swing releases. The current serialization support is appropriate for short term storage or RMI between applications running the same version of Swing. As of 1.4, support for long term storage of all JavaBeansTM has been added to the java.beans package. Please see XMLEncoder.
I've seen this warning on a few Swing classes. After re-re-reading it, I have no idea what they're trying to say, but I'm assuming its EE related (although in the SE Javadocs?). IIRC, RMI is Remote Method Invocation or something to the effect (affect? Arg!) of RPC... I haven't the foggiest what that has to do with short term storage.
At any rate, I stand corrected. Sorry for that rant. Given the chance, I'd do it again, but talk about the Thread class! =)
clusterSSH, FTW!
Simply put - Microsoft is the new IBM; you won't get fired for choosing Microsoft, even if it doesn't play out so well.
Whenever I put myself on the line for a Linux box (server, desktop or otherwise), I always know it's going to have out-perform (in whatever metric is important to the person considering it) the competing Microsoft option by a factor of two to be considered equal.
Even worse: you're searching for a particular/obscure combination of hardware/software/error/hardhack, knowing that someone before you has scratched that itch before and has surely posted the way they got it to work. You blow off the obvious CXO sites with whitepapers and make a line drive for a geek forum. Luckily you find a forum where someone is discussing the exact model of $hardware that you're trying to get working/break/overclock, only to find out that they've got the piece of hardware as their sig on the forum. Someone else has the other hardware/software/whatever in their sig, and you only had to search through a three year old, five page thread to find this out.
Bryansix, don't listen! Hide it!
There are plenty of plugins that will let you interface with real mail servers. Citidel, Zimbra, Kolab, they've all got plugins and one click installers; not even your admin has to know. Think of your children, man!
Customize Google is one of my favorites, alongside Goolepedia which gives you a mini-sized frame with the relevant wikipedia entry on your google search. You can click on a link to show or hide the almost seamless frame from your google search.
If you think you're making progress without ethics, I'm glad that your version of 'progress' is being hindered.
Interesting idea (I want my coffin to have a satellite uplink, FWIW), but at the same time... that could be a bit creepy. Then again... 100 years from now, someone will probably have our posts on this little thread stored on some storage medium marked 'internet circa 2010', collecting dust with the rest of their backups. In that sense, all of our information will still be here, although no one is going to read what we had to say (except for our relatives or children).
;)
I've been meaning to add a section to my will that I want all of my source code uploaded to sourceforge under GPL when I die. Same kind of idea as you've got, albeit in a different format. Then again, 100 years from now, we'll both be dead^H^H^H^Hasleep
When I look at it that way, it's not so important.
You must be new... *checks ID* ...oh, nevermind. :)
I'll get off your lawn now.
This hurts, but I've gotta' say it.
While I generally agree with you, AKAImBatman, I think you've missed the mark on this one. The Serializable interface has been deprecated and will not be forward compatible. Unfortunately, this affects (effects? I always get them mixed up...) just about everything in the javax.swing package.
Granted, swing is somewhat ugly, single threaded (discounting worker threads - you still only have one dispatcher to do painting, anyways... although I want to choke everyone who tries to do everything on the dispatcher and wonders why nothing is responsive), and a generally over engineered toolkit; but it's also been around since like version 1.0 and is still effective for consistent cross platform GUIs. LookAndFeel aside, Solaris, Windows, Linux (X11R6 and R7) and, I would presume, Macs all render the same under Swing. As a bonus, about five lines of code will make a Swing app an applet in any browser with a java plugin, and it still renders exactly the same.
I have no idea why something so proven would be deprecated after all this time, considering how many legacy apps could break. Unless I'm not understanding the rational, which is more than likely considering I've never bothered to follow up on it after reading the deprecation notice in the JavaDocs. If so, feel free to flame me for being so loud about something I was too lazy to look up before opening my mouth.
Dude, chill. It's not like he said dBase IV admin.
[...] Yes, I know programmers love doing all that, but it's a mistake. The design should be left to someone with at least some basic training in psychology and/or ergonomics
Actually, I know that I have no talent for it, and would rather avoid it at all costs... but that doesn't convince the powers that be (or the users themselves) to keep me away from the front ends.
Kinda' like Wake On LAN (I'm assuming) ;)
You've still got bare metal contact to the network, power or not.
From the other perspective, though, how are you supposed to describe an error in twenty words or less? People at work ask me a question, and I can see them lose interest before I've gotten more than five words out. They don't understand the problem, and they don't care - they just want it fixed, even if they can't tell you what it is that's broken.
I hear "are you doing something with the 'system'? It's really slow" a few times a week, where the system could be: the internet, email server(s) (they refuse to believe we have more than one, so I stopped trying to explain to them that there is a web interface if our desktop email app/server dies... I just placed that webmail link on their desktop to mess with them, really.), our accounting application, our POS app, Windows, or their screensaver. It's all just 'the system', and most users stop caring at that point.
How would you like me explain to them that the desktop email application cannot connect to its pop server, but the webmail server has an imap connection to the primary email server, in ten words or less that they're not going to read anyways? I'm over simplifying the whole thing, but my point is that you can't instruct someone who doesn't have any intention of doing anything other than calling me to say "the system isn't working."
Are we talking by traffic volume, or number of incidents? How large is a WOW patch? I don't believe the number either, but it wasn't quantified in such a way that it can be refuted, either.
Don't forget, though, if pirating games puts gaming companies out of business, no one will need new hardware for games.
Actually, I run my Linux desktop on RAID0 Raptors. As far as WD goes, my numbers are skewed from an obscure bug they had in their firmware on their **KS drives. I've got 4 AAKS' in my storage box at home, and 3 RE2 Y(D?)KS' on a rack at work.
I've found that in reality the sheer number of WDs that I've got in boxes at any given moment. Their Raptors are in an entirely different league than their large capacity drives, though. I've got three of those (2 150 GB, and a 75GB) in boxes without a single hitch.
IMHO, WDs drives are just at the right price/performance/failure rate ratio. They're not as solid as Seagate, but they also cost less per GB. Then there's Maxtor. I've seen 2 of those things go under this year. Which is remarkable when you consider that that covers 2/3 that were being used. Avoid Maxtor like the plague. Finally, nothing is holding a candle to my old 5.25" Quantum Bigfoot 20GB drive that's been running for nearly ten years now.
I run two Raptors in RAID 0 with short stroked partitions. If you keep your partition slices to the outside of the drive, with variable data partitions (/var, /tmp (if you put that to HD instead of tmpfs), and swap) between static partitions (/usr, /usr/local), you can get much better performance than if you glob the whole thing on LVM. Oh, yeah, and write off the last 15% of the drive, the seek time to it doesn't justify the storage space since it's the slowest part of the drive. Use the kernels I/O elevator to your advantage and lay out your partitions accordingly. If /var is at the middle of the disk, you're, at most, half a disks width from it and will be passing over it to get to other static data.
You will never be yelled at for releasing software with a well understood and documented defect, but the shit will hit the fan when you release major defects that are not understood.
This is the most true thing I've read in a long time. I've found that being as up front as possible about bugs and defects is always the best policy.
But PCI slots aren't in a 1U.
Yeah, it's the last time I'm going to buy one of those things... until the next sale... or if I need to pick one up at Wal*Mart at 3AM. I've been saying that for three years now. Somehow my drives die just in time for the newest WD's to be on sale.