3 ms·
> Presumably they are now "API-stable" but the page hasn't been updated yet. That's correct. i'll try my best to remember to update that reference the next tim
by sgbeal 2y ago
> Presumably they are now "API-stable" but the page hasn't been updated yet.
That's correct. i'll try my best to remember to update that reference the next time i'm back on the computer.
> It would be great if the SQLite team published an official npm package
Not a chance. We publish only vanilla JS and adamantly refuse to go down the rabit hole of supporting out-of-language tools (none of which any of our project members use). We support an "officially sanctioned" npm build, maintained by Thomas Steiner, but do not actively develop for any JS frameworks.
Direct support for any given framework (npm included) would give the impression that we endorse that framework, and endorsement of third-party projects is something we actively avoid.
- rezonant 2y ago> We publish ONLY vanilla JS and adamantly refuse to go down rabit hole of supporting the frameworks du jour A bit confused at this, NPM is just a package manager / distribution mechanism, not a framework. Totally fair if you don't want to publish for all the package managers, though for Javascript there's only a few that are relevant. NPM has been around for a decade.
- sgbeal 2y ago> A bit confused at this, NPM is just a package manager / distribution mechanism, not a framework It's an out-of-language packaging/distribution framework (and it's not the only one). It's not part of the JS standards. My comments above have been edited to reframe our stance on npm and frameworks in general.
- rezonant 2y agoI don't think there will ever be a package manager dictated by the Ecmascript standards.
- syndicatedjelly 2y agoThen ES will continue to remain an outlier among major language implementations
- sorrythanks 2y agowhat package manager is dictated by the C, C++, Common Lisp, Ruby, Prolog, Pascal... any language's standard? I am struggling to think of a single standardized language whose standard defines the package manager
- kazinator 2y agoLanguages should make it easy to use third party pieces directly, without a package manager. People actually do that, and so that status quo is maintained; any increment in the difficulty of constructing programs out of components will result in loud protests. Package managers are an anti-pattern. When the standard package manager is present, the packaging problem is regarded as solved ("just use the package manager"), and so the actual mechanisms underlying program construction are then out of the negative feedback loop and will rot.
- rezonant 2y agoSomewhat confused by this statement, I'm having trouble thinking of a language where it's hard to consume code without a package manager...
- deleted 2y ago[deleted]
- syndicatedjelly 2y agoImagine a world where your language’s package manager became a company that basically offered “Package Management as a Service”. How effective do you imagine that would be?
- samatman 2y agoI think the communication barrier here is that in JavaScript, framework very distinctly means things like React, Vue, Angular, and so on. It definitely does not refer to projects like Node/npm/Bun/Deno, those are toolchains, sometimes called ecosystems for obscure reasons. If you changed the word "framework" to "toolchain" in your post I think it would make a lot more sense to people.
- sgbeal 2y ago> If you changed the word "framework" to "toolchain" in your post I think it would make a lot more sense to people. Fair point but the edit window has passed ;). For the sake of clarity for those still following along: "framework," in the context of my above comments, includes any non-formally-standardized tools or APIs which are built atop the standardized core.