New features like removing an artificial limit
Lehmanator
joined 2 years ago
Few reasons, some less valid than others.
- replaces GPL license with more permissive one
- wasnt broke dont fix
- missing some configuration features of base sudo
- C people feeling threatened by rust
- people hate rust's overzealous stans
- rust community is pretty queer, so being anti-rust is a nice proxy for anti-lgbtq
Computational theory would be a better name, but it overlaps with a more specific subset of what is normally called CS.
This is exactly it. Regex is super simple. The difficulty is maintaining a mental mapping between language/util <-> regex engine <-> engine syntax & character class names. It gets worse when utils also conditionally enable extended syntaxes with flags or options.
The hardest part is remembering whether you need to use \w or [:alnum:].
Way too few utils actually mention which syntax they use too. Most just say something accepts a "regular expression", which is totally ambiguous.
This is exactly it. Regex is super simple. The difficulty is maintaining a mental mapping between language/util <-> regex engine <-> engine syntax & character class names. It gets worse when utils also conditionally enable extended syntaxes with flags or options.
The hardest part is remembering whether you need to use \w or [:alnum:].
Way too few utils actually mention which syntax they use too. Most just say something accepts a "regular expression", which is totally ambiguous.
This is exactly it. Regex is super simple. The difficulty is maintaining a mental mapping between language/util <-> regex engine <-> engine syntax & character class names. It gets worse when utils also conditionally enable extended syntaxes with flags or options.
The hardest part is remembering whether you need to use \w or [:alnum:].
Way too few utils actually mention which syntax they use too. Most just say something accepts a "regular expression", which is totally ambiguous.
This is exactly it. Regex is super simple. The difficulty is maintaining a mental mapping between language/util <-> regex engine <-> engine syntax & character class names. It gets worse when utils also conditionally enable extended syntaxes with flags or options.
The hardest part is remembering whether you need to use \w or [:alnum:].
Way too few utils actually mention which syntax they use too. Most just say something accepts a "regular expression", which is totally ambiguous.
Depends on what you're doing in your config and what you're changing. My configs are huge and complex because I was a moron when I first started out. Adding packages to your nixosConfigurations is a smell IMO. Most of the time, it would be preferable to add them to a devshell instead.
25 seconds sounds pretty close to my experience, but my machine is beefy and my configs have a lot of bad patterns for eval time.
Gamers 😤 For what it's worth, more users, especially on a gaming-related project probably the effort providing basic support faster than it increases contributions.
The network effect is a real problem tho. Hopefully ForgeFed & Gitlab implementing ActivityPub will help with this. Same with OAuth with GitHub as the SSO provider.
Bridging Matrix seems like the best of both, but takes a lot more work.
I'm a purist, so if I see a project uses Discord, I'll immediately start looking for viable alternatives.
OpenLDAP does.
There's not much to replace GPOs, but you can conditionally provision most settings on NixOS. Would be nice to build an MDM around Nix.