8 points | by ccheshirecat a day ago ago
2 comments
On a little tangent here, but:
- solid intro text of pain points. Best of luck with the launch.
I think it would be great to see an archive of solid intro texts like that somewhere. It could look something like this:
https://www.orangecrumbs.com/hn/?feed=show&story=49046973
but with per-product:
- live site window
- guest book
- demo that combines with face shot to shift attention when the screen is unchanging. EG https://www.pause.build/
- API overview
- AppImage link or some kind of "execute instance of this program in your browser"
- consult with me or users now - that could be hustle-type work and can really extend beyond software launches.
Namespaces, cgroups, mounts, and seccomp account for only 3ms of your 30ms cold start, and exec plus runtime init is 22ms. Is that 22 about the floor for full Node compatibility, or is there still room to cut it?
On a little tangent here, but:
- solid intro text of pain points. Best of luck with the launch.
I think it would be great to see an archive of solid intro texts like that somewhere. It could look something like this:
https://www.orangecrumbs.com/hn/?feed=show&story=49046973
but with per-product:
- live site window
- guest book
- demo that combines with face shot to shift attention when the screen is unchanging. EG https://www.pause.build/
- API overview
- AppImage link or some kind of "execute instance of this program in your browser"
- consult with me or users now - that could be hustle-type work and can really extend beyond software launches.
Namespaces, cgroups, mounts, and seccomp account for only 3ms of your 30ms cold start, and exec plus runtime init is 22ms. Is that 22 about the floor for full Node compatibility, or is there still room to cut it?