Yes, the job is some small factor more complicated, but computers are orders of magnitude faster. There is a big mismatch here.
-
-
Seriously though, the only way you can be making these arguments is if you have no idea how fast your computer actually is.
3 replies 0 retweets 7 likes -
It’s interesting your default (and unwavering!) position is that Riho is ignorant and that all browsers are poorly written. Maybe take a look? They’re all open source.
2 replies 0 retweets 3 likes -
Replying to @mattgperry @Jonathan_Blow and
Why do you remark that Johnathan is being "unwavering"? Is that somehow remarkable? Do you instantly buckle on your position in an argument when someone tries to contradict it? Do you think Riho made better points than Jonathan? From my view it was completely one-sided for J.
1 reply 0 retweets 0 likes -
Replying to @brothir @Jonathan_Blow and
Really? What was the point that Jonathan made that really swung it for you?
1 reply 0 retweets 0 likes -
Replying to @mattgperry @Jonathan_Blow and
Riho insinuated that since some things are more complex than others, bad performance is inevitable, or even if you optimize something slow frameworks are the default, or something. Argument by vague trend, noncentral. J asked straightforward questions that weren't really answered
1 reply 0 retweets 0 likes -
Replying to @brothir @Jonathan_Blow and
He rightfully pointed out that the web is intrinsically more complex than one-size-fits-one, non-accessible, machine-opaque game UIs. “J”
just chewed his lip on “I don’t get why that’s hard” which translated “I don’t get it”2 replies 0 retweets 1 like -
Replying to @mattgperry @brothir and
Clearly never read the spec, knows nothing about browsers, ignorant. Which isn’t generally a position I prefer to condescend from
3 replies 0 retweets 1 like -
Replying to @mattgperry @brothir and
You haven't understood what I am saying. "The spec" as it currently exists is a fundamentally bad idea about how to solve this class of problem. The results are obviously terrible. People should observe and learn from this, but somehow don't.
2 replies 0 retweets 7 likes -
Replying to @Jonathan_Blow @mattgperry and
That's not really true though. I mean as I said before, I'd rather use something better and faster. What do you expect the web dev community to do? Write a different browser? How's that gonna work? Nobody wants to live with legacy APIs and slow code.
2 replies 0 retweets 1 like
The job of engineers is to solve problems. If those problems don't get solved, it is because people didn't solve them.
-
-
Replying to @Jonathan_Blow @mattgperry and
It's not an engineering problem. You can write an amazing new browser tomorrow, but if it doesn't display 90% of the web pages properly, and doesn't handle accessibility and different device types/screens, nobody will keep using it. How do you get people to adopt that?
2 replies 0 retweets 3 likes -
Replying to @RihoKroll @mattgperry and
In the past, people used to believe that they were actually able to make computers better, and do new, better things with them.
2 replies 1 retweet 4 likes - Show replies
New conversation -
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.