He got convinced, its now Auxolotl!
Theres going to be an official reevaluation once the governance has finished bootstrapping.
He got convinced, its now Auxolotl!
Theres going to be an official reevaluation once the governance has finished bootstrapping.
I read it as “a pin nix” like appendix with a lisp
Agreed, I made a thread for it. You’ve got some good names!
You should learn the nix lang, flakes, zero to nix, etc and try not to get bogged down in the Nix/Aux stuff. Be prepared to wait for things to settle down on that side.
Sadly no AFAIK, even ignoring the licensing issues.
“Select where you heard about typst”
-> Fediverse
Finally somewhere that actually has Fediverse as an option, this must be a good app.
I mean, manual approval technically does work. I kinda wanted something that would scale.
While I’m really glad to hear about it, I think it would work great for DDOS detection, I don’t know that it works for preventing spam accounts. I’m pretty sure puppeteer with GPT4 could check that box no problem.
PoW sure, but like what’s the tool name. Rolling my own PoW sounds not-smart. I’ve messed with metamask a bit but last I check isn’t real practical for mobile.
[TOTP] Simple to setup / create, doesn’t depend on 3rd party …
Actually I’m worried its a bit TOO easy to create. I don’t need a bulletproof/airtight system but what’s stopping highschooler from installing bluestacks, downloading the AUTH app, and then handling 10,000 TOTP requests for different bot accounts.
This is pretty cool. I’ve got a couple repos that Microsoft uses for VS Code. I switched one of them to GPLv3, but maybe I’ll switch the other to this license.
Yeah, university is almost certainly going to expect you to be able to install Unreal or Unity, which just isn’t possible AFAIK on NixOS. NixOS is very all or nothing. You can’t just remove the restrictions for one project and hack something together to hit an assignment deadline. Theres still lots of pain points with LD_PATH and 3rd party binaries.
That said, you can use nixpkgs on non-nixos and still get reliability for Godot and other open source tools. For your case, I highly recommend dual booting, and then using nixpkgs without going full blown nixOS.
Fair, I did miss that requirement
It is a sad story. Keeping it in legendary meme status is the best way to remember it IMO.
Temple OS
For standard notes, its got an auto-export plaintext file option on desktop. Were you wanting two-way editing of plaintext? (e.g. Auto export and import)
When you’re editing yaml, why not just always write JSON?
Almost all nix attr keys are unquoted strings. Maybe I’m missing the point list, but I kinda wouldn’t expect it to be on the list.
Despite my love of yaml. I actually think he has a small point with unquoted strings. I teach students and see their struggles. Bash also does unquoted strings and basically all students go years and years without realizing
cat --help
cat "--help"
# ^ same thing
cat *
cat "*"
# ^ not same thing
cat $thing
cat "$thing"
# ^ similar but not the same
To know the difference between special and normal-but-no-quotes you have to know literally every special symbol. And, for example, its rare to realize the --
in --help, isn’t special at a language level, its only special at a convention level.
Same thing can happen in yaml files, but actually a little worse I’d say. In bash all the “special” things are at least symbols. But in yaml there are more special cases. Imagine editing this kind of a list:
js_keywords:
- if
- else
- while
- break
- continue
- import
- from
- default
- class
- const
- var
- let
- new
- async
- function
- undefined
- null
- true
- false
- Nan
- Infinity
Three of those are not strings. Syntax highlighting can help (which is why I don’t think its a real issue). But still “why are three not strings? Well … just because”. AKA there isn’t a syntax pattern, there’s just a hardcoded list of names that need to be memorized. What is actually challeging is, unless students start with a proper yaml tutorial, or see examples of quotes in the config, its not obvious that quotes will solve the problem (students think "true"
behaves like "\"true\""
). So even when they see true
is highlighted funny, they don’t really know what to do about it. I’ve seem some try stuff like \true.
Still doesn’t mean yaml is bad, every language has edge cases.
Its easy for me to say “just start writing JSON in the yaml. It doesn’t get more simple than JSON”, but actually I do think there’s a small point with the unquoted strings.
Back before I knew programming, I was trying to change grammar settings sublime 2, which uses yaml. I had no idea what yaml was. The default setting values used unquoted strings fot regex. I knew PCRE regex and escapes, but suddenly they didnt work, and when I tried to match a single quote inside of regex that also didn’t work. I didn’t know I was editing yaml file (it had a .tmLanguage
extension). Even worse, if I remeber correctly, unparsable settings just silently fail. Not only did I have no errors to google, I didn’t have any reason to believe the escapes were the cause of the problem (they worked in the command line). Sometimes I edited the regex and it was fine, and other times it just seemed to break. I didn’t learn about quoting in YAML until years later.
For me that was an unfortuate combination, which was exacerbated by yaml unquoted weirdness. But when you’re talking about “did you read the spec” that’s a whole other story. .nan
for nan, tabs vs spaces, unquted string weirdness, etc should just be one error message+google away. I think they’re a small hiccups with what is overall a great format.
Use e2e for all communication you can