3 ms·

Designing very large (JavaScript) applications

6 points by cramforce 8y ago

dmitriid 8y ago
You speak so forcefully about empathy and thinking about other developers, and how your decisions impact others. And yet: - https://github.com/ampproject/amphtml/issues/13597 https://github.com/ampproject/amphtml/issues/13597 - https://github.com/ampproject/amphtml/issues/13623 https://github.com/ampproject/amphtml/issues/13623 - https://github.com/ampproject/amphtml/issues/13600 https://github.com/ampproject/amphtml/issues/13600
- SA500 8y ago
  A complete non sequitur.
  - dmitriid 8y ago
    Actions should follow words, n'est-ce pas? When a person writes about empathy like this: > You’re thinking with other software engineers and you’re thinking about how what you do and the APIs that you are giving them, how they impact how they write software. or about things like this: > And my talk is really about, how subtle changes in APIs and so forth, how they impact the programming model. one would expect the person writing this to practice what they preach. In reality though the texts and the actions could not be further apart, as evidenced by the links I provided.
- wanda 8y ago
  I'll be frank—I think these examples reflect more poorly on you and Captain Ahab than on your apparent nemesis. (I am in no way affiliated with your nemesis, AMP, or Google)
  - dmitriid 8y ago
    How so?
cztomsik 8y ago
Really liked the article I also wonder how long it will take until people stop doing react just because it is cool. Choosing a framework is hardly-reversible decision and people (architects) should really evaluate all the benefits and all the costs (and their real needs) and not act based on current hypes. BTW: everybody is blogging about how something is so cool but nobody blogs about how they screwed up. I'd love to read such articles maybe there's a room for new "medium"
- bromuro 8y ago
  Do you know people using React because it’s cool? What do they mean that’s React is cool? And why they should not?

6 points by cramforce 8y ago

You speak so forcefully about empathy and thinking about other developers, and how your decisions impact others. And yet: - https://github.com/ampproject/amphtml/issues/13597 https://github.com/ampproject/amphtml/issues/13597 - https://github.com/ampproject/amphtml/issues/13623 https://github.com/ampproject/amphtml/issues/13623 - https://github.com/ampproject/amphtml/issues/13600 https://github.com/ampproject/amphtml/issues/13600

SA500 8y ago
A complete non sequitur.
- dmitriid 8y ago
  Actions should follow words, n'est-ce pas? When a person writes about empathy like this: > You’re thinking with other software engineers and you’re thinking about how what you do and the APIs that you are giving them, how they impact how they write software. or about things like this: > And my talk is really about, how subtle changes in APIs and so forth, how they impact the programming model. one would expect the person writing this to practice what they preach. In reality though the texts and the actions could not be further apart, as evidenced by the links I provided.
wanda 8y ago
I'll be frank—I think these examples reflect more poorly on you and Captain Ahab than on your apparent nemesis. (I am in no way affiliated with your nemesis, AMP, or Google)
- dmitriid 8y ago
  How so?

cztomsik 8y ago

Really liked the article I also wonder how long it will take until people stop doing react just because it is cool. Choosing a framework is hardly-reversible decision and people (architects) should really evaluate all the benefits and all the costs (and their real needs) and not act based on current hypes. BTW: everybody is blogging about how something is so cool but nobody blogs about how they screwed up. I'd love to read such articles maybe there's a room for new "medium"

bromuro 8y ago
Do you know people using React because it’s cool? What do they mean that’s React is cool? And why they should not?