Technically no, but in that sense everything cloud-based is local in some machine.
I wouldn't consider it "local" if I need to run a web server (!), "upload" if I want to open file or "download" to save it locally. This is client-server approach where both my machine acts as both client and server.
Do you have plans to release it for desktop (maybe using Electron)? One of my main complains about tools like Tinkercad is that they are browser-based, and it's easier/faster to have everything local. That's one of the reasons that I moved to OpenSCAD
I always remap Caps Lock to Ctrl. I understand that Caps Lock needed to be next to Shift in typewriters, but in computers it seems like it is wasting a key in the home row for only be used sometimes for screaming (which can be done by holding shift...)
Yeah. It's hard to express and understand nested structures in a natural language yet they are easy in high-level programming languages. E.g. "the dog of first son of my neighbour" vs "me.neighbour.sons[0].dog", "sunny and hot, or rainy but not cold" vs "(sunny && hot) || (rainy && !cold)".
In the past maths were expressed using natural language, the math language exists because natural language isn't clear enough.
Actually, the Git data model supports empty directories, however, the index doesn't since it only maps names to files but not to directories. You can even create a commit with a root directory using --allow-empty, and it will use the hardcoded empty tree object (4b825dc642cb6eb9a060e54bf8d69288fbee4904).
Since the first time that I saw this here in HN I've been sharing it with several people around me. This including CS students, CS professors and non-technical people who only asked "how does a computer work?". I only say "just type 'cpu.land' and read that". This is one of the best things that I've found here.
Cool! But the title made me think that "cigarette smoke effect" made me think that it was about health issues, and I clicked because I was curious about how shaders could be related to that.
> Maybe consider putting your energy into a good documentation inside the repository.
Commit messages are documentation.
If you have a good commit history you don't need write tons of documents explaining each decision. The history will contain everything that you need, including: when and who changed the code, what was the code change and why the code exists. You have a good interface for retrieving that documentation (git log, perhaps with -S, -G, --grep, -L and some pathspecs) without needing to maintain extra infrastructure for that and without being cluttered over time (it will be mostly hidden unless you actively search that). You also don't need to remember to update the documents, you are forced to do that after each commit.
> Clojure solves the same problems Rust solves in a much simpler way
I'm curious about that, can you elaborate? I'm a beginner in Clojure and I only know a few concepts about Rust, but it seems to me that they solve (at least, currently) very different problems...
I only saw Rust being used in places where C or C++ would be used in the past (Linux kernel, CLI apps, desktop apps), while I only saw Clojure being used as a modern and functional Java and JS replacement.
Not to mention how different they are as languages (static vs dynamic typing, native vs jvm, borrow checker vs garbage collection)
Technically no, but in that sense everything cloud-based is local in some machine.
I wouldn't consider it "local" if I need to run a web server (!), "upload" if I want to open file or "download" to save it locally. This is client-server approach where both my machine acts as both client and server.