FUCKING JAVA

Now, I have to write a crossword solver using Java for an AI class - no problem, right?
...until you factor in FUCKING JAVA.

First, I created an arraylist of constraint objects - now there are only 16 of them on the example I'm running, and it just holds something like four integers. Then I get OUT OF HEAP MEMORY or some gay shit error like that, after swearing at the automatic garbage collection and calling it manually I saw that it didn't help, and then I thought I shouldn't have used a faggy arraylist in the first place - so I make an array.

I use a set of 36 to ensure it fits but I get an out of bounds index error
huh
I increase array size to 90
same error
reduce to 17
same error

WHAT THE FUCK

JAVA SHOULD DIE IN A FUCKING FIRE

>>30
Obviously I would rather code in C. But the 'extreme example' you anticipate is exactly what I'm on about. The 'extreme' part is important -- writing a C compiler in brainfuck solves the general problem of implementing another programming language and in that sense the abstraction, as I've put up, is not excessive.

The deal with abstractions is that, as you say, different languages have different abstractions in their immediate grasp. Many of these are language features, many are library features (and in some cases this distinction is greatly artificial.) Procedural languages (especially the assemblers) tend to come from the point of view of operating a machine--which is in fact the case. Functional and other types begin to depart from this, but few of them do so convincingly in my opinion.

Unless you want to use a Perl, there's always a massive area that requires you to write abstractions. The size of the abstraction you have to write is rarely very large compared to the problem you will solve with it, unless you think you need to implement a full C compiler because you're not really a brainfuck programmer at all. That isn't the proper abstraction for one, and if you're not good with the language in question replacing the one you do with it, just because it has more to say explicitly about the problem (preconceptions and all!) is just about the worst idea you could really come up with.

So to restate, every good programmer who is good with C knows that switching to any other language because C is 'dangerous' or 'takes too long' to code in is complete bullshit. Same goes for just about everything else out there, including brainfuck.

>>31
lurkmoar