• 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: March 15th, 2023

help-circle


  • From the list, openscad requires the least tutorial. Solvespace is really easy also, but you need to watch some exciting modelling videos before you get the idea around it. Blender is hard.

    OpenScad also gives you a different modelling experience that lets you write reusable models, e.g. if you are a carpenter, 90% of your modelling is sizing and positioning fiberboards to shape a box. You can “automate” such tasks, easily. I wrote a script for myself that does that, and I’m now super fast at modelling furnitures. After some modelling you will be also capable of making such lib. (As a developer, I might be biased)

    If you are interested in this library: https://github.com/fxdave/woodworkers-lib





  • That’s my problem with this. It tries to be a desktop display server protocol without unifying all desktop requirements. Sure, X11 is old and have unnecessary things that aren’t relevant anymore, however, as someone who builds their own DE, (e.g.: tiling window managers) I see it as the end of this masterrace. Unless everybody moves to wlroots. Flameshot, for example, is already dealing with this, having at least 5 implementations only for linux, and only wlroots and x11 are standards.

    Also, imo, having windows in windows is useful when you want to use your favourite terminal in your favourite IDE. But as you said DEs can implement it simply. Let’s say wlroots will implement this but others can decide otherwise. And for those the app won’t run.

    Another example, that affects my app personally, is the ability to query which monitor is the pointer at. Wayland doesn’t care having these so I doesn’t care supporting wayland. And I"m being sad about this because X is slowly fading away so new apps will not run on my desktop.

    Moreover with X11 I could write my own hotkey daemon in my lanuage of choice, now I would have to fork the compositor.

    Do I see it wrong?




  • fxdave@lemmy.mltoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    11 months ago

    My brother had that OS. It worked fine until it got a bug that the computer froze when he enabled the wifi, and the only way to stop it was pressing the power button. I couldn’t figure out the cause, and there was many unnecessary things coming with the OS, so I helped him to install Arch instead. Now, it works well and feels clean.

    EDIT: based on the comments, the issue happened with arch too.


  • fxdave@lemmy.mltoLinux@lemmy.mlArch or NixOS?
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    Ofc, Arch users should learn how to resolve a package conflict, or how to downgrade packages, or generally how to debug the system. Sometimes you also have to migrate config files.

    On the other hand, as an arch user, I can tell that it mostly just works. If you customize heavily an ubuntu, it will break more likely. And while you can fix an arch, you probably have to reinstall an ubuntu.

    Moreover, Arch has a testing repository which is not the default.




  • Afaik, Fedora is a free software. I don’t deny that, and I’m a free software fan. I don’t have any problems with fedora besides that it is too heavy for me.

    It looks you also care about your freedom because you use gnu/linux and lemmy. However, it seems you have a different meaning of malware.

    Softwere is a recipe. Any unwanted step is malicious. You can only determine a step as unwanted by seeing its source code.

    Besides this, a softwere can have other functions that are not coming from the code but the license. Similarly they can be malfunctions. For example preventing you from modification.

    So yes, propriatory software is malware. I use some malwares also, because they have no alternatives yet. But let me call them malwares.

    Copyright is the example of capitalism polluting water to be able to sell clean water to people.


  • I wish it would be possible now but it probably won’t happen until windows and mac will have similar features. The problem is that processes cannot just read a file, because in the container it doesn’t exist. It’s maybe due to permission. Maybe not. You cannot tell. Android apps are written in a way that they request access, while pc apps are just reading the files directly without requesting permission.

    So the app has to be written for flatpak. However, afaik, this is the maintainers goal too. Btw, the file open dialog is a currently working example of the dynamic permission handling. It’s just that the app should use these features which is not guaranteed.