cultural reviewer and dabbler in stylistic premonitions

  • 34 Posts
  • 223 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle


  • Thanks. Sorry to see my assumption was correct; that does indeed sound a lot like when they were called OSSO two decades ago.

    Notably absent from the list of things they might open source soon is their current “Lipstick” UI, the graphical shell itself.

    All of the stuff they plan to open source are things I didn’t even figure out were still closed from my 5-10 minutes of research before writing my previous comments. It is difficult to estimate the number (do you know how?) of other small closed components which they can dribble out over the next years to maintain users’ false hope that they will one day have an actually-open-source operating system.

    we’ll see though

    my advice is: don’t hold your breath.

    Sorry if this sounds bitter, but it’s because I am - I naively believed that OSSO might actually ship a free OS one day (to be fair they didn’t say they would either, but they helped us believe that they might… in effect saying “we’ll see” for years while releasing bits here and there) and it was frustrating to realize that it was never a real possibility.






  • Arthur Besse@lemmy.mlMtoLinux@lemmy.mlAnd so it begins
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    1 reason it’s wrong to me: https://nosystemd.org/

    Under “Notable bugs and security issues” there is a big list of issues which were all (afaict) fixed many years ago.

    There have been reasonable philosophical objections to systemd, some of which are still relevant, and as that site shows there are still many distros without it, but for the vast majority of desktop users who want something that JustWorks… using a mainstream distro with systemd is the way to go.

    This blog post from pmOS covers some of the pain of trying to use KDE or GNOME without it.






  • I think you misunderstood me

    Go ahead and post the same link for Google job listings. I’ll wait.

    My comment was in response to your comments (bolded below) in this thread:

    I was already thinking of getting a Linux phone next, this is helping to seal the deal. Fuck Apple the genocide enablers.

    please do explain how Apple is doing anything here. If Israel wants to provide their military with iPhones they’re going to no matter what Apple does.

    They don’t have to do business with/in Israel.

    That still will not stop a nation state (especially Israel) from getting their hands on Apple devices.

    My point was not to say that Google is better than Apple here - in fact, unlike Apple (as far as I know), Google has actually built AI tools specifically tailored for Israel’s genocidal business requirements.

    My point is that if Apple wanted to boycott a country (which in the case of Israel they obviously don’t, which job listings at their R&D centers are just one of many points of evidence of) it would actually make it difficult-to-impossible for any substantial part of the boycotted country’s government to rely on using iPhones.

    (Unlike Android derivatives which can easily be used without direct reliance on Google’s services…)

    As an aside, while I would not use iOS (due to it being proprietary), it is hard to dispute that (for most adversaries, at least) compromising it is generally much more expensive/difficult/unlikely than Android. So, given that Apple is very friendly to them, the IDF’s policy decision to use iPhones makes sense.










  • Arthur Besse@lemmy.mlMtoLinux@lemmy.mlLinux terminal with text selection
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    3 months ago

    “But you can’t copy with Ctrl+C, it’s…” - You can. When something is selected It copies selection to clipboard, otherwise it sends SIGINT.

    What terminal emulator are you using where ctrl-c copies instead of sending SIGINT when text is selected? In every one I’ve ever used, ctrl-c still sends SIGINT even with text selected (and one must must use ctrl-shift-C/ctrl-shift-V to copy/paste).

    I don’t have any suggestion for getting the behavior you’re asking for, but besides the normal ctrl-(shift)-C/V clipboard FYI you also have two other types of clipboard-like things: one which works anywhere (not only in the terminal) and is actually always automatically copying anything you select and lets you paste from it with middle click (this originated with X Windows but i think most Wayland compositors have also implemented it by now), and another which is found in GNU Readline (used by bash and numerous other REPLs) called the “kill buffer” which can be pasted (or “yanked”) from and cut (or “killed”) to using Emacs keyboard shortcuts (which also include various cursor movement controls).

    Notes:

    • the kill buffer is local to a given readline context, it’s not shared across different shell windows.
    • the list of emacs keybindings in that wikipedia article i linked is currently confusingly referring to the kill buffer as “the clipboard”
    • you can drastically reconfigure your readline keybindings and other behavior by editing your .inputrc file, but you cannot achieve what you were originally asking for because there is no concept of text selection in readline.

    HTH!