201–210 of 417 posts
NNCP, from http://www.nncpgo.org/ It's a protocol/tool for async file transfer, built for disconnected/intermittent connectivity amongst known parties (trusted friends as p2p), allowing even for sneakernet-based file transfer. It's started as a modern take on usenet, but it boggles my mind how cool it is: Want to send a TV Series to your friend? send it via nncp, and it will make it through either via line-based file…
- Matrix. It's pretty popular but I see way too many open source projects still saying "join our Discord!" instead of "join us on Matrix!"
Earlier quoted context omitted.
There would be no automated consensus over results of execution of programs that power the applications
Just curious, which would be most reliable? One entity confirms it who confirmed 1000 previous results, 2 who confirmed 500, 10 who confirmed 100 or 1000 who confirmed 1 previously?
- in-process databases (rocksdb, sqlite)
- FoundationDB
- C/C++ and low level programming in general (I wished I learned those instead of js when I was younger)
- State Machines, Actor Model (Orleans Net), Event Sourcing
- Bittorrent for other things than pirating (it looks like it's dying)
- Arduino and similar
- Seastar
- Arrow (ecosystem)
Earlier quoted context omitted.
And for keyboard remapping on macOS there’s GokuRakuJoudo: https://github.com/yqrashawn/GokuRakuJoudo
How did they come up with that name xD
Of course they also might just be a fan of J-Pop https://en.wikipedia.org/wiki/Gokuraku_Jodo
Earlier quoted context omitted.
It's not simple. The nix programming language is like untyped ML. Most people aren't used to it and even if you are familiar with it it gets hella hard to read. Learning curve is huge. One docker file and a poetry file works just as well. And is simpler. It's literally the same thing but using os primitives to manage the environment rather then shell tricks. Makes more sense to me to use a dedicated os primitive for…
nix is far simpler for consumption. My coworkers don't like fancy new things, and they haven't had any complaints. They don't have to dick around with half a dozen different commands to get everything set up, or bother with docker volumes/port mapping/etc. They just run nix-shell and it all works. That's all you have to do with a shell.nix file, it's very simple. It is harder to write on average atm, but it's very mu…
Additionally nix uses shell hacks to get everything working. Docker uses an os primitive DESIGNED for this very use case.
And additionally, because docker uses os primitives you can use docker-compose to manage multiple processes on multiple different environments simultaneously. Something that's much harder to do with nix shell.
In case you don't fancy visiting all the links: - Tarantool is some sort of in-memory DB with optional persistence - Red is a programming language that has made the odd syntax decision to use {} for strings and [] to define scopes - U++ is one of those all-encompasing C++ frameworks like QT - Lazarus is a Pascal(?) IDE - And FASM is a toolkit for building assemblers I'm struggling to find the common thread across the…
Earlier quoted context omitted.
It's not simple. The nix programming language is like untyped ML. Most people aren't used to it and even if you are familiar with it it gets hella hard to read. Learning curve is huge. One docker file and a poetry file works just as well. And is simpler. It's literally the same thing but using os primitives to manage the environment rather then shell tricks. Makes more sense to me to use a dedicated os primitive for…
> One docker file and a poetry file works just as well. And is simpler. It's literally the same thing but using os primitives to manage the environment rather then shell tricks. Makes more sense to me to use a dedicated os primitive for the task it was designed to be used for. 1) not just as well because docker is repeatable, not reproducible 2) not if you need GPU acceleration which is a headache in docker, but not…
Not sure what you're saying here but most likely you're referring to some obscure pedantic difference. Effectively speaking docker and nix shell achieve similar objectives.
>2) not if you need GPU acceleration which is a headache in docker, but not Nix shells
This is true. But this is the only clear benefit I see.
>- devenv.sh - arion - https://flakular.in/intro
right. So? I said nowhere near as straightforward. This isn't straightforward. It's an obscure solution.
>The same was once true for Dockerfile
False. DockerFiles are much more intuitive because it's just a declarative config. With Nix shell it's mostly people who like haskell or OCaml who are into that style of syntax. I like it but clearly that syntax has not caught on for years and years and years. Quite likely Nix will never catch on to that level too.