Announcement

Collapse
No announcement yet.

systemd Clocks In At More Than 1.2 Million Lines

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • pracedru
    replied
    Great..
    I really like systemd. Works great in my opinion.

    Leave a comment:


  • Volta
    replied
    Thanks God systemD exists. SysV init was utter crap.

    Leave a comment:


  • whitecat
    replied
    Originally posted by ThiagoCMC View Post
    I'm serious, really, systemd sucks. It's not even close to being a production ready piece of software.

    I used (Slackware 96) Debian from ~1998 to ~2006 and Ubuntu from ~2006 to this day (2019).

    Some other day a few weeks ago, for the first time in ~20 years, I had to reinstall Ubuntu (a Linux distro) because I could not `ping google.com` and I didn't know what to do to fix it!!! :-O

    I disabled systemd-resolved and added my own `nameserver 8.8.8.8` line within my new /etc/resolv.conf empty file, and it still didn't work!

    Of course, `ping 8.8.8.8` was fine. But `ping google.com` wasn't.

    Solution?
    If you tried to troubleshoot a bit you had find that you request was locked in multicast dns and not even reaching your dns solver.

    This is an integration issue:
    https://bugs.launchpad.net/ubuntu/+s...ahi/+bug/94940

    Leave a comment:


  • speculatrix
    replied
    1.2Mloc?
    that's bigger than the huge kdelibs library
    https://www.openhub.net/p/kdelibs

    Leave a comment:


  • cb88
    replied
    Originally posted by oiaohm View Post

    Fork to C++ hmm someone is kind of missing a major problem.
    https://en.wikipedia.org/wiki/List_o...dings_for_Qt_5
    https://en.wikipedia.org/wiki/List_o...ndings_for_GTK

    Most people miss due to being a C based GUI define GTK has more language bindings.

    C++ is not really suitable if you are wanting lots programming language binding. Yes mesa with opengl might using C++ inside but the opengl bindings are in fact C.

    C as a language has a stable ABI in built binaries. C++ standard does not define a ABI for classes and the like instead leaves it to every single compiler todo what they see fit.

    Horrible reality you want C++ version of gtk with the means to provide same level of language bindings as GTK does now you will end up still using gObject basically exactly how it is now.

    Maybe port gtk core code to Vala.
    Thankfully LLVM and GCC seem to be doing better at this... and LLVM can even pretend to be MSVC++

    Leave a comment:


  • Britoid
    replied
    Nice.

    I just started playing around with systemd-nspawn and it's pretty amazing.

    Leave a comment:


  • oiaohm
    replied
    Originally posted by Bsdisbetter View Post
    Horses for courses. I don't have a problem with the way gObject is implemented. I guess it comes down to it started out in C (probably because that's what the developers knew) and perhaps outgrew itself.
    I'm sure you can fork it off and start a c++ port...
    Fork to C++ hmm someone is kind of missing a major problem.
    https://en.wikipedia.org/wiki/List_o...dings_for_Qt_5
    https://en.wikipedia.org/wiki/List_o...ndings_for_GTK

    Most people miss due to being a C based GUI define GTK has more language bindings.

    C++ is not really suitable if you are wanting lots programming language binding. Yes mesa with opengl might using C++ inside but the opengl bindings are in fact C.

    C as a language has a stable ABI in built binaries. C++ standard does not define a ABI for classes and the like instead leaves it to every single compiler todo what they see fit.

    Horrible reality you want C++ version of gtk with the means to provide same level of language bindings as GTK does now you will end up still using gObject basically exactly how it is now.

    Maybe port gtk core code to Vala.

    Leave a comment:


  • oiaohm
    replied
    Originally posted by Cape View Post
    Making GTK in C was a mistake. You need more tools to manage memory when you bring in advanced GUIs and especially when you need to pass around weird big data structures.
    Its not that straight forwards. C has defined calling standard. C++ does not. Job went object c because they believed that would be better.

    The hard reality there is not a good programming language for writing GUI. Every language you choose you have historically had to compromise something.


    Leave a comment:


  • Bsdisbetter
    replied
    Originally posted by microcode View Post
    Thank you Lennart, I really appreciate this thing, ignore the haters, listen to the genuine critics.
    Those that agree with him.

    Leave a comment:


  • Bsdisbetter
    replied
    Originally posted by Cape View Post

    SO MUCH THIS!
    Making GTK in C was a mistake. You need more tools to manage memory when you bring in advanced GUIs and especially when you need to pass around weird big data structures.
    ??tools?? ??advanced GUIs??? ???? A data structure is just an address in memory. You 'pass around' using pointers.

    Leave a comment:

Working...
X