• 2 Posts
  • 662 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle



  • Aux@lemmy.worldtolinuxmemes@lemmy.worldNo Mercy
    link
    fedilink
    arrow-up
    3
    ·
    3 months ago

    It’s not really a nuke as some processes might be protected. The nuke is to use debugger privileges. Far Manager can kill processes using debugger privileges, that will literally nuke anything and in an instant: the app won’t even receive any signals or anything.


  • Aux@lemmy.worldtolinuxmemes@lemmy.worldNo Mercy
    link
    fedilink
    arrow-up
    9
    ·
    3 months ago

    The end task doesn’t terminate the app, it only sends a message to the window to close itself. The app will then decide what to do on its own. For example, if the app has multiple windows open, it might close the active one, but still continue running with other windows open. Or it might ignore the message completely.














  • There are several issues with native development without a browser layer.

    First of all, native UI toolkits are very different and making a robust cross platform app is pretty much impossible. So, the traditional approach is to use one toolkit, which will be native to one platform, and then let your other users deal with it. For example, GTK apps on Windows and Mac look and feel like shit.

    Another approach is to use a custom cross platform toolkit, which doesn’t use anything native at all. If enough work and thought is put in such application, it can be a very pleasant experience. But often it’s shit for all users.

    The second issue is that it can be quite hard to manage fluid window sizes and to build a proper responsive UI with native toolkits. Some are better at it, some are worse. Native toolkits also tend to punish developers for deep nesting of components making UI development even more painful.

    HTML + CSS solves all that. It’s responsive by design, everyone is used to web apps already, nesting is not a problem at all, etc.