12

Fuck this shitty C ecosystem! Multible compilers, one standard complying, one hacked toghether? Only one GPL poisoned standart library, with no real chance of switching it, which prevents me of making staticly linked programs? And then there is microsofts compiler, with fucking ANSI support. Thanks. No dependency handling. Concurrency? pthreads. Are you fucking kidding. JSON? Have fun finding something static. Compile times where you can read entire books. Segfaults without one helpful info, so you have to debug with prints. And every library, every tool, installer, compiler, stdlib, anything is poisoned by GPL. But hey, its fast. And efficient. After you spend many slow and inefficient months developing something. I am so done with this shit.
Well.

Tommorow i will continue working with C on my backup project.

Did i mention that the stdlib has no features? Not even threading? Which is IN THE STANDARD?

Comments
  • 1
    Ye I know that feeling, tried out C and C++ years ago out. Pain in the arse to make them compile properly without any knowledge (if you have a bug code base). Makefile here makefile there.

    Do you need c? You could try go. Can be used to call native call too.
  • 0
    Do let us know before you shoot yourself. I would love to come to your funeral. Just saying...
  • 0
    @runfrodorun that information would be more palatable without the bragging. You could have condensed it to a single comment, hell maybe even half of one. No one cares how efficient you are, pal.
  • 0
    @runfrodorun My problem is that GCC doesnt really supports switching out the standart library. There is this musl-gcc bullshit, which i tried, but seriously, why is there no --use-this-libc=somelibc flag? I do not like the idea of the gpl, but it is good for some projects. Linux for example. But glibc has gathered a monopoly on linux which just cannot be broken.
  • 0
    @runfrodorun Now your second part: I consider myself as a fairly bright programmer in the journeyman skill level. If you stay within the rules, everything is fine. glibc is fine. I like manpages. GCC/Clang is fine. But its unessesary complicated to break the rules. Using musl. Or use crossplatform threads (with musls C11 threads) I like C. Its fast. I love pointers. But i do not like being forced to use something everytime exactly as someone else wanted.

    Go for example has overcome this problem. Go is fast. Completely static -> no dependencies -> no need for compilations on user side with hundreds of dependencies which cant be linked staticly. And, IMO, the only reason for this is a more permissive LICENSE.
  • 1
    @vortexman100 go has the problem that you can't use shared libraries even if you want to. Try writing a cross platform plugin system with go.
  • 0
    @xxmicloxx fair point. For my usage i am just more a static guy :D
  • 0
    @runfrodorun Thank you very much for your work! I am currently working on a backup program, which has to be portable. My rant was triggered by research about standard compliance. My problem is that i find stuff like "musl-gcc" anoying. It should be easy to just specify another libc. I also read about incompatibilities because of to old glibc's. I think i will switch to something like go in the long run. I think that their standart library + crossplatform + static technique is just better for me.
Add Comment