java

does anyone know of a decent IRC channel for java noobs? not ##java on freenode. full of elitist pricks who would rather not help with anything. thanks!

does anyone know of a decent board for IRC channel noobs? not prog on 4chan. full of elitist pricks who would rather not help with anything. thanks!

i see what you did there >>2

Did you try #getout

did YOU try #shutthefuckupfaggot?

/prog/ is not a board for beginners. If you asked your question on /pr/ or Reddit or Stack Overflow, you might get a better reply to your question.

>>6
people HAVE been replying, its just that you guys are as big of faggot asshole elitists as ##java.

>>7
Rather bigger, I think you'll find. We aren't oblivious enough to think Java is a language worth using.
The fact that you think elitism is a bad thing shows that you'd be more at home on /pr/, with the rest of the morons who puff themselves up with self-righteous indignation when their ineptitude is pointed out.

When you're asking trivial programming questions online of various BBS'es, forums, channels, you're just showing your unwillingness to read the proper documentation and books and experiment with the implementations available, as well as possibly read their source code. It should be obvious why this behaviour is undesirable of a programmer, as a programmer will spend a lot of his time doing some of those things, and if one cannot do it, one cannot be a good programmer. From a different perspective, one can view such actions in a light similar to how an average computer user views a silly newbie who cannot understand a self-describing (supposedly) noob-proof GUI on Windows, or someone who cannot read a manpage on *nix - another kind of such type of programmer is one which is given descriptive error messages and they just CANNOT read it, until you shove the damn message in their face, or read it out loud for them, until it hits them what it says.

If you still have programming questions which do not concern those matters, and cannot be solved by reading SICP, you may ask for help.

While my words may have been a bit harsh, and I do not have problems with people asking for help on the Internet, or doing such things myself (which I rarely do, but I still do them sometimes, usually on things which will shape a possibly larger program to come, when a bad decision will cost many lines of code which will need rewritten), one should only ask questions which cannot be trivially answered by looking things up or reading a few well-known books, reading/searching the source code, or just trying things out in an implementation.

>>9
op here and i understand your point and view on the matter, but you are implying that supposed questions i may have are not because i havent fiddled around with the code myself and tried to come up with the correct way to write said code.

>>8
the problem is elitists act like they were never in a position where they were noobies at one point in their lives, therefore, making them gigantic faggots.

me and the java crew could roll by butt fuck if we up for that

>>10
``Elitists'' will respond in a negative manner if you haven't, and since you called them that way, I assumed you just approached them without having done those things.

I don't use use or write much Java, nor do I go to ##java, so I don't actually know what goes on in there, but I do go to #lisp and sometimes ##c, and the folks there have been helpful, but I never asked them any trivial questions. I've seen newbies ask trivial questions only to be treated badly, or pointed at the appropriate introductory text (as they should have been).

>>11
Most of them weren't the obnoxious entitled fucktard that you are when they were starting out. It's possible to be a beginner without also being a moron. They (and we) know this, so they (and we) won't let you get away with it.

>>14
youre implying things that you dont know about - not once have i mentioned anything worthy enough to label me as an "obnoxious entitled fucktard." fuck off.

>>15
implying that I should go back to the imageboards

>>15
You're the dickbutt who types in lowercase, argues with everyone and takes a big shit on every thread that would be otherwise decent.
Fuck off.

>>16
You're the dickbutt who comes from the imageboards. I'll make a deal with you, if you can make >>15 leave, you can stay. Otherwise, fuck off with you too.

>>15
I strongly beg to differ.

>>17
every thread? ive only posted in THIS thread. fuck off.

>>17
ill leave on my own, considering ive found no help at all.

i hope all of you enjoy coding into the wee hours of the morning ignoring whatever pussy you may have a chance at getting.

>>20
And nothing of value was lost.

>>9
If you're going to be pedantic you might not want to use AMAZINGLY HUGE RUN ON SENTENCES.

>>22
I don't think you know what ``pedantic'' means. Additionally, long sentences are just fine, and what constitutes a run-on sentence is purely subjective. As long as it's grammatically sound, a sentence should be allowed to run on for pages and pages, if the message requires it. The Romans realised this; why don't you?

I'll make you a deal >>1-san. I'll answer every question about Java you have for the foreseeable future, on the condition that you:
A) Post in this thread and this thread only, you are not to use the rest of the BBS.
B) Any post you make in this thread will have the email "sage".

I look forward to your questions and trust that this matter is now resolved.

>>19
And yet, you're arguing.

>>23
Let me use an example:

What you wrote:

While my words may have been a bit harsh, and I do not have problems with people asking for help on the Internet, or doing such things myself (which I rarely do, but I still do them sometimes, usually on things which will shape a possibly larger program to come, when a bad decision will cost many lines of code which will need rewritten), one should only ask questions which cannot be trivially answered by looking things up or reading a few well-known books, reading/searching the source code, or just trying things out in an implementation.

Almost the same thing, using more than one sentence:

While my words might be a bit harsh, I don't have problems with people asking for help on the internet.  I rarely do it myself, usually for decisions that will shape the future of a large program (where a mistake would mean many lines of code would need to be rewritten).  One should only ask others questions that can't be answered just by looking things up, reading a few well-known books, reading/searching the source code, or trying things out in an implementation.

What I would write:

You shouldn't ask other people questions that you can answer yourself with just a little bit of work.  If it's difficult for you to learn by reading the documentation, practice doing it anyway because it is a basic (and essential) programming skill.

>a sentence should be allowed to run on for pages and pages, if the message requires it
I'm not sure what sort of message requires sentences that go on for pages, considering that pretty much every important work in the English language has managed to avoid using them.

There is a popular book among writers called the "The Elements of Style" that describes in detail what makes sentences good or bad, beyond wether they are grammatically correct or not, that I should probably get around to reading myself one day.  You might want to check it out.

PS I don't disagree with your point though, I'm not sure if I've ever asked a programming question on an IRC channel or on a mailing list and I've been doing commercial software development for years.

full of elitist pricks who would rather not help with anything. thanks!

sounds like /prog/

>>26
/prog/ - Not Programming

>>26
I only had one post in this thread and that post was >>9.
You incorrectly assumed I was >>23. I decided not to argue about my English as
  1) I wrote the post in haste, without bothering to edit it.
  2) My english isn't perfect, and it's not one of my first languages.

Anyway, thanks for the English tips. "The Elements of Style" sounds like a book that I should read someday when time allows.

>>26
Nice improvements, but do strip the parentheses; they're unnecessary in this case, and perhaps even detrimental. Remember that parentheses should mark asides, where the text contained could be skipped without affecting the message. In both of your cases, the parenthetical text connects directly with the rest of the sentence and serves to enforce your point.

Enjoy your AIDS AND FAIL, /prog/

Enjoy your AIDS AND FAIL, /prog/