Author here.
I know this is the orange site and we have to expect this type of comment, but still…
I’ve been building software for more than 20 years, and using React since it came out.
You’re right that this event handling system isn’t exclusive to canvas. But then I’m not sure if you read the first part of the article where we talk about the other big reason: performance.
Your assertions that setTimeouts should be banned show immaturity. There are some cases where certain browsers do things in a different order and you really are required to use a hack like that.
You also neglect the fact (and this also points to your immaturity) that products are built by a number of people over a long period of time, with different constraints on them as things change.
The SVG approach was done for good reasons and the code made sense for what it was for initially. Then things got more complex and people started making more complex maps.
What we also found is that the complexity of maps people made increases with our performance gains: the faster the app is, the more people do with it.
I haven’t got time to go into everything either in the articles or certainly this reply, but I’d ask you to have a look at yourself and decide if you really want to be That Guy on HN.
I know this is the orange site and we have to expect this type of comment, but still…
I’ve been building software for more than 20 years, and using React since it came out.
You’re right that this event handling system isn’t exclusive to canvas. But then I’m not sure if you read the first part of the article where we talk about the other big reason: performance.
Your assertions that setTimeouts should be banned show immaturity. There are some cases where certain browsers do things in a different order and you really are required to use a hack like that.
You also neglect the fact (and this also points to your immaturity) that products are built by a number of people over a long period of time, with different constraints on them as things change.
The SVG approach was done for good reasons and the code made sense for what it was for initially. Then things got more complex and people started making more complex maps.
What we also found is that the complexity of maps people made increases with our performance gains: the faster the app is, the more people do with it.
I haven’t got time to go into everything either in the articles or certainly this reply, but I’d ask you to have a look at yourself and decide if you really want to be That Guy on HN.