9
NACK
13d

Learning parallelization in C and then going to java is literally hell

Comments
  • 3
    Been there, done that, it was actually fun.
  • 2
    @netikras I never thought I would miss using pointers
  • 2
    Multithreading in C is awful.
    In assembly it's hell. Or something worse than hell.

    In Java by comparison, it's like eating your favorite cupcake.
  • 3
    @Root there there.. It's not that bad [C] :)
  • 1
    @netikras Ehhhh.

    My second language with z80 Assembly, and even multithreading in C can be better than some of that. Still not something I'd build for fun, though. So it could absolutely be worse.
  • 1
    Wasn't parallelization in C the reason that Mozilla gave up 3 times when trying to implement parallel processing of CSS? They seem to have managed it with Rust in their new Servo browser.
  • 1
    The Javanese people are probably pissed that you think their country is hell
  • 3
    Could be worse: could have been Python.
  • 0
    well i always found java dead simple compared to c concerning parrallelization.
    if you know the libraries and utilities for it that is...
  • 1
    @halfflat python is fiiiine, just spawn several instances of python as separate processes.

    Joking aside, WSGI on Python handles concurrency fairly decently. It is useful enough to be used by Discord for their user and bot HTTP API. (Discord use Erlang for their websocket gateway and Flask on Python w/ WSGI for the HTTP API iirc)
  • 1
    let me take this completely out of context:

    "java is literally hell" - pedrosuoza
  • 0
    @nekokatt Managing the GIL from the C/C++ extension side of things is a right pain, even with pybind11. And of course, it kills performance if you're calling back into Python.
  • 0
    @halfflat that is why you dont use python for performance critical code :)
  • 0
    @Root Multithreading in C and C++ makes perfect sense if you think lower level. You're constrained a lot more, but you can finish your tasks much faster with much less overhead
  • 0
    It's not that hard in C as you can literally do wathever the fuck you want 😉
    Other languages are restrictive in comparison
  • 0
    @Noorquacker My second language was assembly 😋 that's how I think about everything.
  • 0
    @halfflat yeah, I recall it was more restrictive in py than C, just don't remember how.. Tried it 4 or 5 years ago, but I very well remember that all sources suggested using pthread and its implementation was poorer than in C :/
Add Comment