Nathan Shively-Sanders

@sanders_n

Programmer, linguist, dad, Christian. Expect tweets on type systems, video games or dialectology. Tweets are my own. Always bet on Javascript. He/him.

Joined June 2010

Tweets

You blocked @sanders_n

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @sanders_n

  1. Jan 22

    Tip: blocking the bus to get out of your car when you’re late does NOT guarantee you a seat, even if you’re super late.

    Undo
  2. Jan 16

    downlevel-dts now downlevels Typescript 3.8 d.ts files so you can *write* TS 3.8 code but *ship* types that are compatible with 3.5 and earlier. Check out the source at If you're interested in using it, please tell me. I need usability feedback!

    Undo
  3. Jan 6

    I forgot, you can browse all 6,300+ packages with GH's UI: It's pretty barebones and a bit buggy right now.

    Show this thread
    Undo
  4. Jan 6

    Eventually, VS Code's Automatic Type Acquisition will use Github Packages to acquire for JS projects. Full details are here:

    Show this thread
    Undo
  5. Google's starting to shame me because I can't remember URLs:

    Undo
  6. Follow-up to and : typescript@next now supports in Javascript, which behaves the same as readonly in Typescript: class C { /** */ x = 1 }

    Undo
  7. Or Slack. Sometimes they think I work on Microsoft Slack.

    Show this thread
    Undo
  8. (I don't actually say "compiler engineer" at parties -- non-technical people leave with the impression that I helped Microsoft make Office 365 or Skype or something.)

    Show this thread
    Undo
  9. All the people who are using Typescript to solve real frontend/backend problems can contribute their knowledge of things we have never worked with.

    Show this thread
    Undo
  10. Looking at the Demographics section of the state of JS survey and for me: * CSS proficiency: None. * Backend proficiency: Beginner. * How do you introduce yourself at parties? "Compiler programmer" That mismatch is why being open source is so valuable for Typescript.

    Show this thread
    Undo
  11. `this.x` is fine in the same method. Anyway, if you *do* use classes in JS a lot, try out typescript@next and let me know what you think.

    Show this thread
    Undo
  12. Also, today I learned that this isn't allowed in Typescript: class D extends C { /** {C} c */ m(c) { c.x } } ^ Property 'x' is only accessible through an instance of class 'D'. I rarely use classes, so this rule was a surprise to me.

    Show this thread
    Undo
  13. typescript@next now supports and in Javascript files. They work the same as in TS: class C { /** */ x = 1 }

    Show this thread
    Undo
  14. 16 Dec 2019

    If you have the privilege to do so safely, it is incumbent on all of us to film the police whenever they're doing *anything at all*, because this kind of thing can happen at any time in any place.

    Undo
  15. Top ten Definitely Typed packages, by size on disk: 25.9dojo 13.7echarts 6.0fhir 5.2activex-libreoffice 4.9arcgis-js-api 4.8winrt-uwp 4.0openui5 4.0office-js-preview 3.9ignite-ui 3.8office-js (units: millions of bytes)

    Undo
  16. Reminder: The "backlog" tag on the Typescript repo means "No help has come. No help will come. No help can come, only what you yourself provide. May God have mercy on your soul."

    Undo
  17. Optional Chaining just moved to Stage 4 at TC39! 🎉 ?. is now part of ES2020!

    Show this thread
    Undo
  18. More like "DERP-endencies"

    Undo
  19. Show this thread
    Undo
  20. Every Typescript reference page I've written uses the same basic outline: 1. Simple Warm-up Feature. 2. The Important One I Hope You Remember. 3. This One's For Historical Reasons. 4. Here's a Weird Thing We Let You Write. 5. Please Never Use This.

    Show this thread
    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·