Live data from Hacker News

Viewing profile — wperron

wperron

HN member
Joined
Sun, Sep 13, 2020, 4:39 PM UTC
HN karma
84
Public activity
29 items

About wperron

No profile information was provided.

Recent public activity

  1. comment
    Comment #32990696

    Actually the most apt comparison here is if Bob sends over a contract for $1000, but then goes "oh no I'm sorry, I really meant $800" There are not takebacks here. Actually, I know…

  2. comment
    Comment #31828745

    If you're not following those companies' offerings then it stands to reason you haven't heard about it but all three of them did broadcast pretty widely that they were using Deno, …

  3. comment
    Comment #31828492

    It's not a hot take, it's just a bad take, and a complete failure to understand the value proposition of these types of offerings (and why we're seeing so many of them pop up these…

  4. comment
    Comment #31828341

    Has been possible (and surprinsingly easy) for a while through CDNs like skypack or esm.sh

  5. comment
    Comment #31828322

    Netlify, Supabase and Slack whitelabelling Deno Deploy for starters, I'm sure there are others out there self-hosting as well

  6. comment
    Comment #31211041

    It's really not, and it's even saying so explicitly in the article.

  7. comment
    Comment #30294636

    The whole conversation is a bit hard to follow, there was an issue initially, then this PR and then another Discussion that's linked somewhere in the PR. I'll let you go read those…

  8. comment
    Comment #30292900

    Hi, I'm one of those people in the PR advocating for this change :) I think you may have missed the point of comparing the security aspects to NPM. By saying "it's no less secure" …

  9. comment
    Comment #30292589

    If you actually read the (admittedly long) thread, it's pretty clear that those imports are not resolved at runtime, and Deno has never evaluated imports at runtime either. Depende…

  10. comment
    Comment #28279000

    > I’d argue URLs are fine until you get massive use of a single package and it weaves itself into a complex dependency tree across multiple other critical projects. Then you worry …

  11. comment
    Comment #28276045

    deno.land/x is _not_ a central registry. It's something we maintain as a convenience to the community, but we actually go to great lengths to make sure it doesn't receive preferent…

  12. comment
    Comment #28275955

    yeah, it's a bit awkward and you have to dig through the docs to find it. We're thinking about making it the default behavior.

  13. comment
    Comment #28275374

    Transpiling TS to JS on startup does incur a cold start penalty, you can minimize it by using the `--no-check` option to transpile with SWC instead of TSC but it's still there. On …

  14. comment
    Comment #27603206

    > Prometheus has a pull model, which I can see the appeal of, but I don't really like. That's such an antiquated statement at this point. Prometheus might have been pull-only in a …

  15. comment
    Comment #26824021

    Whenever someone tells me "it's just syntax sugar, it doesn't matter" I usually point them to mathematics. This is both beautiful and horrifying in equal measure and _I love it_

  16. comment
    Comment #26798875

    There's a couple of reasons. Internally, there's quite a few things that we do in Rust that aren't actually taken care of by TypeScript -- Having our own LSP allows us to connect t…

  17. comment
    Comment #26798794

    Pro tip: don't import those libs from deno.land/x. The runtime is agnostic to where you're pulling libs from, and that's by design. The AWS SDK v3 for example works great through t…

  18. comment
    Comment #26798689

    Sorry you've had this experience -- the LSP is improving a lot with every release, this one included, try it out and let us know what you think. We really appreciate issues for the…

  19. comment
    Comment #26798659

    The canonical answer is _maybe_. If your Node lib relies on Node built-ins, you won't be able to import it directly from GitHub for example. However, CDNs like Skypack and esm.sh d…

  20. comment
    Comment #26633859

    Thanks for reporting, we recently moved our blog to deno.com/blog and haven't updated the post -- we'll fix that as soon as possible

  21. comment
    Comment #26625533

    Insofar as we take `.ts` files seamlessly yes -- though to be clear, one does not simply "run" TypeScript. There are no runtimes for TypeScript directly (there's AssemblyScript tha…

  22. comment
    Comment #26622908

    We most certainly did not, TypeScript is and continues to be a primary concern for us and we plan on continuing to support it as a first-class citizen of the ecosystem

  23. comment
    Comment #26620802

    _If_ the browsers do get a std lib akin to what we've built for deno, I would be comfortable archiving the deno_std repo and pointing people to use the browser one. We're not yet 1…

  24. story
    Ask HN: Examples of NPM unilaterally removing packages

    Hey, I'm writing an article on the state of dependency management in general but with a focus on the JavaScript community. I think we've all heard here and there than npm sometimes…

  25. comment
    Comment #25375263

    It's important to remember that while, yes, CommonJS made Node popular, it did so because it filled a void in the Javascript syntax and specs. There was nothing to formalize the co…