Then you have the low end shovelware crap being made with the likes of Unity 3D. Although their days are numbered now they got greedy and chose to screw over devs.

Really? What have they done?

Or the democrats, liberals, communists, facists, socialists...

oh, wait...is there anyone left to use the technology?

that doesn't mean it's lacking in good plot and characters

You've got to be joking. Abrams' Kirk is criminally incompetent (even in the first movie, before your "Khan wanted him to screw up" rationalization could apply). The plots of both movies have holes big enough to drive a planet through, let alone a starship. (For example, WTF is the point of starships anymore, since they can apparently just beam across the galaxy now?!)

DS9 got pretty dark (e.g. Homefront/Paradise Lost, In the Pale Moonlight), but it was good. Abrams alleged-'trek' sucked for (many, many) other reasons.

Only on-disk, non-addressable controller proms are "read" by the software in the proms.

The boot prom has to boot stuff or the product can't be sold, and in this case is used to boot a program that runs on the hardware that continuously reads the prom. That HW can verify it, and all the other proms which are reachable from the CPU, including all sorts of stuff plugged into the various busses. That includes some disks, the ones we were worried about viruses wiping.

For some specific disks, you may have to pull the drive and clamp directly to the prom's pins.Those are the ones a spy would want to subvert.

XBox isn't capable as a standalone development platform in the first place, Linux is.

Offering a "port to Linux" button without actually having the development tools work natively on Linux treats Linux as if it were a standalone gaming console, like the XBox, but most actual Linux installs are not used for gaming as an XBox might be.

Clearly, the developers of Unity itself don't actually feel that taking the effort to even port their dev tools to Linux was worthwhile, so why should on earth should a game studio take Linux seriously, when,. as I said, most Linux installs are not generally used exclusively for gaming anyways?

Boot from a randomly chosen Linux rescue disk, and check the various proms. You've used the boot rom to boot a CD/DVD, but what you've booted is wildly different from the Windows systems that are the common target, so the attackers will have great difficulty in hiding what they've done from an unfamiliar system.

It's actually easier to hide evil stuff in disk proms, as your only access to them is via routines *in* the disk prom, as one of the other commentators pointed out,

Sampling the pixels directly from the image reveals that the dress color in the photo has a hue between in or around the range of 230 or so, which happens to be blue. However, because it appears that the dress was not directly lit, that hue may be arising because of diffuse interreflections with its surroundings, something that anything which has a lighter shade can be very susceptible to if the only light hitting it is diffused, and which is the kind of lighting that this dress does appear to be exposed to in the photo.

So there is simply too much information about the surrounding lighting conditions that has been lost from the photo to ascertain with any certainty what the actual color of the dress is... at least from this one photograph alone.

Debating the matter is pointless, because it is impossible to actually arrive at a logically valid conclusion merely from what one can see in this photograph except through sheer guesswork.

Pay them to not fill your brand new machine with crap? Name another market where you do that...

"Natural" vs. regular processed foods.

... the functional requirements are clear, and do not change during the development lifecycle.

Except what usually happens is that a feature change will come along *AFTER* the design phase has already started, or else the requirements weren't unambiguous enough in the first place. Oh... and in the real world, at least in my experience, a developer isn't often in the position of being able to say "we can't do that", unless the developer is also very amenable to finding a different employer in the extremely near future.

This usually puts the programmer in the position of having to be a sort of prognosticator, and anticipating what the most likely types of design changes are going to be while doing development, and designing software that will be robust enough to accommodate such changes with only a modest increase in time spent, without losing any work on design that has already been completed. Sometimes, particularly with an experienced programmer, or one who really knows the people who are likely to make design change requests, and so may be able to predict what they are liable to really want beyond what was stated in the functional requirements documentation, this kind of forecasting is within the grasp of a human being to accomplish But it's never easy.