I'm a troll, I anonymously post links to homosexual pornography, I FP, I crapflood (shitstorm broke my computer, though), and I WANT TO KILL YOU!
I apologise for the parent post.
on
Eclipse in Action
·
· Score: 0, Offtopic
My account appears to have been broken into. Sorry for the inconvenience.
Re:My experiences with Eclipse.
on
Eclipse in Action
·
· Score: -1, Flamebait
I'M GONNA FUCKING KILL YOU!!!
My experiences with Eclipse.
on
Eclipse in Action
·
· Score: -1, Troll
The Eclipse IDE is one of the pinnacles of the labyrinthian open source movement. It is the foremost integration development environment for Java, featuring a compiler, a text editor and an interpreter. I subscribed to a development mailing list and it seems that in the new version they will add support for DMCAscript and other such lightweight clientside scripting technologies; it costs only approximately $4.50 and after that the code is given to you on 3 CDs and is public domain material; this means that free versions are readily available for download in the form of RPMs, DEBs, GENTs and FAGs via countless FTP, HTTP and FQP sites around the Interweb.
I would estimate, as a middle manager, that the Eclipse IDE has saved my department of engineers and marketers approximately $40,000 per year, which doubled after I (unfortunately) had to fire them. Productivity has skyrocketed. Not so happily, the remaining nerds of the organization have discovered some insidious security holes in Eclipse, including the execution of arbitrary Java and JavaScript from unknown hosts on ports 3372 and 1173. This sometimes causes segmentation faults in address 3899 of version 2.1, which makes serious work difficult. We have contacted the developers, but being a product which utilises an open sores decentralised developmental model, it has not been possible to have these problems fixed in the last four releases. As a consequence, our corporation has had to switch to a proprietary solution. The GNU users in our company have objected, but as of this present time there has been nothing for us (a Java solution development identity and partner) to do.
However, we expect great things of Eclipse in future. Keep up the good work!
C'est une conséquence normale des sociétés molles de nouveau promettant tout mais ne fournissant rien. Diable est-ce qu'elles comptent si elles réclament qu'elles vont mettent en évidence des modules de gestion de périphérique et puis rien? Ces personnes sont presque aussi mauvaises que des fabricants de winmodem. Pourquoi le matériel a-t-il besoin même de conducteurs? Quel est le problème avec de bons vieux appels mode d'ioctl()?
Je calme en bas d'un peu maintenant. Mais toujours, pourquoi ces compagnies ne produisent-elles pas des modules de gestion de périphérique pour des systèmes d'UNIX? Elles pensant qu'il n'est pas économiquement viable, mais elles sont aller juste perdre le part de marché et sembler mauvaises, en particulier car elles retournent sur ce qui est efficacement un accord avec une grande communauté. Il est senseless et n'atteint aucun objectif. Naturellement un intrus de grain avec d'la certaine heure disponible sur leurs mains va écrire un conducteur pour lui!
Not quite!
It's not that easy to think up material! You have to quickly bash it out in the first 30 or 40 comments to get noticed, and it's really quite hard. I've already had to do that twice today, so I think I deserve a bit of a break!:-)
The open source development model allows tremendous flexibility, allowing members of a development team to be dropped or added at a moment's notice. With the source readily available and GPLed, one can become familiar with a project's code and CC before applying to be given access to the CVS or equivalent repository. Gradual accretion may produce code in a style not unlike that of James A. A. Joyce's Ulysses manuscripts, but, like James A. A. Joyce, all of the core developers can easily jump from point to point in the code and comprehend the necessary sections and the C/PHP/Python/Java equivalent of their allusions.
Unfortunately, as a result of this decentralised development system, commercial QA, support and RHQ are not as readily available. I'm a middle manager and my company has had a double-sided experience with the MySQL AB organization. They produce a fine product which is perfect for a medium sized corporation such as the one I work for (which shall remain nameless). MySQL worked very well for us, but unfortunately at one point we started receiving segmentation faults when there were more than 30 connections or if a query was greater than 2,048 characters in length. We have reported these bugs to MySQL AB but they have not yet fixed them in their latest gamma/production release. However, they have been very polite and are always willing to cooperate with us; even if small portions of the code are not yet fixable and have escaped the relatively poor QA of the EOD, their TOS have always been reasonable and our MD has always been able to CWT regarding the slight problems and BS our way around them.
Well, it seems like yet another of our technological networking freedoms is being quashed by the state. Seriously, why do we need to have another form of communication censored? If these mechanisms such as email and the W3 client/server system weren't a problem back in the 1950s, 1960s and 1980s, what is the problem with them now? Does anyone genuinely believe that there were somehow through some twist of fate absolutely no paedophilic computer users back when Ritchie and Thompson wrote UNIX in PDP-3 assembler? Why do we need to have HTTP, FTP, P2P, SMTP, LRP and YQP regulated by outside bodies? When did we need to eliminate selfpolicing?
The Internet was founded on the propogation of information as freely as possible. This means that Web surfing, Usenet threads and email messages are all equally valuable and important, and removing free email services would remove the infrastructure of one of the Internet's most fundamental protocols. Though it is true that many free email users are fly-by-night peculiars such as trolls and paedos, we have to understand that they provide a service not unlike those of coin-operated telephone boxes and stamp-operated postal services, and that vigorously spying on free email users is tantamount to removing phone and mail boxes or tapping them.
Besides, keeping an eye on free email services won't reduce the problem. If child pornographers and spammers are determinted to get their messages through, then they can just use encryption, or the Freenet protocol to make them untraceable - or both, in which case nothing can be done. Public key encryption algorithm implementations such as RSA, DES and AES mean that the police would reqire upwards of 75,000 manhours per email message to discover inappropriate content; despite being impossible, this is still a violation of our privacy rights!
In addition to this, by carrying out these actions the police are effectively saying that ISP and other pay email accounts are in some way superior to free email accounts. While they may be superior, there can be no way of saying that an email from someone using AOL is more reputable than one from fastmail.fm or any other ISP/POP3 provider using open source software. Just because an email provider happents to use UNIX/Linux servers doesn't mean that they are necessarily infested with unsavoury characters; in fact, I have received more unwanted email from large ISPs, IAPs and LAPs than from fleeting servers hidden somewhere on Christmas Island.
I could continue, but I think that with more than a cursory notice the other multitudinous incarnadine problems with this new system become clear, and we must make sure that these plans do not become widespread. Fortunately, they are quite impractical, so a few negative anecdotes should encourage most middle managers in service providers and tech support to avoid implementing it.
"I do understand your disappointment at discovering that your trolling was not trolling at all, but quite a reasonable post in light of MySQL crash problems on OpenBSD 3.3_STABLE;-)"
I suppose I'll have to become even more subtly incendiary and make some more outlandish statements. Maybe make some vague references to a controversial and topical subject.
"You might want to reconsider:
(About the fool) He is the most intelligent and insightful [emphasis mine] character in the play and provides simple and clear reasoning for a one sighted King."
+5, Insightful is the holy grail of all trolls, and I suppose I did achieve it with the minimum of effort. Though ideally I would provide a labyrinth of jumbled and inflammatory concepts as opposed to "simple and clear reasoning".
I guess I'll just sleep on it and see if I can come up with a more effective yet equally pernicious troll next time. Oh, well. Good night.
Maybe I should've used more abbreviations in the last few sentences. I would've thought that using the abbreviation "BS" in that context would've given me away, but no!
The open source development model gives tremendous flexibility and leeway for various methodologies such as XP or the more traditional but cumbersome waterfall method, allowing members of a development team to be dropped or added at a moment's notice. With the source readily available, one can become familiar with a project's code before applying to be given access to the CVS or equivalent repository. Gradual accretion may produce code in a style not unlike that of James A. A. Joyce's Ulysses manuscripts, but, like James A. A. Joyce, all of the core developers can easily jump from point to point in the code and comprehend the necessary sections and the C/PHP/Python/Java equivalent of their programmative allusions.
Unfortunately, as a result of this decentralised development system and the reduced usage of traditional ways of programming large-scale projects like WM and RDP due to the geographic dispersion of developers, commercial QA, support and RHQ are not as readily available. I'm a middle manager and my company has had a double-sided experience with the MySQL AB organization. They produce a fine product which is perfect for a medium sized corporation such as the one I work for (which shall remain nameless). MySQL worked very well for us, but unfortunately at one point we started receiving segmentation faults and other similar insidious faults (such as KPs and the like) when there were more than 30 connections to multiple database servers or if a query was greater than 2,048 characters in length. We appreciate that these difficulties can be hard to track down and correct and so our engineers have reported these bugs to MySQL AB but they have not yet fixed them in their latest gamma/production release. However, they have been very polite and are always willing to cooperate with us; even if small portions of the code are not yet fixable and have escaped the relatively poor QA of the EOD, their TOS have always been reasonable and our MD has always been able to CWT regarding the slight problems and make our way around them.
The open source development model allows tremendous flexibility, allowing members of a development team to be dropped or added at a moment's notice. With the source readily available, one can become familiar with a project's code before applying to be given access to the CVS or equivalent repository. Gradual accretion may produce code in a style not unlike that of James A. A. Joyce's Ulysses manuscripts, but, like James A. A. Joyce, all of the core developers can easily jump from point to point in the code and comprehend the necessary sections and the C/PHP/Python/Java equivalent of their allusions.
Unfortunately, as a result of this decentralised development system, commercial QA, support and RHQ are not as readily available. I'm a middle manager and my company has had a double-sided experience with the MySQL AB organization. They produce a fine product which is perfect for a medium sized corporation such as the one I work for (which shall remain nameless). MySQL worked very well for us, but unfortunately at one point we started receiving segmentation faults when there were more than 30 connections or if a query was greater than 2,048 characters in length. We have reported these bugs to MySQL AB but they have not yet fixed them in their latest gamma/production release. However, they have been very polite and are always willing to cooperate with us; even if small portions of the code are not yet fixable and have escaped the relatively poor QA of the EOD, their TOS have always been reasonable and our MD has always been able to CWT regarding the slight problems and BS our way around them.
"Anyone who claims that any Microsoft software is good will quickly be modded to Score:-1."
And anyone who spouts that kind of stereotypical "slashbot" anti-Microsoft bullshit will get modded up Insightful.
And then I'll get slapped with Offtopics and Flamebaits for daring to disagree with the anti-anti-Microsoft zealots. Go ahead and mod me down, it'll just prove my point.
Burn your important bits of paper. Or if you're environmentally friendly, stick 'em in acid. Or you could flush it down the toilet after you tear 'em up. The possibilities are endless. It's easier to get rid of paper data than HDD data, anyway.
If a guy with a new cellphone built by my company flies from Chicago travelling west at 800 miles per hour, and the navigation system locks up, and the plane crashes and burns with everyone trapped inside, does my company initiate a recall?
You take the number of phones in the air (A) and multiply it by the probable rate of disaster (B), then multiply the result by the average cost of an out-of-court settlement (C).
A times B times C equals X. This is what it will cost if we don't initiate a recall.
If X is greater than the cost of a recall, we recall the phones and no one gets hurt.
If X is less than the cost of a recall, then we don't recall.
Everywhere I go, there's the burned-up wadded-up shell of a plane waiting for me. I know where all the skeletons are. Consider this my job security.
For another thing, Gnumeric doesn't like viewing CSV data. Why? It's a simple, plaintext format that even gnuplot handles. I'd love to use Gnumeric instead of playing around with OO Calc or something else, but this fact combined with its barely customisable plotting means that I just use LaTeX and gnuplot w/ pslatex to produce charts and graphs for essays and statistics projects.
You're lucky! Back in my day we had 40 people to a console connected to a mainframe by a string seventy miles long! When it got wet one of us had to drive over there and reset the thing! And we had to use a Timex for a screen! I'm still waiting for 'true' to finish!
"My first thought was to sign the public key with another, use an X.509 certificate or something but the problem is that you can always patch the signature/certificate/checksum/whatever verification mechanism... So what is the solution?"
There is no solution. If someone's got physical access to hardware, all bets are off and there's nothing you can do. The only solution to the problem would be a physical one, such as using superglue to hold the case shut.
Slashdot Mirror
I'm sorry, I have severe scizophrenia.
I'm a troll, I anonymously post links to homosexual pornography, I FP, I crapflood (shitstorm broke my computer, though), and I WANT TO KILL YOU!
My account appears to have been broken into. Sorry for the inconvenience.
I'M GONNA FUCKING KILL YOU!!!
The Eclipse IDE is one of the pinnacles of the labyrinthian open source movement. It is the foremost integration development environment for Java, featuring a compiler, a text editor and an interpreter. I subscribed to a development mailing list and it seems that in the new version they will add support for DMCAscript and other such lightweight clientside scripting technologies; it costs only approximately $4.50 and after that the code is given to you on 3 CDs and is public domain material; this means that free versions are readily available for download in the form of RPMs, DEBs, GENTs and FAGs via countless FTP, HTTP and FQP sites around the Interweb.
I would estimate, as a middle manager, that the Eclipse IDE has saved my department of engineers and marketers approximately $40,000 per year, which doubled after I (unfortunately) had to fire them. Productivity has skyrocketed. Not so happily, the remaining nerds of the organization have discovered some insidious security holes in Eclipse, including the execution of arbitrary Java and JavaScript from unknown hosts on ports 3372 and 1173. This sometimes causes segmentation faults in address 3899 of version 2.1, which makes serious work difficult. We have contacted the developers, but being a product which utilises an open sores decentralised developmental model, it has not been possible to have these problems fixed in the last four releases. As a consequence, our corporation has had to switch to a proprietary solution. The GNU users in our company have objected, but as of this present time there has been nothing for us (a Java solution development identity and partner) to do.
However, we expect great things of Eclipse in future. Keep up the good work!
C'est une conséquence normale des sociétés molles de nouveau promettant tout mais ne fournissant rien. Diable est-ce qu'elles comptent si elles réclament qu'elles vont mettent en évidence des modules de gestion de périphérique et puis rien? Ces personnes sont presque aussi mauvaises que des fabricants de winmodem. Pourquoi le matériel a-t-il besoin même de conducteurs? Quel est le problème avec de bons vieux appels mode d'ioctl()?
Je calme en bas d'un peu maintenant. Mais toujours, pourquoi ces compagnies ne produisent-elles pas des modules de gestion de périphérique pour des systèmes d'UNIX? Elles pensant qu'il n'est pas économiquement viable, mais elles sont aller juste perdre le part de marché et sembler mauvaises, en particulier car elles retournent sur ce qui est efficacement un accord avec une grande communauté. Il est senseless et n'atteint aucun objectif. Naturellement un intrus de grain avec d'la certaine heure disponible sur leurs mains va écrire un conducteur pour lui!
Not quite! It's not that easy to think up material! You have to quickly bash it out in the first 30 or 40 comments to get noticed, and it's really quite hard. I've already had to do that twice today, so I think I deserve a bit of a break! :-)
The open source development model allows tremendous flexibility, allowing members of a development team to be dropped or added at a moment's notice. With the source readily available and GPLed, one can become familiar with a project's code and CC before applying to be given access to the CVS or equivalent repository. Gradual accretion may produce code in a style not unlike that of James A. A. Joyce's Ulysses manuscripts, but, like James A. A. Joyce, all of the core developers can easily jump from point to point in the code and comprehend the necessary sections and the C/PHP/Python/Java equivalent of their allusions. Unfortunately, as a result of this decentralised development system, commercial QA, support and RHQ are not as readily available. I'm a middle manager and my company has had a double-sided experience with the MySQL AB organization. They produce a fine product which is perfect for a medium sized corporation such as the one I work for (which shall remain nameless). MySQL worked very well for us, but unfortunately at one point we started receiving segmentation faults when there were more than 30 connections or if a query was greater than 2,048 characters in length. We have reported these bugs to MySQL AB but they have not yet fixed them in their latest gamma/production release. However, they have been very polite and are always willing to cooperate with us; even if small portions of the code are not yet fixable and have escaped the relatively poor QA of the EOD, their TOS have always been reasonable and our MD has always been able to CWT regarding the slight problems and BS our way around them.
Well, it seems like yet another of our technological networking freedoms is being quashed by the state. Seriously, why do we need to have another form of communication censored? If these mechanisms such as email and the W3 client/server system weren't a problem back in the 1950s, 1960s and 1980s, what is the problem with them now? Does anyone genuinely believe that there were somehow through some twist of fate absolutely no paedophilic computer users back when Ritchie and Thompson wrote UNIX in PDP-3 assembler? Why do we need to have HTTP, FTP, P2P, SMTP, LRP and YQP regulated by outside bodies? When did we need to eliminate selfpolicing?
The Internet was founded on the propogation of information as freely as possible. This means that Web surfing, Usenet threads and email messages are all equally valuable and important, and removing free email services would remove the infrastructure of one of the Internet's most fundamental protocols. Though it is true that many free email users are fly-by-night peculiars such as trolls and paedos, we have to understand that they provide a service not unlike those of coin-operated telephone boxes and stamp-operated postal services, and that vigorously spying on free email users is tantamount to removing phone and mail boxes or tapping them.
Besides, keeping an eye on free email services won't reduce the problem. If child pornographers and spammers are determinted to get their messages through, then they can just use encryption, or the Freenet protocol to make them untraceable - or both, in which case nothing can be done. Public key encryption algorithm implementations such as RSA, DES and AES mean that the police would reqire upwards of 75,000 manhours per email message to discover inappropriate content; despite being impossible, this is still a violation of our privacy rights!
In addition to this, by carrying out these actions the police are effectively saying that ISP and other pay email accounts are in some way superior to free email accounts. While they may be superior, there can be no way of saying that an email from someone using AOL is more reputable than one from fastmail.fm or any other ISP/POP3 provider using open source software. Just because an email provider happents to use UNIX/Linux servers doesn't mean that they are necessarily infested with unsavoury characters; in fact, I have received more unwanted email from large ISPs, IAPs and LAPs than from fleeting servers hidden somewhere on Christmas Island.
I could continue, but I think that with more than a cursory notice the other multitudinous incarnadine problems with this new system become clear, and we must make sure that these plans do not become widespread. Fortunately, they are quite impractical, so a few negative anecdotes should encourage most middle managers in service providers and tech support to avoid implementing it.
I suppose I'll have to become even more subtly incendiary and make some more outlandish statements. Maybe make some vague references to a controversial and topical subject.
"You might want to reconsider
+5, Insightful is the holy grail of all trolls, and I suppose I did achieve it with the minimum of effort. Though ideally I would provide a labyrinth of jumbled and inflammatory concepts as opposed to "simple and clear reasoning".
I guess I'll just sleep on it and see if I can come up with a more effective yet equally pernicious troll next time. Oh, well. Good night.
"Sometimes trolls are right."
I'd rather be King Lear as opposed to his fool.
Hmmph. Maybe I should just post messages calling the MySQL developers 'fagosexuals' or something similar.
Maybe I should've used more abbreviations in the last few sentences. I would've thought that using the abbreviation "BS" in that context would've given me away, but no!
I unintentionally duplicated this comment because my browser was taking too long to post the comment in the first place and I stop/reloaded.
Actually, I'm just trolling.
The open source development model gives tremendous flexibility and leeway for various methodologies such as XP or the more traditional but cumbersome waterfall method, allowing members of a development team to be dropped or added at a moment's notice. With the source readily available, one can become familiar with a project's code before applying to be given access to the CVS or equivalent repository. Gradual accretion may produce code in a style not unlike that of James A. A. Joyce's Ulysses manuscripts, but, like James A. A. Joyce, all of the core developers can easily jump from point to point in the code and comprehend the necessary sections and the C/PHP/Python/Java equivalent of their programmative allusions.
Unfortunately, as a result of this decentralised development system and the reduced usage of traditional ways of programming large-scale projects like WM and RDP due to the geographic dispersion of developers, commercial QA, support and RHQ are not as readily available. I'm a middle manager and my company has had a double-sided experience with the MySQL AB organization. They produce a fine product which is perfect for a medium sized corporation such as the one I work for (which shall remain nameless). MySQL worked very well for us, but unfortunately at one point we started receiving segmentation faults and other similar insidious faults (such as KPs and the like) when there were more than 30 connections to multiple database servers or if a query was greater than 2,048 characters in length. We appreciate that these difficulties can be hard to track down and correct and so our engineers have reported these bugs to MySQL AB but they have not yet fixed them in their latest gamma/production release. However, they have been very polite and are always willing to cooperate with us; even if small portions of the code are not yet fixable and have escaped the relatively poor QA of the EOD, their TOS have always been reasonable and our MD has always been able to CWT regarding the slight problems and make our way around them.
The open source development model allows tremendous flexibility, allowing members of a development team to be dropped or added at a moment's notice. With the source readily available, one can become familiar with a project's code before applying to be given access to the CVS or equivalent repository. Gradual accretion may produce code in a style not unlike that of James A. A. Joyce's Ulysses manuscripts, but, like James A. A. Joyce, all of the core developers can easily jump from point to point in the code and comprehend the necessary sections and the C/PHP/Python/Java equivalent of their allusions.
Unfortunately, as a result of this decentralised development system, commercial QA, support and RHQ are not as readily available. I'm a middle manager and my company has had a double-sided experience with the MySQL AB organization. They produce a fine product which is perfect for a medium sized corporation such as the one I work for (which shall remain nameless). MySQL worked very well for us, but unfortunately at one point we started receiving segmentation faults when there were more than 30 connections or if a query was greater than 2,048 characters in length. We have reported these bugs to MySQL AB but they have not yet fixed them in their latest gamma/production release. However, they have been very polite and are always willing to cooperate with us; even if small portions of the code are not yet fixable and have escaped the relatively poor QA of the EOD, their TOS have always been reasonable and our MD has always been able to CWT regarding the slight problems and BS our way around them.
"Anyone who claims that any Microsoft software is good will quickly be modded to Score:-1."
And anyone who spouts that kind of stereotypical "slashbot" anti-Microsoft bullshit will get modded up Insightful.
And then I'll get slapped with Offtopics and Flamebaits for daring to disagree with the anti-anti-Microsoft zealots. Go ahead and mod me down, it'll just prove my point.
Burn your important bits of paper. Or if you're environmentally friendly, stick 'em in acid. Or you could flush it down the toilet after you tear 'em up. The possibilities are endless. It's easier to get rid of paper data than HDD data, anyway.
It's a story problem.
If a guy with a new cellphone built by my company flies from Chicago travelling west at 800 miles per hour, and the navigation system locks up, and the plane crashes and burns with everyone trapped inside, does my company initiate a recall?
You take the number of phones in the air (A) and multiply it by the probable rate of disaster (B), then multiply the result by the average cost of an out-of-court settlement (C).
A times B times C equals X. This is what it will cost if we don't initiate a recall.
If X is greater than the cost of a recall, we recall the phones and no one gets hurt.
If X is less than the cost of a recall, then we don't recall.
Everywhere I go, there's the burned-up wadded-up shell of a plane waiting for me. I know where all the skeletons are. Consider this my job security.
...but this is my 513th post! This post is the ((2^9)+1)th post of mine! And I still have Excellent karma!
W00T!
Hi Mum!
For another thing, Gnumeric doesn't like viewing CSV data. Why? It's a simple, plaintext format that even gnuplot handles. I'd love to use Gnumeric instead of playing around with OO Calc or something else, but this fact combined with its barely customisable plotting means that I just use LaTeX and gnuplot w/ pslatex to produce charts and graphs for essays and statistics projects.
You're lucky! Back in my day we had 40 people to a console connected to a mainframe by a string seventy miles long! When it got wet one of us had to drive over there and reset the thing! And we had to use a Timex for a screen! I'm still waiting for 'true' to finish!
"Come on.. are we geeks or mice here ?"
Squeak!
"My first thought was to sign the public key with another, use an X.509 certificate or something but the problem is that you can always patch the signature/certificate/checksum/whatever verification mechanism... So what is the solution?"
There is no solution. If someone's got physical access to hardware, all bets are off and there's nothing you can do. The only solution to the problem would be a physical one, such as using superglue to hold the case shut.
"If you know how to read this, you are overeducated."?