any chance of this supporting wikilinks and back references?
I just added support for wiki links and back references (internal)
Show HN: Marmite – Zero-config static site generator
61–69 of 69 posts
Re: Show HN: Marmite – Zero-config static site generator
#62> cargo install marmite I'm not the only one (1) that believes this is wrong direction for cargo, and is abusing it's intent and purpose. If you want to distribute an application, there are lots of ways to do that. If it's a developer tools, for developers, `cargo install` might be suitable, sure... but I think there's a fair argument to be made that if you want a tool: git clone foo cd foo cargo install --path . Is…
I just tried `cargo binstall marmite`, but it feels (in this case?) that it was the same as doing `cargo install`. Anyway, if you have cargo (ergo, the whole rust toolchain), you might as well explicitly download the git repo, as things need to be downloaded when you do a plain `cargo install` as well. A rust-sanctioned way to get just binary builds that do not require the whole rust toolchain installed would be best…
Confirmed, cargo-binstall is not configured for Marmite, so cargo will fall back to install, and the single-binary cargo-binstall will try its heuristics which do not detect
ubuntu-latest-binary.zip or
macos-latest-binary.zip.
Re: Show HN: Marmite – Zero-config static site generator
#63Earlier quoted context omitted.
I just tried `cargo binstall marmite`, but it feels (in this case?) that it was the same as doing `cargo install`. Anyway, if you have cargo (ergo, the whole rust toolchain), you might as well explicitly download the git repo, as things need to be downloaded when you do a plain `cargo install` as well. A rust-sanctioned way to get just binary builds that do not require the whole rust toolchain installed would be best…
Confirmed, cargo-binstall is not configured for Marmite, so cargo will fall back to install, and the single-binary cargo-binstall will try its heuristics which do not detect ubuntu-latest-binary.zip or macos-latest-binary.zip.
Good catch, I will try to learn how cargo-binstall works and provide the proper binary files.
There is an open issue to improve the Github Actions CI related to build and release.
Re: Show HN: Marmite – Zero-config static site generator
#64Re: Show HN: Marmite – Zero-config static site generator
#65Earlier quoted context omitted.
Huh? Why would that be the case?
People post "Something Written in Go" all the time and no-one complains about the title, every rust post that includes that gets complaints.
Well that's sadly true, I am hopeful they'll grow up one day but who knows, there are people on HN who love their prejudice as much as they love their kids, it seems.
Re: Show HN: Marmite – Zero-config static site generator
#66Earlier quoted context omitted.
You also can't be more explicit -- and terse -- by running `cargo install ripgrep`. You said: IF you have to lookup the exact crate name. Well, for 90% of those I use, I don't have to. And it works just fine as your parent commenter said. You have a preference, cool, but don't try to push it as the better way in an objective sense because it's not. It's just one of the alternatives.
What you’re written it literally false. You have no idea what that command does. It fetches something off the internet and builds it and installs it. It is objectively less explicit than having a local folder that you have explicitly fetched, and run a build on. It is also objectively easier to make a mistake when you type a single command that fetches and installs as one step, than it is to clone, and review then bu…
It's wild you're ending all your comments with /shrug - You made a bad take, double downed, and continue to dig.
/shrug
Re: Show HN: Marmite – Zero-config static site generator
#67Earlier quoted context omitted.
What you’re written it literally false. You have no idea what that command does. It fetches something off the internet and builds it and installs it. It is objectively less explicit than having a local folder that you have explicitly fetched, and run a build on. It is also objectively easier to make a mistake when you type a single command that fetches and installs as one step, than it is to clone, and review then bu…
It's wild you're ending all your comments with /shrug - You made a bad take, double downed, and continue to dig. /shrug
[deleted]
Re: Show HN: Marmite – Zero-config static site generator
#68Earlier quoted context omitted.
What you’re written it literally false. You have no idea what that command does. It fetches something off the internet and builds it and installs it. It is objectively less explicit than having a local folder that you have explicitly fetched, and run a build on. It is also objectively easier to make a mistake when you type a single command that fetches and installs as one step, than it is to clone, and review then bu…
The command you suggest also festches something from the internet and builds it. You could just as easily typo and get someone else's git repository, and again, I'm not going and reading the source code to find out if I have the right program. I'm not reviewing the source code to ripgrep, and even if I did, I'm definately not review the code of all of it's dependancies, which are getting downloaded when I build it an…
> Also, it's not objectively easier to make a mistake when you type one command, than when you type three.
It is; because you can pause between doing those three commands. Adding a review step objectively lowers the error rate in activities. That's why we do PRs.
> I would say my error rate goes up as I type more, so I feel it's objectively easier to make a mistake with your method.
The word you're looking for is 'subjectively', not 'objectively'.
> Also, you still haven't discussed that your method does the (in my opinion) clearly wrong thing of building whatever the current state of the master branch is, rather than a release.
Use `git clone -b`... or, use a a proper package manager with support for features like parallel binary dependencies and prebuilt binaries.
Re: Show HN: Marmite – Zero-config static site generator
#69[dead]