Not to mention VSCodium already exists.
Find me on Mastodon, if you want.
Not to mention VSCodium already exists.
I figured they would just run sfc /scannow
and then sit staring at their screen bewildered when it inevitably does nothing.
Just found this article about it that seems to fundamentally misunderstand it in every single way. I didn’t know it was even possible to be this clueless. Either that, or it’s AI.
When the spacing is tight
and the difference is slight,
that’s a moire!
Thor from Pirate Software (a game studio) does this. He has his set up so that if he doesn’t log into a specific server for a year, the source code to his game will be automatically published.
You could do the same thing. Just grab a super cheap server that checks the last login date and sends out emails.
It’s been 4 years since I built my last one, but I still think it holds true.
I’ve heard Intel chips still run hot, especially the 14th Gen i9. However, I came across this article by Puget Systems (a system integrator who mainly deals with professional workstations rather than gaming rigs) who found that decreasing the PL1, which I assume means Power Level, from 253W to 125W was a good enough tradeoff for performance/heat that it’s the default configuration they ship to their customers.
On the other hand, they still do mention that tasks such as UE light baking, V-Ray, Cinebench, and Blender saw gains of 10-18% when using the higher power limit, which seems much more like what OP’s workload is. Puget then proceed to recommend a CPU with a higher core count like a Threadripper PRO for those kinds of workloads, so perhaps OP really would be better off going AMD for their workstation.
As someone who tried NixOS recently for the first time, it feels like an uphill battle.
Some immediate concerns I have as a newbie are below. Bear in mind that I’m a single user on a single system.
Organisation is daunting as fuck
Even a relatively simple desktop config seems rather large to me. I expect the complexity of my config to balloon if I were to use this as my primary OS. There seems to be no consensus on how things should be separated.
I’ve heard home-manager is good, but I don’t really get the point of it. What does it achieve for me that editing configuration.nix doesn’t? I’ve yet to find a benefit. It’s just another place to dump endless configs and another command to remember to run.
Installing software feels like the roll of a dice
I installed NixOS to try Hyprland, and their docs say to just use programs.hyprland.enable = true
, which I’ve come to learn is a module. But that’s not the only way to install things! You also have system packages and user packages! I just want to install some software, I don’t want to have to look up whether it’s a module or a package every time I want something new. I’m never sure what I should add to which section. No other distro that I know of has this problem! Having 3 different places to add software seems excessive. What am I using? Windows? And now there’s Flakes too. I’m sure they’re great, but right now I just see them as yet another way to install software on Nix. Great.
There’s more, but I’ll leave it there for now. I’m sure there are reasonable answers to all that I’ve said, but I’m just frustrated. I really want to like Nix, but it’s not making it easy.
tl;dr: Two things. 1) Lack of consensus on how configs are organised is confusing. 2) Having 3 different ways of installing software (modules/packages/flakes) does not feel better than apt install
or pacman -Syu
etc.
Probably off-by-one errors
You can code in Notepad in the same way you can eat off the floor with your hands. Using better tools is a nicer experience.
As for performance, when one of the world’s most popular editor runs on Electron, it’s not that hard to see why performance could be an issue when working on large projects on older hardware.
I’ve never personally had an issue with VSCode’s performance, but I’m also fortunate enough to be in a position where I can afford a relatively modern machine. Many others have to make do with what they have, which is why Zed might appeal to them.
implying that any developer actually reads warnings
Consider all the gamers with more money than sense buying 4090s for the price of cars and, more importantly, many companies buying datacenter cards for their next generative AI project (not that I think many of them will last).
I don’t see Nvidia running out of money any time soon.
I want to like Forgejo but the name is really terrible.
Is it “forj-joe”? Nah, that double-J sound is way too awkward.
Do you then merge the J sounds to make “forjo”? If so, why not just call it that?
Is it maybe “for-geh-joe”? That seems the most likely to me, but then that ignores the “build < forge” marketing on their website.
I know it’s pretty inconsequential, but it feels weird using a tool that you don’t even know how to pronounce the name of.
Seems like a “haha JS bad” kind of joke, but OP seems to forget that Python is also in a similar boat.
Anon thinks he “won” by getting the girl, not realising that entering a relationship isn’t the finish line.
You at least have to know that it’s a meme format. Otherwise it just looks like someone complaining about async with a bad crop.
Interestingly, this JXL loads in Boost, but the one in the post doesn’t. Perhaps it’s because it’s inside a comment?
I would say finding that the bug is in a library is worse than finding it in your own code.
If it’s your own code, you just fix it.
If it’s in a library you then have to go and search for issues. If there isn’t one, you then go and spend time making one and potentially preparing a minimum reproducible example. Or if you don’t do that (or it’s just unmaintained) then you have to consider downgrading to a version that doesn’t have the bug and potentially losing functionality, or even switching to another library entirely and consequently rewriting all your code that used the old one to work with the new one.
Yeah, I’d take my own bugs over library bugs any day.
Perhaps try making a simple web chat application. I recommend it for a myriad of reasons:
Debianties