@GergelyOrosz I read the OP and almost got mad because I thought you might've been referring to a friend's similarly themed product, which launched today. @alpine4work has been dogfooded from day 1.
@AndaristRake@kettanaito@BookSpotlight I recently finished The Broken Earth trilogy by N.K. Jemisin and it was fantastic. Truly worthy of all the accolades. I could also say the same about the Remembrance of Earth's Past trilogy (Three Body Problem).
@robpalmer2@jitl I can't speak to the frequency, but At Airtable, we wrote a custom lint rule that would automatically fix these to use an internal `pushIterableToArray` utility function with the same behavior as `Array.prototype.pushAll`.
@typesanitizer As a mostly readonly consumer I find bsky posts to have much more engagement. The people I follow on mastodon sometimes feel like they're speaking into an echo chamber
@SeaRyanC@drosenwasser@andhaveaniceday I think a valuable abstraction is something like a database of all the nodes. Not saying you can just stick them into SQLite and call it a day, but something that would facilitate arbitrary type queries would be good not just for building LSPs but also like type-aware lint rules.
The question I'd like to see answered is if this unlocks more efficient serialization of types more easily. In large composite projects the overall time spent parsing declaration files is non-negligible. Even if that step got 10x faster could it be 100x if it was a binary format?
@robpalmer2@TC39 I know things like polyfills depend on these mechanisms but I would think it's possible to introduce new blessed ways to do those things without relying on problematic functionality.
@robpalmer2@TC39 It's been longer since now and when "use strict" was introduced than when "use strict" was introduced and JS was created. Like how about a "use resolute" pragma that prevents mutating runtime builtins and object prototypes? Is that unreasonable?