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.
  • 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
wycats's profile
Yehuda Katz 🥨
Yehuda Katz 🥨
Yehuda Katz  🥨
Verified account
@wycats

Tweets

Yehuda Katz  🥨Verified account

@wycats

Tilde Co-Founder, OSS enthusiast and world traveler.

Portland, OR
yehudakatz.com
Joined August 2007

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • 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. Sexy Emma Costume‏ @nucknyan May 4
      Replying to @wycats @MisterAwesan @amatchneer

      The problem is that webpack has been innovating rapidly while we are left reimplementing that stuff with far fewer contributors. We’re going to get left in the dust

      2 replies 0 retweets 6 likes
    2. Edward Faulkner‏ @eaf4 May 4
      Replying to @nucknyan @wycats and

      I think that frames a false dilemma. Webpack is open source. Any piece of webpack that is too big an investment to reproduce we can literally just use. And we already have a history of doing that (for example, ember-cli already uses Rollup to handle steps that Rollup is good at).

      1 reply 0 retweets 2 likes
    3. Sexy Emma Costume‏ @nucknyan May 4
      Replying to @eaf4 @wycats and

      The differences between Webpack and Ember-CLI will just continue to grow even with that, until eventually it's just not feasible to do that. I'd rather rip the bandaid off and switch from Broccoli to Webpack

      2 replies 0 retweets 2 likes
    4. Edward Faulkner‏ @eaf4 May 4
      Replying to @nucknyan @wycats and

      I know it's hard to productively explain myself in just tweets, but my tl;dr is (1) broccoli and webpack solve different problems, you may actually want both and

      1 reply 0 retweets 3 likes
    5. Edward Faulkner‏ @eaf4 May 4
      Replying to @eaf4 @nucknyan and

      (2) we have a track record of successfully doing much more dramatic internals upgrades than this, while bringing the whole community along.

      1 reply 0 retweets 4 likes
    6. Edward Faulkner‏ @eaf4 May 4
      Replying to @eaf4 @nucknyan and

      Like, if it turns out we really do want to go entirely with webpack over broccoli, that is less dramatic than either of our rendering engine upgrades (stringly handlebars to htmlbars to glimmer).

      1 reply 0 retweets 4 likes
    7. Yehuda Katz  🥨‏Verified account @wycats May 4
      Replying to @eaf4 @nucknyan and

      And the addon API doesn't even have that direct of a relationship to Broccoli, in the same way that the Ember component lifecycle makes sense even if it wasn't generating DOM at the end.

      2 replies 0 retweets 1 like
    8. Sexy Emma Costume‏ @nucknyan May 4
      Replying to @wycats @eaf4 and

      Yeah I won't fault the addon API at all. I love it, I just have gripes with the feeling that ember is constantly reinventing things that it seems (1) everybody else coalesced on a solution for and (2) nobody else can benefit from our reinvention

      1 reply 0 retweets 3 likes
    9. Sexy Emma Costume‏ @nucknyan May 4
      Replying to @nucknyan @wycats and

      It feels like ember picks a tool early in the race and when everybody else hits the same problem and coalesces around an alternative, we stubbornly keep our existing tool due to sunk costs

      1 reply 0 retweets 2 likes
    10. Sexy Emma Costume‏ @nucknyan May 4
      Replying to @nucknyan @wycats and

      … And this results in a weak ecosystem because I can't borrow tools directly from other ecosystems, just ideas. And ideas are frankly near-worthless when I'm trying to build a product quickly

      3 replies 0 retweets 2 likes
      Yehuda Katz  🥨‏Verified account @wycats May 4
      Replying to @nucknyan @eaf4 and

      From the perspective of quickly shipping your product, what would you say are the biggest things from Webpack missing in Ember that are slowing you down?

      11:36 AM - 4 May 2018
      • 1 Like
      • Boring humorist
      4 replies 0 retweets 1 like
        1. New conversation
        2. Chris Freeman‏ @15lettermax May 4
          Replying to @wycats @nucknyan and

          npm install thing -> import stuff from thing is absolutely 100% a real and significant feature of using webpack that ember still lacks (though I know we're getting closer) and the cost of not having this feature is far from trivial in real life apps

          2 replies 0 retweets 7 likes
        3. Alex Matchneer‏ @amatchneer May 4
          Replying to @15lettermax @wycats and

          I definitely quickly feel paralyzed when I go down the path of wanting to use a 3rd party module to solve some problem or experiment with an idea.

          2 replies 0 retweets 3 likes
        4. Yehuda Katz  🥨‏Verified account @wycats May 4
          Replying to @amatchneer @15lettermax and

          When I started thinking about Ember in 2018 over the holidays, "being able to easily import from npm" quickly shot up to the top of my list. It sucks wanting to use an npm module and having to remember the song and dance. Let's fix it.

          5 replies 2 retweets 16 likes
        5. Yehuda Katz  🥨‏Verified account @wycats May 4
          Replying to @wycats @amatchneer and

          (sounds like a good choice for my own #emberjs2018 post)

          0 replies 0 retweets 1 like
        6. End of conversation
        1. New conversation
        2. Yehuda Katz  🥨‏Verified account @wycats May 4
          Replying to @wycats @nucknyan and

          I totally get the frustration of wanting to do something in your app and feeling held back by your tools.

          1 reply 0 retweets 2 likes
        3. Sean Thomas Larkin (肖恩)‏ @TheLarkInn May 4
          Replying to @wycats @nucknyan and

          Emma the problem is that for Ember to go full webpack the "right way" they need to use modules top down, which is (last I worked with the cli team and ember team) is a pretty tough feat. Glimmer is promises of the future however. Just know we actively want to have webpack+ember

          1 reply 0 retweets 1 like
        4. Sean Thomas Larkin (肖恩)‏ @TheLarkInn May 4
          Replying to @TheLarkInn @wycats and

          Ember makes a very valuable yet discrete tradeoff: Compat at the cost of being held back a little, but with a much more stable moving ecosystem.

          1 reply 1 retweet 3 likes
        5. Sean Thomas Larkin (肖恩)‏ @TheLarkInn May 4
          Replying to @TheLarkInn @wycats and

          Dependency Injection would need (or should in my subjective opinion) be repalced with ESM, and that's a whole archetectural rewrite almost.

          3 replies 0 retweets 2 likes
        6. Yehuda Katz  🥨‏Verified account @wycats May 4
          Replying to @TheLarkInn @nucknyan and

          Some cases of DI might want to be rewritten as pure modules, but DI *state* would still want to be separately managed. Also, cases where you use DI to swap out different versions of a service wouldn't necessarily be able to reference a module name directly.

          1 reply 0 retweets 0 likes
        7. Yehuda Katz  🥨‏Verified account @wycats May 4
          Replying to @wycats @TheLarkInn and

          Some sort of build-time DI would be necessary (so that importing from "services/fetch" would be able to be swapped out if needed), but then we could end up with something like:

          1 reply 0 retweets 0 likes
        8. Yehuda Katz  🥨‏Verified account @wycats May 4
          Replying to @wycats @TheLarkInn and

          import Fetch from "app/services/fetch"; import { service } from "@ember/injections"; export default class { @service(Fetch) fetch; handle() { this.fetch // an instance of fetch } }

          3 replies 0 retweets 2 likes
        9. Chris Krycho‏ @chriskrycho May 5
          Replying to @wycats @TheLarkInn and

          Note that an import *roughly* like this is already necessary for @typescriptlang to have enough info to be usable for services today (`@service fetch!: Fetch;`) so rationalizing DI in something like this way would be 💯 from where I stand.

          1 reply 0 retweets 5 likes
        10. 14 more replies
        1. New conversation
        2. Sexy Emma Costume‏ @nucknyan May 4
          Replying to @wycats @eaf4 and

          It's not any specific things, it's just the ecosystem as a whole intangible thing. The minor pain points which are found and solved by the large Webpack community just aren't with the smaller ember community

          1 reply 0 retweets 0 likes
        3. Sexy Emma Costume‏ @nucknyan May 4
          Replying to @nucknyan @wycats and

          We need to accept that we're tiny compared to the broader JS ecosystem and try to match conventions with them, as Rails has done with Ruby's ever-evolving conventions

          1 reply 0 retweets 0 likes
        4. Brian Fitch‏ @brianmfitch May 4
          Replying to @nucknyan @wycats and

          Brian Fitch Retweeted Brian Fitch

          Not to toot my own tweet, but this is exactly what I wrote about in my #EmberJS2018 post today:https://mobile.twitter.com/brianmfitch/status/992475638652112898 …

          Brian Fitch added,

          Brian Fitch @brianmfitch
          Wrote some words on a plane for Ember's Roadmap RFC - Embrace the Javascript Ecosystem: https://gist.github.com/bfitch/4320fd7f7218b616a076978c52e2f36e … #EmberJS2018
          1 reply 0 retweets 4 likes
        5. Sexy Emma Costume‏ @nucknyan May 4
          Replying to @brianmfitch @wycats and

          Yes, this is pretty much everything I've been thinking! Thanks for writing that

          1 reply 0 retweets 1 like
        6. Brian Fitch‏ @brianmfitch May 4
          Replying to @nucknyan @wycats and

          Awesome. Happy to do it.

          0 replies 0 retweets 0 likes
        7. End of conversation
        1. mamadero‏ @mamadero May 5
          Replying to @wycats @nucknyan and

          Speed, code splitting, async imports, import from npm. Also other things that are fixed now but required extra work in addon land line typescript support, GraphQL, etc. Those were solved problems in Webpack that took longer to get to Ember.

          0 replies 0 retweets 0 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          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.

        Promoted Tweet

        false

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