Live data from Hacker News

Viewing profile — inbx0

inbx0

HN member
Joined
Mon, Sep 28, 2020, 1:11 PM UTC
HN karma
439
Public activity
113 items

About inbx0

No profile information was provided.

Recent public activity

  1. comment
    Comment #49256733

    I’m happy for the author, but I feel like that blog post kind of supports parent commenter’s argument. It sounds like Slug would’ve been created even if patents were not a thing. T…

  2. comment
    Comment #48906128

    Simply hosting a front-end only app is almost free on several platforms (e.g. Cloudflare). Certainly less than the $99 Apple developer membership fee. It starts getting more expens…

  3. comment
    Comment #48843908

    What do you mean by runtime? The JavaScript runtimes, like V8? Yeah those are impressively fast for a dynamically typed ”scripting” language, but that has little to do with TS. Typ…

  4. comment
    Comment #48761687

    For me, the main benefit is deployment bundle/artifact size reduction. Mostly from dropping unneeded files from node_modules. Many packages include both esm and cjs builds, sources…

  5. comment
    Comment #48321296

    It's an interesting discussion, but I think simply outputting text can make the software "malware", even if the output isn't executable. What if the output was To use jqwik, please…

  6. comment
    Comment #48015366

    Reminds me of the back and forth competition between Node.js and io.js that we had to endure back in the day. Worked out for the best in the end.

  7. comment
    Comment #47590757

    minimumReleaseAge and lockfiles also pin down transitive dependencies.

  8. comment
    Comment #47585863

    Number 1 would only be a win for zero-installs if it happened that registry was up when you made the security hotfix, since you'd need to install the depdencency the first time to …

  9. comment
    Comment #47584146

    > Run Yarn in zero-installs mode (or equivalent for your package manager). Every new or changed dependency gets checked in. Idk, lockfiles provide almost as good protection without…

  10. comment
    Comment #47334068

    - saves infra costs - saves infra headaches - devs only need to be experts in one system (or well I guess one and a half, probably there's something to learn about ParadeDB too, bu…

  11. comment
    Comment #45970607

    At TypeScript-level, I think simply disallowing them makes much more sense. You can already replace .push with .concat, .sort with .toSorted, etc. to get the non-mutating behavior …

  12. comment
    Comment #45810084

    I don't have much experience in dedicated vector databases, I've only used pgvector, so pardon me if there's an obvious answer to this, but how do people do similarity search combi…

  13. comment
    Comment #45500144

    Ehh what. I would give some merit to arguments like "no one should use lodash in 2025 because you can do most of it with built-ins nowadays" or maybe because it doesn't tree-shake …

  14. comment
    Comment #45467848

    The post links to a TS issue [1] that explains > As of TypeScript 5.0, the project's output target was switched from es5 to es2018 as part of a transition to ECMAScript modules. Th…

  15. comment
    Comment #45276771

    I don't think pinning deps will help you much, as these incidents often affect transitive dependencies not listed in package.json. package-lock.json is there to protect against aut…

  16. comment
    Comment #45272062

    The main issue there is that the maintainer lost access to their account. Yanking malicious packages is better, but even just being able to release new patch versions would've stop…

  17. comment
    Comment #45248833

    fzf [1] provides the TUI. 1: https://github.com/junegunn/fzf

  18. comment
    Comment #45045383

    According to the description in advisory, this attack was in a postinstall script. So it would've helped in this case with nx. Even if you ran the tool, this particular attack woul…

  19. comment
    Comment #45040282

    Periodic reminder to disable npm install scripts. npm config set ignore-scripts true [--global] It's easy to do both at project level and globally, and these days there are quite f…

  20. comment
    Comment #44796973

    My guess would be because they affect property ordering, complicating the stringification. The default object property iteration rules in JS define that numeric properties are trav…

  21. comment
    Comment #44720611

    SeaQuery looks like a similar dynamic query builder for Rust as Kysely is for JS/TS, so yeah, that'd probably solve the dynamic query problem. But I think parent wasn't so much ask…

  22. comment
    Comment #44614560

    To quote a TV show Community character Jeff Winger: > What makes humans different from other animals? We're the only species on earth that observes Shark Week. Sharks don't even ob…

  23. comment
    Comment #43562671

    Yes. And that is what a client should 100% do from the security standpoint. But since you mention caching - from the perf standpoint, it could sometimes be beneficial for the query…

  24. comment
    Comment #43312171

    They seem to be measuring things like how long it takes for the dev server to spin up, and how long HMR updates take. I don't think ESBuild offers these features out of the box. I …

  25. comment
    Comment #43230564

    Does the JSON spec actually say that those objects should be "equal", or does it just leave that detail to implementations? In JavaScript at least, those two are not exactly "the s…