Madeindjs
Madeindjs on Hacker News
I found a tool named [Lossless Audio Checker](
https://losslessaudiochecker.com) : "A utility to check whether a WAVE or FLAC file is truly lossless or not".
I was so sad that this project is not open-source but their Research papers give some interesting clues about detecting bad quality files.
On my side, I used it through a [Bash script](https://gist.github.com/madeindjs/d5e3949313b141f2e5eea62b98...) to detect bad files in my library. The tool produces a lot of false positives since it triggered on some High Res audio musics I bought on Qobuz.
If I got it right, naming all our files with the extension `.mjs` solves the issue as well, right ?
I'm a Ntfy user and I really love this tool! Thank you so much for your work
Why should not use a simple database instead ?
I see an horizontal scroll because of a code block containing a non wrapped URL
I thought the same thing. As a Node.js dev, I can quickly create a .mjs file and use a `module.export` to return a JavaScript object who contains the configuration. Thus, i can use template string and/or function to do what I want. I can even load JSON files natively
I made basics bash scripts to do some simple stuffs. Scripts I use more often are:
1. A script who help me to make conventional commits name (ex: `feat(xyz): add some stuff. JIRA-ID`). It add Jira Id at the end using git branch, get scope using path of the folder and ask me the rest
2. Create a markdown file for the day as worklog. An another script create markdown file for the Jira issue that I work on and add a wikilink on the worklog
3. Read scripts in package.json and ask me what I want to execute using fzf
I try to do more and more since it's really useful and I had some fun to made them.
But I imagine that you want to sit at 25°C all day long during the winter...
As a developer, I love JavaScript ecosystem for some of theses drawback of this package manager.
I'm be able to quickly publish a library on NPM and this is great IMO. Few years ago, I tried to do it for Maven in Java and it was a nightmare.
> We don't need two million packages. We probably don't even need two thousand.
I don't think so. There are many tools, frameworks and libraries in JS and I love that. I learn from all of them and this is exciting. I don't want an ecosystem with only JQuery to do all I want. Sometimes I may use Vue.js, sometimes Angular or React... and that's great.
This is a really great resource. All of theses tips are implemented in Nest.js framework. I can't recommend enough to give it a try, it'll force you yo have best practices.
With plaintext you can do what you need. For example, with todo.txt context are just prefixed by `@`. You can also add special tag with `key:value`. So for example you can add `location:paris` and retrieve it with whatever search tool.
JavaScript now include workers and with Node.js have Worker threads. I am pretty sure that MS guys use it into VSC.
I thought that author of Faker don't ask a new maintainer, he just ask for money. So I think this point is valid.
A maintainer role could be to just accept some occasional pull request if he don't want to make it a bigger project.
I use it since many years and I could not use anything else. I installed it on my girlfriend's phone (non techie person) and she also loves it.
Did you give a try of Deno. This is a JavaScript runtime but it produce a single binary. This would make sense in your case because it can be harder to inspect it.
I had a black page with JavaScript disabled. You should at least display a message "please enable JavaScript".
I not totally agree with this. Architecture is really important because it can make new feature less expensive in term of development. If you judge a work only in terms of final product UX, you miss this point.
Is it equivalent to initialize Git repository in $HOME ?
You totally miss point of this article: Markdown, even if not so powerful, have many more tools and support than other markup language (including org-mode)
I not agree for all theses points but some of those are very good advices. IMO best of those are
> (25) If you have decided to rewrite a component/service always rethink your decision. It is harder to read code than to write it, that's why "I should rewrite it!" is very common in software development.
So maybe come back to old BlackBerry with physical QWERTY keyboard?
It works until you try using a library not available with Sprocket...
Why did you choose Demo over Node.js? Is this making performances improvements?