The state of web development on the shelves. Opinion of one expert in 25 tweets
Translation of the article mentioned in my previous translation .
Not many experts are well aware of all the ins and outs of the web. Among them is Joe Hewitt . For the past ten years, he has worked for industry giants like Netscape, AOL, Firefox, and Facebook (where he currently works). About iPhone Hewitt also knows not by hearsay. He was the first to write a great Facebook web application for iPhone (when there were no native applications before), and then the native client is one of the best applications on the iPhone platform. Therefore, when Joe says something on the case (he does it from time to time), people listen. And today he decided to speak out.
Responding this morning to an email from Apple CEO Steve Jobs about Flash, Hewitt went on twitter to share his thoughts. I asked Joe if I could put them in an article, he replied, "of course, why not." Hewitt, as many of you know, stopped developing iPhone applications due to a conflict with the AppStore user agreement.
Today, watching a wave of anti-flash propaganda on Twitter, launched by Jobs' letter, Hewitt said:
')
- Address your dissatisfaction with the Flash-em on the W3C, the annoying sluggishness of which forced developers to use plug-ins due to the weakness of the standards themselves.
- In addition, I appeal to you, the developers, whining whenever the browser offers a "non-standard" but innovative API.
- Browser manufacturers must offer non-standard APIs that the W3C can standardize even after they are distributed. Waiting for innovation from W3C - death like.
Thus, Hewitt believes that Flash (and other plug-ins) exist only because the W3C (Administrative Council for Web Standards) is too slow in formulating and adopting new technologies. He urges browser manufacturers to move away from the limitations of W3C and start experimenting with new APIs.
Then he begins to defend Microsoft, the winner (although everyone, including the US government, believes that this was done by dishonest methods) to another company where Joe (Netscape) began his career.
- 10 years ago we ran into Microsoft, forbidding it to develop IE, transferring the reins to the W3C. What came of it?
- For those of you who are too young to remember, IE has been developing at a crazy pace from 4.0 to 6.0, just as long as the DOJ (Department of Justice) and the W3C got in the way.
- Come on. In addition to ActiveX, during 1996-2000, Microsoft developed the web faster than any other browser maker.
“I don't know why MS abandoned IE, but I know that web developers asked them to stop innovating and just follow the W3C standards.
Hewitt believes antitrust measures against Microsoft have stopped the development of Internet Explorer. In 1996, when, according to Joe, the real innovations in IE just started, this browser did not even have a 10% market share, while Netscape had almost 90%. And as a catch-up, IE had to innovate. Until he captured the entire web, and then Microsoft, being on a horse, abandoned the product.
Hewitt then pays attention to the development of online stores (including, yes, the Apple AppStore).
- Why do online stores threaten the web and scare developers like me? “Evil” proprietary technology breaks the web into pieces.
- I desperately want to become a web developer again, but if I have to wait until 2020, while browsers can finally offer something that Cocoa can already in 2010, then well, it nafig.
“The“ evil ”proprietary technology breaks the web into pieces.” Is a very challenging quote (still holding back not to use it in the title of the article). Again, Hewitt claims that the web has not yet reached the capabilities of non-web technologies like Cocoa - and will not reach it in the next 10 years.
- Did Microsoft patent its non-standard html / javascript / css extensions, not allowing other browsers to implement them?
“It's true that [W3C] does not dictate its standards, but developers are ashamed of those who use non-standard APIs. That's the problem.
He reasons here why some of the Microsoft standards were not adopted by the committee (W3C)? Then he condemns web developers for criticizing other developers who use technology unauthorized by the administrative board.
- I am outraged by the fact that I have to forget about Cocoa in order to return to creating web applications. It upsets how serious opportunities I have to lose.
- As it should be: browsers introduce various innovations, users choose the best, after that the W3C standardizes what users choose, the losing browsers implement the missing APIs.
This is the essence of the Hewitt argument. Web technologies are not developing fast enough, and why should we use a less powerful language in order to meet web standards? Again, he hopes that browsers will begin to innovate and force the W3C to embrace these innovations.
- I like what Cocoa is capable of, I just don’t like C-like languages ​​for UI programming.
The reason why Hewitt lacks Cocoa, even if he finds it to be the best of the web languages. i.e., iPhone Cocoa for creating iPhone applications].
- Users will understand that they are required to choose if more developers will sharpen their sites for certain browser technologies. Developers will actually choose the winner.
And encourages developers to take active steps to reverse the trend.
- IE6 was pretty darn cool in 2000. It's just not fair to compare it with modern browsers.
Attention to those who criticize IE6 - remember what happened when it came out.
“Unfortunately, I would recommend Cocoa [and not web languages] at the moment.” I wish I didn't say that.
- Cocoa, while not being perfect, is better than web languages.
- So make another browser. Spit it out. You know what is not trifling? Buy a new phone for every AppStore.
Interesting idea. Hewitt says that it can be a hassle, programming the web for different browsers, much more hemorrhoids - programming applications for various AppStore.
- I do not blame ActiveX, but the html / css / javascript in IE was one time at a very high level.
Again, protects IE in those times.
And starting from here, Hewitt reflects on the topic of web applications against native ones.
- Yes it is. It would be better for developers to force users to launch different browsers instead of creating thin cross-browser sites.
- Something like this happens in the mobile web, where native applications are against web applications, except that the AppStore does not expand the browser, but replaces it.
- “Best viewed in X” was not as bad as “buy another phone”, which we have now since we were allowed to rot on the web for the sake of developing native applications. Those who tried to develop serious native and web applications for the iPhone know that the iPhone Safari is a joke compared to the iPhone Cocoa.
Hewitt believes that the AppStore have replaced the web, simply because their programming languages ​​are better. And this is our fault with you that the web is rotting, and we allowed it. His latest tweet message is especially strong: Hewitt, having extensive experience in both native and web technologies, considers iPhone Safari a “joke” compared to what can be done in native applications. This is something that many developers are whispering on the sidelines, but rarely speak openly.
In the end, Hewitt clarifies some of his statements.
“I was cruel to Flash, but we all have to thank Macromedia / Adobe for 10 years of continuing the relay, started by the W3C, Microsoft and Mozilla.
“And actually, it would be bad if the WebKit team were not so damn competent.” Everything, I go out, thanks for listening.
Honestly, a lot of juicy comments in one day.
UPDATE. Translator's Notes:
Since the comments have a lot of answers about IE, I want to note that the article is not about that.
An article on how to simplify web development by creating innovative extensions (for example, Cocoa) in browsers, and then, using these extensions for all mobile platforms, become independent from AppStore. Let there be one browser (for example, on the WebKit core) for all platforms with Cocoa-extension, which will work from any mobile phone, communicator, axis, than programmers will create their own version for each AppStore (Apple, Google, Nokia, Samsung, MS) web applications.
Not many experts are well aware of all the ins and outs of the web. Among them is Joe Hewitt . For the past ten years, he has worked for industry giants like Netscape, AOL, Firefox, and Facebook (where he currently works). About iPhone Hewitt also knows not by hearsay. He was the first to write a great Facebook web application for iPhone (when there were no native applications before), and then the native client is one of the best applications on the iPhone platform. Therefore, when Joe says something on the case (he does it from time to time), people listen. And today he decided to speak out.
Responding this morning to an email from Apple CEO Steve Jobs about Flash, Hewitt went on twitter to share his thoughts. I asked Joe if I could put them in an article, he replied, "of course, why not." Hewitt, as many of you know, stopped developing iPhone applications due to a conflict with the AppStore user agreement.
Today, watching a wave of anti-flash propaganda on Twitter, launched by Jobs' letter, Hewitt said:
')
- Address your dissatisfaction with the Flash-em on the W3C, the annoying sluggishness of which forced developers to use plug-ins due to the weakness of the standards themselves.
- In addition, I appeal to you, the developers, whining whenever the browser offers a "non-standard" but innovative API.
- Browser manufacturers must offer non-standard APIs that the W3C can standardize even after they are distributed. Waiting for innovation from W3C - death like.
Thus, Hewitt believes that Flash (and other plug-ins) exist only because the W3C (Administrative Council for Web Standards) is too slow in formulating and adopting new technologies. He urges browser manufacturers to move away from the limitations of W3C and start experimenting with new APIs.
Then he begins to defend Microsoft, the winner (although everyone, including the US government, believes that this was done by dishonest methods) to another company where Joe (Netscape) began his career.
- 10 years ago we ran into Microsoft, forbidding it to develop IE, transferring the reins to the W3C. What came of it?
- For those of you who are too young to remember, IE has been developing at a crazy pace from 4.0 to 6.0, just as long as the DOJ (Department of Justice) and the W3C got in the way.
- Come on. In addition to ActiveX, during 1996-2000, Microsoft developed the web faster than any other browser maker.
“I don't know why MS abandoned IE, but I know that web developers asked them to stop innovating and just follow the W3C standards.
Hewitt believes antitrust measures against Microsoft have stopped the development of Internet Explorer. In 1996, when, according to Joe, the real innovations in IE just started, this browser did not even have a 10% market share, while Netscape had almost 90%. And as a catch-up, IE had to innovate. Until he captured the entire web, and then Microsoft, being on a horse, abandoned the product.
Hewitt then pays attention to the development of online stores (including, yes, the Apple AppStore).
- Why do online stores threaten the web and scare developers like me? “Evil” proprietary technology breaks the web into pieces.
- I desperately want to become a web developer again, but if I have to wait until 2020, while browsers can finally offer something that Cocoa can already in 2010, then well, it nafig.
“The“ evil ”proprietary technology breaks the web into pieces.” Is a very challenging quote (still holding back not to use it in the title of the article). Again, Hewitt claims that the web has not yet reached the capabilities of non-web technologies like Cocoa - and will not reach it in the next 10 years.
- Did Microsoft patent its non-standard html / javascript / css extensions, not allowing other browsers to implement them?
“It's true that [W3C] does not dictate its standards, but developers are ashamed of those who use non-standard APIs. That's the problem.
He reasons here why some of the Microsoft standards were not adopted by the committee (W3C)? Then he condemns web developers for criticizing other developers who use technology unauthorized by the administrative board.
- I am outraged by the fact that I have to forget about Cocoa in order to return to creating web applications. It upsets how serious opportunities I have to lose.
- As it should be: browsers introduce various innovations, users choose the best, after that the W3C standardizes what users choose, the losing browsers implement the missing APIs.
This is the essence of the Hewitt argument. Web technologies are not developing fast enough, and why should we use a less powerful language in order to meet web standards? Again, he hopes that browsers will begin to innovate and force the W3C to embrace these innovations.
- I like what Cocoa is capable of, I just don’t like C-like languages ​​for UI programming.
The reason why Hewitt lacks Cocoa, even if he finds it to be the best of the web languages. i.e., iPhone Cocoa for creating iPhone applications].
- Users will understand that they are required to choose if more developers will sharpen their sites for certain browser technologies. Developers will actually choose the winner.
And encourages developers to take active steps to reverse the trend.
- IE6 was pretty darn cool in 2000. It's just not fair to compare it with modern browsers.
Attention to those who criticize IE6 - remember what happened when it came out.
“Unfortunately, I would recommend Cocoa [and not web languages] at the moment.” I wish I didn't say that.
- Cocoa, while not being perfect, is better than web languages.
- So make another browser. Spit it out. You know what is not trifling? Buy a new phone for every AppStore.
Interesting idea. Hewitt says that it can be a hassle, programming the web for different browsers, much more hemorrhoids - programming applications for various AppStore.
- I do not blame ActiveX, but the html / css / javascript in IE was one time at a very high level.
Again, protects IE in those times.
And starting from here, Hewitt reflects on the topic of web applications against native ones.
- Yes it is. It would be better for developers to force users to launch different browsers instead of creating thin cross-browser sites.
- Something like this happens in the mobile web, where native applications are against web applications, except that the AppStore does not expand the browser, but replaces it.
- “Best viewed in X” was not as bad as “buy another phone”, which we have now since we were allowed to rot on the web for the sake of developing native applications. Those who tried to develop serious native and web applications for the iPhone know that the iPhone Safari is a joke compared to the iPhone Cocoa.
Hewitt believes that the AppStore have replaced the web, simply because their programming languages ​​are better. And this is our fault with you that the web is rotting, and we allowed it. His latest tweet message is especially strong: Hewitt, having extensive experience in both native and web technologies, considers iPhone Safari a “joke” compared to what can be done in native applications. This is something that many developers are whispering on the sidelines, but rarely speak openly.
In the end, Hewitt clarifies some of his statements.
“I was cruel to Flash, but we all have to thank Macromedia / Adobe for 10 years of continuing the relay, started by the W3C, Microsoft and Mozilla.
“And actually, it would be bad if the WebKit team were not so damn competent.” Everything, I go out, thanks for listening.
Honestly, a lot of juicy comments in one day.
UPDATE. Translator's Notes:
Since the comments have a lot of answers about IE, I want to note that the article is not about that.
An article on how to simplify web development by creating innovative extensions (for example, Cocoa) in browsers, and then, using these extensions for all mobile platforms, become independent from AppStore. Let there be one browser (for example, on the WebKit core) for all platforms with Cocoa-extension, which will work from any mobile phone, communicator, axis, than programmers will create their own version for each AppStore (Apple, Google, Nokia, Samsung, MS) web applications.
Source: https://habr.com/ru/post/95612/
All Articles