38 replies

1. Nicholas C. Zakas 28 min later

   Fake it til you something something…

   1. Luca Casonato 🏳️‍🌈 11 hr later

      Hey, that's not nice - what are we faking?

      1. Nicholas C. Zakas 15 hr later

         The premise of “backwards compatibility” is that the other thing is old and your thing is new. You can’t be backwards compatible with a competitor. You can be compatible, though.

         FWIW I’m glad Node.js compat is finally here. Just maybe the marketing folks don’t grok the relationship.

2. Private reply 38 min later
   1. Phil Hawksworth 13 hr later

      I confess this hadn't occurred to me. I read that as meaning you can move to Deno from Node with good compatibility. Feels like standard language inn this context.

      But it's interesting to hear that this ruffles feathers. I don't think shade was intended. Perhaps greater sensitivity is needed here.

      1. Phil Hawksworth 14 hr later

         Needed this rather sooner than I had hoped (but not that much sooner than expected)

         bsky.app/profile/phil...

      2. Private reply 15 hr later
         1. Phil Hawksworth 15 hr later

            This is helpful feedback. I'll make sure we talk about this here.

         2. Kilian Valkhof 15 hr later

            Excellent opportunity to cram "orthogonal" in there instead and sound real clever.

            1. Anthony Cregan 15 hr later

               I just used this word in a document I am preparing and I am very proud of myself.

            2. Phil Hawksworth 15 hr later

               For greater synergies, we can probably facilitate actioning that

3. Private reply 1 hr later
   1. Michael 1 hr later

      Oh man, you gotta try Eleventy! Check out my overbuilt starter! Join the discord! One of us! One of us!

      1. Private reply 2 hr later
         1. Zach Leatherman 15 hr later

            we need a Deno champion! I’ve been testing a little bit and it works with eleventy-base-blog

            1. Zach Leatherman 15 hr later

               www.11ty.dev/docs/javascr...

            2. Phil Hawksworth 16 hr later

               🫡

      2. Vale 14 hr later

         You guys got some sorta cult happening over there?

         1. Michael 15 hr later

            😏

         2. Zach Leatherman 15 hr later

            I hope not

            no gods no masters

            1. Vale 16 hr later

               It would appear that God is dead. 11ty killed him.

               1. Zach Leatherman 16 hr later

                  we all need to learn to get along in this great big foxhole called life

                  1. Michael 16 hr later

                     *bong rip noise increases*

                     1. Zach Leatherman 16 hr later

                        (this was the perfect response thank you)

4. Ben Schwarz 2 hr later

   Maybe you are? Why are you side eyeing??

   I think Deno/Ryan see Node.js as the past and Deno as the future, hence backwards compatible

   1. Ben Schwarz 15 hr later

      Having read the takes on this thread I feel like people should lighten up, sheesh.

      1. Zach Leatherman 15 hr later

         you’re right — this is pretty harmless (but it’s also okay to have opinions 🥹)

5. Kamran Ayub 3 hr later

   Mostly*.

   *Ok, like 75%**.

   **Ok, like 50% fully and 25% partially.***

   ***And like 6 that definitely aren't yet.

   docs.deno.com/runtime/refe...

   1. Kamran Ayub 3 hr later

      Marketing would not approve of my copy 😜

   2. Nicolò Ribaudo 10 hr later

      To be fair it would be great to see those percentages weighted by how frequently those various APIs are used.

      1. Josh Collinsworth 14 hr later

         My understanding is that, while the percentage of overall Node support appears to be a relatively low number, it does indeed represent the vast majority of use cases.

         Similar to how just adding React support to something would be like 0.001% of npm, but would cover like 70% of current use cases.

         1. Nicolò Ribaudo 14 hr later

            This matches my experience

      2. Kamran Ayub 16 hr later

         For sure. I haven't had any issues so far but I don't necessarily do production development in Deno yet. I'm sure they prioritize the major use cases first. In fact I recently ran a Qwik City app in Deno without any issues. 🤘

6. Phil Hawksworth 13 hr later

   This hadn't occurred to me as bring derogatory TBH. Is that the issue?

   I guess if you invent Node, and then invent Deno to be "Node done the way I wish I had done it to start with" (not 100% a quote from @tinyclouds.org, but sorta) then this language would feel about right.

   1. Phil Hawksworth 13 hr later

      FWIW, much of the Deno community were keen for a clean break and distinct separation from Node, but then many more asked for greater compatibility to ease adoption and migration.

      I think this wording is intended to represent that. Not throw stones.

      1. Zach Leatherman 15 hr later

         I *really* need to stop posting things to socials at the end of the day 😭

         Yeah, I can see it both ways — I don’t think it was intentional shade!

         I think the folks that see the accidental shade in “Backwards” are more likely to think of Deno and Node as peers, fwiw.

         1. Phil Hawksworth 16 hr later

            I'm glad you mentioned it. It doesn't seem like you were the only one who felt these feels.

7. Michael 15 hr later

   Co-compatible seems like the right word