Even more valuable when you consider that Pall has stepped down as head of LuaJIT dev and handed off maintainership to others.
3,634 karma · joined February 21, 2007
Coding in Clojure, Fennel, and Lua.
The Marathon trilogy starts off a bit slow, but it's got some great sci-fi writing (if you like sarcastic AIs that are constantly making opaque references to classical literature) and twitch action.
If twitch action is your thing though, it's hard to beat Descent and Descent II.
I'm currently playing through Planescape Torment, which is less like an RPG and more like an avant-garde fantasy novel.
Many people would uninstall and download it over again when running into that kind of error message.
I think this is largely why aptitude exists; a single unified command for all common package tasks. Most of the Debian docs have been switched over to recommend its usage, but for some reason Ubuntu hasn't followed suit. That said, I just keep using the same old shell aliases I added in 2003 personally.
Have you ever tried to run a mail server before? It's a nightmare wrapped in a fiasco.
Right now Twitter is up in arms about proposed changes which make users not have control over their feeds; there will be algorithmic curation so you only see the most popular content from your followers. "Just create a CLI wrapper" only works assuming the APIs are not effected by the changes they are making to the main product, which doesn't really make sense.
It's a great success in many ways, but the problem it solves is completely self-inflicted by rubygems. I've also been doing Ruby for over a decade, but I've also learned a lot from other library ecosystems, and I feel pretty confident saying that disallowing version ranges makes all those headaches completely evaporate.
Yes, this is the way that Guix and Leiningen and rebar3 and a bunch of other things work, and it is wonderful.
Pulling in new code without you asking is a fine idea for something like apt-get where you have a huge team doing QA on the entire system working together before it even hits your repositories, but for most package managers, the dev team is the one doing the testing, and upgrades should be done only with great care.
It does mean you have to watch for security updates, but this is true of all package managers.
A thread? But that'll never scale!
Lack of arity checks is definitely much more problematic than this, but still... if you can count the number of tragic design flaws in your language on one hand, you're in great shape compared to the rest of what's out there!
I read it more as "relying on a runtime that must be installed on the user's OS instead of included in our executable is a nightmare". The dramatically reduced conceptual footprint of the language is a nice bonus though.
However, I felt that using their astronomical names/numbers would be unrealistic--if these stars ever ended up being colonized, they would be given colloquial names, so I made up my own names for most of them.
Sure it's not that there are known problems, but security isn't a thing you have or don't have; it's a process. If your process for identifying and fixing security flaws is broken, that's insecure.