Why C and C++ are Awful Programming Languages

submitted by [deleted] from radford.edu

all 15 comments
sorted by:
top
newinsightfulfun

[–][deleted] 2 insightful - 3 fun2 insightful - 2 fun3 insightful - 3 fun -  (17 children)

Why this is a terrible website

But, for real though, was this website made before CSS became a thing?

[–]madcow-5 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (1 child)

There's no stylesheet or CSS on it, that's raw html. My guess is it's intentional, or being hyper engineer-brained, the author doesn't see styling the article as necessary.

[–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

I always take the time to write, at the very least, a basic stylesheet. A margin could really improve the article, at least in my opinion.

[–][deleted]  (14 children)

[deleted]

    [–]madcow-5 2 insightful - 2 fun2 insightful - 1 fun3 insightful - 2 fun -  (1 child)

    There's zero CSS. You're looking at blank html.

    [–][deleted] 1 insightful - 2 fun1 insightful - 1 fun2 insightful - 2 fun -  (11 children)

    They could've at least used a margin so the text wasn't squished against the edge of the screen.

    [–][deleted]  (4 children)

    [deleted]

      [–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (3 children)

      You don't need a CSS file. Just add a style property to the body tag and give it a margin.

      [–][deleted]  (2 children)

      [deleted]

        [–][deleted] 1 insightful - 2 fun1 insightful - 1 fun2 insightful - 2 fun -  (1 child)

        Yeah, but in the situation it would work, if you just want a margin on your body.

        [–]bobbobbybob 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (5 children)

        It isn't squished, there's at least 8px

        [–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (4 children)

        Ah, yes, a whole eight pixels, that's a loooooot of pixels...

        [–]bobbobbybob 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (3 children)

        its is infinitely times more than 0

        [–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (2 children)

        Technically it's undefined times more than zero, because in order to get how many times larger so'm is: you need to be able to divide the larger number by the smaller number, and dividing by zero is impossible, and will return undefined.

        You can check this by adding zero over and over; you'll never reach eight because zero plus zero is always equal to zero. Even infinity is not enough, because any number that is multiplied by zero returns zero — even infinity.

        [–]bobbobbybob 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (1 child)

        division by zero z/0 for z in C*!=0 in the extended complex plane C-* is defined to be a quantity known as complex infinity. This definition expresses the fact that, for z!=0, lim_(w->0)z/w=infty (i.e., complex infinity)

        Also

        if you use differential mathematics, you see that the limit of 1/x approaches infinity as x approaches 0

        so excuse me if I don't "check this" by adding things together.

        [–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

        My calculator can't do none of that shit, so I'll just pretend it doesn't exist.

        [–]zyxzevn 1 insightful - 2 fun1 insightful - 1 fun2 insightful - 2 fun -  (1 child)

        It was designed with the "bad is good" principle. The idea that, if it works for most of the time, it is ok.
        So, it is not designed to work all of the time. Or at least with a well defined sub-set.

        From the low level, the problem is that everything is cast to an integer. Like one that fits in a register.
        So a character is an integer, a boolean is an integer, any address is an integer. Etc. And this is usually not true on low level.

        Another problem is the mixing of statements and expressions. Like "ptr++".
        This becomes unpredictable with: "(p==(++p))?p++!p--)"

        But by mixing integers and addresses made it possible to make complicated memory structures. Like: "value= Tensor[row4+ column+ depth16+ plane*64].imaginary"

        So the memory is complicated by default, including memory management.

        [–]bobbobbybob 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (0 children)

        I must confess to abusing the fuck out of C to get it to do fancy multidimensional math in tiny amounts of memory, reducing paging as much as possible (rooms full of RAID to get fastest non-volatile paging possible for the big data sets we were using in the 90's)