• 29 Posts
  • 51 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

















  • One breaking change, that they doesn’t list as breaking (I guess since I assume the old was always broken) is: Dynamic registration of LSP capabilities. An implication of this change is that checking a client’s server_capabilities is no longer a sufficient indicator to see if a server supports a feature. Instead use client.supports_method(<method>). It considers both the dynamic capabilities and static server_capabilities.

    So if you had code like

    if client.server_capabilities.inlayHintProvider then
    ...
    end
    

    you now should use

    if client.supports_method("inlayHintProvider") then
    ...
    end
    

    So, not really a breaking change I guess, but something you should change any way.
















  • I know I have used it since Fedora made it default in 2016. I think I actually used it a while before that, but I don’t have any thing to help me pin down the exact time.

    Since I only use Intel built-in GPU, everything have worked pretty well. The few times I needed to share my screen, I had to logout and login to an X session. However, that was solved a couple of years ago. Now, I just wait for Java to get proper Wayland support, so I fully can ditch X for my daily use and get to take advantage of multi DPI capabilities of Wayland.


  • Didn’t they switch to a license with stronger mechanisms to keep the source available? SSPL, is basically AGPL but have even stronger protection from large corperations to use the code in their data centers without contributing the changes back. This is basically a move to prevent AWS/Google/Microsoft/et al, from leaching on the contributors work without giving anything back.

    Or am I reading this wrong?

    EDIT: Note, that the Mastodon account is to an AWS employee… so for him, this might be bad, since it no longer allows them to have their own internal fork without contributing back. Now, they will need to use a real for and maintain that them selves without leaching on the redis contributors.



  • But is the desktop really the most relevant measurement? Wouldn’t it be more relevant to talk about “primary” devices? When I grew up, the desktop was what people used to connect with Internet and everything that comes with that. Hence, Linux on the desktop seemed to be relevant. Now, that is still relevant in relation to work and gaming, but for general use people use other devices. So instead of “on the desktop” I think we should talk about “for work”, “for gaming” and “for programming”.





  • From their documentation

    Unlike classic terminals, Warp requires you to sign up and log in to get started with the app.

    So, yeah, it might be that people are not very impressed by a terminal that requires a cloud account.

    But, if you don’t type anything sensitive on to your terminal, like passwords and such, then you should be fine…