bitdiffusion

Maybe because the explanation isn't so much an explanation but an admission that core functionality was broken in a minor version release - and therefore almost orthogonal to the use of AI. If there had been no major regressions, do you think anyone would have complained?

People are (correctly) not going to be held to some kind of lower standard just because they "used AI" and "were fixing security issues".

yes

There was a post a few days ago about how the quality of SnowHN had gone down with people asking how they could block this category of submissions - so I wouldn't be too quick to equate an increase in ShowHN with anything positive.

Two possibilities:

1. Boredom 2. Infamy (although nobody seems to claim responsibility for attacks like this so not sure how that can be a motivating factor - but who knows).

The article attempts to explain "why not".

Here is the TLDR as I see it: If you insist of hiring over-qualified people, they are more likely to jump-ship as soon as something better comes along - staff turnover is a major issue.

They give you hardware that is capable of storing the advertised amount of data - they advertise it the same as any other vendor (nobody advertises "usable diskspace" unless there is a 59GB iPad out there).

When do you think hardware vendors should start specifying available disk space as part of their SKU? When it's less than 10%? 20%? Should this value include pre-installed applications?

It's not in defence of the OS - it's a rebuttal to the people who ignore all the other benefits of upgrading to a newer OS and cite the (often repeated) notion that the desktop as we know it is gone for good.

More FUD about the disk space issue... yes - there is a large recovery partition and yes - you can delete it to free up space. Any yes - perhaps MS would have been better off if they included a USB drive for recovery purposes (although I imagine trying to walk the average user through "booting from USB" to restore their partition would be a support nightmare).

This is just like the "omg - the desktop is gone and all we are left with is Metro!". Um yes... unless you "show desktop" and move on with your life...

And the "purpose of the surface pro"? How about "a tablet for those who need to be productive in a windows environment"?

For those that want the modern equivalent to relive your old time crisis, HOD, op-wolf days, (e.g. for mame cabinets), apparently the ones that use a dedicated infrared sensor (like the wii) are the most accurate (e.g. www.arcadeguns.com).

From the documentation:

Personal licenses are not available to companies in any way or form. Transfer of personal licenses to any third party and/or reimbursement for personal license purchase by a company are prohibited by the Personal License Agreement.

So not sure what to make of that exactly... Individuals can buy it and use it commercially but companies can't? Even if you're a contractor working in your spare time, you are likely to be registered as a limited company.

btw - personal licences only (i.e. not commercial licenses).

Maybe if you're only building a simple app, but I suspect most people at some point need other components like date pickers, format masks, form validation, table filtering/sorting etc. of which many require jQuery anyway.

This is just a re-imagining of the Steam interface to be optimised for large screens - I think the post above yours is referring to the rumoured "Steambox" that Valve themselves are supposedly working on.

Been waiting for this for two reasons: a) websocket support and b) now the version of IIS that runs under visual studio 2012 and the server matches hopefully avoiding any surprises (v8).

Oh - and provisioning a new server doesn't require 3 hours to apply updates :-)

"Look, there is what you intend and what you write. Your bugs are in between the two."

Umm no. Bugs are usually

a) a misinterpreation of the requirements (no amount of comments are going to save you) or

b) a (hopefully) subtle error in the code - again - I don't see how a comment is going to help you unless the comment is practically pseudo-code which I (hope) nobody is advocating.

Anyone have an example of the typical type of bug that is easier to fix when there are comments around? I agree about commenting "non-obvious" code though - at least in terms of it's intentions. Not necessarily as a way to fix bugs, but to prevent the next programmer from removing something that looks superfluous because nobody can remember why it's there. Something like (totally made up):

"Assign the customer id as a prefix to the comment field; SAP expects the format of <customer_id>__<comment> during import".