alexgrover

Any photographer who pretends to not understand what the term “full frame” is referring to is an asshole.

There are so many examples of large companies and open source projects that have moved off of npm that I just don’t think this is true anymore. PNPM and bun are fast enough that the increase in development velocity is worth the occasional rough edge IMO.

Alternative options include Rectangle (free and open source) and Raycast which is a Spotlight replacement but also includes window management

Yes, there’s a large group of users that use 3rd party apps like Apollo

I think the point they’re trying to make is that the “open” command does something very different than the Mac builtin

The moat comment depends on the company, not all or even most businesses depend on actual innovation as their moat.

Also, I think we’re agreeing here, but there are a huge set of things that you may need to build an application that aren’t the core value prop of your company. Buying into a more mature ecosystem makes it more likely that you don’t have to build those things and can spend more time on the moat stuff.

I doubt the reservation is with the language/runtime itself, especially with elixir and the BEAM. More likely, it’s with the maturity of the community. Especially at a small startup, building on elixir even today might still mean having to build things in house you may not in Django/Rails/JS.

In my corner of Twitter there’s no correlation between any of those.

Many/most people don’t though. Dataloader libraries exist for a reason.

All of those problems and solutions are not unique to either tech choice. You can use OpenApi for documentation, a variety of libraries like React-query for caching, and N+1 issues exist (and are arguably more complicated to solve) in graphql.

Coming back to this after the other thread cooled down a bit lol - to me, unknown actually implies that the function doesn’t care about the values more than any, as the compiler will enforce that they’re unused.

And in any case, I’d almost always lean towards the option with stronger type safety guarantees. Especially in a team environment when someone else may be modifying your code later. As a convention, I almost never use any.

The problem with that is that when consuming of the dictionary, “doesn’t know” is actually more appropriate. If you then access Object.values(foo) in your method you are given an iterable of anys which is unsafe.

Well, no longer free on Heroku, but it was

Why would they be missing out? Vercel can host static sites just fine, whether that’s one generated by Next or any other framework or written by hand