Why do Japanese programmers suck?

I'm serial guys, why?

Because they don't have imagination, they simly copy ideas from europeens and ameritards.
Not only in programming.

Give some examples of Japanese programmers sucking. Also, in b4 Ruby.

one word, ruby.

>>2
That doesn't really explain it -- the things they copy, they do better.  This is not the case for programs -- Japanese programs are riddled with bugs and incompatibilities.

>>3
Any doujin game.

Japanese are fucktards that's why.

Why do Finnish programmers suck?

I'm serial guys, why?

>>1
>I'm serial guys, why?
Because you're not parallel guys.

Japanese programmers suck because none of them understand english and can't google for help with their programming issues. Thus isolated from documentation and help, they write their crap totally ignorant of any standards or programming guidelines. The resulting code is acceptable to them as long as it sort of runs in Windows with Shift-JIS set as the system character set.

Try running a Japanese program in a non-japanese Windows... and then cry or laugh as it can't even write text on the screen as it's unable to deal with the character sets everyone else uses.

tl;dr: Japanese programmers suck.

The great rule of programming: Write it in English. If you think no one except the speakers of your native language are going to use or modify it, you are either:

- Wrong, and people are going to rewrite it and you're going to get called an idiot for what you did
- Right, and absolutely no one is ever going to use or modify your program, in which case you are pretty safe

>>11
Meaning that if you used a great program written by a Japanese person, you probably never even noticed, just like every other nationality.

>>1
You'll have to give more and better examples of Japanese programmers that demonstrate their kind's suckiness. You can't just keep passing us the bits one at a time.

Have you ever even played any video games? Look at the credits. MY GOD IT'S FULL OF JAPANESE PEOPLE.

>>13

I remember spending ages watching the credits from SONIC THE HEDGEHOG loop around after I completed, reading all these wonderful sounding foreign names.

>>1
Japanese programmers rock, or at least they don't suck. The best videogames ever are Japanese. But they suck at one thing: they still haven't gotten their heads out of their asses and think Japan is all there exists in the world. They write 8-shits C, they're so full of their Shit_JIS. They haven't discovered the world nor Unicode.

>>8
I am an EXPERT PROGRAMMER, and I am Finnish. What the fuck are you talking about!

>>15
EUCJP or die!

>>16
THERE ARE NO EXPERT PROGRAMMERS IN FINLAND.

Because they have to program in English. THAT'S WHY

>>19
YES. English, unlike Finnish, isn't even touring-complete.

I just ordered another copy of SICP

bumpu

ZUN is pretty good.

>>24
He still releases executables compiled in debug mode. That said, looking at the debug strings at least shows that he uses meaningful type names and seems to care about error handling.

Also, c:\cygwin\home\zun\prog\th12\src\core\../core/zunlib.h.

He still releases executables compiled in debug mode.
I can't believe I just wrote that. It's utterly false.

>>26
I haven't looked at the latest, but he did release executables with some custom debugging info. Executable itself seemed to have been optimized properly (debug mode by default uses little to no optimizations). It was probably be cause he used to use a mix of Intel's ICC and MSVC. I'd have to look at the latest executable to see what he's using now - if that path is an indication it would be gcc, but that would be a strange choice on Windows at least (it's fine, but optimization's worse than MSVC and ICC, and given that he cared enough to use ICC, why move to GCC?)

>>27
Are you sure GCC's optimizations are worse than MSVC and ICC? GCC has gotten way better in the past few years and it now has whole-program optimization. IIRC it generates code of the same quality as ICC.

>>28
GCC has gotten way better
0/10

There's nothing wrong with releasing libraries compiled with debug information.

I work at a Japanese company and they really are pretty bad mostly because they never admit mistakes, waste time always consulting with one another and usually go with the "safest" lowest common denominator solution.

one word bicoin

>>29
GCC is well known as being terrible. It might beat Intel's on AMD, but that's more because Intel has gotten better at pessimising AMD performance than anything GCC has done.

There is no relevant performance difference between GCC, ICC or VCC.

>>34
Define `relevant'.

>>35
#define RELEVANT

>>36
Thanks.

http://code.google.com/p/kene-touhou-mohofu/source/browse/trunk/src/game_core/douchu/game_clear.c
#define YUYUKO_PASSWORD     "TABERARENAINO9"
#define CIRNO_PASSWORD        "CIRNO9PASSWORD"
#define REMILIA_PASSWORD    "RUMIAISMYBRIDE"
EXPERT TOUHOU SECONDARYFRIENDSHIP PROGRAMMING!!

>>1 makes a good point. While Japanese videogames for consoles are usually of superb quality, anything they do for PCs (which, in Japan, means Windows) tends to never work outside the developer's machine, is full of bugs and generally awful technology; Bangalore quality. And of course, it's in Japanese. Among the 127 million Japanese there must be about as many English speakers as in the average Russian household.

Part, though by no means most, of the insanity, comes from the fact they haven't ever heard of Unicode and write Shit_JIS Windows bullshit. Since Windows is a toy OS, software written and compiled in one country won't run properly in another (this is actually an ameritard business strategy: others are divided, while their ASCII shit runs everywhere because everything is backwards-compatible with ASCII).

And of course, while every Japanese person knows about ass eels, nobody ever heard of free software, the GNU Project, Linux, UNIX, or anything of the sort over there. They only use amerifag corporation bullshit.

When the fuck did we get IDs and why don't the other threads have them?