• 0 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: December 7th, 2023

help-circle



  • Just to chime in with my own opinion on JetBrains’ tooling, my first language was Java - admittedly its been a while since I tried Java (and other JVM languages like Kotlin) in VSCode but when I last did it was a bit of a challenge. I also did some Android development for a while and if “standalone” Java was awkward in VSCode I assume Android development would have been too (Android development in general was nightmare fuel until Android Studio came along, never really did like Eclipse all that much).

    After expanding out into other languages, I have enjoyed the specialization of each of the JetBrains IDEs. VSCode always felt like a “Jack of all trades, master of none” type of experience for me personally. I have tried out Zed recently and while I think its going to be a decent editor, I still have similar issues with it that I have in VSCode (in that how well it works depends on what language you’re using).

    The exception to their tooling that I haven’t really liked though is Fleet - which was their answer to creating an equivalent to VSCode. It hasn’t really seen a lot of development and feels more like the forgotten step child of JetBrains. Also the “Remote Development”/JetBrains Gateway features can be really hit or miss though thankfully I don’t need that sort of functionality often.


  • The p2p meshnet that they were referring to basically is a local/small group ISP.

    As for why a single person cannot (effectively) become their own ISP? It’s complicated. Really complicated. ISPs have to pay other ISPs just like you and I do, unless they’re a Tier-1 ISP/Network. Otherwise you’re always going to be paying to connect to (and generally paying for bandwidth) another network that has access to a network that then has access to a T1 network. T1s are basically the largest networks that hold (or can directly access) the majority of people on the internet. Top of the food chain, so to speak.

    So in theory, yeah, you can become your own ISP - but you’ll still need to pay and be at the mercy of other ISPs. Datacenters are typically their own ISP, but they have to pay others to get online just like we do.




  • I always assumed it was more or less targeting the federation of issues/MRs.

    The git side of things is already distributed as you said, but if you decide to host your random project on your own GitLab instance you’ll miss out on people submitting issues/MRs because they won’t want to sign up for an account on your random instance (or sign in with another IdP).

    This is where a lot of the reliance of GitHub comes from, in my opinion.



  • I’m quite confused by some of the pain points that the author mentioned. For example, the Dolphin view switch icon - you absolutely don’t need to click on the dropdown to change the view, you can click the icon itself and it’ll change (and I’m pretty sure this is why the button is “two buttons” and has the divider next to the dropdown icon).

    For Spectacle, regarding the extra mouse clicks - most of the functions include a (global) keyboard shortcut by default and for the few that don’t, you just need to set one.

    Floating panels: Whether you like the design of a floating panel or not is of course subjective. However the author mentions that you need to “aim like an idiot and waste your time hitting the ‘floating target’” - except no, you don’t. They can “slam their mouse into the screen corner” because the target zone for the applets extends below and to the corners of the screen. If you want to open the Application Launcher for example, you can “slam” your mouse to the bottom left corner and click - it will open. Same with every applet (I do not believe this to be something the applet controls, but rather the panel itself so it should work with any applet).

    Kubuntu’s “anti-user move” is not controlled by the KDE team. Not sure how much control Ubuntu spins have over their packages, but it is either a Canonical move or a move by the Kubuntu team - regardless, its not something the KDE team mandated (AFAIK they are not removing X11 support). The only thing the KDE team has done is make the Wayland session the default.

    Regarding the bugs they’ve found, I hope they reported those on the KDE bug tracker.

    This line in particular made me laugh a bit though:

    … plus “simple” interfaces is NOT going to win the hearts and minds of the common people. That’s not how it works.

    Yes, it does. A “common” person does not care in the slightest that libmyfancylibrary was updated to version 1.2.3.4, I mean I’d argue they don’t care in general about updates but I digress.


  • I’d be highly surprised if Wayland actually has a protocol for applications to just type across other applications, we barely even have global shortcuts (it’s getting there but reaaaaaally slowly).

    KPXC might be able to get around it by using whichever method ydotool does (by faking a device AFAIK) - probably needs root to do this though, and it would also need to implement the global shortcuts API to be able to respond to a key bind I believe.

    So perhaps a bit of column A and column B.


  • Russ@bitforged.spacetoProgramming@programming.devThe Copilot Delusion
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    7 months ago

    As long as it is done properly and honest, I have nothing against a “Pro” and a “Contra” article.

    Neither do I, personally. Though I am certainly less than inclined enjoy an article where the author is oddly preachy/“holier-than-thou”, sayings things such as you’re not a “real” programmer unless you sacrifice your health debugging segfaults at 3AM or have done the handmade hero challenge (certainly an interesting series to watch, but one that I have zero interest in replicating). Yet the author accuses copilot of having a superiority complex. I cannot say for sure, however I would assume if the article was in favor of AI rather than against, then there would definitely be comments about exactly this.

    The overarching tone of the article seems like if it were written as a direct comment toward a user instead, it would run afoul of beehaw’s (and surely other instances’) rules, or at the least come really close to skirting the line - and I don’t mean the parts where the author is speaking of/to copilot.


  • According to another user in here, blocking on Mastodon actually works. So seems like it is possible to do in the Fediverse.

    I was not aware of this, but their implementation of how they do this does bring up the limitation I mentioned. The other user cannot see your posts only if you are on the same server:

    If you and the blocked user are on the same server, the blocked user will not be able to view your posts on your profile while logged in.

    I actually thought blocks were public already.

    They’re not, well - the operator of your instance could go into the database and view it that way in the same way that they can see your email address. But aside from someone who has database access to your instance, blocks are not public. What is public is the list of defederated (“blocked” so to speak) instances for an entire instance (this can be viewed by going to /instances of any instance), which might be what you were thinking of?

    And personally I don’t see how it would be an issue if people that I haven’t blocked can see who I’ve blocked.

    How exactly would you enforce that, though? If your blocks were public, all the person who you’ve blocked would need to do is open a private browsing window and look at your profile to see that they’ve been blocked.

    If we’re looking at blocks as being a safety feature, I would think that having your blocks broadcasted to every single instance would be classified as harmful and a breach of your privacy. This is why although an instance that you register with has to have your email address that you signed up with, they don’t broadcast it to all other instances (same with the encrypted value of your password) - because otherwise it would effectively be public.

    Perhaps I’ve just got the wrong stance, but considering that you can never block someone from viewing your content with an absolute guarantee (if the blocks were broadcasted, you still couldn’t prevent someone from just simply logging out, or standing up their own instance and collecting the data anyways) I would not consider that tradeoff to be worthwhile. Not that my stance has any weight since I’m not a maintainer for Lemmy (or any of the Fediverse software), but I wouldn’t be surprised if that has at least come up to those who are developing the various Fediverse software.


  • Aside from the rest of the discussion that has already occurred here, I’m not actually sure how this would work from a technical perspective.

    You and I are on two completely different instances, if I were to block you, how is your instance supposed to know this in order to stop you from reading my comment?

    The only way I could see that working is if the list of users you blocked were federated too, and effectively made public (like votes currently are) - which seems counterproductive to the problem at hand.

    Then what happens if you post in a community where someone you’ve blocked is a moderator? Or if you block the admin of another instance? If you can “cloak” yourself from being moderated by just blocking them, that seems like an exploit waiting to happen. As far as I’m aware, on Reddit blocking a user doesn’t hide your comments from them - but they can no longer reply to them, and I assume this is why that is the case. Unless that has very recently changed.

    The biggest difference between Lemmy (and all software within the Fediverse - for example, I’m pretty sure Mastodon is this way as well), is that there is not one singular authoritative server. Actions like this need to be handled on all instances, and that’s impossible to guarantee. A bad actor running an instance could just rip out the function that handles this, and then it’s moot. I mean, they wouldn’t even need to do that - they’d have the data anyways.

    You could enforce it if both users are on the same instance I suppose, but this just seems like it would only land with the blocking feature being even more inconsistent.


  • I don’t see how that’s going to work out well. That’s asking to end up with a mess that you’re just going to have to rewrite anyways.

    I do not even have a complete hatred for AI like a lot of folks do, but I don’t trust it that much (nor should anyone).

    You’d be better off with an actual deterministic transpiler for that (think TypeScript -> JS but the other way around I suppose), not something with a ton of random variables like an AI.


  • Patching Comic Code? It was quite a while ago unfortunately, so I don’t have the exact commands available, but I used their Font Patcher tool in order to do so.

    From what I recall, the tricky thing was actually getting the dependencies it required to be installed properly, Font Forge would be up and running but then the script’s errors indicated that it couldn’t resolve all of the necessary dependencies. Not sure what OS you’re on so your mileage may vary - but for Linux they now have an AppImage that looks to contain everything it needs, and for macOS/Windows if you have Docker available there also appears to be a pre-built container for it. There’s also quite a few examples that I don’t think were there when I used it, since I also recall not being 100% sure of what flags were needed to run it



  • Oh hey, someone else who uses Comic Code - greetings!

    I remember when I first saw it, I laughed - and then it grew on me. Then it turned into “I can’t believe I am buying a derivation of comic sans” but it is actually a really nice monospaced font.

    Only thing I didn’t like was having to figure out how to use Font Patcher to make a copy of it that supports nerd fonts, but it was a one and done process.

    (I also don’t really like how it looks in my IDE the few times I find myself on Windows, but I don’t really blame the font for that one - looks perfect in the same IDE on Linux…)


  • COSMIC is definitely a really neat desktop, and I’m looking forward to the stable release!

    I have had the alphas installed and usually give it a go for a day or two each revision. Currently there’s definitely some oddities regarding graphical glitches, such as after suspending the system - but I like where it’s headed.

    For me right now the biggest roadblock is the lack of a night light mode (blue light filtering). I’ve gotten so used to relying on it in other desktops.

    I do have some crappy $20 blue light filtering glasses, but they’re… Not great or comfortable to wear for any extended amount of time. And my monitors’ built in color shifting mode is also pretty lackluster.