So your recommendation would be to assess an individuals contribution as a part of the whole, assign a percentage value, and vest that over 4 years with a 1 year cliff?
Hopefully browser companies will be more rigorous about migrating their users to newer versions so that we avoid the issues IE6 has presented by still having a large install base even after two subsequent versions have been released.
And still no full release version for Mac / Linux. I find this particularly interesting considering the Google "Operating System" is going to be a custom interface on top of a Linux kernel.
Judging by the number of Erlang stories on the front page (19 out of 25 currently) I would say that's your problem right there...(wholly in jest, half in earnest)
I agree and think this is especially relevant for sites and apps that target tech-savvy users - as a group they will most likely already be using a browser other than IE and even if they do will be more likely to understand the reason for lack of total cross browser compatibility. If this became a trend it would begin to do one of two things - either cause Microsoft to consider adopting web standards compliance or cause users to adopt alternate browsers. Both options should be equally as welcome in the web development field and help to reduce the time wasted on needless hacks and workarounds to accommodate one product.
I am really interested to see where Andriod devices go in the marketplace. I really like my iPhone but would happily consider an Android phone if it offered the same level of hardware/software integration and polish of operating system I enjoy with the iPhone. I think the biggest struggle for Google may be providing that experience since they do not manufacture the hardware.
I would definitely pay (whether $5 or $50 doesnt matter) a year but feel that paying just to post/comment would merely serve to limit the number of people committed to quality contribution without offering added value to the core community. Essentially you would have to pay to help other HN users. What if the stories remained public but viewing/participating in the discussion required membership (at a cost)?
One of the really great aspects of Dropbox is that it versions all content and just transmits/saved the delta's after the original file is saved. It there an easy way of achieving that around a webdav share?
I am really glad to see that they are updating it for Django 1.x. I have not programming background but have been trying to decide on a web-focused language/framework to learn, and Django was highest on my list. Up until now, however, there weren't any online resources (that I had found) that detailed getting started with Django 1.x. I've started looking at Ruby/Rails, but may have to reconsider my decision now that there is a good resource available.
From what I've been reading recently, the startups the recession will hurt most will be those that have weak plans to monetize. That is encouraging because it will force startups to consider their path to profitability more carefully and hopefully result in companies that are more successful long-term. Which will ultimately benefit everyone else as well.
I have lurked here for a while and have only recently began submitting stories and am starting to participate. My personal opinion is that people who haven't frequented the site enough to obtain the karma required to downvote (such as myself currently) do not understand the culture of the site enough to know what is that should stay vs. go. By reaching a certain level you are proving that you are working effectively on behalf of the community here and that your opinion should be taken more seriously. Just my take on it though.