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".

Or if you're a REAL expert, "Is NYC playing second fiddle to silicon valley?"

Here is one to add to the list - if you delete records and/or entire collections, you won't reclaim the associated disk space automatically. Once the space is allocated, it remains allocated and will be reused when more data is added later. If you want to reclaim the "empty space", you need to run a repairDatabase() which will lock the entire database while it's busy.

Yes - because whenever you buy hardware, optional upgrades are always available to purchase at cost-price /sarcasm

Although I guess it's not quite as bad with something like a notebook where at least you have the choice of buying your own upgrades and installing them yourself...

This attempt at being "clever" has definitely backfired on apple. If they had just done what was asked the first time, that would have been the end of it. Now it has to be dredged up and people will be reminded (again) that they lost the case. I find it hard to believe that their lawyers advised them that they would get away with something like this.

It's like this for every major product launch - gives the techbloggers something to talk about. Give it a few weeks and they will be bemoaning the next IOS / Android / Ubuntu release. I put this kind of thing into the "Bad News Sells" category. See http://pewresearch.org/assets/pdf/NewsInterest1986-2007.pdf

I've had 8 of these calls in the last month (had two in one day a few weeks back).

For me, the most frustrating part of the experience is that regardless of what you say, they follow their script to the letter - they're like method-actors which never get out of character. Just once I wanted them to say "ok - you got me!" but alas - apparently not having a PC or Windows is not enough to sway them.

I'm not sure early adopters are the easiest people to please... thinking of "antennagate" from iphone4 and now "scuffgate" from iphone5 I would say early adopters (who I suppose are generally experts - or at least technology-orientated) are more likely to pick up and report on things that

a) get viewership (i.e. complaining) and b) are so subtle the eventual mainstream user wouldn't even notice without it being pointed out to them.

I don't have any hard science to back my claim either way ;-)

Has there ever been an OS release where (at first) people prefer the new one? Windows 7 might be the exception only because the previous incarnation was so awful.

Ubuntu with Unity? we want the old desktop! IOS6? we want IOS5 and our maps! OSX Mountain Lion? We want Lion!

Change is always hard and almost never goes down well - this is not a new phenomenon and occurs naturally at the beginning of most major software versions. People will get used to it and move on with their lives...

It's not necessarily all or nothing - I have worked on several projects now each using multiple database-type options: mongodb for read-intensive, loose-schema type stuff where the growth is generally predictable (e.g. products, suppliers, logs), postgres for relational-type stuff (orders) and solr for searching (I know solr isn't a database but people seem hung up on whether mongodb supports case-insensitive searching - hint: don't use any database for search).

I doubt that, unless it's extremely simple, any set of requirements are an exact match to only one of these technologies... mix and match is the future :P

Here's a little confirmation bias at work... those with kids can't really undo that decision so spending time with the family is a knee-jerk "number one priority" (how many people would really come out and say they would prefer to work than see their kids? even if it's true, I doubt it would be socially acceptable).

Those who prefer the 100-hour weeks will no doubt say work is the number one priority. See "saving money for the future" vs. "spending money in case you die tomorrow" as other examples.

Agreed - this is fantastic. Although the getbootstrap docs have some neat things in there - it's sometimes hard to differentiate what comes built-in vs. what has been customized for the docs (and to extract the doc-specific functionality can be tricky).

I would favour a first-party device like the surface pro in this case rather than one of these as my perception is that something is likely to "just work" if hardware and software are from the same vendor (see: apple).

Should be interesting to see how the likes of asus can compete in the long run (I am guessing price and slightly garish features will most likely differentiate); having an actual product on the shelves surely gives you a head-start.

What I took away from reading this article is that because the umbrella of "software development" is so wide; everything from a static html page for your local charity up to curiosity/ mars rover - it's not practical to define a single set of methodologies, tools and techniques that will work, be pragmatic or make sense for all situations.

Do what you think is best for whatever it is you're building :)

It's not like this is the first time MS have done the hardware/software combo (which has been pretty successful for them)... xbox anyone?

Not a word, exactly, but certainly a variation of http://en.wikipedia.org/wiki/Onomatopoeia