Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Government

Submission + - Just the Facts: S&P's $2 Trillion Mistake (treasury.gov)

suraj.sun writes: In a document provided to Treasury on Friday afternoon, Standard and Poor's (S&P) presented a judgment about the credit rating of the U.S. that was based on a $2 trillion mistake. After Treasury pointed out this error — a basic math error of significant consequence — S&P still chose to proceed with their flawed judgment by simply changing their principal rationale for their credit rating decision from an economic one to a political one.

S&P incorrectly added that same $2.1 trillion in deficit reduction to an entirely different oebaseline where discretionary funding levels grow with nominal GDP over the next 10 years. Relative to this alternative baseline, the Budget Control Act will save more than $4 trillion over ten years — or over $2 trillion more than S&P calculated.

S&P acknowledged this error ( http://online.wsj.com/article/SB10001424053111903366504576491421339802788.html?mod=WSJ_hp_LEFTTopStories ) — in private conversations with Treasury on Friday afternoon and then publicly early Saturday morning. In the interim, they chose to issue a downgrade of the US credit rating.

U.S. Dept of the Treasury: http://www.treasury.gov/connect/blog/Pages/Just-the-Facts-SPs-2-Trillion-Mistake.aspx

Comment Re:It is a TEA (party) tax (Score 1) 1239

This seems to be the new Republican party talking point as I see that George Will is pushing it extensively. If you mean the vote on the final debt ceiling bill which is not just a debt ceiling increase but a pure Republican spending cut bill with no tax revenues to help pay down the debt. So it is not surprising that many voted against it.

And how would these Democrats have made the teabaggers irrelevant? What would their vote have helped to shape a final bill that they strongly disapproved of?

Comment This is not going to happen (Score 1) 271

Sorry, wishful thinking is not going to do it. This is not going to happen in my 20 years. I doubt if it will happen in 50 years. There are many problems to be solved in making this trip and this is going to take a concerted effort and a LOT of money and we just don't have the will to do it. This is just not the kind of mission that can be done on the cheap.

No one regrets that more than me but wishing is not going to make it so.

Comment Re:[sigh] (Score 1) 457

That's a pretty myopic view. Other app translation layers are going to be knocked out of the market too.

To Apple that is just unfortunate collateral damage. Regrettable, but the enemy must be eliminated. And that is my point.

You can't develop for a game console without using the certified tools from the console vendor, and paying out the ass for the privilege. Prior to the iPhone, there were plenty of phones and platforms with even more draconian restrictions. Any app for any phone on Verizon Wireless required code to be written in Java.

So porting your iPhone app to another platform isn't much of an issue anyway. Unless the other target platform restricts you to Java.

In essence Apple's updated section 3.3.1 policy would require you to manually retype and reprogram your application unless it was originally written in one of Apple's approved languages. I doubt very few if any of the vendors that required the use of their development tools actually specified how that code got written - even if it was Java. As long as it was in their approved language utilizing their specified APIs. Whatever the target language requirements the code could still be generated from another language - except in the Apple iPhone/iPad world.

Again the target was absolutely Adobe Packager in this case. It will hurt others, but they would never haven enacted this policy without the Packager.

I'm not sure why this "bloatware" argument came up here. The generated code may or may not be more "bloated" than a hand generated program in the approved language. I'm sure many of the existing hand written apps in the App Store are not shining examples of efficient, tightly written code. Any apps generated from ActionScript or another language/platform would require the same approval from Apple before being released into the store.

And Apple will continue its war on Adobe with the slavish approval of the Apple fans.

Comment Re:[sigh] (Score 3, Insightful) 457

While I don't necessarily agree with Apple's iPhone policies, I don't see anything anticompetitive with regards to this particular policy (you must develop only in C, C++, or objC).

Please have the guts to say whether you agree or disagree with their policy instead of the constant waffling and weasel words displayed by most of the Apple and Jobs fans here.

This policy disallowing cross-compilers is clearly aimed at one company - Adobe. I have been around computers for a long time and I've never seen such a ridiculous restriction - ever. It is very odd and is clearly and carefully worded in such a way to crush the Adobe Packager, but in such a way that they hope can avoid legal ramifications.

There is absolutely no technical reason for it - even to accomplish Apple's stated goals of having a consistent user experience. A cross compiler can generate native Apple code using documented API's. It still has to meet Apple's approval to get into the App Store which still allows them reject it if it didn't meet their other criteria.

It is clearly anti-competitive - whether it is illegally so would hopefully be explored in an investigation - although I'm not holding my breath.

But it is definitely wrong and I would hope even Apple and Jobs fans would have the courage to at least complain to Apple that attempting to crush their competitors will not be tolerated by their developer community (and I'm definitely not holding my breath for that).

Comment Re:Blurring only targets makes them easy to pick o (Score 1) 597

Oh, good point. I often forget about the Pentagon, since they happened to hit the side of it that was empty.

Just to correct your use of the word "empty" to describe the section of the Pentagon that was struck by Flight 77. There were 125 people killed inside the Pentagon in the collision. Not to mention the 54 innocent people on Flight 77 itself.

So I hardly think the word "empty" applies to the Pentagon air strike.

Slashdot Top Deals

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...