joehewitt

8 ms·

31.
by joehewitt 15y ago
The existence of the HTTP Accept header shows that HTTP was designed with a variety of incompatible user-agents in mind. If you write new user-agent, use Accept to specify what content types you can render. Intelligent web servers can serve
32.
by joehewitt 15y ago
It's rarely at #1, but it has been a permanent fixture in the top 20, while most other apps are only on the chart for a short time. That adds up.
33.
by joehewitt 15y ago
My point wasn't that Linux or Python or jQuery own their sectors. I responding to your claim that a single owner promotes stagnation. It's important to distinguish the Internet from the collection of web technologies. The Internet is the t
34.
by joehewitt 15y ago
Hell yeah, they had data binding in the 90's. Was ahead of its time, like XMLHttpRequest, but never caught on. http://msdn.microsoft.com/en-us/library/ms531385(v=vs.85).as...
35.
by joehewitt 15y ago
It gave us Chatroulette! :)
36.
by joehewitt 15y ago
Yeah, the checklist of web technologies is getting longer, but that's only part of the solution. They don't all work together very well. For example, Alex Russell has been opining recently about the way DOM interfaces are awkwardly adapted
37.
by joehewitt 15y ago
It didn't take a seer to imagine that having camera access was a good idea, but it takes a pretty boneheaded committee to wait this long to do it. Hell, Adobe put camera access in Flash years before iOS even existed. I don't love Flash, bu
38.
by joehewitt 15y ago
Has Linux stopped improving? Has Python stopped improving? Has jQuery stopped improving? It all depends on who the owner is.
39.
by joehewitt 15y ago
I clearly stated you need more than just a single owner, you need a single owner that is competent and cares. We can't just snap our fingers and have that, but I'm hoping to at least help people to start thinking about it.
40.
by joehewitt 15y ago
You're right, it's not the best sentence I've written in my life. Thanks for the feedback. I was trying to convey that the web is always going to have to fight for its survival, contrary to the common assumption that the web has some magic
41.
by joehewitt 15y ago
The W3C writes specs, not code. They do not own the actual rubber that hits the road, and so they are only indirectly responsible for what happens on the real web. I want to remove the separation of architecture from implementation and have
42.
by joehewitt 15y ago
Exactly the kind of arrogance I cited. You don't want to risk a bad owner so you'll let the whole thing die from neglect by committee. I would rather have Microsoft be the only browser vendor than have the web shrink dramatically.
43.
by joehewitt 15y ago
Sorry if I didn't make it clear I meant the web will never be the dominant platform in the future once the current trends play out. I am aware of current market share proportions.
44.
by joehewitt 15y ago
HTML is capable of anything, given the makers of browsers will it to be so. There's nothing inherently special about "native" technlogies, other than OS makers tend to give new features to the platforms they own first. It doesn't have to b
45.
by joehewitt 15y ago
Are any of the big registrars trustworthy? I'm trying to consolidate all of my domains on Namecheap right now. I transferred one domain from Dyndns and they did the transfer within a few hours (nice!). Then I went to transfer another from
46.
by joehewitt 15y ago
I recently wrote something just like this for Node.js: https://github.com/joehewitt/markdom It's used on http://uponahill.com to extract Flickr urls so I can query the Flickr API and get complete metadata about each photo. My gf, who d
47.
by joehewitt 15y ago
I'm excited by OnSwipe's potential and I'm optimistic they're going to get it right eventually. For me, the biggest problem has been that OnSwipe makes no attempt to handle URLs correctly. URLs from the desktop version redirect to the TOC
48.
by joehewitt 15y ago
When you scroll horizontally, you're indicating that you want to see more photos, so naturally the text should disappear. When you scroll vertically again, you're indicating that you want to move to the next post, so naturally the text sho
49.
by joehewitt 15y ago
I made it so you have to scroll the text a little bit further so that the photo would stay pinned down long enough that you could see it, and scroll horizontally to the other photos. You're right, though, that page up/down (and arrow keys)
50.
by joehewitt 15y ago
The goal here is not to be "truly innovative", but to emulate scrolling behavior which should ideally be performed by mobile WebKit, but isn't. But I must have done a good job since you only notice the background image being pinned, and no
51.
by joehewitt 15y ago
It will work on Android as soon as I get some Android devices to test with. It should currently "work" on Android, but probably not well.
52.
by joehewitt 15y ago
Make sure you're on the latest version of Chrome (12). The new hardware acceleration is necessary for the large photos to scroll smoothly.
53.
by joehewitt 15y ago
I assume you're testing on an Android device then... I don't have one to test (but I will soon), so I'm not surprised it doesn't perform well there. Anyway, the current code is trying to replicate the feel of iOS scrolling. An Android impl
54.
by joehewitt 15y ago
Libraries like these should not be necessary, but since Apple has not implemented proper scrolling of elements and iframes, we're left to do it ourselves. Perhaps iOS 5 (just two weeks until wwdc!) will solve the problem and make this proj
55.
by joehewitt 15y ago
Making it easy to save Firebug CSS changes back to the source file was at the top of my todo list in 2007, and I was really bummed that I didn't get the chance to build it. Years later the Backfire extension came out, which does alleviate
56.
by joehewitt 15y ago
There is definitely an opportunity to create an amazing HTML5 IDE, but I also think that smaller and more focused tools have value. I intend to avoid the temptation to try and boil the ocean so that I can actually ship something useful thi
57.
IOS games using JavaScriptCore without WebKit(phoboslab.org)
141 points by joehewitt 15y ago|28 comments
58.
by joehewitt 16y ago
That's a disappointing attitude. Let me give you a great counterexample. Chrome was initially a completely fork of Webkit, but Google eventually chose to work with Apple and merge all of their changes to the Webkit trunk. This was only po
59.
by joehewitt 16y ago
I am obviously expecting that in a few years time Android will suck much less, or I wouldn't bother investing time in it.
60.
by joehewitt 16y ago
I never said it was "hard", just that I was surprised that the simple task of "get me this URL" required me to work with some abstract classes for "async tasks". Strikes me as overengineering. The networking classes could easily encapsula

More ›