They didn't run roughshod over checks and balances. He had more or less full congressional authorization. Congress in the 1990s had made regime change official US policy and in 2003 authorized the war.
Democrats did not want a foreign policy election. Had they thwarted Bush Democrats "undermining the US war on terror" would have been the election. They probably would have won, but in 2002 the American people were solidly behind Bush.
$3t is a lot of money to bring stability. We probably could have stabilized about 100 countries for that. Moreover Iraq ain't really all that stable now.
Saddam was annoying and somewhat dangerous. He was difficult for the USA to deal with. Replacing him might have been a good idea. A long term occupation of Iraq made replacing him militarily not worth it.
You take their word that production dropped sharply?
Yes. The FBI compiles and publishes crime statistics. If the aggregate statistics didn't coincide with local ones that would get noticed. If they do than you have hundreds of independent case studies.
I don't, if production dropped sharply I would expect a sharp jump in street prices. That never happened.
Not necessarily. That's called velocity. Supply changes induce demand changes or they induce price changes. In this case demand dropped off which was the desired result. Meth became harder to get. In general during the 1990s dealer prices were stable but street prices were slowly falling which made it less profitable. What does seem to happen though is sharp shifts in purity. Meth becomes rarer and harder to get, purity drops, Meth becomes less desirable and less available leading to lower demand... Eventually it stabilizes at a new lower level with high purity.
These problems don't go away with pdf. Assume I pick a pdf.
1) PDF demands line by line spacing but I can either kern or not. Should the e-reader support both? 2) PDF allows bitmaps and simple vector graphics. But if I want different resolutions I need to run different pdfs. How should I handle view (low dpi screens) vs. print? 3) PDF group everything with fixed position on a page. The document has no idea what is grouped with what, grouping is a reader function? What should the e-reader do? 4) PDFs don't allow for any variable content, so 4 is resolved. 5) PDF's do allow for unlimited callouts and hyperlinks. They also can imbed arbitrary multimedia... 6) PDFs don't support testing
As an aside though, to a limited extent PDFs do support DRM.
There was nothing knee-jerk about it. After years of discussing they put the ban in place and meth production dropped off sharply. They allowed the sale again and meth production shot back up. They banned it and meth production dropped sharply.
You may not like it, but this piece of drug legislation is doing exactly what it is supposed to.
OK lets talk about things that have nothing to do with lockin?
1) Should the system export simple text or export typeset text? Typesetting can be important for advertising, poetry, math while untypeset works better for fiction?
2) Should should the system allow bitmaps, and if it does multiple bitmaps for different sizes or should vector graphics be mandatory?
3) How should graphics be grouped? Should they be attached to specific pages, i.e. the system preserves layout or just specific
4) Should the system resolve advertising at time of read, at time of publish or at time of sale? If time or sale or time of read can the system make use of other information like: age, other ads you've responded to... Note this has a huge impact on the cost of books. People willing to tolerate ads get much cheaper media.
5) Should the system support multimedia: sound and video or no? For example foreign language textbooks.
6) Should the system support testing? Should the end user always be able to override the testing or should the testing be under the control of purchaser not the end user?
If EA were acquiring a company they'd be involved. But no, not a major release. That's still too small scale until it blew up. Board members typically are people who are politically connected, connected to like possible acquirers, connected to financiers... EA has plenty of people in the gaming industry inside the company they don't need the board to provide that kind of experience.
A board of directors is generally responsible for things like regulatory issues. They may not even know what Sim City was until it became a PR disaster.
Paul Vivek -- from GE Leonard Coleman -- from Heinz and baseball team owner (probably helps on sports licensing) Jay Hoag -- finance guy Jeffrey Huber -- adverting Maffei -- media Ubinas -- Ford Simonsian -- mobile expert 3 ex EA guys
The kernel differs other levels of the OS differ. It is a different OS, like moving from Linux to OSX. The APIs are similar but do different things.
You were claiming before it was deliberate. If your claim now is that this was a ton of work and they should have done it anyway, then while I still disagree it becomes a question of opinion not fact.
Samsung is barely present. So with the exception of HTC who else could be selling Windows phones? Next year several more vendors are hitting Windows phones.
As for sold, Nokia is supply constrained not demand constrained.
I understand, answering machines might even be earlier. There were automatic phone recorders since the 1960s. But voicemail OTOH not so. Same function very different mechanism.
Dude it is worse than that. The Symbian / MeeGo crowd are generally the people who were emotionally or financially invested in Nokia's old Symbian / MeeGo strategy. They despise Stephen Elop, the move to Windows phone and the Lumias. This isn't fan boys this is broken hearted lovers.
HTC did another 12m or so in 2012 and is expecting growth.
Carriers pushed through huge subsidies all during 2012 and Verizon continues to see Microsoft as key to their business strategy.
What sort of product doing 40% year-over-year growth, good reviews, moderate or better OEM support, so or better developer support, and a good fit for Microsoft strategy gets cancelled?
No latency is much lower than 16ms under that situation. It is close to 0, it is just relying on the fact that the visual system will fill in missing details at 60hz. But it will fill in the detail with continuing the previous motion. 33ms would be a problem except that the later frames will be inconsistent with the delay so the brain fixes it. If the delay were really 33ms then it would be visually stressing.
This has been tested. With computer graphics up to about 125fps and instant response feels better. Do a web search on frame rates and computer graphics.
Surely you meant RFB, as RDP is a proprietary Microsoft protocol, and "most distributions" only include a client for it. As I have mentioned before, RFB is inadequate.
That's bullshit [in reference to buffering] Application programmer does not have to know details of X protocol,
You are reading my comment backwards. In those situations where applications need to control buffering they can't under X11. Obviously applications that don't care about buffering won't have to worry about it under Wayland or X11.
RDP is designed for Windows, and would be suboptimal for any modern GUI toolkit other than Windows.
I don't think so. I think RDP works fine as long as the client (usual meaning, server for X11) has a toolkit capable of responding to high level instructions. So a Qt clients needs to have Qt but not.NET, a Gnome client needs to have GTK...
Authentication, encryption, session management, support for absolutely everything that can be displayed, has to be done once, on one level.
RDP is a secure protocol. Encryption is handled like any other network protocol. Authentication is handled using the security system on the server. Session management is handled by the server.
____
Anyway I think I've shown pretty conclusively that far from vaporware this is going on, this is the direction. It is being implemented, the support exist...
KDE, Gnome and most (hopefully) most other toolkits are going to support RDP Wayland is going to have RDP clients Most distributions will include RDP server software
So Wayland apps run remotely. It isn't part of the graphics system because part of the design of Wayland is that remote use changes things like buffering strategies that applications needs to know about. The graphics system is too far down the chain, far better is something like the toolkit.
They cancel out human noise fine. I use them in noisy places and I can relax and focus. You are going to want to listen to some sort of music, just pick something easy to listen to like new age.
OK good, you get the point that act of war is stronger.
In the case of Hezbollah the claim of the Lebanon is that the Lebanese army is weaker than Hezbollah. That is Lebanon is not the sovereign agent over South Lebanon / Hezbollah territory. Since Hezbollah does not answer to the Lebanese government that territory is now either:
a) Under the control of a rebel army group b) Occupied territory.
Since Hezbollah does answer to Syria / Iran technically the world treats Southern Lebanon as occupied territory. Lebanon's inability to handle that territory helps. Everyone agrees that Hezbollah would kick the Lebanese army's butt.
Slashdot Mirror
They didn't run roughshod over checks and balances. He had more or less full congressional authorization. Congress in the 1990s had made regime change official US policy and in 2003 authorized the war.
Democrats did not want a foreign policy election. Had they thwarted Bush Democrats "undermining the US war on terror" would have been the election. They probably would have won, but in 2002 the American people were solidly behind Bush.
$3t is a lot of money to bring stability. We probably could have stabilized about 100 countries for that. Moreover Iraq ain't really all that stable now.
Saddam was annoying and somewhat dangerous. He was difficult for the USA to deal with. Replacing him might have been a good idea. A long term occupation of Iraq made replacing him militarily not worth it.
You take their word that production dropped sharply?
Yes. The FBI compiles and publishes crime statistics. If the aggregate statistics didn't coincide with local ones that would get noticed. If they do than you have hundreds of independent case studies.
I don't, if production dropped sharply I would expect a sharp jump in street prices. That never happened.
Not necessarily. That's called velocity. Supply changes induce demand changes or they induce price changes. In this case demand dropped off which was the desired result. Meth became harder to get. In general during the 1990s dealer prices were stable but street prices were slowly falling which made it less profitable. What does seem to happen though is sharp shifts in purity. Meth becomes rarer and harder to get, purity drops, Meth becomes less desirable and less available leading to lower demand... Eventually it stabilizes at a new lower level with high purity.
These problems don't go away with pdf. Assume I pick a pdf.
1) PDF demands line by line spacing but I can either kern or not. Should the e-reader support both?
2) PDF allows bitmaps and simple vector graphics. But if I want different resolutions I need to run different pdfs. How should I handle view (low dpi screens) vs. print?
3) PDF group everything with fixed position on a page. The document has no idea what is grouped with what, grouping is a reader function? What should the e-reader do?
4) PDFs don't allow for any variable content, so 4 is resolved.
5) PDF's do allow for unlimited callouts and hyperlinks. They also can imbed arbitrary multimedia...
6) PDFs don't support testing
As an aside though, to a limited extent PDFs do support DRM.
There was nothing knee-jerk about it. After years of discussing they put the ban in place and meth production dropped off sharply. They allowed the sale again and meth production shot back up. They banned it and meth production dropped sharply.
You may not like it, but this piece of drug legislation is doing exactly what it is supposed to.
OK lets talk about things that have nothing to do with lockin?
1) Should the system export simple text or export typeset text? Typesetting can be important for advertising, poetry, math while untypeset works better for fiction?
2) Should should the system allow bitmaps, and if it does multiple bitmaps for different sizes or should vector graphics be mandatory?
3) How should graphics be grouped? Should they be attached to specific pages, i.e. the system preserves layout or just specific
4) Should the system resolve advertising at time of read, at time of publish or at time of sale? If time or sale or time of read can the system make use of other information like: age, other ads you've responded to... Note this has a huge impact on the cost of books. People willing to tolerate ads get much cheaper media.
5) Should the system support multimedia: sound and video or no? For example foreign language textbooks.
6) Should the system support testing? Should the end user always be able to override the testing or should the testing be under the control of purchaser not the end user?
If EA were acquiring a company they'd be involved. But no, not a major release. That's still too small scale until it blew up. Board members typically are people who are politically connected, connected to like possible acquirers, connected to financiers... EA has plenty of people in the gaming industry inside the company they don't need the board to provide that kind of experience.
A board of directors is generally responsible for things like regulatory issues. They may not even know what Sim City was until it became a PR disaster.
Paul Vivek -- from GE
Leonard Coleman -- from Heinz and baseball team owner (probably helps on sports licensing)
Jay Hoag -- finance guy
Jeffrey Huber -- adverting
Maffei -- media
Ubinas -- Ford
Simonsian -- mobile expert
3 ex EA guys
The kernel differs other levels of the OS differ. It is a different OS, like moving from Linux to OSX. The APIs are similar but do different things.
You were claiming before it was deliberate. If your claim now is that this was a ton of work and they should have done it anyway, then while I still disagree it becomes a question of opinion not fact.
Huh? WP7 uses the CE architecture WP8 uses the NT architecture. They aren't similar.
This isn't propaganda this is easily checkable fact. The systems are 3rd cousins not siblings.
Yes there is. But investing money to expand production is rather clear evidence a product isn't being abandoned which was the original claim.
Those are manufacturing numbers. Lumia is supply not demand constrained.
Samsung is barely present. So with the exception of HTC who else could be selling Windows phones? Next year several more vendors are hitting Windows phones.
As for sold, Nokia is supply constrained not demand constrained.
I understand, answering machines might even be earlier. There were automatic phone recorders since the 1960s. But voicemail OTOH not so. Same function very different mechanism.
Dude it is worse than that. The Symbian / MeeGo crowd are generally the people who were emotionally or financially invested in Nokia's old Symbian / MeeGo strategy. They despise Stephen Elop, the move to Windows phone and the Lumias. This isn't fan boys this is broken hearted lovers.
WP 7 to WP8 was a major architectural shift. WP8 -> WP9 isn't going to be one.
As for Silverlight, that wasn't good but that was a trauma for developers not end users.
Nokia alone is doing
35m for 2012
55m for 2013
85m for 2014
HTC did another 12m or so in 2012 and is expecting growth.
Carriers pushed through huge subsidies all during 2012 and Verizon continues to see Microsoft as key to their business strategy.
What sort of product doing 40% year-over-year growth, good reviews, moderate or better OEM support, so or better developer support, and a good fit for Microsoft strategy gets cancelled?
This article sounds like flamebait to me.
If you're a Pavlovian Dog, yes. The polite thing to do, if you have Free Will, is let your answering machine or voicemail take the message.
We are talking about the days when phones had physical bells. There was no voicemail.
No latency is much lower than 16ms under that situation. It is close to 0, it is just relying on the fact that the visual system will fill in missing details at 60hz. But it will fill in the detail with continuing the previous motion. 33ms would be a problem except that the later frames will be inconsistent with the delay so the brain fixes it. If the delay were really 33ms then it would be visually stressing.
This has been tested. With computer graphics up to about 125fps and instant response feels better. Do a web search on frame rates and computer graphics.
Second, no GUI toolkit supports such a thing, or ever announced any intention to do so, so you are talking out of your ass.
http://www.kde.org/applications/internet/krdc/
http://sourceforge.net/projects/gnome-rdp/
Surely you meant RFB, as RDP is a proprietary Microsoft protocol, and "most distributions" only include a client for it. As I have mentioned before, RFB is inadequate.
Microsoft publishes the spec:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa383515(v=vs.85).aspx
That's bullshit [in reference to buffering] Application programmer does not have to know details of X protocol,
You are reading my comment backwards. In those situations where applications need to control buffering they can't under X11. Obviously applications that don't care about buffering won't have to worry about it under Wayland or X11.
RDP is designed for Windows, and would be suboptimal for any modern GUI toolkit other than Windows.
I don't think so. I think RDP works fine as long as the client (usual meaning, server for X11) has a toolkit capable of responding to high level instructions. So a Qt clients needs to have Qt but not .NET, a Gnome client needs to have GTK...
Authentication, encryption, session management, support for absolutely everything that can be displayed, has to be done once, on one level.
RDP is a secure protocol. Encryption is handled like any other network protocol. Authentication is handled using the security system on the server. Session management is handled by the server.
____
Anyway I think I've shown pretty conclusively that far from vaporware this is going on, this is the direction. It is being implemented, the support exist...
No you are missing the point.
KDE, Gnome and most (hopefully) most other toolkits are going to support RDP
Wayland is going to have RDP clients
Most distributions will include RDP server software
So Wayland apps run remotely. It isn't part of the graphics system because part of the design of Wayland is that remote use changes things like buffering strategies that applications needs to know about. The graphics system is too far down the chain, far better is something like the toolkit.
http://www.bose.com/controller?url=/shop_online/headphones/noise_cancelling_headphones/index.jsp
They cancel out human noise fine. I use them in noisy places and I can relax and focus. You are going to want to listen to some sort of music, just pick something easy to listen to like new age.
http://crackberry.com/blackberry-q10
I'll do you better than design:
http://lists.freedesktop.org/archives/wayland-devel/2013-March/007740.html
It's done.
OK good, you get the point that act of war is stronger.
In the case of Hezbollah the claim of the Lebanon is that the Lebanese army is weaker than Hezbollah. That is Lebanon is not the sovereign agent over South Lebanon / Hezbollah territory. Since Hezbollah does not answer to the Lebanese government that territory is now either:
a) Under the control of a rebel army group
b) Occupied territory.
Since Hezbollah does answer to Syria / Iran technically the world treats Southern Lebanon as occupied territory. Lebanon's inability to handle that territory helps. Everyone agrees that Hezbollah would kick the Lebanese army's butt.