• 4 Posts
  • 75 Comments
Joined 3 years ago
cake
Cake day: March 15th, 2023

help-circle
  • fxdave@lemmy.mltolinuxmemes@lemmy.worldFacts
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    5 days ago

    Like KDE? It would be a lot more complex. I would fear giving KDE for newcomers. It’s basically windows 98, but with frosty glass themes, fragmented apps.

    Or Cinnamon? You upgraded to windows XP. Congratulations.

    Deepin? Looks cool until you try to use it.

    Xfce? That’s stable and fast. But would you advertise Linux as that outdated?

    Cosmic, still early.

    Budgie, maybe.

    I really think gnome is the best default.


    Nevertheless, It’s you mixing intuitive and familiar. Moreover, people who give Linux a trial, they wish for something different. And they really like Gnome from my experience.


  • fxdave@lemmy.mltolinuxmemes@lemmy.worldFacts
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    5 days ago

    Not at all. Newcomers want intuitive UI. And gnome is really that.

    Examples:

    One unified settings app. Containing all the settings that as a average user needs. It’s always at the top right corner.

    Change the wallpaper? Top right corner -> settings

    Add a network? Top right corner -> settings

    Extend display to projector? Top right corner -> settings

    It’s not weird at all.

    What would be a better starter DE then?


  • fxdave@lemmy.mltolinuxmemes@lemmy.worldFacts
    link
    fedilink
    arrow-up
    1
    ·
    6 days ago

    If somebody is coming from a different DE he wants the same interactions that they used to do. It’s easy to hate Gnome because people see that first. And they find:

    • there’s no tray
    • what’s that line at the top
    • where’s the start menu
    • where are the opened apps
    • is the app drawer really that ugly

    And these are only expectations and you just learn to do things differently.

    Just because it has a different workflow that big players implanted in people, Linux needs to match that?

    The worst thing you can do is to install a dock extension to make it feel like you are in your previous DE. If you want to get the real Gnome experience, you need to let it be Gnome.


    As for the design, it’s indeed subjective, but we can agree that it is modern with balanced spacing. You can feel that a graphic designer worked on it. And if you don’t like it, that’s the same as with other DEs, install a theme. As you can’t change QT apps to use titlebar you can’t change GTK apps to use app menu instead.


    And finally the keyboard efficiency: Indeed every major DE is keyboard efficient, but I wasn’t expecting it for Gnome when I was learning it, because I’m videos, you always see clicks, so I mentioned it.








  • I don’t think it’s ADD. There’s a book called ‘thinking fast and slow’. In that book the psychologist separates the mind functions into two systems. System 1 is for intuition, no effort, fast thinking. System 2 needs effort, slow, but precise. What happens here is that simply people are trying to be efficient with their thinking and they use less system 2 which is required for reading.


  • I used claude code to migrate a small rust project from raw sql to an ORM. It was next level. In a timespan of a small bug fix I could rewrite the data model. It tested the code, it fixed the errors, I was amazed. I reviewed every change, so I could spot problems like migration would fail with prod data. I wrote a new prompt to fix that and it fixed.

    For anybody new to claude code: It’s a tui app where you can log in and write prompts for the project in the current directory. The way it works, it searches files in the project based on the prompt, and it locates the related code sections. So it gathers the context pretty well. It can suggest changes, it can suggest running CLI commands, it can read its output. It reacts to itself. You can accept or intercept and correct it anytime.

    I ran it in docker just in case.

    In summary, this is a real deal, but of course the code needs to be reviewed. Sometimes, it produces, simply put, unmaintainable code, that shouldn’t be used. Works or not, it should move.









  • By IO heavy I meant db operations or other external requests. When the request handler starts, it waits for the IO to be completed. While it waits, it can accept other requests and so on, so the bottleneck is the IO in my case, not the request parsing.

    I imagine it like this (imaginary numbers):

    • DB operation: 20ms
    • Express request handler: 1ms
    • Brhama request handler: 0.5ms

    Which case, it wouldn’t matter which http framework to use. However, there are probably other use-cases.