Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)N
Posts
7
Comments
278
Joined
2 yr. ago

  • Deleted

    Permanently Deleted

    Jump
  • Wikipedia is quite resilient - you can even put it on a USB drive. As long as you have a free operating system, there will always be ways to access it.

  • Agreed. People just think the first tool that they learned is the easiest to use. I've been a longtime Gimp user and find it pretty easy to do what I want.* The few times someone asked me to do something in Photoshop, I was pretty helpless. Of course, I'm a pretty basic user - I wouldn't dispute that Photoshop is more powerful, but which one is easier to use is very subjective and the vast majority of the time, it just boils down to which one you use more often.

    I've seen the same with people who grew up on Libreoffice and then started smashing their computer when they were asked to use MSOffice.

  • To add to subignition's point, there is a value in learning useful software. More complicated software means that there is a learning curve - so while you are less productive while learning how to use it, once you gain more experience, you ultimately become more productive. On the other hand, if you want the software to be useful to everyone regardless of his level of experience, you ultimately have to eliminate more complex functionality that makes the software more useful.

    Software is increasingly being distilled down to more and more basic elements, and ultimately, I think that means that people are able to get less done with them these days. This is just my opinion, but in general I have seen computer literacy dropping and people's productivity likewise decreasing, at least from what I've observed from the 1990s up until today. Especially at work, the Linux users that I see are much more knowledgeable and productive than Apple users.

  • But without Microsoft’s “PC on every desktop” vision for the '90s, we may not have seen such an increased demand for server infrastructure which is all running the Linux kernel now.

    Debatable, in my opinion. There were lots of other companies trying to build personal computers back in those times (IBM being the most prominent). If Microsoft had never existed (or gone about things in a different way), things would have been different, no doubt, but they would still be very important and popular devices. The business-use aspect alone had a great draw and from there, I suspect that adoption at homes, schools, etc. would still follow in a very strong way.

  • Deleted

    Permanently Deleted

    Jump
  • Whatever. The next generation will have to learn to trust whether the material is true or not by using sources like Wikipedia or books by well-regarded authors.

    The other thing that he doesn't understand (and most "AI" advocates don't either) is that LLMs have nothing to do with facts or information. They're just probabilistic models that pick the next word(s) based on context. Anyone trying to address the facts and information produced by these models is completely missing the point.

  • The handbook is outstanding. Read as much of it as you can. Even if you're not a Void user, you'll learn so much!

    https://docs.voidlinux.org/

  • It's really annoying. It no different from people who go into Linux forums and talk about how much they love Windows.

  • Void Linux uses runit, for example. Here's the documentation they provide on how to use it: https://docs.voidlinux.org/config/services/index.html

    It only takes 5-10 minutes to read and understand how to manage all your services and write your own. Simple and fast. If only systemd were this easy!

  • The lesson learned (in my opinion) is that if you're going to design a language where errors need to be handled explicitly, you need to design the language from the ground up to support monadic error handling syntax. At this point, it seems too late to add it to Golang. What a shame - it could have been so much better of a language without this flaw.

  • This would undoubtedly be wildly unethical, but those people should have been recorded and played back to anyone who refused vaccinations, for any disease really.

  • Ubuntu is doing stupid things with packages, replacing them with their proprietary packaging system (called Snap). It has been controversial, the way that they are pushing it, especially since the Snap server is proprietary and non-open source.

    A lot of people won't consider using Ubuntu at all for this reason alone, and it makes sense - when you consider that there are so many other distros to choose from these days, Ubuntu just doesn't really provide a whole lot of added value anymore.

  • and that the parents were universally obnoxious and resistant.

    Wow, I would have never guessed....

    (/s, obviously)

  • I've seen even worse! Sticky headers with sticky sidebars on both sides. Only about 10-15% of the viewport was left for content. And this is for documentation, so you can only read about 100-200 words at once.

    Why even bother having a webpage at that point. Just make the whole thing a non-interactive .png file.

  • Sticky headers. Unbearably distracting.

    Also, wasted space and a lack of information density.

  • I've said it before and I'll say it again: presidential systems suck. I'm not an expert on Polish politics, but it seems at the very least like the Poles were given a good choice of a candidate. Still, having too many people voting for a single candidate for a single office repeatedly leads to bad outcomes. France, Turkiye, USA - now we can add Poland to the list too.

    Abolish presidencies! Embrace parliamentary systems!

  • 100% agree. But I like posting articles like these because it brings me back to how I learned programming, and Linux specifically - namely by reading a bunch of articles from similar link aggregators and sharing sites.

    My hope is that sharing articles like these is a form of planting the seeds for another cycle for people to learn the way that I did.

  • I just disabled this today and life is so much better. Thanks! Everything works so much better now.

  • There are a lot of other helpful replies in this thread, so I won't add much, but I did find this reference, which you could read if you have a lot of free time. But I particularly liked reading this summary:

    • _start calls the libc __libc_start_main;
    • __libc_start_main calls the executable __libc_csu_init (statically-linked part of the libc);
    • __libc_csu_init calls the executable constructors (and other initialisatios);
    • __libc_start_main calls the executable main();
    • __libc_start_main calls the executable exit().
  • Reserving main is definitely more hacky. Try compiling multiple objects with main defined into a single binary - it won't go well. This can make a lot of testing libraries rather convoluted, since some want to write their own main while others want you to write it because require all kinds of macros or whatever.

    On the other hand, if __name__ == "__main__" very gracefully supports having multiple entrypoints in a single module as well as derivative libraries.