I don’t get why the RFC show an example returning 403 with body “You do not have enough credit.” although there is a dedicated status code " 402 Payment Required". Isn’t more correct to use 402 in this situation?
I don’t get why the RFC show an example returning 403 with body “You do not have enough credit.” although there is a dedicated status code " 402 Payment Required". Isn’t more correct to use 402 in this situation?
So which one are you using ?
I tried Helix but my muscle memory around Vim movements was a non - starter for me. Also , Helix wasn’t working out of the box with Vue.JS (it needs to be tweaked a bit.
So I gave a try to LazyVIM and everything works almost as is. I’ll never look back.
The video mentions some “de facto” standard libraries like Lodash or Underscore. But there is also Bun which try to promote their standard library like their test runner, their HTTP server, etc…
I like Deno’s approach, since they try to make their “Standard library” also available for other platform. But only few of them are compatible with Node.js.
For instance, @std/cli
is only available for Deno. So I’ll stick with commander which is more standard for CLI tools, and it works with Deno, Bun & Node.js.
my two cents,
I personally buy some music from Bandcamp, and I’m pretty sure those songs don’t exist on the Apple Music catalog. So I don’t want to handle multiple apps to listen what I want.
Also, streaming platforms have the internet constraints. Sometimes, like when I’m driving, I don’t have a stable internet connection
Recompress to a lossless format (…) There is very little reason for you to do this
I though there are no reasons at all to do it. What could be a valid use case for this ?
You can get pretty far using a bit of JS and Tamper Monkey . You can even search in existing user scripts if someone already did it.
I installed it on a cheap VPS a few years ago, and it just works. I never had to do any maintenance. I love it
I guess it is https://en.wikipedia.org/wiki/Turtle_(syntax)