I mean, yeah, that’s the point of compression. I don’t quite get what you mean by that comment.
I really don’t think that’s a lot either. Nowadays we routinely process terabytes of data.
Oh, I know, believe me. I have some painful first-hand experience with such code.
I think portability and easy parsing is the only advantage od CSV. It’s definitely good enough (maybe even the best) for small datasets but if you have a lot of data you need a compressed binary format, something like parquet.
Is 600 MB a lot for pandas? Of course, CSV isn’t really optimal but I would’ve sworn pandas happily works with gigabytes of data.
Exactly this! Powerful tiling without the need to build your own DE from scratch sounds incredible!
Right, in the simplest case it’s a single option declaration and a single lib.mkIf
. I was probably overthinking the complexity. I will probably go with this approach.
Thanks for the answer and happy nixing!
I’m currently learning NixOS myself and was wondering about the same thing. I’m definitely leaning towards namespacing but I would like to hear an expert’s opinion.
Also, just a question. Are you planning to expose all your configuration modules via custom options? When I’m looking at other people’s configs I feel like the most popular approach is to enable modules just by importing them. I really like the idea of having custom options for everything but it’s additional work and complexity and I can’t decide if it’s worth the effort.
Thanks for the info. I’m very relieved, I love the bottom bar!
I recently migrated to their hosted plan and can highly recommend. It’s as close as you can get to Google Photos with E2EE right now.
I want a good tiling DE solution so much. I really hope COSMIC will fill in that gap.