i only like my mac because of the speakers; ultra the bright screen; and the cmd & ctrl key separation. as soon as someone else decides to build a laptop with those qualities (preferably better) i’d ditch mac in a heartbeat.
A meme about Linux and BSD and all those nerdy things on a general meme subreddit community that has more than 500 upvotes (with 1000 being a really high number of votes)? If this post was back on Reddit, say r/Memes, it would probably only get 100. Lemmy needs to somehow diversify its demographics such that less technical don’t feel as alienated after joining. (To be clear, this is not a criticism on this post.)
Calm down. All I’m saying is that if the Fediverse wants to succeed and actually beat Reddit, Discord, and Twitter, we need to have more than Linux users (I am too) on our platforms.
Fedora in the ‘has a life section’? Yes, having to reinstall an old version of shim-x64 on an encrypted disk, because the new version breaks the handover from UEFI to bootloader (and therefore even rescue mode is not accessible) is something that everybody is able to do in an instant.
Or dealing with a crashing window manager, getting your Bluetooth headset to work in a stable and predictable manner, etc.
I’ve had Fedora as a daily driver for over two years, switched to Manjaro because I grew tired of having to deal with a constant stream of issues and crashes. I won’t say that there is anything inherently bad about Fedora and I may have had a stroke of bad luck, but it is relatively bleeding edge and therefore one should expect issues to pop up from time to time.
I’ve been using fedora for about 2 years as well, absolutely the best and most stable Linux experience I’ve ever had. Been using Linux as my daily driver since about 2008
Every dev I know must be terrified of technology as they all use apple laptops. I don’t love apple but they make a pretty sweet *nix laptop for dev work.
My shop is about half and half, and I wouldn’t say that the devs with macs are afraid of technology, but I would say they don’t look real comfortable using a command prompt…
Please, please, PLEASE do not use Kali as a daily driver… The maintainers and the organization and every hacking role-model and educator on the internet says to not use it as a daily driver. You want Debian Testing if you’re that worried about having debian-like features but getting a rolling release
My main Problem is with my music production Software and Hardware, which cant be easily installed with wine. Other than that i have affinity suit which works with wine, but not without Problems. Lastly i use davinci resolve, which claims to Support linux natively but barely works.
So I have some old music projects that are basically stuck on Windows. Even if I moved over all the files and ran the plugins through WINE, I would have to go through the entire project and fill in the blanks with the WINE-bridged plugins and redo all the automation I have. Running the program through WINE isn’t really an option because my projects were just below the performance limit on native Windows. I know some programs run on WINE better than Windows, but I need real-time audio with a specific audio interface that doesn’t support Linux. I could use WINEASIO, but I would still be losing a lot of performance compared to native Windows, where again I am regularly reaching the performance limit of my setup.
Also, I’m holding off for a few months on installing Debian onto my Windows work laptop because all my technical programs are ready on Windows immediately. I’m waiting until I get more storage and until I know if the programs I need for my future job are compatible with WINE.
I love WINE as much as the next Linux user, but it can’t solve everything. I acknowledge that it is Windows rather than WINE or Linux that is making things difficult for us. Unfortunately, I need to have a native Windows partition for the foreseeable future, although I’m doing almost everything else on Debian on my home PC.
I’m aware of Yabridge. The problem with Yabridge (or any other plugin bridges, like Carla) is that any plugin used with it will be treated by the DAW as an instance of Yabridge rather than an instance of whatever plugin it is. This changes what parameters the DAW looks for.
If I remember correctly, the DAW is aware of parameter names in the VST3 standard. Most of my existing plugins are VST3 (compiled for Windows). In a typical situation, this is exposed to the DAW by the plugin when it is instantiated, and the automation and knob settings of those parameters are written to the project file under those names. However, when the project is moved over to Linux (or anywhere else other than Windows with all the same plugins), the DAW will scan the list of plugins that it is aware of, not including the Windows ones because it doesn’t know how to parse them. The DAW will simply give me a couple hundred “plugin not found” warnings. If I remember correctly, my DAW gives me the option to find and link these plugins by hand.
So I could theoretically go through the whole project and remap all the plugin automation by hand, but there wouldn’t be any technical benefit. It’s just simpler to keep a Windows partition.
Also, I have switched to Linux (Debian Bookworm w/ KDE) on my home PC for everything else. I’m loving it so far, especially KDE Plasma and KDEConnect. I don’t know how I lived without it. I might end up producing new tracks on Debian, but I have to install more software before I make that commitment. Really, it needs to “feel right”, which is admittedly not well-defined.
when I get a larger hard drive I will dualboot. Linux is MUCH easier for development stuff. I am using windows right now so I can continue to use some software (like Affinity Photo)
Add comment