• 0 Posts
  • 42 Comments
Joined 2 months ago
cake
Cake day: July 22nd, 2024

help-circle

  • leisesprecher@feddit.orgtoScience Memes@mander.xyzelucidating 🤌🏼
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    4 days ago

    Well, actually you’re kind of wrong, at least in some contexts.

    So I’m not sure, how that works in other countries, but here in Germany, a large bid for some public contact has to parrot the requirements. The process includes a bloke essentially ticking all of the boxes in their request, and if you say (just for example) “we will deploy that in our k8s cluster” but they require a cloud ready solution, the bloke will not tick the box. Yes, that’s incredibly stupid.

    Apart from that, who reads the bid texts? Not technical people, but bean counters and MBAs. The technical people on the other side are only asked for comment, they have no say.

    I wish you would be right, but in a world full of people desperately trying to justify their existence, fluff is essential.


  • Most “professional” writing is just a bunch of phrases interspersed with a few chunks of information.

    I’m involved with bidding and grant proposal stuff for software and it’s 90% empty words. I draw two diagrams and a page of text, sales deletes 60% of the text, misinterprets the rest and then puffs it up to 30 pages.




  • The long-term goal is for Rust to overtake C in the kernel (from what I understand

    Your understanding wrong. Rust is limited to some very specific niches within the kernel and will likely not spread out anytime soon.

    critical code gets left untouched (a lot of the time) because no one wants to be the one that breaks shit

    The entire kernel is “critical”. The entire kernel runs - kind of by definition - in kernel space. Every bug there has the potential for privilege escalation or faults - theoretically even hardware damage. So following your advice, nobody should every touch the kernel at all.






  • No, I’d argue you simply didn’t want to invest in the other tools.

    Think about it, you probably spent hours on customizing and automating vim, and then say you’re faster in that. Well, that’s called a habit.

    IDE are objectively more powerful and since you can actually see options and navigate quickly, you don’t need to memorize every obscure feature.

    All the terminal editor enthusiasts are actively holding us back, because they insist everything outside vim is garbage for enterprise and kiddies.

    If your tool of choice is actively hostile to new users for no reason other than “that’s how it’s always been, and thus it’s better”, well then you’re digging a moat to automate your gatekeeping.


  • I understand it very well. And that’s exactly why I’m writing this.

    Ok, I can see you have no idea what you’re talking about.

    Then say, grandmaster delusion, what purpose does vim serve, where it is actually the best tool? Writing code? Hardly, it’s way too limited and requires a ton of upfront investment and headspace. Writing config files? Hardly, because if you write these by hand, you’re living in the 90s, that’s what Ansible, Terraform etc are for.

    You just don’t want to admit, that vim is nothing more than a habit. Muscle memory.


  • You’re using the terminal, because you’re used to it. It is not the better tool, it’s simply what you happen to know already.

    People who argue with productivity because of some key bindings live in the world of the 80s. You don’t just sit there and type code 12h a day, that’s not how modern software development works.

    And all those blockheads down voting me are caught up in their weird superiority complex. They are the powerful superhackers, and don’t understand that we are just highly qualified plumbers.




  • And that’s especially true for Linux and other big projects.

    I’m not a kernel or C developer by any stretch, but a few years ago fixed a small bug that caused my knockoff PS2 controllers to act super weird. Nothing serious, something like one constant and maybe 5 lines of code. Would have gladly pushed that upstream, but fuck me sideways is that a complicated process. Patches via email??? And the argument is always “but it works for us”, yeah burning witches and slavery also work for some people, doesn’t mean it’s something to continue doing.

    If there isn’t a serious revamp, Linux will die a slow death or become just a corporate graveyard product like Cobol.