Which is why today I am finally going to exclude Katz from my list of authors...
/. should do a db dump of the excludes from the user prefs, and post it... I'd like to see the % of people who exclude each author... it'd be interesting.
I always check for replies (my karma level is happy enough to be irrelevant most of the time, though I am hurt to see my posts at 0 8^D)...
I've suggested the reverse option for the +1 bonus myself... not sure if things have fallen on deaf ears, or if somebody really has a good reason. I agree with most moderation (I don't find nearly as many items to mark 'unfair' in M2 as there used to be), but every once in a while, somebody gets targeted (I had a lot of AC flames that same week for karma whoring (what a surprise))... Started to feel like Sig, Enoch, et. al.... Probably just pissed somebody off with one of my comments 8^)
Moderation is a Good Thing, though... it's been very helpful (haven't seen a ninja/natalie/ascii art/smut story post in a while (except when somebody mods them up as "funny", which is pretty unusual).
I think that *is* the smell of burning karma;-)
Re:Keep in mind- Intel is a moving target too
on
1.4-1.6 GHz Alphas
·
· Score: 1
Biggest problem (still) with the x86 architecture is the variable length instructions (and all of the old cruft that hasn't been used since the 286 days). Fixed length instructions are so much cleaner, and more efficient. The whole FP architecture for the Pentium-line is slowed up... Check out the SpecFP for the Alphas and Power/PowerPC chips... much happier at the same clock speed - with the same number of execution units, geneally. It's all in the design, and that's one thing that Mertanium was supposed to be fixing...
Um... every chip fabbed at IBM will have the option of using this tech. You only make money off of licensing if you actually let other people use it... and the proposition of using should draw more chips to the IBM fabs. So... it's not only the POWER/PowerPC lines.
Hehe - actually, I thought your.sig was pretty funny...
I've stopped posting at 2, after three or four days where every post I sent at 2 was immediately marked Overrated... even if it was later modded up for other reasons... kind of a pain.
I still see people complaining "Why did this crap get up to 2, it sucks!" and then several other people explaining the bonus... this community is getting less informed as more people jump in without a little reading... like another comment on this story - "Proposed New Slashdot slogan: Read First, Post Later" It might actually help...
(now posting with a +1 to see if I'm still being targeted - and I didn't think I deserved any attention 8^D)
The whole interconnect / gate speed thing has been a cycle, and probably will continue to be (though it's getting to be more and more interconnect lately). You architect a system - all is good, and you are usually held back by your logic, not your wires. You respin your chip a few times, ramping up the clock speed with new technology, until your wires get in the way... uh-oh! Time to fix a few things an re-release this one (think P-II/III)...
The newer the design, the better you can take advantage of all of the new technologies, and really gain the most... you have total control over your wiring, and most of your paths. If you need to stay fully compatable with a previous chip, and want to retain as much of the logic as possible (finally got that pesky FP thing working right), then you are going to suffer in how far you can take things.
There's tons of overhead in a full redesign (person-years, dev costs, etc) - look at AMD with the Athlon (maintaining compatability, but redesigning most of the internals), but look at the gains in clock speed (more complicated in many areas than the P-lines, but easier to ramp up).
There's quicker cheaper fixes, but they don't buy you as much at one time - here we have the PPro/PII/P!!!/P!!! Coppermine...... re-optimize a little bit and you get a good MHz percentage increase... but you have to make these changes more often. (there are changes to be made with any chip that needs to ramp up the clock - even the Athlon, though as of now, a lot of that can be attributed to process rather than design - a good place to be).
The Merced (aka Itanium, aka PA-Risc w/IA-64) is a good step at breaking out of a rapidly dying ISA (though Willamette shows some promise at extending the life of this storied line even further), but the delays there have really soured some people on it, and many are looking at the next generation Alphas and the next POWER chips from IBM (and PowerPC line, of course). There's a lot of good 64 bit solutions out there, and there's no doubt we should continue to push forward, but I'm doubting that Iced/Mertaium will get to market in time for its performance point...
That doesn't look all that useful... (/. swallowed your angle brackets again)...
And actually, your version (repaired) compiles to a larger size and uses more CPU time than his (at least on my box)... which is bloated </C++ bloat flame>
Summary of the "Fire!" analysis as it relates to our Declaration of Independance (completely ignoring the constitution and all laws/regs):
Their right to life outweighs your right to the pusuit of happiness, and ends up revoking your right to liberty.
Re:Do we understand the implications?
on
Microsoft Loses
·
· Score: 1
No bash on an RS/6k by default - it's all csh (though you can plug in whatever shell you want, of course...) Given the number of workstations out there, I wouldn't claim that bash is quite everywhere...
There's also commercial solutions such as phonepatch (which works really well, and gives you a 30 day trial). There's a web interface for configure and everything... alas, my license ran out back in Jan...
On the plus side, Dialpad links to ipmasq patches that let it work properly... pretty nifty...
True, true... but if you get creative and have your DDOS program crawl and start a session (by following an item link, or even better, use a search) then you can more or less guarantee getting fresh dynamic pages (and cause more problems)...
The main dynamic pages (store front, product listings, etc) would be cached, but hey, if one is planning a DDOS attack, one should be smart enough to take more down more efficiently;-)
Won't work for pages that are built dynamically, though (i.e./. or Amazon)... If it uses incoming info (like cookies) to produce the page, then your solution won't really hold up too well... If everything is static, then you wouldn't have as many problems to start with - the server and database load is what ends up killing you, and if that doesn't, there could end up being far too much traffic through the pipe to be able to do anything anyway...
I've got a slightly older 21" Cornerstone 50/101sf... I've run quite clearly at 1600x1200 at 85+, and made a few efforts above 1920x1200 - still really clear. It's not an ultra-flat (like the Trinitron FDs), but it only ran me ~$400 (w/ shipping) on auction (1 yr warantee reconditioned). I get some ghosts at 1280 and up, but that's when I'm connected through my Cybex KVM switch... when I connect the cable directly, it's crystal.
Shouldn't someone be modding up a good post or blasting a real troll instead of wasting a point on a comment that really didn't deserve any attention (either way)?
Moderate this down to -1 (this one actually *is* offtopic), but the parent wasn't...
Moderation only works if it's used properly... hope this gets caught in M2 </whine, bitch and moan>
There's a growing number of sites using slashcode (mine was using.9.2 until a couple days ago), and there's a good number of people on the mailing list, naming bug, submitting patches, and making suggestions.
As for your concern about 1.0s and messy code floating around. Yup, there's lots of messy code out there. If you don't like it, help out or don't use it. You don't have to rewrite it, but if you can recognize 'messy code', you should be able to help out in one way or another. It's only free beer if somebody makes it first.
As much respectas I have for RMS and ESR, I don't think that a smackdown from them would be good for things, and a point of having open source is to *NOT* keep it to yourself until it is "cleaned up and ready" - it's easier to get it ready if you have more help. That's why it works.
Open Source implementation varies from person to person, project to project... you can't place the blame on any person for anyone else's shortcomings.
I've been using slashcode since.9.2, and aside from a few things, most of it is actually working pretty well (.9.4 solved a lot of outstanding problems). It's still a little effort to get running, and isn't the easiest thing to run on a virtual domain, but it is doable and actually pretty easy to hack around in (coming from someone who doesn't have a whole lot of Perl background)... I like it, though there's certainly a lot that could be improved. Don't think *all* the bugs will be out by.2.... you'd need a pretty big overhaul to restructure some parts...
Check out slashcode.com - there's the usual/. web interface, and there's a mailing list to sign up for... a lot of the patches go over that list, and I believe out on server 52 there's some form of bugtracking...
Remember that mainframes (i.e. 390) have some really nice kill and redundancy features... processor or memory stick dies... oh well, shut it down and keep going, then fire off an alert to the admin. Concurrent matainance.... mmmm....
Well, the new mainframes have really taken back a good chunck of the market, and are especially good for the ultra-high transaction areas (think financial companies). Mainframes value I/O performance above number crunching, and that is what's important for certain apps. You wouldn't want to run Quake 3 on it, but on the other hand, you aren't going to notice a lot of slow-down with heavy loads, either...
That and all these linux instances are mostly idle... unless it was 41k instances of RC5;-)
Slashdot Mirror
he always has been - haven't you read his other columns?
Which is why today I am finally going to exclude Katz from my list of authors...
/. should do a db dump of the excludes from the user prefs, and post it... I'd like to see the % of people who exclude each author... it'd be interesting.
true asynch subsystems don't *have* clock speeds 8^D
Of course... if your communication to the other areas could be clocked, if that's what you mean...
That's why I browse at 1, with highest scores first.... a lot easier on the eyes 8^)
I always check for replies (my karma level is happy enough to be irrelevant most of the time, though I am hurt to see my posts at 0 8^D)...
;-)
I've suggested the reverse option for the +1 bonus myself... not sure if things have fallen on deaf ears, or if somebody really has a good reason. I agree with most moderation (I don't find nearly as many items to mark 'unfair' in M2 as there used to be), but every once in a while, somebody gets targeted (I had a lot of AC flames that same week for karma whoring (what a surprise))... Started to feel like Sig, Enoch, et. al.... Probably just pissed somebody off with one of my comments 8^)
Moderation is a Good Thing, though... it's been very helpful (haven't seen a ninja/natalie/ascii art/smut story post in a while (except when somebody mods them up as "funny", which is pretty unusual).
I think that *is* the smell of burning karma
Biggest problem (still) with the x86 architecture is the variable length instructions (and all of the old cruft that hasn't been used since the 286 days). Fixed length instructions are so much cleaner, and more efficient. The whole FP architecture for the Pentium-line is slowed up... Check out the SpecFP for the Alphas and Power/PowerPC chips... much happier at the same clock speed - with the same number of execution units, geneally. It's all in the design, and that's one thing that Mertanium was supposed to be fixing...
Um... every chip fabbed at IBM will have the option of using this tech. You only make money off of licensing if you actually let other people use it... and the proposition of using should draw more chips to the IBM fabs. So... it's not only the POWER/PowerPC lines.
Think about it.
Hehe - actually, I thought your .sig was pretty funny...
I've stopped posting at 2, after three or four days where every post I sent at 2 was immediately marked Overrated... even if it was later modded up for other reasons... kind of a pain.
I still see people complaining "Why did this crap get up to 2, it sucks!" and then several other people explaining the bonus... this community is getting less informed as more people jump in without a little reading... like another comment on this story - "Proposed New Slashdot slogan: Read First, Post Later" It might actually help...
(now posting with a +1 to see if I'm still being targeted - and I didn't think I deserved any attention 8^D)
The whole interconnect / gate speed thing has been a cycle, and probably will continue to be (though it's getting to be more and more interconnect lately). You architect a system - all is good, and you are usually held back by your logic, not your wires. You respin your chip a few times, ramping up the clock speed with new technology, until your wires get in the way... uh-oh! Time to fix a few things an re-release this one (think P-II/III)...
The newer the design, the better you can take advantage of all of the new technologies, and really gain the most... you have total control over your wiring, and most of your paths. If you need to stay fully compatable with a previous chip, and want to retain as much of the logic as possible (finally got that pesky FP thing working right), then you are going to suffer in how far you can take things.
There's tons of overhead in a full redesign (person-years, dev costs, etc) - look at AMD with the Athlon (maintaining compatability, but redesigning most of the internals), but look at the gains in clock speed (more complicated in many areas than the P-lines, but easier to ramp up).
There's quicker cheaper fixes, but they don't buy you as much at one time - here we have the PPro/PII/P!!!/P!!! Coppermine...... re-optimize a little bit and you get a good MHz percentage increase... but you have to make these changes more often. (there are changes to be made with any chip that needs to ramp up the clock - even the Athlon, though as of now, a lot of that can be attributed to process rather than design - a good place to be).
The Merced (aka Itanium, aka PA-Risc w/IA-64) is a good step at breaking out of a rapidly dying ISA (though Willamette shows some promise at extending the life of this storied line even further), but the delays there have really soured some people on it, and many are looking at the next generation Alphas and the next POWER chips from IBM (and PowerPC line, of course). There's a lot of good 64 bit solutions out there, and there's no doubt we should continue to push forward, but I'm doubting that Iced/Mertaium will get to market in time for its performance point...
oh well...
#include
using std::cout;
int main()
{
cout }
That doesn't look all that useful... (/. swallowed your angle brackets again)...
And actually, your version (repaired) compiles to a larger size and uses more CPU time than his (at least on my box)... which is bloated </C++ bloat flame>
oh, yeah - namespaces suck </C++ flame 2>
Silly, it's not a "grabelcrochit", it happens to be a "dwunklegleebzit" (or so I'll keep telling myself) 8^)
Summary of the "Fire!" analysis as it relates to our Declaration of Independance (completely ignoring the constitution and all laws/regs):
Their right to life outweighs your right to the pusuit of happiness, and ends up revoking your right to liberty.
No bash on an RS/6k by default - it's all csh (though you can plug in whatever shell you want, of course...) Given the number of workstations out there, I wouldn't claim that bash is quite everywhere...
Check out http://www.openh323.org/
There's also commercial solutions such as phonepatch (which works really well, and gives you a 30 day trial). There's a web interface for configure and everything... alas, my license ran out back in Jan...
On the plus side, Dialpad links to ipmasq patches that let it work properly... pretty nifty...
True, true... but if you get creative and have your DDOS program crawl and start a session (by following an item link, or even better, use a search) then you can more or less guarantee getting fresh dynamic pages (and cause more problems)...
;-)
The main dynamic pages (store front, product listings, etc) would be cached, but hey, if one is planning a DDOS attack, one should be smart enough to take more down more efficiently
>But, alas,that would require more political muscle than I have!
;-)
We could always give our governor a call... he's got the muscle... though how much of it is political muscule is another story....
Maybe we could start the new Jesse V. site - whomping-ass-in-MN.com
Won't work for pages that are built dynamically, though (i.e. /. or Amazon)... If it uses incoming info (like cookies) to produce the page, then your solution won't really hold up too well... If everything is static, then you wouldn't have as many problems to start with - the server and database load is what ends up killing you, and if that doesn't, there could end up being far too much traffic through the pipe to be able to do anything anyway...
I've got a slightly older 21" Cornerstone 50/101sf... I've run quite clearly at 1600x1200 at 85+, and made a few efforts above 1920x1200 - still really clear. It's not an ultra-flat (like the Trinitron FDs), but it only ran me ~$400 (w/ shipping) on auction (1 yr warantee reconditioned). I get some ghosts at 1280 and up, but that's when I'm connected through my Cybex KVM switch... when I connect the cable directly, it's crystal.
Shouldn't someone be modding up a good post or blasting a real troll instead of wasting a point on a comment that really didn't deserve any attention (either way)?
Moderate this down to -1 (this one actually *is* offtopic), but the parent wasn't...
Moderation only works if it's used properly... hope this gets caught in M2
</whine, bitch and moan>
Seems like a troll, but I'll bite...
.9.2 until a couple days ago), and there's a good number of people on the mailing list, naming bug, submitting patches, and making suggestions.
There's a growing number of sites using slashcode (mine was using
As for your concern about 1.0s and messy code floating around. Yup, there's lots of messy code out there. If you don't like it, help out or don't use it. You don't have to rewrite it, but if you can recognize 'messy code', you should be able to help out in one way or another. It's only free beer if somebody makes it first.
As much respectas I have for RMS and ESR, I don't think that a smackdown from them would be good for things, and a point of having open source is to *NOT* keep it to yourself until it is "cleaned up and ready" - it's easier to get it ready if you have more help. That's why it works.
Open Source implementation varies from person to person, project to project... you can't place the blame on any person for anyone else's shortcomings.
I've been using slashcode since .9.2, and aside from a few things, most of it is actually working pretty well (.9.4 solved a lot of outstanding problems). It's still a little effort to get running, and isn't the easiest thing to run on a virtual domain, but it is doable and actually pretty easy to hack around in (coming from someone who doesn't have a whole lot of Perl background)... I like it, though there's certainly a lot that could be improved. Don't think *all* the bugs will be out by .2.... you'd need a pretty big overhaul to restructure some parts...
That's http://server51.freshmeat.net/projects/9
not 52 (D'Oh!)
Check out slashcode.com - there's the usual /. web interface, and there's a mailing list to sign up for... a lot of the patches go over that list, and I believe out on server 52 there's some form of bugtracking...
Remember that mainframes (i.e. 390) have some really nice kill and redundancy features... processor or memory stick dies... oh well, shut it down and keep going, then fire off an alert to the admin. Concurrent matainance.... mmmm....
Well, the new mainframes have really taken back a good chunck of the market, and are especially good for the ultra-high transaction areas (think financial companies). Mainframes value I/O performance above number crunching, and that is what's important for certain apps. You wouldn't want to run Quake 3 on it, but on the other hand, you aren't going to notice a lot of slow-down with heavy loads, either...
;-)
That and all these linux instances are mostly idle... unless it was 41k instances of RC5