IsaacSchlueter

18 ms·

1.
by IsaacSchlueter 1y ago
Yeah, I got scooped. Was busy crying. It's fine though, I wrote this for therapeutic benefit, not social media clout.
2.
Remembering Mikeal Rogers(blog.izs.me)
2 points by IsaacSchlueter 1y ago|2 comments
3.
by IsaacSchlueter 1y ago
Mikeal Rogers was a prolific Node.js developer and community leader. He created the popular "request" library, ran the initial NodeConf events, helped design the npm registry, and provided a strong leadership that helped get Node.
4.
by IsaacSchlueter 1y ago
That trip is the origin of many of my happiest memories. It was amazing to meet you all, and to share that adventure with him. The playnode.io team and the Korean JavaScript community treated us with such incredible warmth and kindness, we
5.
by IsaacSchlueter 3y ago
100%. The main reason we created https://priceops.org is that there's a real mind-shift that has to happen for someone to realize that there's even a "there" there. Most people who've been through it und
6.
by IsaacSchlueter 3y ago
> written entierly by Isaac I see what you did there ;)
7.
by IsaacSchlueter 3y ago
I enjoy tutorials like this, in the same way and for the same reasons that I enjoy videos where people make cutting tools out of obsidian that they chip by hand. Personally, though, when I have to actually cut something, I use stainless ste
8.
by IsaacSchlueter 4y ago
Many startups will go out of business because they don't address this concern. Startups have extremely little information to guide their pricing and packaging decisions, and often find right away that they've just picked the wro
9.
by IsaacSchlueter 4y ago
Take the data point for what it's worth (ie, not much). I have never found these chat popovers useful, I have always found them obstructive, and I have always been seething with resentment when forced to use one for an interaction with
10.
by IsaacSchlueter 4y ago
Just to clarify: > This is reasonably fast, but if it's uncached, it is an API call to Stripe It will be cached after the first request you make with the sidecar/SDK, and unless you have a truly impressive number of users, it
11.
by IsaacSchlueter 4y ago
I just played around with the NextJS starter demo app, and it seems like you can `import tier from 'tier'` and call `tier.subscribe()`, `tier.report()`, and `tier.limits()` without any issue in a NextJS API route.
12.
by IsaacSchlueter 4y ago
I am not super familiar with NextJS, but I'll take a look. The Node SDK is a pretty standard Node library (not clientside JS, for probably obvious reasons). It does spawn a child process if it isn't given a TIER_SIDECAR environme
13.
by IsaacSchlueter 4y ago
> You see a hundred blog posts of "why you should experiment with your pricing", but actually doing that is often such a pain that nobody ends up doing that (and admittedly the reason why I would have shied away from such proje
14.
by IsaacSchlueter 4y ago
I completely agree. Whoever[1] made that page should probably not be allowed to make web pages without the assistance of a real designer. [1]: me. I'm talking about me.
15.
by IsaacSchlueter 4y ago
I don't think that's 100% accurate implementation-wise, but the gist is definitely correct. Basically, yes, owing to the way that these things have to get mapped into Stripe's objects, having a plan without any features woul
16.
by IsaacSchlueter 4y ago
Ah, I somewhat misunderstood your previous comment, my apologies. This could certainly be clearer in documentation and the priceops.org presentation, I'll take the note on that and think about how to make it more clear. When we say &q
17.
by IsaacSchlueter 4y ago
> Might be wrong, but brief review of this appears to show the “thesis” of PriceOps is yield-based metered feature pricing The "thesis" of PriceOps is less "you must have metered feature pricing", and more "you s
18.
by IsaacSchlueter 4y ago
Grandparenting in old accounts is baked into the system. Plans are immutable[1] once pushed live, so if you add a new plan and put it on your signup page, new customers will use the new plan, but existing customers will keep on with the
19.
by IsaacSchlueter 5y ago
True story, the npm registry was once taken down (not maliciously, just by accident) by a ReDOS in node-semver. That was extra fun to debug because the failure happened inside of CouchDB.
20.
by IsaacSchlueter 5y ago
> I've been in the node scene since 0.10. That's around 10 years. My packages have billions of downloads annually. My viewpoint here carries the weight of hours of debug time and frustration and confused users of my code, as we
21.
by IsaacSchlueter 7y ago
Your take on the installer in npm v6 is not wrong. It got that way by a process of gradual iterative evolution, and it has lots of warts. npm v7 features a ground-up rewrite of the tree resolution and deification logic in the @npmcli/a
22.
by IsaacSchlueter 7y ago
Yes, this has always been possible. Just specify the tarball url instead of a version or range.
23.
by IsaacSchlueter 8y ago
You might be surprised (or maybe not) to learn that many service providers are far more willing to spend money on predictably large bandwidth bills than on less predictable changes in their infrastructure which require human time and attent
24.
by IsaacSchlueter 8y ago
If you run `npm install` with an argument, then you're saying "get me this thing, and update the lock file", so it'll do that. `npm install` with no argument will only add new things if they're required by package.
25.
by IsaacSchlueter 8y ago
If you run `npm install` with no arguments, and you have a lockfile, it will make the node_modules folder match the lockfile. Try it. $ json dependencies.esm < package.json ^3.2.5 # package.json would allow any esm 3.x &gt
26.
by IsaacSchlueter 8y ago
It's been a few years since I was directly involved in engineering, but my fairly educated understanding is that it's more around reading of possibly-private packages than publishing. Publishing is a relatively rare event compared
27.
by IsaacSchlueter 8y ago
This highlights the problem of averages. Most (99.87% or so) humans download zero npm packages. But those that do, often download them in the thousands at a time. And yes, clean-room CI servers are a big part of that.
28.
by IsaacSchlueter 8y ago
I mean, we still write the overwhelming majority of our code in JavaScript. We port to Rust when CPU-heavy task becomes a bottleneck to the rest of the system. It's not as if this paper is saying (nor is it the case) that we've
29.
by IsaacSchlueter 8y ago
That is incorrect. Both `npm install` and `npm ci` respect the lock file, and if a lock file is present, will make the `node_modules` tree match the lock file exactly. `npm ci` is optimized for a cold start, like on a CI server, where it&#
30.
by IsaacSchlueter 9y ago
That's great to hear! Reliability sure was tough in those days. npm wasn't secondary or tertiary or any-ary to Joyent. It was my nights and weekends project the whole time I was there, and IrisCouch generously donated infrastruc

More ›