Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
mathias's profile
Mathias Bynens
Mathias Bynens
Mathias Bynens
Verified account
@mathias

Tweets

Mathias BynensVerified account

@mathias

I work on @ChromeDevTools & @v8js at Google and on ECMAScript through TC39. ♥ JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.

Munich, Germany
mths.be
Joined January 2007

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. craig martin‏ @thecraigmichael 9 Nov 2018
      • Report Tweet
      • Report NetzDG Violation

      @BrendanEich ...why? `new Date('2018-01-01') => Sun Dec 31 2017 19:00:00 GMT-0500 (EST) So don't 0 pad month? `new Date('2018-1-01')` => Mon Jan 01 2018 00:00:00 GMT-0500 (EST) But then: `new Date('2018-10-01')` => Sun Sep 30 2018 20:00:00 GMT-0400 (EST)

      4 replies 0 retweets 0 likes
      Show this thread
    2. BrendanEich‏Verified account @BrendanEich 9 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @thecraigmichael

      What are you testing in? > new Date('2018-01-01') 2018-01-01T00:00:00.000Z is what Node.js says.

      1 reply 0 retweets 3 likes
    3. craig martin‏ @thecraigmichael 9 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BrendanEich

      Oh yeah! Hmmm.. I ran into this (and subsequently tested it) in Chrome.pic.twitter.com/wVgDFN7mIC

      1 reply 0 retweets 1 like
    4. BrendanEich‏Verified account @BrendanEich 9 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @thecraigmichael

      What version of Chrome? cc: @domenic

      2 replies 0 retweets 0 likes
    5. craig martin‏ @thecraigmichael 9 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BrendanEich @domenic

      This is probably (?) not surprising, but using node's inspect utility, the correct date is printed in the terminal, but not in the v8 Inspector 🤷‍♂️pic.twitter.com/jiPBYWyv6t

      2 replies 0 retweets 1 like
      Mathias Bynens‏Verified account @mathias 9 Nov 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @thecraigmichael @BrendanEich @domenic

      Both those strings represent the same date. On the left: `.toTimeString()` On the right: `toISOString()`

      8:08 PM - 9 Nov 2018
      • 6 Likes
      • Wang Zuo Marvin Hagemeister ⚛️ 🇩🇪 Eduardo Nogueira craig martin Guy Balaam Rob Palmer
      2 replies 0 retweets 6 likes
        1. New conversation
        2. craig martin‏ @thecraigmichael 10 Nov 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @BrendanEich @domenic

          craig martin Retweeted craig martin

          Oh yeah! So the node v chrome thing was a red herring. Going back to the original Q, the dates from `2018-01-31` and `2018-1-31` are inconsistent. EG `new Date('2018-9-15') .getDate() != new Date('2018-10-15') .getDate()` (whether node or chrome) Why?https://twitter.com/thecraigmichael/status/1061036620231651329 …

          craig martin added,

          craig martin @thecraigmichael
          Is it because '2018-01-01' and '2018-01-01' is ISO 8601 format (and so the date is created for UTC, offset back my TZ and so to the previous day), while '2018-1-01' is not (and so created for my TZ)?
          Show this thread
          1 reply 0 retweets 1 like
        3. Mathias Bynens‏Verified account @mathias 10 Nov 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @thecraigmichael @BrendanEich @domenic

          Mathias Bynens Retweeted Mathias Bynens

          Date parsing is specified to be implementation-dependent for input strings that do not match the expected format, like this one. Similar case: https://twitter.com/mathias/status/1006913349047717888 … @gibson042 is working to broaden the uniformly supported inputs: https://github.com/gibson042/ecma262-proposal-uniform-interchange-date-parsing …

          Mathias Bynens added,

          Mathias BynensVerified account @mathias
          🐙 Get your daily dose of JavaScript octopus jokes by watching the #jsconfeu TC39 panel! https://www.youtube.com/watch?v=Hj5q8uyqGYc … Date.parse('1 Octopus 2018'); // → “works” in @v8js & JSC/@webkit // → returns `NaN` everywhere else // → everyone is correct per spec! https://twitter.com/jsconfeu/status/1006909114692218880 … pic.twitter.com/eNaEyQZDYd
          Show this thread
          1 reply 3 retweets 11 likes
        4. 1 more reply
        1. New conversation
        2. BrendanEich‏Verified account @BrendanEich 10 Nov 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mathias @thecraigmichael @domenic

          Thanks -- do you know why tools differ on which to call implicitly? Seems bogus.

          1 reply 0 retweets 1 like
        3. Mathias Bynens‏Verified account @mathias 10 Nov 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @BrendanEich @thecraigmichael @domenic

          No idea, but I can see the case for either option in tooling. One is more human-readable, the other is consistent across time zones. 🤷‍♂️

          0 replies 0 retweets 2 likes
        4. End of conversation

      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.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info