brentb

Inability, perhaps. Unwillingness? You're out of your mind.

Microsoft has had their fingers in smartphones, music players, search engines, touch computing, web mail, [you name it] for YEARS. And they are not just dabbling... they have poured billions into these areas, trying to come up with something that gains traction.

Microsoft doesn't make "the occasional try" at innovation, they are a veritable firehose of attempts to innovate. Microsoft Research is HUGE (and well respected within the research/academic community) and as I mentioned above they spend billions every year trying to develop new products and break into new markets.

The fact that Microsoft's efforts in this area have been largely unsuccessful over the past decade doesn't mean they aren't trying or aren't willing.

This ruling is really only one or two steps away from a court mandating that all ISPs monitor network traffic for unlicensed content and restrict it accordingly (since they are enabling piracy just as much as Limewire was).

I know Limewire has been around for a long time and all the cool kids moved on to other filesharing networks and technologies long ago, but I think this news is significant and troubling.

The fact that the music industry has managed to shut them down is just one more lost battle in the net neutrality war.

First of all, others might upvote this post simply because they're intrigued by the experiment itself (or for any number of other reasons) and not because of what is or isn't in the title. Secondly, your sample size is one and there is no control group (that I know of).

If you're truly interested in studying this, might I suggest reviewing historical hacker news submissions and, after controlling for as many other effects as you can (author reputation, time of day, other keywords in title, etc.), measure the statistical impact of having the words "Hacker News" in a title. It might be a bit of work to gather, parse and analyze the data you need, but I'm sure the community would be interested.

So while you're right that the instance-hour cost has remained flat since the launch, the actual costs of using the AWS platform as a supercomputer or server farm has fallen dramatically.

"Higher tax rates for the upper brackets don't lead to less taxes paid by the poor - they lead to more taxes paid by the poor."

You're confusing correlation (or, perhaps more accurately in this case, coincidence) with causation here. You correctly point out that "the fraction of tax revenue paid by the richest 1, 5, and 10% are much higher now than they were when the top tax rates were higher", but this obviously can only be the case because the income gap has widened. Despite paying lower marginal rates than they have through much of recent history, the richest 1, 5 and 10% of Americans now make so much compared to the other 90% of Americans that they still account for a larger share of revenue. If the income gap had remained stable or shrunk, the opposite would be the case. Now don't get me wrong... I'm certainly not anti-income gap and I have no agenda around redistributing wealth. I'm simply explaining why your statement is dead wrong.

What I do have an agenda around is making the tax burden distributed in the way that is best for society (and, thereby, individuals within that society, including myself). I feel that this involves heavily graduated taxation, despite the fact that I'm in that uppermost bracket. I'm not being selfish and looking for a handout and I'm not suggesting that there's anything wrong with making obscene amounts of money... I simply feel its better for society to impose higher taxes on those who can more easily afford it. Warren Buffett (and countless others) agree with me. You obviously don't, but that's no excuse to twist facts to support your agenda.

It's true that you can order the markup however you want and write the CSS to make it look right, but the key point is recognizing that (unless you position everything absolutely) there is still no true separation between the markup and the CSS (at least where layout is concerned). If they were truly independent, then it wouldn't matter what order the elements appeared in the markup... the CSS would lead them to render the same way on the screen every time.

It's worth pointing out that there is true independence between the markup and CSS where styling is concerned (and this is where CSS shines). If you style the background, font, opacity, whatever of a particular element and then move that element to a different location within the markup, the element will still look exactly the same (unless the new position in the DOM subjects it to other CSS rules that override the old ones).

I'm rambling a bit here, but all I'm really trying to say is that CSS has its place in the web development toolbox, but old-school tables often have the edge when looking for a layout that just works.

Quality matters, but there are other things that also matter, such as actually getting working code written. Some of us (and I've personally struggled with this for a long time) have a hard time letting go of our quest for perfection and settling for shipping code that's imperfect but works. When Jeff says that "quality just doesn't matter that much," what I took this to mean is: quality matters, but it matters less than we sometimes feel like it does. And that doesn't mean he's condoning writing crappy code; he's simply saying that we tend to overvalue this abstract concept of quality and that can have a crippling effect on our productivity.

Joel focuses on dogmatic adherence to development methodologies/principles as an example, specifically testing. I got the impression that he thinks testing is great and it has its place in the software development ecosystem. It tends to increase software quality and there are certain types of software for which it is really, really important (Jeff mentions framework code as an example). That said, taken to an extreme, testing can get in the way of getting things done... getting working code written and out the door / live on the server / whatever. It can also get in the way of modifying working code, as intentional changes to the way that code works always breaks some percentage of your unit tests, just as a regression will. And while catching unintentional regressions is great (and one of the best reasons you should unit test), constantly having to rewrite your tests every time you change the behavior of an internal class can be a real drag on your productivity. And that can be bad.

The key is to avoid being overly dogmatic in your adherence to development principles. Instead, be pragmatic and find a balance. Test enough to ensure adequate quality (whatever that happens to be for your product), but no more. Otherwise you're just doing yourself (or your employer) a disservice.

I didn't... I clearly stated that those were the top marginal rates and further down in my comment, I noted the difference between what someone making 400K would pay marginally and on average.

When folks don't spend their money, they buy dumb.

I don't understand this comment at all... please explain.

If it's so patriotic [to pay taxes], why do you want to exclude people from it?

I, like Buffet, Gates and many others, believe that those of us who are in a position to pay 40% of our income and still live in extraordinary comfort should do so. Those who aren't in such a position shouldn't be expected to do so. I don't have rich parents and I started out relatively poor... if it wasn't for low tax rates when I was broke and not making much, it would have been much, much harder for me to make a success of myself. Now that I'm doing better, I'm happy to pay it forward to the next generation struggling to make something of themselves and make everyone in the country better off a result. Even from a purely selfish viewpoint, graduated tax brackets make sense.

Unfortunately, such a simple and effective solution is politically very unpopular, which is why we have yet to see it passed into law. People want to take care of the environment, as long as it doesn't cost them anything. Well, most people anyway.

This is actually a great heuristic, but pollution is only part of the story. A more general (and correct) statement would be "excluding externalities (including pollution) the cheaper one really is better for the environment".

Externalities are basically costs or benefits (to society, the environment, etc.) that aren't reflected in the price paid for an item. One really important thing to note is that externalities extend far beyond pollution and can be both positive and negative.

Pollution is one of the more visible negative externalities that get discussed, but there are plenty of others (for example, driving a car involves a host of negative externalities in addition to pollution such as increased road congestion (longer commute times, more fuel burned in traffic, more accidents)).

There are also plenty of positive externalities that often get ignored. Take windmills, solar panels and hybrid cars. The positive externalities associated with manufacturing these items include lower future manufacturing costs for such items (and lower prices and environmental costs as a result) and investment in R&D aimed at making electricity and/or transportation cheaper (both in terms of environmental and financial costs). So even though solar panels may currently be losing proposition environmentally, there are positive externalities that make buying solar panels today (and thereby moving the industry forward) a Good Thing for the environment.

You state that your company is profitable. In this case, if you pay yourself a low salary and get audited, the IRS can (and will) retroactively adjust your salary to whatever THEY feel is reasonable and comparable for a CEO of a successful small company. Then you will owe back taxes, penalties and interest on whatever amount they determine you cheated them out of. The process isn't very democratic and getting audited is a HUGE pain, so I'd recommend going with something reasonable in the 100K range to avoid scrutiny.