Alternative definition of "NSA" == Network Storage Attachment
In no particular order - dealing with management not interested in product quality - dealing with management who is biased towards their local site over product quality (Tel Aviv is full of ass-hats in this regard) - dealing with management that interprets "Agile" as being 30-45 minute "standups" every day that are nothing more than "I worked on Bug X today" rehashes. - dealing with management wherein the people hired by a particular manager are automatically given more credibility than people who are forcibly transferred in. Yes, I refer to AMD from direct experience.
Larry Niven has gone into a great deal of theoretical depth on monopoles. Worth reading
Yup. A Troll-bait comment subject. But not every project is one where it can be afforded to "fix it" next month/next quarter. Device drivers. Compilers. Mainframe OS's. I heard a figure recently (from in-person discussion with a Mainframe SW person) that downtime costs them upwards of US$10,000 PER SECOND of downtime. Agile focuses on fast responses to customer bugs, not on ensuring that the number of bugs experienced by the customer is virtually zero. The point is that Mission Critical content has to have a correctness level which is an order of magnitude (or more) than a game or a less-than-wonderful UI. A bad case scenario: Oh, I'm sorry, Miss/Mr. medical patient of Therac25 (http://en.wikipedia.org/wiki/Therac-25) - we'll fix that in two revisions by using our Agile process (its a tough bug to fix), and we're sorry that you will contract a horrible form of cancer in the meantime.
Change the acronym, now relevant to OO-fans.
Wait - you forgot the 3 pages of required COBOL prologue to create a "hello world" style program.
The problem isn't Windows per-se. It is Metro. Metro is just not usable unless you have a touch screen. Enterprise PCs are not touch screen. Existing PCs are not touch screen. Making it horribly difficult to use a "traditional" (non-touch-screen) interface is a fatal flaw. And not just for Windows. Some of the newer linux distributions are equally unusable. I tried Fedora 17 for my web server. Truly worthless UI. Fine if you are running a tablet, but completely unsuited for a server. Went back to CentOS on my web server. And I've used RedHat/Centos on a regular basis since kernel 1.3.57.
Phalse. Windows 3.x did NOT have "task scheduling" It was "pre-emptive multi-tasking". My college OS project was better at Multi-tasking (and context switching) than WinDoze 3.x. In that sense, Windows 3.x was actually "less" than an application on top of DOS - it constrained things to prevent actual multi-tasking.
Bzzzzt. Use of Qt presumes some sort of GUI. Not all applications need a GUI. Why would a loader need Qt? For the puzzled, a loader is
/lib/ld.so* and is the key bit of code which manages where your application sits in Virtual Memory, along with the statically bound dynamic libraries. For general application developers, It is something well beyond your capacity to understand, so stick with your burger-flipping.
How many people _actually_ shoot more than 10 frames/minute on a regular/continuous basis? Really. Think about your personal usage. The likelyhood is that the answer is Z-Eee-Arrr-Oooh. ZERO. or close to it. Those who do are serious about their video, and are much more picky about things than simple capture rates.
Liar and/or Troll.
Too bad the AMD sacked the vast majority of their software people with any sort of Linux skills/background at the end of October. They could have been relevant.
It is unfortunate that the Linux kernel still does not support a number of key features available in currently available hardware. Such as some features that Windows8 supports out-of-the box. Here's one example: AMD's LWP feature set. It requires XSAVE/XRSTOR, but has been rejected by the Linux kernel developers. No, I'm NOT an AMD employee. Yes I do own a couple of desktops based upon AMD cpus. Motivation: COST, COST, COST.
Writing anonymously as a former AMD-er: the performance has absolutely NOTHING to do with the underlying architecture. The root cause is a software development (if you can call it "development") culture which is completely incapable of moving at more than a snails pace. Thank you Ben Bar-Haim & associated Markham Bozos. I've met a lot of developers who are actually focused on quality at AMD, but they generally seem to be in the minority. Too many managers/directors of SW products at AMD seem to believe that the "look and feel" of the UI is much more important than actually being correct, let alone performant. I personally know for a fact that the shader compiler team is totally dedicated to correctness and high performance. But when they are [under] staffed at N, while the UI portion of the Catalyst driver is staffed at N^2 (or greater) the end result is inevitable. Goals are set on how "pretty" it is, rather than on performance and correctness.
An anonymous reader writes "I used to run a small web design service--the domain for which, I allowed to expire after years of non-use. A few weeks ago, I noticed that my old site was back online at the old domain. The site-cloners are now using my old email addresses to gain access to old third-party web services accounts (invoicing tools, etc.) and are fraudulently billing my clients for years of services. I've contacted the Russian site host, PayPal, and the invoicing service. What more can I do? Can I fight back?" Define "fight back" - you purposely abandoned the sites, so your "can I fight back" whinging seems like you are simply jealous of "them" for billing on behalf of completed services.. To simplify, you come across as an SCO-style-entity even though you _EXPLICITLY_ gave up the rights to your domains. For your stupidity, do not pass go, do not collect $0.01.