POCO VS nixpkgs

You can also look into Poco https://pocoproject.org/

I can't say enough good stuff about POCO for this type of work - when I first got my teams using it we used to joke that POCO was what Boost wants to be when it grows up. And nlohmann/json - cracking library for working with JSON in C++.

We use https://github.com/pocoproject/poco in most projects, very easy to set up a http listener

Did someone used Poco's Net Library to create a Rest Api? Poco Project

But CLion is so slow. Tested with Poco C++ standard build (https://pocoproject.org/). Moving around with Go To Definition takes sometimes up to 20 seconds if file is first touched. Using 'back' and 'forward' delays for 1-2 seconds.

Yes, you need NetSSL - take a look at find_package(Poco REQUIRED COMPONENTS ... NetSSL) requires an aditional find_package(OpenSSL) since poco-10.

poco (portable components) https://pocoproject.org/

I mean, sure, except that many large open-source projects (e.g. Linux [1], Nixpkgs [2], etc) require this as part of their AI policy. Omit attribution in your own projects if you want, but the maintainers of these projects are owed at least that level of transparency.

[1] https://docs.kernel.org/process/coding-assistants.html

[2] https://github.com/NixOS/nixpkgs/commit/d18b8f3238abdb2cd878...

In case you're curious, here's a Nix derivation to make Balatro for any other system playable on Linux:

https://github.com/NixOS/nixpkgs/tree/master/pkgs/by-name/ba...

I wrote half a blog post when I did the derivation. One day, I should finish it and post it here.

I've encountered the same KDE bug in NixOS though from what I understood when I did some digging[0][1] it doesn't manifest on distros like Fedora.

Now I'm using Cinnamon until the bug gets fixed which I enjoy too but it doesn't come close to the ease of use of KDE. And when I say ease of use on KDE I refer to the fact that out of the box you can pretty much do everything you need to without having to search for extensions or hunt for settings, someone already thought of what you wanted to do and made it straightforward to do. Sure it's overwhelming to be presented with a lot of things at once e.g. the screen capture UI but when you need to do something that's not the base case it's easy to see that the UI has got you covered.

[0]: https://www.reddit.com/r/NixOS/comments/1pdtc3v/kde_plasma_i...

[1]: https://github.com/NixOS/nixpkgs/issues/126590

If you really need things others are no longer willing to maintain, then it’s time to learn how to help yourself.

The Nix or Guix package managers are likely your easiest bet. See

https://nixos.wiki/wiki/Lazarus

https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...

Then I use "$GREP" in the script itself, and develop with grep in my path, but it's trivial to prepend all of my dependencies when I bundle it up for nix.

1: https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/no...

Interesting, I have taken a stab at maintaining a repo on the nixpkgs and using a --sparse approach, i.e. `git clone --filter=blob:none --sparse --branch nixos-25.11 https://github.com/NixOS/nixpkgs.git nixpkgs-dorion