• 23 Posts
  • 382 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle





  • Actually that’s my biggest issue. Give me settings, give me choice

    That’s an GNOME issue mostly I think. It has this least possible settings and oversimplification approach, because GNOME thinks people can’t handle it. Ubuntu modified the configuration of GNOME that it looks and behave somewhat similar to previous Unity versions.


  • But its not about just how it started. Snap was more focused on phones and servers, not on desktop in the beginning. And there were not much, because Snap was usable over the following years (like Flatpak). Canonical could see how the entire rest of the Linux communities and distributions adopted Flatpak and could have switched to it. But contrary to it, Canonical was very pushy about Snap. So my argument is, Canonical should have dropped Snap early when they still could (just like they did with Mir in example). But they didn’t.

    Obviously now its a different situation, but you were talking about the beginning in this reply.


  • Here we go again… Some historical reasons, and some technical. Here are a few (strong points) that comes to my mind:

    Ubuntu has a track record to do their own thing and splitting community or the entire Linux eco system, such as with Unity, Mir and Snaps. Unity was badly implemented desktop environment in the beginning and lot of people didn’t like it. Although I think it was a great DE over time, it was just another fuel in the fire. More serious problem was Mir. Mir was an alternative to Wayland, because Canonical was not happy with Wayland and they didn’t want to implement what Ubuntu tried to do on phones. But that meant the programs and protocols to support was now X11, Wayland and Mir. And related to it, the focus of mobile user interface on desktop (Mir+Unity) was something lot of desktop fans didn’t like at that time. Canonical gave up on Mir and Unity (and smartphones entirely).

    Snaps were very slow at the beginning, some people does not like that it fills the device loops, and not many apps were available as snaps. Snap is a similar but alternative technology to Flatpak. Again, because Canonical was not happy with Flatpak and Snap truly has some advantages over it. But it means splitting the eco system once again. But what made it really upsetting for many is, that not only Snap is pushed by Canonical a lot, but also when installing a native package, the package manager would silently install the snap version instead. That is sneaky. And not only that. The Snap repository from Canonical is proprietary. And if you want support Snap, you have to use that repo or use your own repo. Unlike Flatpak, you cannot have multiple repositories. That means in Snap you can only use Canonicals proprietary Snap repository, because otherwise you would not have all the apps in it.

    There was some Amazon related datas send to Amazon with an app, every time you searched in the search bar of Unity. Even though this is gone for long time, it still is something people (me included) remember. Some say it was spyware… which is kind of was, but is up to debate.

    Also some do not like that Canonical is a corporation. I personally don’t have a problem with that (and used it for 13 years exclusively), but its something to mention what problems have with. Also Ubuntu is used in Windows too, so people have conspiracies too or do not like their cooperation. I’m fine with that and actually like that Linux gets more exposure this way. But again, some people don’t like it.


  • My point is, it depends on the workflow and the tools. Try editing complex images with keyboard alone with GIMP or Inkscape. I’m a Vim user and used tiling window managers for years, so I know exactly what you mean with keyboard centric workflow being productive. But sometimes ignoring the mouse can make the workflow harder, not easier. Off course it always depends on what you actually do.

    Edit: Guess I answered my … question (even though it wasn’t a question). Never mind.








  • Maybe a better place to ask would be one of the following places:

    For your question, are you talking about streaming videos? At least on YouTube videos are at 60 fps. The higher the fps, the more bandwidth and space is required on the servers. Therefore YouTube will limit 4k at 60 fps to paying customers. And for the casual smartphone videos, isn’t 30 fps at 4k not the default? People like to have higher resolution, because they don’t understand what fps probably is (I mean the non tech mommies).

    Are you talking about movies? Movies often aren’t filmed at 60 fps, therefore it would be lot of waste to stream them at 60. I’m not sure if this is still true with modern films though. I didn’t keep up with tech much.



  • Yeah. Lot of people also use Ai generated code… so…

    I have tested if clippy would warn me with a simple example (generates 6.7gb memory usage, be careful not to crash your computer if you add another 0…), while I watch with a system monitor (in KDE):

    use std::thread;
    use std::time;
    
    fn main() {
        let mut vec = Vec::new(); // Create an empty Vector.
    
        for number in 0..900000000 {
            let bign: i64 = number * number;
            vec.push(bign);
        }
    
        thread::sleep(time::Duration::from_secs(10));
    }
    

    I used the pedantic option of clippy and the only thing it complained was about the notation of the number…:

    $ cargo clippy -- -W clippy::pedantic
    warning: long literal lacking separators
    --> src/main.rs:7:22
    |
    7 |     for number in 0..900000000 {
    |                      ^^^^^^^^^ help: consider: `900_000_000`
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unreadable_literal
    = note: `-W clippy::unreadable-literal` implied by `-W clippy::pedantic`
    = help: to override `-W clippy::pedantic` add `#[allow(clippy::unreadable_literal)]`
    
    warning: `notright` (bin "notright") generated 1 warning
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.00s