I spent about six months working on adding new pigments to my palette, and his research was invaluable. Highly recommended for anyone who is intermediate at watercolour. For beginners, he has a page that recommends some beginner palettes, which is quite useful.
For those looking − as the GP said, it's not fantastically organized − pigments information is available here: https://www.handprint.com/HP/WCL/waterfs.html. Top links yield access to pigments, organized by "color family".
Two other similar resources on pigments − always good to check what's in the tube before buying!
I've been using a Wispr equivalent I made myself since 2023. It's wild to me that people pay for it, and I've wondered if I should try to monetize what I use. It is not as slick and polished, but provides essentially the same service: better speech-to-text than the built-in speech-to-text for Macs.
Not that it's super complex, but I'm surprised it didn't pick up an npm package. I wrote tarsec[1] and have been eyeing ohmjs[2]. And of course nearley is a classic.
Recursive descent parsers are basically mechanical structures, if you get the grammar right (which encapsulates all the logic).
When I was a CS student, they seemed like magic to me as well, but later I got to revisit them for a project at work, and finally managed to understand the logic.
Imo, the biggest complexity in using them comes from how they handle operator precedence, with recursive nested expressions in the grammar, which I still don't find intuitive at all.
If you decide to hand-roll your own parser/syntax today, I recommend you look at Pratt-parsers, they are much nicer to write by hand. Modern languages (Rust, Go) , ironically are much simpler to parse, since they defined the syntax in such a way that they can be parsed unambigously by looking 1-2 tokens ahead.
And since all of them follow the same logic, AI has a ton of sources to learn from.
I'm also working on my programming language, and AI assistants have been able to generate these parsers for well over a year.
Edit: Oh, I think the main dev is just using Claude to do the commits (I guess to summarise changes, etc). It does not mean that Claude wrote all that code.
For those less in the know: is it for convenience? Because most systems have a package manager that can install Python, correct? But `pip` is more familiar to some?
I think it’s more for Python libraries that depend on JavaScript.
Lots of packages rely on other languages and runtimes. For example, tabula-py[1] depends on Java.
So if my-package requires a JS runtime, it can add this deno package as its own dependency.
The benefit is consumers only need to specify my-package as a dependency, and the deno runtime will be fetched for free as a transient dependency. This avoids every consumer needing to manage their own JavaScript runtime/environment.
The zig one allows you to build native modules for your python project from setup.py without having to have a C/C++ toolchain preinstalled. Here's a talk about this:
It's because when you use the native Python packaging tools, you can install a Python "wheel" into an arbitrary Python environment.
If you get Deno from the system package manager, or from deno.com directly, you're more constrained. Rather, it seems that you can set an environment variable to control where the Deno home page installer will install, but then you still need to make your Python program aware of that path.
Whereas a native Python package can (and does, in this case, and also e.g. in the case of `uv`) provide a shim that can be imported from Python and which tells your program what the path is. So even though the runtime doesn't itself have a Python API, it can be used more readily from a Python program that depends on it.
Pypi is the only OS agnostic package manager already installed on every OS.
Also, it's VERY convenient for companies already using python as the primary language because they can manage the dependency with uv rather than introduce a second package manager for devs. (For example, if you run deno code, but don't maintain any JS yourself)
I'm no expert when it comes to software packaging and distribution issues but this does give off Internet-Archive-as-CDN levels of Hyrum's Law for me. What could possibly go wrong hmmmmmm....
The list has helped me plan as its forced me to cut things, and just admit I won't have time to do them. For example, I took about fifty books off my shelf and to the little free library. They've been sitting there for years.
Unfortunately a pre-req would be me severely downgrading what I think is worth writing down as an accomplishment, or switching to writing down meaningless tasks (though that IS what the original tada list idea recommends)
Funny timing, I've been building something like this for my own use -- but your feature list has everything I wanted :) How much do you charge? Would love to know without downloading an app
reply