Tweetovi

Blokirali ste korisnika/cu @drosenwasser

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @drosenwasser

  1. Prikvačeni tweet
    5. velj 2018.

    "There were like 77 Levenshtein distance packages on npm and all of them said they were the fastest." - That's why the JavaScript ecosystem is great. Everything is the best.

    Poništi
  2. proslijedio/la je Tweet

    Looking for more developers who want talk about TypeScript and JavaScript in Visual Studio ? DM me :) I’m open to hearing all comments, issues, critiques and etc!!! (RT please)

    Poništi
  3. proslijedio/la je Tweet
    2. velj

    Best practices: Don't pollute the global scope. Open source devs:

    Not to worry, I have a permit.

I'm writing a test framework.
    Poništi
  4. proslijedio/la je Tweet
    31. sij

    Join Microsoft, live and work in beautiful Prague, and be a leading F# open source community tooling contributor, helping others across the world to contribute to the compiler, library and tools, and help Microsoft deliver these at high quality to users

    Poništi
  5. proslijedio/la je Tweet
    30. sij

    We’ve added official TypeScript support to our Node.js library. 🎉 You now have type errors, autocompletion for API fields and params, in-editor documentation, and much more! Get started at and catch those errors early. 📝

    Poništi
  6. proslijedio/la je Tweet
    30. sij
    Odgovor korisniku/ci

    Yes, using old computers is awful. In fact, on rare occasions it can be nearly as terrible as using modern computers.

    Poništi
  7. proslijedio/la je Tweet
    28. sij

    Tell me something unbelievable about JavaScript

    Prikaži ovu nit
    Poništi
  8. 29. sij

    Me on GitHub: please file actionable issues in good faith and have empathy Me on Windows:

    Poništi
  9. proslijedio/la je Tweet
    27. sij

    I'm looking for JavaScript developers using webhooks and to provide feedback on a new abstraction that aims to make webhooks a little easier to use. Interested? Let me know, DM me, or ping me at auchenberg@stripe.com (RT = 💖)

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet
    23. sij

    We are migrating to and found some blockers. Very pleased to see quick resolution and fixes in the TypeScript compiler, making future JS -> TS easier! Hopefully we can provide guidance when we are finished, for others who want to do the same.

    Poništi
  11. proslijedio/la je Tweet
    23. sij
    Odgovor korisnicima

    ExCuSe mE itS a VeRy WelL AcCePteD FaCt

    Poništi
  12. proslijedio/la je Tweet
    21. sij

    ECMAScript excitement 😉 Congrats to on landing TC39 Stage 4 proposal Optional Chaining (?.) in upstream SpiderMonkey. Heading for Firefox 74. Thanks for the reviews from Tooru Fujisawa

    Poništi
  13. proslijedio/la je Tweet
    21. sij

    and then one day the dev came back, and the git repo shook with joy, and said, “come, Dev, and clone my trunk, and pick my cherries, and check out my branches, and be happy”

    Poništi
  14. proslijedio/la je Tweet
    20. sij

    I rewrote my TypeScript code formatter from TypeScript to Rust and I'm quite happy with its performance on single files so far. For a certain 37K line 2.11MB file it takes less than a second on my machine.

    Prikaži ovu nit
    Poništi
  15. proslijedio/la je Tweet
    20. sij

    “Let’s hear it for the oys” sounds like a Weird Al Yankovic parody of Footloose meets Fiddler on the Roof

    Poništi
  16. proslijedio/la je Tweet

    Having a bit of late night fun in the TS compiler and I stumbled upon the gem that is `FlowNode.__debugToString`. It print the CFA graph for a node. Definitely a game changer with regard to my understanding of CFA magic 😁

    Poništi
  17. 17. sij

    Notice, the use-cases don't include "smaller bundle sizes" or "avoiding accidentally importing a huge dependency" because we were already dropping imports that you weren't using at runtime before.

    Prikaži ovu nit
    Poništi
  18. 17. sij

    Using `import type` everywhere you can quickly becomes painful. Upcoming changes we're making will alleviate that, but it can be very annoying when you have to manage two kinds of imports constantly.

    Prikaži ovu nit
    Poništi
  19. 17. sij

    Reason 2 is useful if you want to turn off import elision. Maybe your modules have side-effects (e.g. projects using the older Angular.js 1.x). Or maybe you have an ideological issue with import elision. But be careful, you might be signing up for more pain than you realize!

    Prikaži ovu nit
    Poništi
  20. 17. sij

    Reason 1 was the motivation for the feature. People had to bend over backwards to re-export types in Babel or under isolatedModules. Seems bad! That's an expressivity gap for a lot of users!

    Prikaži ovu nit
    Poništi
  21. 17. sij

    You need them when 1. you hit an issue when you need to emit files independently (e.g. Babel, isolatedModules, transpileModule) 2. you are dead-set on turning off import elision for whatever reason

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·