AND... I've gained 3 new foes since I posted to this thread. Out of over 400 posts to slashdot, I've only ever acquired one foe, and then because I bash java performance the number quadruples? What a bunch of idiots.
Thank god there's at least one other voice of reason here, even ifhe is a coward. I can't believe someone modded my post funny. You really think any of that was a joke? In the interest of complete honesty, the 100,000 user java app only had 40,000 users, but it was stress-tested and designed for 100,000 to accomodate growth and for performance headroom. It ran on room-full of IBM SP/2 frames for app servers and a few E10Ks for the database. And the most of the DOS software I've written with "copy con" were extremely tiny utilities in the range of like 64 bytes long. Still, how many people do you who have ever written software directly in hex without looking at any books and without even a proper editor?
1) I see Java-lovers have knocked me down -2 overrated so it's back down to 3. Way to squelch opposing opinion there.
2) To ALL the repliers here: I know exactly what I'm talking about. I have coded expertly and will continue to do so in everything from x86 asm to C to C++ to Java to Perl to..... enough to know. I have written enterprise-class multi-platform java software with 100,000 users and a terabyte database behind it. I've written dos.com program using "copy con" and the numeric keypad, and everything else inbetween. I'm here to tell you, Java is a fucking pig, and you need to realize it. Don't fool yourself with propoganda just because Java is your life and income.
1. Make new website freepixarchive.com. 2. Convince VCs you can charge a monthly fee for access to a well-organized archive of public domain imagery. 3. Ask Slashdot where to get the damn images from because you can't find any. 4. ???? 5. Profit!
On this backup stuff, An even better idea is to teach yourself to use cvs or something similar. CVS is braindead easy to install, it will take 15 minutes of a competent unix guy's time. When you start a new project, make a new module. Train yourself to do "cvs commit -m 'blahblahblah'" after every major accomplishment, and every time you get up from the keyboard for a cigarette. Not only do you have a backup incase of rm problems, you also have a version history for when you decide that the change in direction you made an hour ago sucked and you want to revert.
It's not a stereotype, it's a fact. I write code all the time, I know what I'm talking about. To start with java is fundamentally slow in theory because it's running in a JVM. With efficient optimizing compiler in both cases, native code will always be faster. However, it's slower than the use a virtual machine would indicate, which means the virtual machines aren't exactly optimal to begin with. Don't even get me started on the memory wasteage.
Write any app in JSPs or EJBs or what-have-you, and I'll write the same app in mod_perl, mod_php, and I'll develop it faster, it will be more stable, and it will perform and scale better. C/C++ will of course trounce even perl/php on performance and scaling, but even with some solid libraries and macros at your side, C/C++ is a pain in the ass to work with for HTTP and HTML.
Re:Seems like a silly move...
on
Yahoo Moving to PHP
·
· Score: 5, Insightful
Eep, why J2EE? It's slow, it's a memory hog, it doesn't deliver on the write-once-run-anywhere promise of Java because of the vendors' differences. Perhaps most importantly for them, you really can't use Java w/o threads, and thread support on FreeBSD is not great. Read that over again. That means that Java doesn't scale well for you if your OS's thread don't scale well for you. If you're running FreeBSD, then that's the case, which further limits Java's absymal performance.
You obviously are working with morons. Very few data-oriented applications need to write their own data-stores. Almost anything you can imagine (complex relational data, object-oriented data, xml stuff, photos, video footage, 3/4D spatial data, etc, etc..), someone has written database software tuned for it. Use it and be happy.
Imagine if Oracle and Veritas did this. Most major companies would be up the creek with no paddle if they had to re-license those kinds of software for a major enterprise. Well, actually they might all move to Sybase or PostgreSQL or something, funny how competition makes it all work out:)
Not only is the licensing cheaper, but you'll get better performance. In a theoretical sense, there can be some distinct advantages to 4CPU over 2CPU assuming the Mhz are equivalent (e.g. 2x2Ghz vs 4x1Ghz), but in reality, especially in a Microsoft reality, the scalability just isn't there. The biggest win comes from moving from Single to Dual, and after that it drops like a rock.
Or in the case of no ads, he states the problem is the site might change. Well, Slashdot stories on the front page aren't *that* many a day. Run a little caching daemon that checks for an update to slashdot's copy every 30 minutes or so. Expire sites out of the slashdot cache when the story is 3 days old. Surely they have the disk and bandwidth for that, they just seem to have trouble actually coding it. I think the big problem here is CmdrTaco getting some perverse pleasure from the/. effect.
They don't have to sell their opto-isolators cheaper. They can just manufacture them cheaper, claim they're better in some way or other, and sell them at the same price. People will buy the "new better" technology and they'll turn more profit than the existing opto-isolator manufacturers.
If they are going to absolutely insist on touching your machines, just set up a partition with a fresh copy of Win95 or something, let them mess about there, and then destroy it when they leave. Or if you weren't pre-prepared for that, just let them isntall and then re-install your OS after they're gone. If you're running a Winbloze variant, you should be re-installing your OS every 2-3 months anyways just to clear the cruft.
A 25" TV sucks compared to even a 17" monitor. Your 25" TV gets 320x240 resolution only (unless you've got some high res digital screen, and the xbox as well as linux/xfree86 support the resolution).
You say "ubiquitous drag-and-drop", and then later that it works if you have two programs written with Indigo Magic desktop integration code in them which are few and far between. This is the same problem every Desktop has, Indigo is no better. KDE and Gnome both the capability to the same and more, if people would just use the "desktop integration code" in their apps. The unix desktop world would be a whole lot better off if we'd develop some common APIs for things like this. There's supposedly an XDND protocol, but why don't KDE and Gnome both use it and drop to each other? I always have problems with that.
In a DDoS the flood is coming from helpless slobs all over the net who didn't start it and are unaware. You're going to roundtrip that garbage traffic across the net a second time for even more congestion, and then push it at the client sending it?
If they do it right it may help a small amount in awareness, but the real answer to DDoS is that there's no good answer in the current Internet. Just like Curious Yellow, the only good answer is that OS vendors change their ways very soon and get security together, so that breakins are infrequent and require intelligent effort, as opposed to todays world of a 3-month old script off the net easily seizing 100,000 machines.
The progressive abstraction of computer languages slow to a creep a long time ago. OO has been around very a very long time, just not neccesarily in the form of C++. Essentially the CS world has settled on some mutual understanding the the range of abstraction around C++, Java, and Perl is a pretty good place to be depending on how OO and whatnot you want to be (and of course we will always have the ever-enduring C for simpler and systems programming), and we can't seem to come up with anything better that's got more useful abstraction than that.
There's been a dream of a useful and successful 4GL for many many years now, and from time to time someone claims they've done it, but it's a shoddy system that isn't flexible enough and too proprietary (comes with it's own crappy OS just for that programming language, etc). 4GL (4th generation language) is supposed to supremely abstract away the need for code altogether, or at least try to. In my idea of a proper 4GL, programming would consist of composing one well-structered XML document describing the objects your problem domain deals with, what they can do, and your business rules for dealing with them. It should be something a non-technical person who understands the business can write with a little help for a helper gui. From there 3GL (C++, Java) source code, GUI elements in whatever, middleware servers, database design and sql code, should all spring forth on it's own. But like I said, so far 4GL has been a pipe dream, we seemed to have reached a point where it's going to be very difficult to get much further without figuring out true-AI first, which is some ways off.
Hmm I've never had to deal with printers in my places, so I've never heard of the paper curl thing, interesting. I could've swore it was below 50 though, but like I said, it's been a while since I've been involved at that level. Now I'm all off in software, I really miss doing the hardware stuff myself and building out things like this:(
The only way to run a mission critical app is to make sure that your apps can and are built to either cluster or failover cleanly. If you aren't doing this, you're gambling, and the game doesn't change whether you're using blades or not, just the odds. I prefer the odds stacked in my favor, which means you use the most reliable hardware you can find for a reasonable price, and then assume it has a high failure rate and cluster the crap out of it.
Most of the labs I've built or worked in, we've set up the ACs somewhere around 70-72 degrees. It's plenty cold while still leaving a small amount of headroom. The headroom is useful in case there's a sudden influx of heat and it takes a while to restabilize the temperature. Can't really predict what sorts of wierd things might cause that - a crapload of new equipment, an A/C unit going out of service for an hour, etc, etc..
It's very important to get your humidity correct as well. If the humidity is too low, static buildup becomes easier and static damage more frequent. If it gets too high, corrosion occurs faster. Computers like to be in the middle, if I remember right the ideal for most machines is around 35% humidity? It's been a while, that might be off by a bit.
Don't forget the whole BTUs thing. All your equipment will have a sticker or manual (or call the company) saying how many BTU of heat it puts out at max. Add them all up and make sure you have enough A/C capacity to account for the BTUs during a failure scenario (e.g. Buy 3 AC units that can handle 1/2 the desired BTU, so you have N+1 redundancy). Be sure to estimate the future as best you can in the BTU calculations - replacing A/C units when upgrading new servers in a fully loaded production room can be a bitch.
Computers like stability too, so try to set it up such that the humidity and temperature stay constant while all your gear is running. If they're wobbling up and down throughout the day or week, you need to fix it. You can buy cheap chart recorders for this, they drag a pen over a graph and show you a temperature line for a week or more. Assuming your A/C is adequate for the BTUs, the wobbling is most likely from bad airflow design.
Airflow design can be a black art, so you might want to get a professional. In general, most datacenter-class machines suck cold air from the bottom and/or front and exhaust out the top and/or back. Space out your vent tiles, too many too clsoe together can shunt air away from the inlets on your equipment. But by all means place vent tiles here and there in the empty areas to even out the room.
And if you're looking for professionals to do these kinds of things, up to and including designing and building new datacenters from scratch, I can't recommend IBM Global Services high enough. They really kick ass at these things. It almost makes up for AIX sucking so bad:)
Most moderators are just using it as another avenue to push their opinion, which is sad.
Good for them
on
Blogger Hacked
·
· Score: 3, Insightful
I hate the word blog and all its derivatives, they deserve it for promoting this pop-culter-esque net phenomenon. Either you run a news site, a discussion site, a community, a personal journal or something along those lines. Blog is a stupid term someone made up to sound cool.
Now I can see a large galaxy colliding with a smaller cluster of dwarfs or whatever it was - but at the end of the article they talk as if it's a fairly well-known fact that the Milky Way and Andromeda will collide at some point in the distant future. Now, I seem to remember the classic marker-spots-on-a-balloon explanation that so long as the universe is expanding each galaxy continues to get further and further away from each at a high speed (near light speed but not quite?). Is this simplistic explanation wrong, and in fact large stable galaxies can and do collide into each other, or are they talking in terms of after a theoretical turning point where theuniverse starts shrinking again?
Slashdot Mirror
CNN is reporting on a widely-publicized 1/4-mile drag-race between a broken lawnmower and an earthworm.
AND... I've gained 3 new foes since I posted to this thread. Out of over 400 posts to slashdot, I've only ever acquired one foe, and then because I bash java performance the number quadruples? What a bunch of idiots.
Thank god there's at least one other voice of reason here, even ifhe is a coward. I can't believe someone modded my post funny. You really think any of that was a joke? In the interest of complete honesty, the 100,000 user java app only had 40,000 users, but it was stress-tested and designed for 100,000 to accomodate growth and for performance headroom. It ran on room-full of IBM SP/2 frames for app servers and a few E10Ks for the database. And the most of the DOS software I've written with "copy con" were extremely tiny utilities in the range of like 64 bytes long. Still, how many people do you who have ever written software directly in hex without looking at any books and without even a proper editor?
1) I see Java-lovers have knocked me down -2 overrated so it's back down to 3. Way to squelch opposing opinion there.
2) To ALL the repliers here: I know exactly what I'm talking about. I have coded expertly and will continue to do so in everything from x86 asm to C to C++ to Java to Perl to
1. Make new website freepixarchive.com.
2. Convince VCs you can charge a monthly fee for access to a well-organized archive of public domain imagery.
3. Ask Slashdot where to get the damn images from because you can't find any.
4. ????
5. Profit!
On this backup stuff, An even better idea is to teach yourself to use cvs or something similar. CVS is braindead easy to install, it will take 15 minutes of a competent unix guy's time. When you start a new project, make a new module. Train yourself to do "cvs commit -m 'blahblahblah'" after every major accomplishment, and every time you get up from the keyboard for a cigarette. Not only do you have a backup incase of rm problems, you also have a version history for when you decide that the change in direction you made an hour ago sucked and you want to revert.
It's not a stereotype, it's a fact. I write code all the time, I know what I'm talking about. To start with java is fundamentally slow in theory because it's running in a JVM. With efficient optimizing compiler in both cases, native code will always be faster. However, it's slower than the use a virtual machine would indicate, which means the virtual machines aren't exactly optimal to begin with. Don't even get me started on the memory wasteage.
Write any app in JSPs or EJBs or what-have-you, and I'll write the same app in mod_perl, mod_php, and I'll develop it faster, it will be more stable, and it will perform and scale better. C/C++ will of course trounce even perl/php on performance and scaling, but even with some solid libraries and macros at your side, C/C++ is a pain in the ass to work with for HTTP and HTML.
Eep, why J2EE? It's slow, it's a memory hog, it doesn't deliver on the write-once-run-anywhere promise of Java because of the vendors' differences. Perhaps most importantly for them, you really can't use Java w/o threads, and thread support on FreeBSD is not great. Read that over again. That means that Java doesn't scale well for you if your OS's thread don't scale well for you. If you're running FreeBSD, then that's the case, which further limits Java's absymal performance.
You obviously are working with morons. Very few data-oriented applications need to write their own data-stores. Almost anything you can imagine (complex relational data, object-oriented data, xml stuff, photos, video footage, 3/4D spatial data, etc, etc..), someone has written database software tuned for it. Use it and be happy.
Imagine if Oracle and Veritas did this. Most major companies would be up the creek with no paddle if they had to re-license those kinds of software for a major enterprise. Well, actually they might all move to Sybase or PostgreSQL or something, funny how competition makes it all work out
Not only is the licensing cheaper, but you'll get better performance. In a theoretical sense, there can be some distinct advantages to 4CPU over 2CPU assuming the Mhz are equivalent (e.g. 2x2Ghz vs 4x1Ghz), but in reality, especially in a Microsoft reality, the scalability just isn't there. The biggest win comes from moving from Single to Dual, and after that it drops like a rock.
Or in the case of no ads, he states the problem is the site might change. Well, Slashdot stories on the front page aren't *that* many a day. Run a little caching daemon that checks for an update to slashdot's copy every 30 minutes or so. Expire sites out of the slashdot cache when the story is 3 days old. Surely they have the disk and bandwidth for that, they just seem to have trouble actually coding it. I think the big problem here is CmdrTaco getting some perverse pleasure from the
They don't have to sell their opto-isolators cheaper. They can just manufacture them cheaper, claim they're better in some way or other, and sell them at the same price. People will buy the "new better" technology and they'll turn more profit than the existing opto-isolator manufacturers.
If they are going to absolutely insist on touching your machines, just set up a partition with a fresh copy of Win95 or something, let them mess about there, and then destroy it when they leave. Or if you weren't pre-prepared for that, just let them isntall and then re-install your OS after they're gone. If you're running a Winbloze variant, you should be re-installing your OS every 2-3 months anyways just to clear the cruft.
A 25" TV sucks compared to even a 17" monitor. Your 25" TV gets 320x240 resolution only (unless you've got some high res digital screen, and the xbox as well as linux/xfree86 support the resolution).
You say "ubiquitous drag-and-drop", and then later that it works if you have two programs written with Indigo Magic desktop integration code in them which are few and far between. This is the same problem every Desktop has, Indigo is no better. KDE and Gnome both the capability to the same and more, if people would just use the "desktop integration code" in their apps. The unix desktop world would be a whole lot better off if we'd develop some common APIs for things like this. There's supposedly an XDND protocol, but why don't KDE and Gnome both use it and drop to each other? I always have problems with that.
In a DDoS the flood is coming from helpless slobs all over the net who didn't start it and are unaware. You're going to roundtrip that garbage traffic across the net a second time for even more congestion, and then push it at the client sending it?
If they do it right it may help a small amount in awareness, but the real answer to DDoS is that there's no good answer in the current Internet. Just like Curious Yellow, the only good answer is that OS vendors change their ways very soon and get security together, so that breakins are infrequent and require intelligent effort, as opposed to todays world of a 3-month old script off the net easily seizing 100,000 machines.
The progressive abstraction of computer languages slow to a creep a long time ago. OO has been around very a very long time, just not neccesarily in the form of C++. Essentially the CS world has settled on some mutual understanding the the range of abstraction around C++, Java, and Perl is a pretty good place to be depending on how OO and whatnot you want to be (and of course we will always have the ever-enduring C for simpler and systems programming), and we can't seem to come up with anything better that's got more useful abstraction than that.
There's been a dream of a useful and successful 4GL for many many years now, and from time to time someone claims they've done it, but it's a shoddy system that isn't flexible enough and too proprietary (comes with it's own crappy OS just for that programming language, etc). 4GL (4th generation language) is supposed to supremely abstract away the need for code altogether, or at least try to. In my idea of a proper 4GL, programming would consist of composing one well-structered XML document describing the objects your problem domain deals with, what they can do, and your business rules for dealing with them. It should be something a non-technical person who understands the business can write with a little help for a helper gui. From there 3GL (C++, Java) source code, GUI elements in whatever, middleware servers, database design and sql code, should all spring forth on it's own. But like I said, so far 4GL has been a pipe dream, we seemed to have reached a point where it's going to be very difficult to get much further without figuring out true-AI first, which is some ways off.
Hmm I've never had to deal with printers in my places, so I've never heard of the paper curl thing, interesting. I could've swore it was below 50 though, but like I said, it's been a while since I've been involved at that level. Now I'm all off in software, I really miss doing the hardware stuff myself and building out things like this
The only way to run a mission critical app is to make sure that your apps can and are built to either cluster or failover cleanly. If you aren't doing this, you're gambling, and the game doesn't change whether you're using blades or not, just the odds. I prefer the odds stacked in my favor, which means you use the most reliable hardware you can find for a reasonable price, and then assume it has a high failure rate and cluster the crap out of it.
Most of the labs I've built or worked in, we've set up the ACs somewhere around 70-72 degrees. It's plenty cold while still leaving a small amount of headroom. The headroom is useful in case there's a sudden influx of heat and it takes a while to restabilize the temperature. Can't really predict what sorts of wierd things might cause that - a crapload of new equipment, an A/C unit going out of service for an hour, etc, etc..
It's very important to get your humidity correct as well. If the humidity is too low, static buildup becomes easier and static damage more frequent. If it gets too high, corrosion occurs faster. Computers like to be in the middle, if I remember right the ideal for most machines is around 35% humidity? It's been a while, that might be off by a bit.
Don't forget the whole BTUs thing. All your equipment will have a sticker or manual (or call the company) saying how many BTU of heat it puts out at max. Add them all up and make sure you have enough A/C capacity to account for the BTUs during a failure scenario (e.g. Buy 3 AC units that can handle 1/2 the desired BTU, so you have N+1 redundancy). Be sure to estimate the future as best you can in the BTU calculations - replacing A/C units when upgrading new servers in a fully loaded production room can be a bitch.
Computers like stability too, so try to set it up such that the humidity and temperature stay constant while all your gear is running. If they're wobbling up and down throughout the day or week, you need to fix it. You can buy cheap chart recorders for this, they drag a pen over a graph and show you a temperature line for a week or more. Assuming your A/C is adequate for the BTUs, the wobbling is most likely from bad airflow design.
Airflow design can be a black art, so you might want to get a professional. In general, most datacenter-class machines suck cold air from the bottom and/or front and exhaust out the top and/or back. Space out your vent tiles, too many too clsoe together can shunt air away from the inlets on your equipment. But by all means place vent tiles here and there in the empty areas to even out the room.
And if you're looking for professionals to do these kinds of things, up to and including designing and building new datacenters from scratch, I can't recommend IBM Global Services high enough. They really kick ass at these things. It almost makes up for AIX sucking so bad
It's my 400th post, so I thought I'd make a totally offtopic post on whatever topic was at the top of the page.
Happy 400th post to me!
Happy 400th post to me!
Well, that doesn't even match syllables with the bidrthday song does it?
Haha, here's great proof of moderators moderating based on their opinion of the subject matter (taken from my post above as of about 2:30pm cst):
Moderation Totals: Flamebait=1, Troll=1, Insightful=3, Interesting=2, Overrated=2, Total=9.
Most moderators are just using it as another avenue to push their opinion, which is sad.
I hate the word blog and all its derivatives, they deserve it for promoting this pop-culter-esque net phenomenon. Either you run a news site, a discussion site, a community, a personal journal or something along those lines. Blog is a stupid term someone made up to sound cool.
Now I can see a large galaxy colliding with a smaller cluster of dwarfs or whatever it was - but at the end of the article they talk as if it's a fairly well-known fact that the Milky Way and Andromeda will collide at some point in the distant future. Now, I seem to remember the classic marker-spots-on-a-balloon explanation that so long as the universe is expanding each galaxy continues to get further and further away from each at a high speed (near light speed but not quite?). Is this simplistic explanation wrong, and in fact large stable galaxies can and do collide into each other, or are they talking in terms of after a theoretical turning point where theuniverse starts shrinking again?