“Falsehood flies, and truth comes limping after it, so that when men come to be undeceived, it is too late; the jest is over, and the tale hath had its effect: […] like a physician, who hath found out an infallible medicine, after the patient is dead.” —Jonathan Swift

  • 15 Posts
  • 242 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2024

help-circle
  • I would honestly recommend against Ubuntu. I had the same issue: tried Ubuntu because it’s “the beginner distro”, and it turns out it wasn’t that at all. Ubuntu for me was a cobbled-together piece of shit with a terrible UI, corporate enshittification, and a major breakage around every corner. After a while dual-booting on my laptop, it started taking ~4 minutes to boot into it. Windows, meanwhile, was taking about 30 seconds. It also nuked my config twice, so everything I’d set up to mitigate Ubuntu’s default “person who designed this just had their eyes dilated” trash was undone. I quit Linux for years before giving it another try, because if this broken trainwreck was the “beginner” experience, why would I want to go further?

    If you want KDE (which I think is the best DE and it’s not even a little close), I think you’ll find a nicer experience in something like Fedora. Fuck, I think you’d experience less maintenance burden with something like CachyOS, although please don’t treat that as a recommendation. I use EndeavourOS now, and I would genuinely go out and buy a macOS device if my only Linux distro option were Ubuntu (that’s not high praise of macOS) on the grounds that it’s such a poorly designed hunk of dogshit.









  • TheTechnician27@lemmy.worldtoFediverse memes@feddit.ukPieFed be like
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    13 days ago

    I’m surprised you put C in there. Its limited vocabulary does mean you don’t have to deal with e.g. C++'s 50 million ways to do something, but this combined with a lack of guardrails makes it agonizingly difficult to do a lot of basic things – most notoriously dealing with strings.

    I actually consider C a good beginner language, but only in the sense that 1) it does have that simple toolkit, 2) it and its descendants are widely used, and most importantly 3) the bullshit C makes you deal with gives you a better understanding of what higher-level languages do for you automatically and why. To me, it’s probably the hardest mainstream language to learn after maybe something like x86 or ARM assembly (which, for better or worse, hit points 1 and 3 even harder than C).

    I generally agree though that Rust has always been somewhere in the middle for me.


  • TheTechnician27@lemmy.worldtoFediverse memes@feddit.ukPieFed be like
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    8
    ·
    edit-2
    13 days ago

    As someone who routinely works on a complicated C++ codebase, had to use C, Python, and Java all the time through school, has had to use absolute trash like JavaScript and PHP, and has dabbled in languages similar-ish to Rust like Go and Swift, Rust to me is simple to work with.

    The compiler is extremely helpful when I do something wrong, it has sensible conventions like immutability by default, Cargo is a streamlined build system, I’ve found the documentation easy to read, I actually prefer curly brace-delimited scopes to tabbed ones and explicit type declarations for readability, and in the obvious comparison to C/C++, Rust lacks extremely common memory footguns.

    Obviously compared to Python – with its mountain of syntax sugar and a library for everything – Rust is going to be more difficult. But for languages in general? Rust is not at all one of the harder ones I’ve learned or used.

    (Btw I hate Java; it’s the worst language I’ve ever used.)


  • TheTechnician27@lemmy.worldtoFediverse memes@feddit.ukPieFed be like
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    8
    ·
    edit-2
    13 days ago

    Notice how the OP specifically said well-known and widely used.

    I did notice. If Rust isn’t “widely used”, then I’ll need to let Apple, Microsoft, Google, Amazon, Mozilla, Huawei, Meta, the Linux kernel devs, and a fuckload of open-source projects know that they actually don’t exist.

    It’s plently widely used, and unlike a scripting language (edit: Python), it’s performant – as server software should be. Rust is not a hard language to use or learn either, and it’s great for large projects.



  • efforts to extend Xorg’s life or replace it with similar alternatives continue.

    This is 100% true, but the efforts are negligible and not even worth consideration.

    • Xorg maintainers are doing just that: maintaining it (and, for the most part, begrudgingly). It will continue to exist for a long time, but that’s the only remarkable thing about it.
    • XLibre is made by some anti-vaxx conspiracy dipshit who thinks ^ is an exponentiation operator in C and who got kicked off Xorg for being a moron who did functionally nothing of any importance while carelessly breaking things like the ABI. Enormous quantity but zero quality to speak of. It will go nowhere and only has any crumb of relevance because of the maintainer’s virtue signaling.
    • Phoenix basically just started, yet Linux outlets are tripping over themselves to report on it, showing there’s very little real work to speak of in this space. It’s a nothingburger of a story. It doesn’t even do basically the only thing X11 is even good for anymore, which is support legacy applications.

    As GNOME and KDE drop X11 and DEs like Cinnamon adopt Wayland, more and more actively maintained applications will stop giving a shit about X11. Even if they don’t explicitly not support it, none of the developers will be using it, and most of the userbase won’t either; thus, applications’ support for X11 will just rot away if it isn’t outright deprecated. Obviously X11 will always have a base of legacy applications, but you’re going to be seriously hard-pressed even two years from now to find someone who would use X11 over Wayland – except for specific and severely outdated hardware, conspiracy nutjobs, and the rare case where XWayland doesn’t properly support a legacy application.



  • One of the best side effects of having gone vegan is that the cost of food has gone through the floor. Plant-based staples are dirt cheap and extremely shelf-stable, and because most times it’s easier and more interesting to cook for myself, I learned a lot of insanely cheap, yummy, and healthy foods to cook. I just bought 8 lb of Desi chickpeas and 20 lbs of basmati rice – enough to feed the fucking Artesh for a year – for about $30 (and I wasn’t trying to penny-pinch). The spices, herbs, sauces, oil, nuts, etc. that go into making that, meanwhile, barely even factor in cost-wise.

    Even with a non-plant-based diet, you’ll find cooking staples like chicken at home saves you a fuckload of money.



  • TheTechnician27@lemmy.worldtolinuxmemes@lemmy.worldThe Terminal
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    28 days ago

    I mean use of the CLI on Linux generally. I used “terminal” vaguely because the original comment used it vaguely. “Down pat” is to say that I’m perfectly comfortable with it, namely that the course taught me:

    • How to execute programs from the shell (and interrupt execution/kill processes).
    • How to navigate and alter the filesystem, search for files and their contents, etc.
    • How to install, remove, and configure software.
    • How to set aliases.
    • How to write shell scripts.
    • How to edit files (although 99% of the time this is useless; I’ll just use something like Kate instead).
    • How to parse and interpret program output.
    • How to read man pages.
    • Generally how to do anything I couldn’t/wouldn’t prefer to do from a GUI instead.

    I use the shell vastly more than 99.99% of people and haven’t had a problem with or changed how I interact with it since that course; that to me is “down pat” for the terminal itself. I don’t care if I don’t know every application and flag ever made, because that’s not the point – like knowing how to use a GUI doesn’t mean you’ve memorized all GUI software, just that you know how to interpret the design language of and successfully use new GUI software. If I need to do something my current tools can’t, I can just search for the right program and use the man page to quickly write a command.

    Meanwhile, with something like LibreOffice Calc, which I understand is much less feature-rich than the industry standard Excel, I don’t just learn about new functions like CORREL(), akin to what I said before about learning new CLI applications; I fundamentally learn how to create and edit spreadsheets more quickly. In Impress, I still learn how to make presentations more appealing, more readable, etc. Basically things that aren’t just rote memorization of gadgets that I could look up at any time. That’s what sets it apart to me – the fact that anything I don’t already know about the Linux terminal is present in readily available reference material and better off not memorized.


  • TheTechnician27@lemmy.worldtolinuxmemes@lemmy.worldThe Terminal
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    29 days ago

    Well yeah, because I did. What else is there? I knew how to do everything I would ever need to do in the Linux command line. Anything I need to do beyond fundamental interactions, what else do I need to know besides how to 1) find a relevant CLI application and 2) read the man page to write a command? I even knew how to write basic shell scripts, which I would argue goes beyond “using the command line” and strays into “using a scripting language”. After that course, I never struggled with the Linux CLI because it taught me how to reason about it; is there a problem with that statement?

    Is the timeframe and the setting the problem? Because I’m talking about going from never having used Linux or a CLI to being fluent with both, and the class was still a blowoff.


  • TheTechnician27@lemmy.worldtolinuxmemes@lemmy.worldThe Terminal
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    29 days ago

    I know you already pointed out your sample is heavily biased, but to reiterate: macOS users you know predominantly from computer science and adjacent engineering fields are a very skewed sample. You can say that sprinkling terminal usage into a middle school computer literacy class is worthwhile, and I might even agree. But to treat it as anything more than something used by enthusiasts, programmers, IT professionals, scientists (on a very basic level that can be learned in 10 minutes), teenagers trying to look badass, and the one-in-a-million frustrated “normie” user who falls into it through some troubleshooting/game modding/etc. tutorial simply isn’t realistic.

    Regarding ping: what good is it going to do a normal user who doesn’t understand basic networking? It can rarely tell me basic useful information, like that my DNS is fucked up (can’t get to websites but can ping). For normal users it’ll just tell them the Internet isn’t working, which they probably already figured out, but how do they resolve it? Pictured: a normal user who can use ping figuring out their Internet isn’t working. To make something like ping meaningfully useful, you need to teach them basic Layer 3 concepts too, which is fine, but that’s not a terminal skill – that’s networking skills with a trivial terminal command stapled on.


  • TheTechnician27@lemmy.worldtolinuxmemes@lemmy.worldThe Terminal
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    3
    ·
    edit-2
    29 days ago

    Anyone can learn to use an office suite on their own in very little time

    Okay, should I say the same about a terminal then? I took a single-semester Linux course and had the terminal down pat. Meanwhile, I grew up learning how to use an office suite day in and day out in K–12 and still find new ways to improve my workflow in one.

    so there’s no reason to teach it

    Besides the fact that it’s a cornerstore of modern society that any white-collar professional will routinely have to work with, sure. (If you want to pull the “we shouldn’t be turning our kids into workers” card for why teaching them basic job skills is bad, things like word processing and spreadsheets are/can be very useful outside of industry too.)

    Being able to use the command line is a valuable skill that makes you a way better computer user no matter what you’re doing

    Okay, like… kind of? It gives you a better mindset, but in terms of a specific application, unless you’re in a niche part of industry or have niche interests, you will never in your life need to touch the terminal at this point. You will be just fine. Even as a power user, there are few problems normal users would face where I look at the terminal and see a shortcut to something that would be tedious in the GUI – and fuck knows most people use their desktop OS less than I do if they even have one anymore.

    and it’s one that a lot of people are missing these days.

    Because as noted, no major OS except desktop Linux makes you interact with the terminal in any meaningful way – and even desktop Linux is changing that because designers understand that, while the terminal is a godsend for power users, everyday users have no compelling reason to deal with it.

    I don’t think you can really say you know how to use a computer if you can only use it in the very specific ways someone happens to have made a gui for

    This is elitist bullshit that isn’t reflected in the real world. It’s not 1992 anymore. If people can efficiently complete the workflows they need via a GUI and never touch the terminal, then good for them; they know how to use a computer. This comment is so profoundly out-of-touch with how most actual humans live their lives that I feel like I’ve tripped and fallen into another reality.