I agree with you that the distinction is blurring and that we should attempt to blur it even more.
4,866 karma · joined October 7, 2008
I agree with you that the distinction is blurring and that we should attempt to blur it even more.
Yes, that's my point, and I think a major point of the article. It's getting there, but very very slowly. The main reason for that is the required consensus of the various browser vendors. There is nothing inherent to the web model (apps built with HTML/CSS/js and distributed by visiting web URLs) that makes it impossible to do everything you can do with "native" UI framework X.
> let alone have the abilities to allow you to implement something like InDesign, Maya or Cubase using its technologies.
The UIs for those apps could easily be implemented using web technologies. The number crunching would require an extension to our current set of web technologies, like Google's native client. JavaScript implementations have come a long way in recent years, but not that long. ;-)
Still, the point is not that all apps can currently be written using web technologies. The point is that it's theoretically possible and that the world is moving in that direction. Sure, there are barriers to overcome. So, let's overcome those. It's not impossible. It's not even that difficult.
Unfortunately, Joe is correct that "Web technology is still relatively weak, and improving slowly." On the iPhone (and, to a lesser extent, on the desktop) there is no comparison between the quality of native apps and the quality of web apps. Native apps still afford much more to the developer. Yet the web stack has proven to be very developer and user friendly. Unfortunately, it is crippled by the browsers (especially one browser in particular...).
Somehow we need to accelerate the empowerment of the web stack. One way to do this is to diminish the power of various "native" stacks. Ironically, Apple is one of the companies leading the way in this regard. The latest version of iTunes is almost entirely WebKit based. Mobile Safari on the iPhone can use all those amazing CSS capabilities that other browsers can't yet, even on the desktop.
In the end, I have to agree with Google's strategy: bet big on HTML5. Eventually, all apps will be web apps (though hopefully they won't require a native app -- the browser -- to run). I just don't know what to do in the interim while the web stack is still crippled by the browsers.
The first challenge I can think of for someone creating a service like this is spam. If I put out a request for patio furniture, how does your service prevent all sorts of other vendors from replying to my request and trying to sell me something other than patio furniture?
Google's interview process isn't a nightmare. It's entirely typical. If you plan on interviewing for any job, you should spend a lot of time studying the interview process and how to excel in it. If you're interviewing for programming jobs, this course is an invaluable resource: http://courses.csail.mit.edu/iap/interview/
Read all the handouts 5 times, and you won't be caught off guard like this girl was.
</sarcasm>
I still find HN to be a friendly, positive environment. Let's keep it that way!
Edit: Wow. Either starting your comment with a joke is somehow no longer OK, or nobody else agrees with me that HN is still friendly and positive. I've been reading HN everyday for a very long time. I think these negative trends are mostly just an illusion due to the novelty wearing off for newer users. "If your account is less than a year old, please don't submit comments saying that HN is turning into Reddit. (It's a common semi-noob illusion.)" (http://ycombinator.com/newsguidelines.html)
The criticism here is of Dustin's incredible arrogance in calling everyone at AA completely incompetent (which is patently untrue), and in his eagerness to make it a public controversy in order to shine the spotlight on himself. His web site is a virtual shrine to himself. Everyone knows that creating controversy draws public attention. Just check every 37signals talk or blog post. It works. All you have to do is vehemently argue that the experts are morons and that you know better, and people will pay attention. Some people don't appreciate the deliberate use of controversy to gain attention, though. That's the issue at hand.
The "contextual" part of Contextual Design means real users using real products in their real context. That is how you extract useful data from your users and enable yourself to design something centered around them.
It seems like this is exactly what Wave is designed for.
Half of the point of my original comment, however, is to say that Wave seems to be designed exactly for everything, which is one of my biggest criticisms of it.
No doubt this guy is looking back at what he accomplished at Microsoft. Whether it's his fault or not, I doubt that he wants to hear that his work was a waste of time.
Not the most tactful thing to say about a friend who has just been laid off.
Text files have a super low-level API (stat, seek, read). I think the system he describes would be much more usable if he picked slightly higher-level data abstractions. I would recommend Python's built-in types: list, tuple, dict, set. Most data can be easily represented by these types and they provide a higher level API than streams (files), which means the barriers to using them are much lower.
> Please keep in mind that things are early, and there will still be many changes, so your feedback is important.
That's a lot to ask of people after a hugely hyped launch. I'm starting to feel like Google will still be asking me to try out buggy previews/betas of Wave 3 years from now. I can already sense that even many in the HN crowd have stopped caring.
"Release early, release often" works for startups, but it doesn't work well for big companies who are in the spotlight. Wave is incredibly ambitious and a monumental effort. With all of these early launches, I don't think users will stick with it long enough to get it past the beta stage.
The only explanation I could ever imagine is that a small part of my mind was tied up thinking about the game, so I was less prone to day dream while playing. However, I had played so much that I didn't really have to think about it any more, so enough of my brain was free to process what the teacher was saying.
This study indicates that something similar is going on while listening to music. I think this could be a powerful discovery.
For the speaker, preparing the talk has been top of mind for the past N hours/days/weeks. Not so for the audience. If you think about the situation from their perspective, you'll realize they don't want to hear about how you prepared the talk or how you approached the talk (usually). They want to hear your thoughts on the topic -- the result of your preparation.
This rule generally eliminates phrases like "while preparing this talk, I realized...", "when Joe asked me to give this talk...", "I didn't really prepare for this talk...", "I get nervous giving talks like this...", etc.
In almost all cases, you can simply strike those phrases from the script and your talk will be more focused and concise for it.
I will get just as much out of paul's talks because I love his talks and will always pay attention to every word. Some percentage of the audience, however, will take a lack of preparation qualifier as a reason to zone out.
As Jason notes in the article, spontaneity can be a huge boon. I don't immediately see how the latter can be, though it's possible.
I suppose paul may truly be an exception, but it seems that I would get just as much out of his talks (which is to say, a ton) whether or not I knew how much time he had spent in preparation.
With ShopTalk, we're trying to solve just one (very important) piece of the puzzle: real-time communication. We don't want to own the group, though, as the article says. Since most organizations have some sort of LDAP server (MS Active Directory being the most common), we'll be rolling out LDAP integration soon, so that you only have to add/remove/update users in one place and they only have to remember one password. SSO ftw.
No, but the gold rush might be. The iPhone is still a very viable platform for making money selling software. Mobile apps can be incredibly useful, and the App Store makes it easy for people to spend money.
It's hard to get noticed right now because there has been an absolute flood of apps. As people start to figure out that not all app developers get rich, that flood will slow to a more reasonable stream.
There does seem to be a market inefficiency in the huge disparity in sales between apps that are featured by Apple and apps that aren't. Picking up that slack in the market has to be an opportunity for a startup. If Apple isn't providing a good way for great apps to be found in the App Store, someone else should.