Mobile software engineer.

  • 1 Post
  • 83 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle
rss

  • Yeah, just a note, basically these Linux distros are the same at their “core”, but what differs among them is mostly about the software they have and the way they’re managed.

    So you have distros that offer only open source software in their repository, some include proprietary drivers. Some distro families will have some differences in the path of certain folders, different families use different formats of their packages (which include the actual binary of the software together with the metadata about how to install them in the system), although a purely Linux binary should be executed in any Linux distro. Some offer more guidance during installation and setup, some offer a more “raw” experience that force you to chose every little detail, and so on.

    Another difference is in their philosophy of how the packages and dependencies are made available. Distributions such Arch Linux and its derivatives always offer the latest versions of each package, reason why they’re called “rolling release”. Distributions such as Debian offer a specific version that’s “frozen” and tested thoroughly until a new version of Debian is released with more updated software.

    Some say a rolling release distro is better for gamers because you always get the latest features and performance improvements, but they’re naturally less reliable than a stable distro.

    So I’d say the important thing is to understand the trade-offs so that you can choose the best thing for you. And also there’s no downside of experimenting different distros in a virtual machine, for example.





  • This is a troll’s or a teenager’s line of thinking.

    Kinda reminded me back in college I had a friend who I’d describe as a genius in computer science and programming. I was always so jealous how he was so knowledgeable about everything teachers talked about to the point of correcting them sometimes (and hurting the ego of some of them, which isn’t very smart).

    He was like a C++ nuts to the point of having some of his code on the Boost library (which was impressive for a 20yo), but when Rust started getting popular back then, he really got into it and quickly became an “evangelist”. For some years, everything was about Rust, if you stopped to talk to him.

    I met him year later and asked if he was still working with Rust, and he said after using it for enough different use-cases, he actually started to dislike it and pointed out a lot of problems and flaws that I wouldn’t possibly remember. I think he also said the community was very toxic and was taking the language to a direction he didn’t like. I suspect nowadays he is just another fella using Lua and C++ for his personal projects.




  • …so might as well say that “agent” is simply the next buzzword, since people aren’t so excited with the concept of artificial intelligence any more

    This is exactly the reason for the emphasis on it.

    The reality is that the LLMs are impressive and nice to play with. But investors want to know where the big money will come from, and for companies, LLMs aren’t that useful in their current state, I think one of the biggest use for them is extracting information from documents with lots of text.

    So “agents” are supposed to be LLMs executing actions instead of just outputting text (such as calling APIs). Which doesn’t seem like the best idea considering they’re not great at all at making decisions—despite these companies try to paint them as capable of such.







  • Only chatGPT has these kinds of comments as if you’re seeing code for the first time. 😆

    I’m not against adding comments where is needed: in the company I work for (a big bank) my team takes care of a few modules and we added comments on one class that is responsible to make some very custom UI component with lots of calculations and low level manipulations. It’s basically a team of seniors and no one was against that monster having comments to explain what it was doing in case we had to go back and change something.

    For 99% of the code you just need to have good names though.


  • Just a reminder that reencoding already compressed videos is a recipe for destroying the quality, unless you’re using a very high bitrate, which quite often gets you the same size as the input video.

    I think the consensus is that if your video isn’t 4k or higher, there isn’t much gain in using HEVC if it is already H.264.

    So if you want to store them long term, reencoding them now means that if you decide to do it again later (for whatever reason) you’ll have too many artifacts accumulated.



  • If the distro is rolling release, it can always support the latest software in theory, you’d just need to have the correct package formula, which is exactly what AUR offers.

    The problem with AUR is just that the author of the package is likely not the author of the software and not affiliated with the distro, so you should normally check what the script is doing.


  • I really understand how hard is maintaining something for every single package manager and distributions

    But for apps distributed in your system’s package manager, it’s not the devs that are distributing them in every package manager. It’s the distribution itself that goes to each repository, checks and tests the dependencies they need and creates the package for the distribution, along with a compiled binary.

    When they aren’t offered in the distro’s package manager (or the version is outdated because the distro isn’t rolling release) things become more complicated indeed, and sometimes you can’t even do it because the dependencies are older than the ones you require.