• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle
  • sLLiK@lemmy.mltoMemes@lemmy.mlI LOVE MANUAL TRANSMISSION
    link
    fedilink
    arrow-up
    61
    arrow-down
    1
    ·
    1 year ago

    I do, too, and drove one for many years. I’ll be the one to splash cold water on the conversation, though.

    Driving a stick arguably requires the use of both hands and legs, which is great and partly the reason why so many enjoy it - that sense of engagement. It’s far less boring.

    But here’s the deal. Injure any one of those appendages and driving a manual becomes a whole lot less fun. In some cases, you can get by, but it’s less than ideal. Having your arm closest to the shift in a sling, for example, makes your vehicle undrivable.

    It won’t matter to most people… right up until the moment it does.






  • Syslog (rsyslod) is usually the standard answer for the average sysadmin, but it depends a lot on your needs. A lot of newer loggers output as pure JSON, which offer benefits to readability and more approachable search logic/filters/queries (I’m so tired of regex).

    When you start venturing down the road of finding the right way to store and forward the output of logging drivers from Docker containers, as one example, rsyslod starts to feel dated.

    The easy answers if you want to throw money at the problem are solutions like Splunk, Datadog, or New Relic. If you don’t want to (and most people wouldn’t), then alternatives certainly exist, but some of them are just as heavy on system resources. Greylog has relative feature parity with Splunk Enterprise, but consumes just as much compute and storage if not more, and I found it to be a much larger pain in the butt to administer and keep running.

    The likeliest answer to this problem is Grafana Loki, just based on what I’ve read of its capabilities, but I haven’t had a chance to circle back and test it out. Someone here who has might be able to weigh in and speak to its strengths/weaknesses.





  • One of the main reasons my wife hasn’t taken the Linux plunge is Photoshop support and a lack of feature-complete alternatives with sane UI design choices. We would gladly pay for a Linux version of Photoshop at this point.

    It"s dawning on me now as I write this that Proton could be the secret sauce that slays this monster. Has anyone tried adding Photoshop as a non-Steam app to the Steam client, lately?


  • As others have stated, the cleanest option for a single monitor setup is to either share a specific window, or start making use of multiple virtual desktops, sometimes referred to as workspaces. Windows, Mac, and Linux are all capable of it, now - the only difference is how you set up, arrange, and navigate them.

    Linux options offer the most versatility, Mac’s implementation is a decent balance between ease of use and scalability (with caveats), and the Windows native implementation is the newest entrant to this playing field… but it’s an adequate offering that gets the job done for this use case.




  • That doesn’t represent disinterest by the developers. In fact, that’s a big red circled F on a report card to them, and including that comment is intentionally bringing attention to a glaring deficiency. It’s very likely that they have a plugin implemented in their IDE which surfaces TODO items vividly, and their associated Jira task or epic can’t be closed out until all of the remaining work is complete.

    I’d be more worried if the code presented a clear danger to privacy and DIDN’T directly address concerns in one form or another. You should be praising this dev for raising awareness to his peers and making sure this gets done, not the opposite.