I'm not even sure what bit you're mad about, all of the web? You're plenty sharp enough to understand all of the diversity of quality of software is as present on the web as it is in all other kinds of software.
-
-
-
Replying to @Jonathan_Blow
I'd take a thousand silly startup ideas for the chance we land on one Wikipedia. Everyone just does what they can. Mechanical sympathy isn't the only way.
1 reply 0 retweets 0 likes -
Replying to @david_whitney
Okay, but ... it doesn't actually work. The theory is that the way these things are programmed is a trade-off, you give up efficiency, you get productivity and reliability etc. But productivity and reliability are both extremely low. And the amount of efficiency traded off was
1 reply 0 retweets 3 likes -
Replying to @Jonathan_Blow @david_whitney
tremendously higher than claimed. At some point, isn't someone supposed to notice this and question wtf is going on?
1 reply 0 retweets 2 likes -
Replying to @Jonathan_Blow
The same spread of productivity and reliability exists in web programming as in all others. We gained a boatload of accessibility on the way though. Fairly sure that most of programming is frequently reflective and this isn't news, there's no prize for being annoyed about it.
1 reply 0 retweets 0 likes -
Replying to @david_whitney
I find your first assertion here very difficult to agree with if I just look at the numbers.
1 reply 0 retweets 0 likes -
Replying to @Jonathan_Blow
You keep on mentioning "the numbers" and "these things" like stuff on the web is all the same and it really isn't. I get the ire and frustration, but different categories of solutions fit different problem spaces. There's plenty of utilitarian web things that just work.
2 replies 0 retweets 0 likes -
Replying to @david_whitney
Like what? I can't think of a single web site that works for me consistently. By "the numbers" I mean, for example, the number of employee-years per unit of functionality implemented, across various fields.
1 reply 0 retweets 1 like -
Replying to @Jonathan_Blow
The implication there is that there's an alternative, non-web, way to implement that same functionality that would somehow magically be better. As if targeting something that isn't the browser is somehow cheaper (which, well, market rates on the app market indicate otherwise).
1 reply 0 retweets 0 likes
It would be much better, but not magic, in fact it would have way less magic, in terms of hand-waving blind trust that various barely-known-of layers will somehow do the right thing. Re cheaper, I am not sure what argument you are making there, it seems to be a context switch.
-
-
Replying to @Jonathan_Blow
Re: cheaper - that was in response to person years/unit of function. The web is well known and extensively documented. And standardised, and democratised as a result. If arbitrarily fat clients were more effective and reliable and explicable, everyone would still be doing that.
2 replies 0 retweets 0 likes -
Replying to @david_whitney @Jonathan_Blow
The web and it's associated protocols are absolutely the most extensively documented and well known things in *all* of computing. I'm not really following the "hand wavey trusted" point at all.
0 replies 0 retweets 0 likes
End of conversation
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.