Tom Dale

@tomdale

Created Ember.js, founded Tilde, amateur baker

NYC
ಜನವರಿ 2007 ಸಮಯದಲ್ಲಿ ಸೇರಿದ್ದಾರೆ

@tomdale ತಡೆಹಿಡಿಯಲಾಗಿದೆ

ನೀವು ಖಚಿತವಾಗಿಯೂ ಈ ಟ್ವೀಟ್‌ಗಳನ್ನು ನೋಡಲು ಬಯಸುವಿರಾ? ಟ್ವೀಟ್‌ಗಳನ್ನು ನೋಡುವುದು @tomdale ಅವರನ್ನು ತಡೆತೆರವುಗೊಳಿಸುವುದಿಲ್ಲ.

  1. ಪಿನ್ ಮಾಡಿದ ಟ್ವೀಟ್

    What idiot called it Paris Fashion Week instead of French dressing?

  2. Not everyone agrees with each other about the best tactics, but the sense of shared mission is pretty unique. Great thanks.

  3. Nah it's fine :) I honestly feel to be working with this many great people during this time.

  4. I just want to say that for all the sharp words on Twitter, I really enjoy working alongside the authors of fellow web frameworks :D

  5. well, uhhhhh, i might be out of hot takes.

  6. I want the web to win, and I think the only way to do that is to work together. I hope we can do that in the future.

  7. I'd like to see Google say clearly that community libs like React are an integral part of the web platform, not a temporary hack.

  8. You can't ask yourself whether the people have their heart in the right place—you have to ask what bad people with that power could do.

  9. But when you control how the world finds information AND a smartphone OS, there is no level of scrutiny that is too high. That's real power.

  10. Let me close by saying: there are a ton of great people at Google working to build a better web. I appreciate all the hard work they do.

  11. if AMP usage means more clicks (which I assume it does or the onebox would have gone by now) it is a de facto boost

  12. it does affect SERP presentation, which in this case means above the fold display, effectively a ranking boost.

  13. (Unclear which is worse; both are pretty bad. But it's worth being precise when---justifiably---railing against it.)

  14. Be a bit more precise... AMP doesn't bump your rank in normal search results. Just gives you a place in a special carousel tier.

  15. AMP got instant adoption because it bumps your rank. You're naive if you think Google may never try the same thing with a web framework.

  16. Yes, exactly. The past results of Google trying to own the stack have not been pretty.

  17. Wow, 's attitude towards other libraries reflects really, really poorly on Google IMO.

  18. This is why 's talk was so heartening in the sea of shit-talking at IO. He did the work to help OSS projects, not tear them down.

  19. This atittude creates enemies out of allies. Google should be trying to lift the web as a whole, not the Google-flavored version of it.

  20. From the above-linked thread, it's clear Google thinks they need to own not just the browser but the stack that runs inside of it, too.

  21. I can't recall a recent event where there was more shit-talking of so many non-Google projects. It's finally spilled out into the open.

  22. Google has a loooong history of wanting to reboot the web and do it their way–Dart, {Strong,Sound}Script, NaCL, Web Components, etc.

  23. Each of these projects is given a heavy open-washing to make you think it's "the web," but it's not. It's Google.

  24. Basically, Google has gone from motivating outcomes–fast! great experiences!–to pushing Google-controlled projects like Polymer and AMP.

  25. There's a palpable attitude from Google of "thanks, but we've got it from here"–it's a condescending attitude towards the web community.

  26. Was having a hard time putting my finger on what was so upsetting about Google I/O this year. I think this nails it.

  27. Damn, gotta steal this line next time I'm trying to sell something.

  28. So I really, really appreciate taking the time to tell people "this is how you apply these ideas to what you're doing right now"

  29. As on the web as in business, most problems are *distribution* problems, not technical. Frameworks are a distribution channel to real users.

  30. That helps contribute to the feeling of churn about the web that people have.

  31. And I think sometimes it's easy to get carried away and (inadvertently) insinuating that the way people are doing things _now_ is broken.

  32. And that's great! But there's a huge gulf between "tiny demo" and "tens of thousands of people using it in production."

  33. I think devrel folks have a tendency to discover new techniques, validate them in demo apps, and start talking about it as the One True Way.

  34. (…and I hope tools like FastBoot make it so easy to support SSR that people just turn it on because it doesn't cost them anything.)

  35. (My take: both sides make great points. As with everything, it's highly dependent on the context of your project.)

  36. hi Tom! I started with Ember but I have no experience with it. Looking for someone to help PR/pair on getting it in there.

  37. I'm too old for this, someone want to submit a PR?

  38. your early 20s vs your late 20s

  39. Wanted to buy a suit for my birthday, but they're not making it easy. Like not even replying to emails…

  40. Me when I hear unlocking the front door.

    What about dogs? #runningmanchallenge
    Vine by Khoa Phan
    Vine ನಲ್ಲಿ ವೀಕ್ಷಿಸಿ
  41. Today Google introduced an AI you can converse with, while saying: "It is too hard to measure if a website is fast. We must invent AMP."

  42. TLDR 2: Rewarding publishers for using Google's proprietary, open-washed tech is a VERY dubious precedent, even if positive at the moment.

  43. TLDR 1: I wish Google rewarded _outcomes_, not specific technologies.

  44. E.g., imagine Google told publishers "We will highlight content that uses Polymer." Would _anyone_ use React? It's an anti-competitive move.

ಲೋಡಿಂಗ್ ಸಮಯ ಸ್ವಲ್ಪ ತೆಗೆದುಕೊಳ್ಳುತ್ತಿರುವಂತೆನಿಸುತ್ತದೆ.

Twitter ಸಾಮರ್ಥ್ಯ ಅಧಿಕವಾಗಿರಬಹುದು ಅಥವಾ ಈ ಕ್ಷಣದ ತೊಂದರೆಯನ್ನು ಅನುಭವಿಸುತ್ತಿರಬಹುದು. ಮತ್ತೆ ಪ್ರಯತ್ನಿಸಿ ಅಥವಾ ಇನ್ನಷ್ಟು ಮಾಹಿತಿಗೆ Twitter ಸ್ಥಿತಿ ಗೆ ಭೇಟಿ ನೀಡಿ.

    ಇದನ್ನೂ ಸಹ ನೀವು ಇಷ್ಟಪಡಬಹುದು

    ·