I originally read the question as (47 X 75) + 25.
Due to some quirk of the font that was used, "%" was not visually distinct from "+".
There is always room for an honest misunderstanding.

Also, (45 x 75) / 24 = 140.625

The defendant made legal errors regarding personal jurisdiction, thus losing their opportunity to get the case dismissed for lack of jurisdiction AND their opportunity to argue the merits.
The plaintiff made legal errors regarding discovery, thus losing their opportunity to recover damages.
The trial judge made legal errors that twice resulted in the verdict being overturned.

In the end, the case was decided without any actual evidence on the merits being admitted.

Justice!

Actually, this was the one implication of TFA that I had a problem with. The profitability of an investment is not necessarily tied to growth. It is perfectly possible to use your resources to make tools, use the tools to make resources, and end up with more resources then you started with. Profit! While it is not possible to perpetually plow the profit back into the business and perpetually grow the profit, it is possible to perpetually plow the principal back into the business, and live off the profit.*

*For small values of "perpetual."

We are in an exponential growth phase. If you don't grow during the growth phase, you don't survive until the next phase...

Suppose you have a bacteria colony that grows exponentially, doubling in size every day, until their resources are used up, and they all die.
Suppose this colony grows exponentially for a thousand years, doubling in size every day.
Fully half the bacteria are born on the last day before the resources are exhausted, and they all die.

Exponential growth is not pretty.

And yes, things do change quickly.

Your comment is based on the false assumption that the music business is about selling music. Since the artists provide the music, they are entitled to the lion's share of the profits.

In reality, the music business is more of a chump matching service. The music companies match up chumps who are willing to pay for music with chumps who are willing to sign away their rights to music. Since the music companies provide the chumps, they are entitled to the lion's share of the profits.

My experience in the software development field is that employers generally consider two kinds of software developers to be a "net negative:"
1) People less than two years out of college
2) People in their first few months at a new job.
They perceive these people as not understanding their trade and/or not understanding the job that needs to be done. They may be able to produce something of value, but they require a significant amount of mentoring by someone who is much more productive. Further, there is a significant chance that anything actually produced by an inexperienced developer will have to be thrown out and/or redone.

This perception makes it hard to enter the field. Employers much prefer to hire someone with a few years of experience rather than a new grad.

All the "If the company asks you to work for free, they are trying to rip you off" comments miss a fundamental point: If interns were economically advantageous for the company, there would be a lot of companies staffed mostly by interns. But there aren't. Instead you see companies very reluctantly get one or two interns in order to address their corporate citizenship obligations. And then they neglect the interns, because they don't care enough about corporate citizenship to actually invest in the interns.

Co-ops and internships (paid or unpaid) are a way for newcomers to the field to get past this barrier to entry. I'm not saying every intern has a good experience. But internships in general address a very real problem for the intern. My advice to anyone who wants to be a software developer is: get as much on-the-job experience (paid or unpaid) as you can while you are in school. If you don't, you will have a difficult time finding a job at graduation. There is a very real chance that you will have to take a job that diverts your career in a direction you don't want it to go.

The problem with the Unix security model is that it is designed to protect users against other malicious users. It does this by allowing each user to trash his own space, but not anyone else's space. But in modern computing environments, there is usually only one user, and sometimes less, and the challenge is to protect the computer against malicious programs. So, letting every program trash the one user's space isn't really that useful.
Of course the Unix security model can be adapted to protect against malicious programs. But in practice it is so difficult that no one bothers to try.

It appears to me, after a brief scan of TFA, that vsys just provides finer granularity without addressing the fact that the security model is fundamentally broken.

We need a model that makes it natural and easy to run every program in its own sandbox.

"Do not track" is a nice way of saying "It is illegal to have certain kinds of information on a computer."
This makes me very nervous.
If my browser caches pages, does that mean I am illegally tracking?
If my web site saves logs for troubleshooting, am I illegally tracking?
If I use peer-to-peer file sharing software, am I illegally tracking?

What powers of search and seizure will the state need to enforce "Do not track?"

I haven't read this particular bill. Maybe it has some well thought out way of targeting advertisers without placing a huge new regulatory burden on everyone who uses a computer in California, or makes software that might be used on a computer in California. But I doubt it.

To address your points one by one:
1) Bankruptcy
Cutting this research would reduce the federal budget by about 0.0025%
The United States has a serious decision to make whether to: Cut military spending, Cut Medicare spending, Raise taxes, and/or Go bankrupt.
No other budgetary changes that the US can make will make any difference to the crisis we find ourselves in.
Trying to solve our budget problems by cutting research spending is just a way of denying the real problem.
http://en.wikipedia.org/wiki/Amdahl's_law

2) No shortage of energy
The resources used by our current energy technologies will be exhausted in a few decades. All of the replacement technologies being considered will take at least a few decades to deploy on the required scale.
Energy is THE scarce commodity in our economic system. A discovery that halved the price of energy would double the standard of living of every person on earth.

3) Corruption/Inefficiency of government funded research
If government does not fund this research, who will? Private companies tend to fund R&D that will make them rich, not basic research that will make future generations rich.
Is it better to do the research inefficiently or not do it at all?

The following discoveries were brought to you by US government funded research:
Nuclear power, Communication Satellites, The Internet

How many more kindles will this pricing option sell?
Are there really that many people out there that would walk away from a $139 kindle, but are willing to buy a $114 kindle with ads?
The discount would have to be much steeper in order to result in a measurable increase in sales.

I suspect that this is really about improving margins, not selling units. People who were already going to buy a kindle will opt for the cheaper one. The ad revenue it brings in will more than offset the purchase discount.

When interviewing people for QA positions, I routinely ask "Do you know what an SQL injection attack is?"
I have never yet interviewed a candidate who answered yes.
So, then I explain what an SQL injection attack is, and ask how they would test for vulnerability to one.
Almost without exception, the answer is "I guess I would try entering some special characters and keywords into the GUI, and see what happens."

Design patterns (or OO for that matter) do not provide any help with actually making a program work. They are solely about organisational concerns. They assist in making large codebases readable, reusable, and maintainable.

The distinction, at least in my mind, is that OO focuses on 'natural' objects and design patterns focus on 'artificial' objects. Natural objects exist in the business domain of the program. Things like Manager is a subclass of Employee is a subclass of Person. Artificial objects do not exist in the business domain. They exist purely to solve programming problems. Thing like Singleton, Visitor, and Facade.

In either case, they are specialized tools for solving specific problems.

The widespread use of "Design Patterns" is useful in explaining why OO should NOT be taught to college freshmen.
I view design patterns as an alternative methodology to OO methodology. Design patterns allow the productive use of OO languages without the unproductive baggage of OO methodology.
OO languages were originally created to facilitate the pre-existing ideas of OO programming and OO design.
Then, when programmers actually had these languages, they evolved a way of using them that is radically different than what was originally intended.
Clearly, there is enough value in OO that the languages are worth using, and enough difficulties that the methodologies are not worth using.
I expect that the next generation of tools and methodologies will take what is good from OO, and forget the rest.
In the mean time, I don't see the value of explaining to college freshmen a set of tools that were meant to be used one way, but in practice should be used a different way. (Actually, I do think that is a valuable lesson. But I think most freshman level courses treat the techniques being taught as unambiguously good.)

Presumably, most of the cost in this system is the concentrators, not the PV cells. So, perhaps the PV cells can be replaced when they deteriorate without driving the overall system cost up too much.