Considered harmful

Post technologies and techniques considered harmful, with a very short explanation/tag on why.

- Non-Unicode anything (charset hell, no support for some characters, exploitable, Americans and Japanese don't give a shit, etc.)
- C char type (signed, gives the false impression of being a character)
- Locales (hell, ambiguous, problematic, Americans don't give a shit, lack of standard)
- COBOL (shitty)
- Java (shitty)
- Current shell scripting (shitty)
- Goto (spaghetti code)
- Null-terminated strings (inefficient, non-binary)
- Variables with default value (i.e. read before assignment/definition yields null or some crap)
- Automatic string-int conversion (1+"1"=shit)
- PHP register globals and magic quotes
- Non-nesting quotes like " (quote escape hell, as opposed to Perl's q{}, q(), etc.)
- Lack of functions (as in Java, sometimes you need them)
- C standard library (OH EXPLOITABLE!)
- Obsessive generalization and overengineering (Java API: unusable, unproductive)
- XML obsession (people believe it works automagically, verbose, inefficient)
- FHS (shitty mess, can't manage applications, non-relocable, no several versions of applications)
- Windows Registry (shitty mess, hard to manage and repair, ugly)
- "Different on purpose" attitude in some GNAA projects (different from the good things too)
- Compile obsession (waste of time just to suck Richard Stallman's cock)
- Win32 API (NULL, NULL, NULL, hwnd, lpszLabel, ssdSecurityDescriptor)
- Lack of net neutrality (corporate fags, shitty Internet for everyone)
- Email (shitty naive protocol, best for spam, poor specs, can't be fixed)
- FTP (shitty protocol, control/data connection insanity, active/passive insanity, braindamaged send IP in protocol fucks with NAT)
- H.323 (braindamaged send IP in protocol fucks with NAT)
- MSIE (world exploit me, broken everything)
- Windows Vista (DRM OS, wasteful, shitty)
- DRM (shit, braindamaged)
- Media corporations (shit)
- HD-DVD (DRM)
- Blu-ray (DRM)
- Windows Media (DRM)
- iTunes (DRM)
- Software patents (American shit)
- Lawyers (no need to explain why)
- SCO (lawyers)

UNIX (unless your time is worthless)

Python-One word, the forced indentation of code. Thread over.

>>2 is an idiot

>>1 :
>- C standard library (OH EXPLOITABLE!)
but that's good for us :D

>- Goto (spaghetti code)
i think that goto is faster than a while(1) since goto doesn't compare anything just jmp's str8 away.

>- Win32 API (NULL, NULL, NULL, hwnd, lpszLabel, ssdSecurityDescriptor)
oh i agree. but who cares about windows

>- Automatic string-int conversion (1+"1"=shit)
those are languages for pussies.


>- Lack of functions (as in Java, sometimes you need them)
Write your own then. Don't expect a library for every thing you have in your mind

COBOL ? who the fuck uses cobol?
Java ? who the fuck likes java?


As for my 2 cents, i'd say

Web server side languages - Because they all suck
Ruby - because its syntax is awful
Perl fags - because they think that small code equals to speed
Vista - because it's the worst mistake in the history of computarz
Vista - oh, wait.

>>3
Forced memes considered harmful

>>4
but that's good for us :D
hello im fairX the haxxor join my community of hackers if you payme enough i will give you access to a private area of haxx ;) http://forum.curse-x.com/index.php

i think that goto is faster than a while(1) since goto doesn't compare anything just jmp's str8 away.
What do you think while(1) gets compiled to?

oh i agree. but who cares about windows
I do. Lots of idiots use it. That's why it's harmful.

those are languages for pussies.
Automatic string-int conversion (Perl, PHP, JavaScript...) is thus considered harmful.

Write your own then. Don't expect a library for every thing you have in your mind
Ew. Lack of functions in a language. Java does not have functions.

COBOL ? who the fuck uses cobol?
Thousands upon thousands of banks who need constant maintenance and expansion of their shitty old COBOL shit. COBOL is still one of the most used languages today. Only that the ones who have to write COBOL to eat are too ashamed to talk about it. It's taboo.

Java ? who the fuck likes java?
Nobody. But being liked or not, I consider it harmful.

Web server side languages - Because they all suck
You considered harmful. Please learn and understand what you talk about before you do.

Ruby - because its syntax is awful
Not as bad as Perl. And even if Ruby could have been much, much cleaner, I don't consider it harmful for that.

Mostly agreed, but.

C's char type is perfectly good, long as you remember that C originates from the "ASCII, bitch, do you know it?" era. There's wchar_t for unicode, and even then you have to take combining characters into account so it's not like you can skip characters with a fixed stride.

Locales in the sense of "ooh this timestamp looks like the second of march, or is it the third of february?" are fucking stupid. Everyone ought to go with ISO recommendations, like 2007-03-15 15:38 and so on. Localization in the sense of translating programs from one language to another is good good good.

Gotos are good in C for primitive error handling. I.e. if you limit them to branch forward only and so that you never goto into another scope from outside.

Null-terminated strings is just the way it is. If you learn to deal with them, it'll be far less trouble than feeling like someone is ramming a baseball bat sideways up your bum all the time. Deal with it, or use a different language and deal with its idiosyncrasies; there's no escape.

Variables having default values is perfectly OK, but there should be a compiler warning when they are used as such. Explicit initialization is good, except where it's not needed and would mislead the reader; all code should be written to be read by people first and by compilers second.

Perl's special quote operators have major issues of their own. You've perhaps heard that the only thing that can parse Perl is Perl itself.

GNU's quite OK. The original Unix tools were written before computers had several megabytes of memory for each user, so GNU's taking a different approach to some things is entirely cool. Plus, no son of SCO on the userspace toolchain.

Richard Stallman is a LISP dude first and foremost. I heard most of his hacking today is done in Emacs Lisp. Griping about compile obsession in connection to him is strange, given that Lisp is basically the ur-dynamic runtime language. Indeed, the various Lisp environments show how to do dynamic runtimes right, unlike Java (256 megs to run Azureus? What the butt?) and C#.

E-mail might be shitty, but its shittiness is manageable. And as you said it can't be fixed, which includes replacing it all at once.

>>OP
Goto? Null Terminated Strings? WTF. These are the basics of machine level programming, without them there are no computers. Like saying the x86 prosessor should be considered harmful.

The world is complex, chaotic and doesn't work the way you want it to. It doesn't matter how secure something is made: anything can be hacked, cracked and disassembled. That is the core functionality of the IBM-architecture computer, but also it's downfall.

>>1 is a core user of /prog/.  He's the one with all the opinions fagging up all the threads.

>>7
x86 is one of the shittiest instruction sets evar.

>>9
Well it was a good replacement for the Z80. Back in, oh, 1977. Remember those times? 8 bits per register and 16-bit addressing. Joy!

- PHP (makes insecure things easy and easy things hard, all while making people think they are still easy; a horrible mess in general)
- C as a general-purpose programming language (it isn't)
- C++ (solution to a made-up problem)
- Lack of garbage collection (unless you consider memory leaks a feature)
- Lack of type inference in statically typed languages (we're not living in the 70s anymore)

>>1

Win

>>11

Lose, Different shuoves for eating different kinds of food are good.

>>7
Hay yu ar talkin bout sum assebly and muchine code! I dunno if e'reywun or OP els is doh

>>9

All assembly brances around and gotos, even motorola's 68k and like architectures, its all memory location hopping, cant get by without it.

BTW, processors do not need to be the gatekeeper for security, they are giant calculators and their ONLY job is to do what they are told. If its in the machine, its exploitable, cold hard fact of life, wont change either.

>>8

He seems to know his shiznit though.

>>11
Memory leaks are a bug. All bugs are introduced by the programmer. If you cannot write C without making memory leak bugs, then perhaps you should take up washing your mouth with buckshort in the evening.

>>13
Why crawl on the floor using C when you can ride a porsche with PYTHON?

>>14

Not everyone wants to use a zillion megabytes of memory, you know.

- Lack of functions (as in Java, sometimes you need them)

declare a method as static, as in public static void myMethod() and you have a function. (Use: Classname.myMethod(); )

>>14

Allowing memory leaks is a gateway habit. Next you'll be complaining about the forced indentation of code. It can only go down hill from there.

- Haskell, because it allows mathematicians to fiddle with programming, without having any proper programming background.

Win32 API (NULL, NULL, NULL, hwnd, lpszLabel, ssdSecurityDescriptor)
More like HWND _hwnd = CreateWindow(NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL);

>>16
It's not a function unless I can pass it as the argument to another function.

>>20
In before someone responds to this with an inane inner class hack.

>>21
NO INNER CLASSES HERE

interface vvfuncptr {
    public void func();
}

class func1_ implements vvfuncptr {
    public void func() {
        // ...
        System.out.println("func1");
    }
}
class func2_ implements vvfuncptr {
    public void func() {       
        // ...
        System.out.println("func2");
    }
}
// ...
class funcn_ implements vvfuncptr {
    public void func() {
        // ...
        System.out.println("funcn");
    }
}

class myfunclib {
    public static func1_ func1 = new func1_();
    public static func2_ func2 = new func2_();
    // ...
    public static funcn_ funcn = new funcn_();
   
    public static void doit(vvfuncptr callback) {
        // ...
        callback.func();
        // ...
    }
}

class go {   
    public static void main(String args[]) {
        myfunclib.doit(myfunclib.func1);
        myfunclib.doit(myfunclib.func2);
        System.out.println("...");
        myfunclib.doit(myfunclib.funcn);
    }
}
output:

func1
func2
...
funcn

- Opera (www.opera.com)

>>7
Null Terminated Strings? WTF. These are the basics of machine level programming,
helo i hav nevar heard of rep movs* lol

Null-terminated strings are a relic of the PDP-11, chump. In x86 a better way to do it is move a count into (e)cx and proceed from there. While you can certainly check every byte if it's 0, like C-style strings, it's a lot slower.

So no, null-terminated strings aren't some requirement of "machine level programming". Get a clue next time, okay?

- Non-Unicode anything RULES (8 bits per character saves space!)
- C char type RULES (characters are SUPPOSED TO BE 8 BITS)
- Locales (illusion of care better than out and out saying I don't care)
- COBOL RULES (Very readable.)
- Java RULES (Cross-platform)
- Current shell scripting RULES (IT'S A SHELL NOT A PROGRAMMING LANGUAGE, GO SUCK POWERSHELL'S BALLS NIGGER)
- Goto RULES (sidesteps stack exploits)
- Null-terminated strings RULES (ANYTHING ELSE MIGHT BE INTERNALLY INCONSISTENT, i.e. stated length does not match actual length)
- Variables with default value RULES (one less statement I have to write)
- Automatic string-int conversion RULES (um, we use text-based data sometimes)
- PHP register globals and magic quotes RULES (i'm sure, haven't tried but i'm sure they rule)
- Non-nesting quotes like " RULES (they do!)
- Lack of functions RULES (stop programming like it's 1969)
- C standard library RULES (it's standard!)
- Obsessive generalization and overengineering RULES (helps economy)
- XML obsession RULES (pretty soon all data in world can be parsed with xml - I am a nazi)
- FHS RULES (SHORT NAMES and RUNNING MORE THAN ONE VERSION OF SHIT IS STUPID)
- Windows Registry RULES (<- Sorry, I can't even PRETEND to like the registry)
- "Different on purpose" attitude in some GNAA projects RULES (this is the fault of copyright and patent law)
- Compile obsession RULES (CFLAGS JUST KICKED IN YO)
- Win32 API RULES (What better way to force insecure applications on the public and open them up to vulnerabilites.  Not on my system though)
- Lack of net neutrality RULES (Turning the Internet into a big jewish controlled digital TV network is FUCK AWESOME if you're jewish like me)
- Email RULES (i like sending bulk messages)
- FTP RULES (dual channels help counter connection hijacking)
- H.323 RULES (NAT sucks)
- MSIE RULES (90% of world uses it)
- Windows Vista RULES (I like how the Autoplay function is in the Control panel now.)
- DRM RULES (Why should I have control over my own computer.  I clearly don't know what I'm doing)
- Media corporations RULES (WAR IS PEACE)
- HD-DVD RULES (15GB AND GTFO)
- Blu-ray RULES (30GB AND GTFO)
- Windows Media RULES (WMP11 looks awesome!)
- iTunes RULES (So easy to use!)
- Software patents RULES (Litigation is fuck win, make money and do no work)
- Lawyers RULES (Being productive is overrated)
- SCO RULES (Their UNIX is the best)

>>6
C's char type is perfectly good
I know, I was just being picky. I run the Unicode inquisition.

I see goto as a way to break from several nested looks when major shit happened, for the lack of break n.

I've been dealing with null-terminated strings for a long time, it's just that I consider them harmful.

Perl's special quote operators can be parsed with recursive regex more easily than single quotes with escape characters can.

The "suck Richard Stallman's cock" thing was an attempt to be humorous at pointing out GNU is tabliban about compiling; some of its people going as far as making a difference between sources and compiled form of freaking interpreted languages.

>>7
Goto is considered harmful in languages implementing loops, break and continue (and preferrably the modern goto: exceptions). As for null-terminated strings, no, they are not the basic of anything. Just one of the simplest ways to do it, and a bad one.

>>25
Lol

>>26
GOTOs are good only when jumping to error handling code in C. Getting out of nested loops using only break is not fun! Pretty much everywhere else they're either being used by ASM programmers or premature optimizers.

GET OUT JAPFAG

What?

The algorithm to generate add revenue not.

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boyAll work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boyAll work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boyAll work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boyAll work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boyAll work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boyAll work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

All work and no play makes Jack a dull boy

op (sucks cock)

>>11
java or c sharp babby detected

Sure where a lot of foolish people on here with a freakish obsession of programming.

I think I posted in this thread.

GC considered harmful.

GC is shit.

>people wanting to make video games but not even knowing what they want to make once they have the knowledge to make it

These people should just gtfo the video game industry and be code monkey slaves that work on boring stuff.

Bringing /prog/ back to its people
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy