This is clearly not “a russian wondering what’s wrong”, this is “a russian living in russia who doesn’t want to die in prison”. This would be a fair criticism if there wasn’t a law criminalizing pacifism together with many laws making it easy to deanonymize internet users.

Silence does not fix things.

Neither does grandstanding on Lemmy. It especially wouldn’t fix anything if a person in Russia trying to build international relations would go to prison for it.

This is about as useful as suggesting to an average USian/brit/german that they violently overthrow their oppressive governments and install socialism. The punishment for trying (at least in UK/germany) is about the same as it would be for a russian wearing an anti-war T-shirt, the benefits for the humanity would be greater than they would be for overthrowing Putin’s dictatorship, and yet I don’t see people yapping about it any time someone from those countries posts an open-source project.

There’s almost no civil society of any kind left in Russia, so it’s impossible to say if a nation overall supports or opposes the warfare. People with an active pro-war or anti-war stance are minorities, somewhere in the 10-20% range, and neither are allowed to speak up (interestingly, quite a lot of pro-war social media influencers are in prison right now for daring to speak up against corruption in the army or similar). The vast majority of people are just going about their days. Does that technically help with the war? Yes, I guess, it drives the economy, people pay taxes etc, but then the same can be said about an average american, brit or german right now - I don’t see them blowing up munitions factories (that directly supply the ongoing genocide).

There is a complex sociopolitical history as to why it’s likely Russians aren’t as vocal about these sorts of things

There’s also a very simple reason: Russian Criminal Code article 280.3, which criminalizes pacifism with up to 7 years’ imprisonment.

I don’t think there’s a law in the US that criminalizes pacifism [yet] (with actual prison time as punishment)

It’s easy to blame russians for not resisting the war when you don’t have the prospect of spending 7 years in a russian prison

The basis of trust has been breached by whole nation, so it has to be earned by every single member of that nation.

1. WTF is this collective punishment nonsense? Replace “nationality” with “race” (keeping in mind that a person typically doesn’t choose either and it’s decided by who their parents were) and you should be able to see the issue here
2. I hope you rather quickly uninstall almost all popular FOSS software from your devices, because almost all of it contains sizeable contributions from russian citizens and I don’t think you’ve individually verified their intentions

For context I’ve been using aerc as my email client for a while now, and was looking for something similar for calendars/tasks myself

I’ve tried:

• calcurse: fine but clunky, also a bit difficult to set up. The most mature option and probably the best one available, but I just couldn’t get used to the interface
• calcure: similarly clunky interface, glitchy/blinking rendering to the point of being headache-inducing, lacking features (couldn’t figure out how to look at all event attributes?)
• khal: limited in features (compared to calcurse) and slow when there are a lot of events (even when it’s only 2-3 per day), also there are some rendering bugs sometimes. Probably the most intuitive and clean interface of all, and good scripting opportunities.
• gcalcli: only Google Calendar (I also need support for arbitrary CalDAV), didn’t investigate further
• plann: no TUI as such, just CLI

A couple weeks ago I’ve decided to start writing my own. It’s still very much a hacky WIP but I’ll update in this thread if I ever decide to publish it. In the meantime, I hope one of the above works for you!

Because C++ doesn’t have a single well-defined build system, clangd doesn’t know how exactly to compile the files you are asking it to - in this case, it doesn’t know what headers to include. On some other distros it might “just work” because all headers are lumped together somewhere in /usr/include or something, and something somewhere tells clangd to just look in there. This isn’t the case on NixOS (in fact the headers are not installed at all with your system), and so you have to tell clangd where to look for them.

Typically, your build system will have that information somehow. The process can vary depending on the build system you are using - some (like CMake or meson) can do it natively, for others you have to resort to a very useful hack called bear. Judging by your shell.nix, I would guess it’s make, which doesn’t have native compile_commands.json support, so what you have to do is:

1. Add bear to your nativeBuildInputs
2. Enter the shell again so that you have it in $PATH
3. Run make clean (or otherwise ensure there are no build artifacts already present - maybe git clean -fx but be careful with that)
4. Run bear -- make from the project root.

make should then build your entire project, compiling every file in the process. bear will inspect the system calls that make is executing and determine which commands (and hence which command arguments) it used to compile each file, and create a file called compile_commands.json recording this information. clangd should then automatically find that file and use it to figure out which headers (and other arguments) it needs to compile each file.

This is the setup I personally use to hack on Nix itself BTW, and it works great. Although I’m using helix and not neovim, but that shouldn’t matter.

Hmm, clangd should support compile_commands.json directly. Not sure why your script is needed.

Nah, actually, in a typical company the lower down the ranks you are the less likely you are to be fired, statistically speaking (to a point, of course you’re more likely to be fired while on probation or something).

GitLab: a lot of cool features, well-integrated, polished. Downsides: resource hog, open-core model (some features locked behind a paid license when self-hosting)

Forgejo (the thing that powers codeberg): it’s federated & lighter on resources usage. Downsides: some features still missing/in development

Well shit. I will still self-host sourcehut because it’s so cool from a technical standpoint, but now with disgust for its author

Yes, it’s not linear. The progress of GenAI in the past 2 years is logarithmic at best, if you compare it with the boom that was 2019-2023 (from GPT2 to GPT4 in text, DALL-E 1 to 3 in images). The big companies trained their networks on all of the internet and ran out of training data, if you compare GPT4 to GPT5 it’s pretty obvious. Unless there’s a significant algorithmic breakthrough (which is looking less and less likely), at least text-based AI is not going to have another order-of-magniture improvement for a long time. Sure, it can already replace like 10% of devs who are doing boring JS stuff, but replacing at least half of the dev workforce is a pipe dream of the C-suite for now.

It’s categorically the same as printing out a PNG onto a sheet of paper. I can see how you might call that “storing”, even if it’s a lossy process.

This is needed for Flake-based setups where you use some NixOS modules that aren’t in Nixpkgs (home-manager being the most common use-case).

Honestly, yes. I have days when I want to code something new and experiment, and days when I just want to drudge through existing code and carefully refactor/clean up so that it still works (or even works better in some cases).

There’s a short explanation in this section: https://nixos.org/manual/nixos/stable/#sec-option-types-submodule (look for specialArgs) and in this section: https://nixos.org/manual/nixpkgs/stable/#module-system-lib-evalModules-param-specialArgs. I don’t know whether it’s documented properly somewhere.

I have experimented with something very similar in the past. I think the main issue is that it is quite confusing to read, being familiar with what the old <> syntax does.

BTW, you shouldn’t really need extraSpecialArgs in most cases; setting a _module.args config option should be enough.

To be fair, systemd also fixed a bunch of issues (by making the boot sequence declarative and also consolidating a bunch of previously disparate services into a cohesive ecosystem); it also introduced new ones which are now difficult to fix due to compatibility. I still prefer it.