Yarn, pnpm, webpack all have solutions for this. Great to see this becoming a standard. I have a project that is severely handicapped due to FS. Running 13k tests takes 40 minutes where a virtual file system that Node would just work with it would cut the run time to 3 minutes. I experimented with some hacks and decided to stay with slow but native FS solution.
What I really want is a way of swapping FS with VFS in a Node.js program harness. Something like
node --use-vfs --vfs-cache=BIG_JSON_FILE
So basically Node never touches the disk and load everything from the memory
The way to do this today is to do it outside of node. Using an overlay fs with the overlay being a ramfs. You can even chroot into it if you can't scope the paths you need to be just downstream from some directory. Or, just use docker.
yes and no. Waiting 40mins for every test run is pure pain, platform specific ramfs type mounting is quite scriptable. Yes some devs might need to install a dependency, but its not a complex script.
I've done some work on compression really long ago but I am very far from an expert in the field, in fact I'm not an expert in any field ;) The best I ever did was a way to compress video better than what was available at the time but wavelets overtook that and I have not kept current.
I'm curious about two things:
- is it really that much better (if so, that would by itself be a publishable result) where better is
- not worse for other cases
- always better for the cases documented
I think that's a fair challenge.
- is it correct?
And as a sidetrack to the latter: can it be understood to the point that you can prove it is correct? Unfortunately I don't have experience with your toolchain but that's a nice learning opportunity.
I think the copyright issue is the bigger one to solve, you can't really contribute it anywhere because you don't actually own it. You'll need to convince potential users somehow that you're in it for the long haul and not having ownership is going to put the brakes on distribution.
I thought this too. If they're using the camera to do brightness, it needs to be on when the user isn't using it - if the activity LED is tied to the camera power rail (not sure if it is), it might look like there's something nefarious going on. No way Apple would let that go out the door.
Yes, but as a producer I would like to have more simplistic generations such as "Generate me 15 variations of a kick that sounds like X", I think stuff like this would be much more useful.
What I really want is a way of swapping FS with VFS in a Node.js program harness. Something like
So basically Node never touches the disk and load everything from the memoryreply