Live data from Hacker News

Viewing profile — bakkoting

bakkoting

HN member
Joined
Tue, Mar 08, 2016, 8:33 PM UTC
HN karma
344
Public activity
134 items

About bakkoting

TC39.

Recent public activity

  1. comment
    Comment #48979535

    Depends on exactly where you draw the line at "breakthrough", but there's been at least a few novel and interesting results coming from outside mathematicians. Recently for example…

  2. comment
    Comment #48613469

    They didn't open a PR against zig either, the compiler concurrency work they did was also only ever in their own fork.

  3. comment
    Comment #48613439

    In case anyone missed it, this PR is based on that: > This is an implementation of the design Filip Pizlo published in 2017: "Concurrent JavaScript: It Can Work!".

  4. comment
    Comment #48477440

    This used to be more common but the pattern these days is to have the binaries split into optionalDependencies which declare their supported CPU etc, one per supported platform. Th…

  5. comment
    Comment #48359080

    I have; you specify one optional dependency per platform and set the requirements in each package. It works fine. A bunch of packages do this (e.g. esbuild). I don't know what your…

  6. comment
    Comment #48358875

    They have taken action as of very recently. The latest version [1] of npm warns when there are install scripts and tells you they will be disabled by default in a future version, w…

  7. comment
    Comment #48214688

    The proposal used to do more thing and we didn't change the URL after we ultimately arrived at this set of APIs.

  8. comment
    Comment #48197696

    There's an RFC for this: https://github.com/npm/rfcs/pull/868

  9. comment
    Comment #48197653

    > most people use pre-built distributions (wheels) for their architecture from PyPI, so don't execute arbitrary code to install packages Technically true, but wheels can include a …

  10. comment
    Comment #48160755

    These things are usually caught by tools specifically scanning npm or by the maintainers noticing their account is compromised, not by people auditing their own installed packages.…

  11. comment
    Comment #48102775

    2fa being enabled for people on the team is different from 2fa being required for publishing. It is not current possible to enforce (or use) 2fa for publishing with trusted publish…

  12. comment
    Comment #47801908

    > type safety without having to transpile code from another language (so no build processes that rival C++ in complexity just to still have interpreted code at the end) All major s…

  13. comment
    Comment #47801679

    Ehhhhh basically none of those exploits generalize beyond one very specific engine and set of conditions, and half of them are things to do with interactions between JIT tiers and …

  14. comment
    Comment #47691210

    I agree that the original cancellation discussion was bad. I don't agree that these threads reflect the same disfunction. They're a new effort (from me). No one was working on it p…

  15. comment
    Comment #47679819

    Browsers have said that they are unwilling to ship any new cancelation mechanisms given that AbortSignal already exists, so we can't ship a different CancelToken. But I think there…

  16. comment
    Comment #47480072

    We haven't refused, it just takes time! There was an update at the meeting two weeks ago [1]. There's a lot of other machinery which needs to be specified and implemented before mo…

  17. comment
    Comment #47477749

    Python and Rust have such a thing, but not e.g. Java, Go, C#. And I can't find any libraries on npm which do this. That seems like a very niche need, not actually the sort of thing…

  18. comment
    Comment #47183050

    Observables has moved to WHATWG [1] and been implemented in Chrome, although I don't know if the other browsers have expressed any interest (and there's still some issues [2] to be…

  19. comment
    Comment #46673503

    Neat! I wonder how slow this would be running in wasm. In my dream world it would also use WebGPU but that's a much bigger lift.

  20. comment
    Comment #46652008

    You're thinking of a previous report from a month ago, #897 or #481, or the one from two weeks ago, #728. There's a new one from a week ago, #205, which is genuinely novel, althoug…

  21. comment
    Comment #46370658

    Formally JavaScript is specified as having TCO as of ES6, although for unfortunate and painful reasons this is spec fiction - Safari implements it, but Firefox and Chrome do not. N…

  22. comment
    Comment #46368145

    Have you seen the YoWASP toolchain for VSCode [1]? It sounds pretty similar. [1] https://github.com/YoWASP/vscode

  23. comment
    Comment #46280979

    And there's an open issue for that already: https://github.com/bearcove/arborium/issues/62

  24. comment
    Comment #46089253

    Yes. I'm on TC39 as well, and I've talked to Jordan about this topic. It's true that there are a few people who publish packages on npm including polyfills, Jordan among them. But …

  25. comment
    Comment #46081384

    This hasn't been true since version 5.4.2, released in 2017. `npm install` will always use the versions listed in package-lock.json unless your package.json has been edited to list…