So far I just pinned the rustc version used by requiring rustup as a build dependency. Let's see if this lets me drop it or if it is still easier in the end to build with pinned version.
> In addition, if you add "donate" button you'd see a lot of artists being showered with cash.
There are donation buttons for some artist on Spotify. I guess the artist need to enable it? ("Signum Regis" is an artist that has a Donate button for example)
This looks really nice and useful! I wonder if I could configure it to open things in vim directly? Because currently it seems to use xdg-open which then opens it in whatever application is configured.
I finally managed to build an ArchLinux kernel that supports out-of-tree modules written in Rust. If you're interested in the whole journey there are also the following posts:
> The real problem is that you can't use crates to improve incrementalism when you have a type in one logical part of the module hierarchy implement a trait from another logical part. Due to orphan rules and coherence, it is not possible to implement a foreign trait for a foreign type.
Well you can implement a trait for a type from another logical part either in the crate of the trait or the crate of the type.
What is the use-case for implementing a foreign trait for a foreign type if you have both under control?
> I wanted to separate the type, the trait and the implementation of the trait in different crates.
I usually put the traits in a separate crate, but keep concrete types and implementations for them in the same crate.
What is the use-case for splitting a type and it's implementation into separate crates? (except for cases where the trait or the type are out of your control, then one indeed needs to use the new-type escape hatch)
I had three different goals, one for the traits, one for something else where the types fit best, and the third which I achieved with the implementations of the traits.
The problem was that the trait implementations of the types was something like not a core task of the types themselves.
I use Pelican (https://getpelican.com/) for my blog, which works decently for me. It is a static site generator written in Python.
But you probably won't learn much Python by using it (or Rust when using a generator written in it) since you probably won't need to change anything in it.
The only Python code you need to write for Pelican is the configuration, which is just setting a few variables.
Pelican was one of the options I had in mind too; will consider it more seriously thanks to your recommmendation!
You know, I was wondering about that myself. I guess one of the selling points of these frameworks/products is their ease of configuration, which might mean very minimal hacking required, if any. So it's entirely possible I may not get to learn very much Python this way. Thanks for sharing your experience!
So far I just pinned the rustc version used by requiring rustup as a build dependency. Let's see if this lets me drop it or if it is still easier in the end to build with pinned version.