lil_baka

u/lil_baka@ani.social
1 posts · 37 comments

Recent posts

Recent comments

Yeah, there are many places where it's possible to draw the line, and I personally wouldn't go into extreme self-sabotage for something like this. So, if there are few dozens alternative DE/WMs that do absolutely the same thing but are not vibecoded, it's very little effort to switch using those, but if you literally have to give up on your whole system stack or even your whole hobby because of Krita or Blender or Linux Kernel accepting AI assisted code, that's just too much.

I have an impression that this is some legal rhetoric device that is intended to be used in courts in case there are copyright infringement claims. By saying that they don't accept such contributions they probably can make it a clear legal responsibility of the one who submitted the code and not the GCC project as legal entity. At least that's how I see it, but I'm not an expert in this topic.

Doesn't seem to be full-featured alternative for desktops:

I guess it can be hard if possible at all to use apps like Blender, Krita, etc. Also, I'm getting quite used to Portage and Gentoo FreeBSD project is obsolete and unsupported now so it would be very risky to try to run it with FreeBSD kernel.

I wonder if there's anything positive to be said about ISBNDB. On one hand, they're supplying AI companies, yes, on the other hand, they seem to be digitalizing previously unavailable paper books, which is kinda useful for preservation? Except, I'm not entirely sure it's possible to properly get this data out of them on consumer scale: they seem to sell API access, but it's a big question of how usable and affordable it would be to retrieve a digital version of some rare ancient book that could just disappear into oblivion otherwise. Their cheapest subscription is 15$/month, but I have little idea of how what's listed there translates into volumes of books you can retrieve during this month.

Yeah, but with Linux Kernel there is no choice. So people who are against AI can be unhappy with Linux Kernel as well but they only can choose to use alternative to Xfce but not to Linux Kernel. For now they can express their annoyance about it being allowed in kernel and hope that some day policy gets changed there as well. I don't see any moral inconsistency here.

I only used something similar to mess around with Hytale modding a bit, but it was only easy because there was fully ready-to-use premade solution. But in general, if you're willing to go that way, I think the most simple option would be to create a distrobox with ubuntu/debian/fedora/arch (depending on which distro covers things you need better), install vs code there (using native package manager of given distribution), and then distrobox-export VS Code from that distrobox. Then you can simply manage everything inside of distrobox using full power of distribution you chose. To make things even better, distrobox has automatic passthrough of most hardware. For Nvidia in particular, you need to pass flag "--nvidia" when doing "distrobox-create". After that, you can even use game engines like Unity or Godot from distrobox with full GPU passthrough.

Well they basically forked Bazzite DX image and customized that... The hyprland fork author stopped maintaining it 8 months ago so it's not gonna work anymore with any recent Bazzite versions. So what they did is how Bazzite itself was created in the first place - by forking Fedora Atomic image and customizing it. I wouldn't really count this as "Bazzite supports other DE/WM", but yeah, if someone decided to go this far and make a fork like this then great, you can use it and hope they'll keep maintaining it.

I kinda agree, but it can also be pain in the ass. For example, using flatpak VS Code is massive pain in the ass. You end up needing to do tons of tricky workarounds for all kinds of language server/formatter/etc addons to work properly. It's okay when you only need to do it once for a single language (Rust, for example), but it becomes very annoying when every new addon you install is highly likely to need you to write some flatpak-spawn based wrapper scripts in ~/.local/bin or whatever extra userspace bin folder you added to your PATH.