I have attempted to bring this issue to my chain of command in the following ways, and it has met with stonewalling and been ignored: -- Date X, letter to Officer Y, outlining same details.
On date X+1 I was regrettably killed in a friendly fire incident, and so I never wrote this letter subsequently.
Drop a Beagle USB bus analyzer between the mouse and the host, try changing all the settings you posibly can, and use the recorded results to write a libusb client application that can set all of the settings. Problem solved.
I hate that people complaint about eminently solvable software engineering problems simply because they don't want to be the ones to solve them.
There are also economic reasons that Android replicates a lot of internal Linux APIs in order to get out from under the EXPORT_SYMBOL_GPL() so it can have faster/closed source graphics drivers.
Look, I most recently worked for Google on the ARM ChromeBook that Samsung recently announced. In the process, I did bring-up on the cellular modem and the camera, fixed the PMIC code, and did other things that ended up in the Linux Samsung 5250 board support, as well as rewrote the i8042 keyboard driver in u-boot in order to let it support ANSI 3.64 escape sequences for keys that couldn't be repreented by a single keycode. I also did work on the embedded controller and touchpad integration in the older original commercial Chromebooks from Acer and Samsung both.
I also filed for two patents.
Linux gets a lot of tactical development being released for free, and it gets a lot of strategic development that remains closed source. Just like much of the original Tivo work, and just like the actually high performance 3D nVidia support, all of which are also closed source.
A company which "gets" open source development "gets" that you give away the tactical stuff so that you offload your maintenance, and you hold the strategic stuff very close to you so that you can continue to afford to pay developers to work on stuff.
Google is in a fairly unique position in that most of the people playing with open source inside Google aren't supported by amortization of their work product, but instead are supported by advertising revenue. Frankly, most of them are not contributing to Googles bottom line (and I did not kid myself about this; I did some outstanding work, but probably the patents which could be used defensively if applied to phones or tablets was my biggest contribution to the bottom line).
So yeah, nice work if you can get it, but not something that generally generates revenue, and I know for a fact that there is a lot of code that Google has been struggling to get into Linux for many years (e.g. the virtual TSC resynchronization code for AMD processors, for one).
And the claim that BSD doesn't get a lot of commercial development is also BS.
I was on the Core OS kernel team at Apple for 8 years, and was the primary kernel person involved in getting Mac OS X's UNIX certification. Inside Apple, you are not allowed to write papers for external publication, or books, without a VP signature, and you are unlikely to get one, so even if things don't get crowed about, there's a hell of a lot of commercial effort going into BSD there.
Juniper also does a lot of commercial BSD development, and so do 3 of the top 4 L3/L4 switches and load balancers.
You just don't see it because people who Mention features or use" of BSD licensed code, at least for the traditional BSD license, have to give credit when they are claiming a specific feature, and so rather than bother, most companies simply don't mention it.
A lot of graphics software infringes on existing patents, but that isn't a reason you can state without risking treble damages in a lawsuit, so most of the graphics driver writers tend to just look the other way and hum as they dance past that particular graveyard. Practically, it's impossible to write genuinely competitive graphics code without infringing some East Texas idiot's patent.
There are also cases where code has specific strategic value to a company, and they want to amortize the cost of development over some period of time before they let their competitors use the code. For example, the Soft Updates code that Kirk McKusick, Julian Elisher, and I worked on for FreeBSD was licensed under a free-for-non-commercial-use license for a period of two years before we opened it up for general use. This was to allow us to recoup the investment on developing the code by allowing us to run our hardware without a UPS, while everyone else in the market had to have a UPS to deal with power failure and recovery. If you don't have it, you have to treat a power failure as a kernel panic and do a full fsck in order to return your disk to a known good state, since you can't otherwise guarantee that it wasn't a crash followed by a triple fault, which might have written bad data to some portion of the disk. So all the competing border router/SOHO server devices had to have batteries, which increased their cost relative to our product. It's one of the reasons IBM bought our company.
Yeah, it'd be great if some idiot were to spend 10 years of their free time neglecting their families so that all this stuff could be free, but no one really wants to be that idiot: people work on free software for love, and they work on the hard problems and productization in exchange for money, since no one is going to do scut work for free unless they're a masochist (if you happen to know one, though, I have a project or two they could tackle if they really wanted to suffer).
I know a lot of rural area ISPs, and using PtP, you can get 150 mile ranges out of the equipment at 300Mbits speeds, although typically they are operated between 3,5 and 15 miles, depending on customer density. The Cambium Networks equipment in particular used to be known as Motorola Canopy, until it was sold off in 2011.
Above a certain threshold, EarthLink or other large providers will also happily buy you out, if you let them, in order to grow customer base (buying out small ISPs has been EarthLink's primary means of business expansion for decades now). I know two providers in Utah and one in Idaho who have chosen this route as their exit strategy.
Note that you can also use certain microwave backhaul frequencies without needing to have a specific FCC license to use them, though the cost per link hardware for full duplex unlicensed spectrum tends to run in the $10K-$15K range. You can typically use a one or two hop configuration to get to a large urban area where bandwidth is cheaper to come by, although your customers aren't going to be winning an Unreal Tournament battles at that ping latency.
It's actually a combination of battery and cooling unit, and it uses Argon gas in order to enable the acquisition indicators, which are needed for the IR and UV targeting systems. Without those parts, you're back to a relatively dumb aiming mechanism. Not that I don't think that any DRM you tried wouldn't be hackable anyway.
Probably they would just get Russian SA-24 "Grinch" missiles instead, which are roughly equivalent to Stingers, with much less DRM than the proposed missiles.
So you say that it is best to solve this problem in each application inidividually instead of, say, running one process on each system which makes sure that the clocks stay in sync for all applications?
No more than you appear to be saying that protocols should be implemented in each user space process instance, rather than once in the kernel and shared by all processes, I think. This is a protocol level problem, not an application level problem.
It's one of the few Federal programs I would actually like to see expanded.
They would have more to work with if they could do away with the bloated govt contractor process.
I know we pay them public money, and they can be bought off for the purposes of industrial espionage or for just plain espionage by corporations or foreign powers, but it's still disrespectful to call them "contractors" instead of "Senators".
If by "big iron", you mean "IBM Mainframes or similar kit", then your question has meaning.
If by "big iron", you mean "lots of irritating PCs that I think I can add up into a supercomputer because all problems are amenable to parallel solutions", then your question is meaningless.
Assuming the second, you are much better off just using identical hardware for everything, since it will mean you have the components on hand should anything go wrong, and it will mean that you have a single maintenance SKU. In the long run, that's going to save you a hell of a lot more money than having one or two specialty boxes per rack of set of 8 or 16 racks, since it means you don't lose 8 or 16 racks worth of your "big iron" everytime one of your cheap little specialty boxes fails.
NTP servers are NOT about consistency, they are about making badly designed protocols, such as NFS, capable of limping, instead of just falling on their face.
If the requests on these protocols used a client timestamp for the client's idea of the current time, then the server on receiving the request could look at its idea of the current time, and arrive at a delta before it actually did anything other than enqueue the request locally.
Then when the server responded with a non-"now" timestamp in any client response, it could apply this delta to the response value, and as far as the client was concerned, it and the server would have synchronized ideas of "now", without resorting to all of this NTP BS or worrying about clock drift, or anything.
I lobbied very strongly to try to get this fixed in NFSv4; maybe we will get our collective heads out of our butts by NFSv5.
This really doesn't demonstrate using the same interface transparently across a desktop and a tablet.
Unless it's one of those vertically mounted tablets that normally comes with an attached keyboard and mouse (i.e. a touchscreen PC or laptop), it's really pretty uninteresting as far as the tablet video information goes.
Please provide a video of doing exactly the same things on a standard (non-touchscreen) desktop using a mouse.
Kosovo was also "a region within Serbian sovereign territory", but when the Serbs started to wipe out the locals - which, according to you, they had full rights to, as a sovereign country - their whole country was pounded much worse than Georgia.
By "you", I assume you mean the US government, which I assure did not represent my personal views in the matter, and whose executive at the time was an asshole I voted against in the previous presidential election, right?
Get a grip: the US has an internal revolution every 4-8 years; we just do it peacefully, rather than by lobbing shells between the red and blue states. You might want to try it some time.
You guys really don't "get" Democracy yet, do you? So the majority of you elected an asshole, Gamsakhurdia. Georgia has Parliamentary elections every three years; ignore the inflammatory rhetoric from the asshole, and work to get a majority for some other party in the next election in 3 years. Problem solved.
The foreign power in question built the barracks because it was part of a peacekeeping force that was officially accredited as such by the joint commission from all sides of the conflict after the last war. Said agreement was not formally withdrawn by Georgia until September, i.e. after the conflict. Ironically, the commander of the Georgian battalion of the same peacekeeping force received orders to participate in the take-over of the city (and carried them out).
If you can't resolve the conflict internally, then an internally accredited peacekeeping force isn't going to be able to do it either. Appeal to the UN for intervent. There appear to be 189 countries willing to back that, including 3 of the 5 permanent UN security council members, and as of that date, 6 of the remaining 10 non-permanent serving members would probably voted for a resolution as well, if only to piss Putin off.
As for where I live...I live in the New Orleans area...I've been through more than my share of storms on the level of intensity that NYC got, and I do know what they are like.
I'm pretty sure the New Orleans area building codes are not up to snuff for a Loma Prieta level earth quake.
It's similarly unfair to expect the NYC codes to be up to snuff for a Sandy-like storm (although I'd expect them to be a lot closer than they were, given the 20 and 50 year storm history for the area, as you implied, I wouldn't expect them to be quite there still).
Of course, the codes were not up to snuff in New Orleans for Katrina, but it was a worse disaster than it should have been, given that the levee (redesigned) levee system was started in 1965 and was supposed to have been completed in 1978/1979 - 25 years before Katrina hit.
PS: A lot of the levee delays were environmentalist opposition, legal opposition, local populace opposition, and local government failures to maintain the parts of the system that had already been handed off from the corps of engineers to local authorities.
"Tskhinval or Ch'reba; Russian: ()), is the capital of South Ossetia, a disputed region which has been recognised as an independent Republic by Russia and another four UN members, and is regarded by Georgia and all other UN member states de jure as a region within Georgian sovereign territory."
Perhaps you should shell a barracks when a foreign power builds one in one of your cities. At least according to the 189 of the 193 members of the UN who agree that Ossetia is part of Georgia. I'm pretty sure if Mexico built a barracks in San Antonio Texas, if they didn't leave, we'd shell it too.
Without broadcasting the power to the airliner from a couple square miles of battery-backed array, so the airliner doesn't need to carry the weight of the power source, it's not going to work.
It was separatists, not the Georgian military, and it happened after a long list of provocations by Russia involving Abkhazia and South Ossetia. In 2008, Russia shot down a Georgian drone over Abkhazia, which they did not technically have the right to do, as it was part of Georgia. Things got worse from there.
The eventual equilibrium saddle for this, after everyone is done punching and counterpunching, is:
(1) The new law destroys the fair use provisions of France Intellectual and Property Code, Art. L. 122-5(3)(a) (2) Content providers may request payment for content on what was previously "fair use" (3) Google offers free listing to those who allow indexing of content (a cross-licensing agreement) (4) Google considers indexing any content requiring payment to be advertising, and charges for it (5) Net zero money actually exchanged (6) France taxes the "listing" and "advertising" transactions
The result is a net loss in revenue for both Google and the French newspapers by the amount of the tax.
I'm pretty sure that the only news sources not opting into a cross-licensing agreement would be state-run news organizations.
One final point: Google could always just set up the advertising fees formula such that they always balance at a net zero loss to Google after the French tax, putting the entire burden on the French providers who do not opt into the cross-licensing.
Probably that he's not the right person to be in charge (sorry, Tim).
Ive is an industrial designer (make it pretty). Forestall is a software engineer (make it work). Cook is an industrial engineer (make it cost less).
Steve was able to balance the trade-offs in these interests because he was the 800 pound gorilla. He also had Avi (technological visionary) and Bertrand (better software engineer than Forestall (again, sorry Scott; he was much better at managing simultaneous projects with radically different requirements)) to rely upon before that.
Tim is very good at optimizing supply chain, because it's instinctual for him: control access to supplies of at least 6 key components of products to prevent copycats and third-shifting by the Chinese factories; hold a knife to the throat of key suppliers like Sharp for displays to control costs; etc.
The latest iPhone display is a bean-counter decision, not a Steve decision; changing the aspect ratio relative to all previous iPhone models because "that's what there was a lot of in the warehouse" when Apple still has a knife to Sharp's throat was a horrible mistake. Unless it wasn't a mistake, in which case I have to say "good job monetizing the App Store by requiring application rebuys": still a bean counter decision, and not a Steve one.
Personally, I fault Steve himself for never working to develop a protege within Apple, which is how the COO got turned into the CEO by default and power vacuum.
Some people have pointed to Apple's 20% increase in year-over-year profits as portending the future value of the company; however, I would have to say the rapid decline from 20% year-over-year innovation is probably a better indicator.
I have to say, I actually did expect a faster decline due to recognition of new_product = previous_product++ by the larger world, but that much money can't just evaporate overnight, and neither do good employees, despite who is at the helm (with the exception of the large option/RSU cliff timed exodus following the "Steve is stepping down" announcement).
For 10 concurrent developers it will set you back about $10,000. BattleMap (now called McCabe IQ) will set you back about $30,000 a seat, and can generate test cases for unit tests which will test every branch path, and correlate them back to line items in your requirements documentation.
Probably overkill, if you are not working on a life support system of some kind, but the tools exist.
I'm probably in a better position that you are to know what costs are and aren't.
You should also be aware that it's Samsung manufacturing the thing, and Google has only supplied software engineering resources, and a number of hardware reference designs.
HAN Communications - Frequency: 2.4 GHz ISM Band - Spreading technology: Direct Sequence - PHY/MAC: 802.15.4 - Transmitter output: 20 to 23 dBm (200 mW) - Receiver sensitivity: -97 dBm for 1% PER - Power, Transmit: 1.6 W (1.8 W max.)
The transmissions on the HAN band are nearly continuous, since it does station connection heartbeat broadcasts at 11 second intervals (same as anything talking to a 2.,4GHz AP with SSID enabled).
This is specifically why PGE has had to remove the "smart meters" on homes with Arlec Model PC600 "Automatic Light", which operate on ultrasonics in the 2,5GHz band, and which are capable of being triggered by the 2.4GHz "smart meter" broadcasts. Basically the damn security lights turn on every 11 seconds; time out after 5 or so, go dark for a bit, and then come back on. All night long.
Start with the Java it requires in order to run the client. Then move onto the licensing that prohibits redistribution of the client, and therefore the client can not be signed code, and then move onto the known replay attack CERT advisories for the Cisco VPN system itself.
Slashdot Mirror
I have attempted to bring this issue to my chain of command in the following ways, and it has met with stonewalling and been ignored:
-- Date X, letter to Officer Y, outlining same details.
On date X+1 I was regrettably killed in a friendly fire incident, and so I never wrote this letter subsequently.
Drop a Beagle USB bus analyzer between the mouse and the host, try changing all the settings you posibly can, and use the recorded results to write a libusb client application that can set all of the settings. Problem solved.
I hate that people complaint about eminently solvable software engineering problems simply because they don't want to be the ones to solve them.
There are also economic reasons that Android replicates a lot of internal Linux APIs in order to get out from under the EXPORT_SYMBOL_GPL() so it can have faster/closed source graphics drivers.
Look, I most recently worked for Google on the ARM ChromeBook that Samsung recently announced. In the process, I did bring-up on the cellular modem and the camera, fixed the PMIC code, and did other things that ended up in the Linux Samsung 5250 board support, as well as rewrote the i8042 keyboard driver in u-boot in order to let it support ANSI 3.64 escape sequences for keys that couldn't be repreented by a single keycode. I also did work on the embedded controller and touchpad integration in the older original commercial Chromebooks from Acer and Samsung both.
I also filed for two patents.
Linux gets a lot of tactical development being released for free, and it gets a lot of strategic development that remains closed source. Just like much of the original Tivo work, and just like the actually high performance 3D nVidia support, all of which are also closed source.
A company which "gets" open source development "gets" that you give away the tactical stuff so that you offload your maintenance, and you hold the strategic stuff very close to you so that you can continue to afford to pay developers to work on stuff.
Google is in a fairly unique position in that most of the people playing with open source inside Google aren't supported by amortization of their work product, but instead are supported by advertising revenue. Frankly, most of them are not contributing to Googles bottom line (and I did not kid myself about this; I did some outstanding work, but probably the patents which could be used defensively if applied to phones or tablets was my biggest contribution to the bottom line).
So yeah, nice work if you can get it, but not something that generally generates revenue, and I know for a fact that there is a lot of code that Google has been struggling to get into Linux for many years (e.g. the virtual TSC resynchronization code for AMD processors, for one).
And the claim that BSD doesn't get a lot of commercial development is also BS.
I was on the Core OS kernel team at Apple for 8 years, and was the primary kernel person involved in getting Mac OS X's UNIX certification. Inside Apple, you are not allowed to write papers for external publication, or books, without a VP signature, and you are unlikely to get one, so even if things don't get crowed about, there's a hell of a lot of commercial effort going into BSD there.
Juniper also does a lot of commercial BSD development, and so do 3 of the top 4 L3/L4 switches and load balancers.
You just don't see it because people who Mention features or use" of BSD licensed code, at least for the traditional BSD license, have to give credit when they are claiming a specific feature, and so rather than bother, most companies simply don't mention it.
A lot of graphics software infringes on existing patents, but that isn't a reason you can state without risking treble damages in a lawsuit, so most of the graphics driver writers tend to just look the other way and hum as they dance past that particular graveyard. Practically, it's impossible to write genuinely competitive graphics code without infringing some East Texas idiot's patent.
There are also cases where code has specific strategic value to a company, and they want to amortize the cost of development over some period of time before they let their competitors use the code. For example, the Soft Updates code that Kirk McKusick, Julian Elisher, and I worked on for FreeBSD was licensed under a free-for-non-commercial-use license for a period of two years before we opened it up for general use. This was to allow us to recoup the investment on developing the code by allowing us to run our hardware without a UPS, while everyone else in the market had to have a UPS to deal with power failure and recovery. If you don't have it, you have to treat a power failure as a kernel panic and do a full fsck in order to return your disk to a known good state, since you can't otherwise guarantee that it wasn't a crash followed by a triple fault, which might have written bad data to some portion of the disk. So all the competing border router/SOHO server devices had to have batteries, which increased their cost relative to our product. It's one of the reasons IBM bought our company.
Yeah, it'd be great if some idiot were to spend 10 years of their free time neglecting their families so that all this stuff could be free, but no one really wants to be that idiot: people work on free software for love, and they work on the hard problems and productization in exchange for money, since no one is going to do scut work for free unless they're a masochist (if you happen to know one, though, I have a project or two they could tackle if they really wanted to suffer).
This. Here's a handy resource, the WISP Technician Wiki: http://www.wisptech.com/index.php?title=Main_Page
I know a lot of rural area ISPs, and using PtP, you can get 150 mile ranges out of the equipment at 300Mbits speeds, although typically they are operated between 3,5 and 15 miles, depending on customer density. The Cambium Networks equipment in particular used to be known as Motorola Canopy, until it was sold off in 2011.
Above a certain threshold, EarthLink or other large providers will also happily buy you out, if you let them, in order to grow customer base (buying out small ISPs has been EarthLink's primary means of business expansion for decades now). I know two providers in Utah and one in Idaho who have chosen this route as their exit strategy.
Note that you can also use certain microwave backhaul frequencies without needing to have a specific FCC license to use them, though the cost per link hardware for full duplex unlicensed spectrum tends to run in the $10K-$15K range. You can typically use a one or two hop configuration to get to a large urban area where bandwidth is cheaper to come by, although your customers aren't going to be winning an Unreal Tournament battles at that ping latency.
I could definitely live without another push for COPPA.
Children are already protected by not being able to legally enter into contracts before their 18th birthday.
It's actually a combination of battery and cooling unit, and it uses Argon gas in order to enable the acquisition indicators, which are needed for the IR and UV targeting systems. Without those parts, you're back to a relatively dumb aiming mechanism. Not that I don't think that any DRM you tried wouldn't be hackable anyway.
Probably they would just get Russian SA-24 "Grinch" missiles instead, which are roughly equivalent to Stingers, with much less DRM than the proposed missiles.
And then download the free version of UnixWare 2.1.2:
http://web.archive.org/web/19990117023208/http://www.freebird.org/freeUW.html
Otherwise, time to update your OS, and keep copies of the installation media this time.
So you say that it is best to solve this problem in each application inidividually instead of, say, running one process on each system which makes sure that the clocks stay in sync for all applications?
No more than you appear to be saying that protocols should be implemented in each user space process instance, rather than once in the kernel and shared by all processes, I think. This is a protocol level problem, not an application level problem.
It's one of the few Federal programs I would actually like to see expanded.
They would have more to work with if they could do away with the bloated govt contractor process.
I know we pay them public money, and they can be bought off for the purposes of industrial espionage or for just plain espionage by corporations or foreign powers, but it's still disrespectful to call them "contractors" instead of "Senators".
The ability to record everything you say and do from one foot away and follow you when you leave the surveillance areas and continue to monitor you.
I'm pretty sure you are missing this guys point. We are getting close to the threshold of their being no way to leave surveillance areas.
If by "big iron", you mean "IBM Mainframes or similar kit", then your question has meaning.
If by "big iron", you mean "lots of irritating PCs that I think I can add up into a supercomputer because all problems are amenable to parallel solutions", then your question is meaningless.
Assuming the second, you are much better off just using identical hardware for everything, since it will mean you have the components on hand should anything go wrong, and it will mean that you have a single maintenance SKU. In the long run, that's going to save you a hell of a lot more money than having one or two specialty boxes per rack of set of 8 or 16 racks, since it means you don't lose 8 or 16 racks worth of your "big iron" everytime one of your cheap little specialty boxes fails.
NTP servers are NOT about consistency, they are about making badly designed protocols, such as NFS, capable of limping, instead of just falling on their face.
If the requests on these protocols used a client timestamp for the client's idea of the current time, then the server on receiving the request could look at its idea of the current time, and arrive at a delta before it actually did anything other than enqueue the request locally.
Then when the server responded with a non-"now" timestamp in any client response, it could apply this delta to the response value, and as far as the client was concerned, it and the server would have synchronized ideas of "now", without resorting to all of this NTP BS or worrying about clock drift, or anything.
I lobbied very strongly to try to get this fixed in NFSv4; maybe we will get our collective heads out of our butts by NFSv5.
This really doesn't demonstrate using the same interface transparently across a desktop and a tablet.
Unless it's one of those vertically mounted tablets that normally comes with an attached keyboard and mouse (i.e. a touchscreen PC or laptop), it's really pretty uninteresting as far as the tablet video information goes.
Please provide a video of doing exactly the same things on a standard (non-touchscreen) desktop using a mouse.
Kosovo was also "a region within Serbian sovereign territory", but when the Serbs started to wipe out the locals - which, according to you, they had full rights to, as a sovereign country - their whole country was pounded much worse than Georgia.
By "you", I assume you mean the US government, which I assure did not represent my personal views in the matter, and whose executive at the time was an asshole I voted against in the previous presidential election, right?
Get a grip: the US has an internal revolution every 4-8 years; we just do it peacefully, rather than by lobbing shells between the red and blue states. You might want to try it some time.
You guys really don't "get" Democracy yet, do you? So the majority of you elected an asshole, Gamsakhurdia. Georgia has Parliamentary elections every three years; ignore the inflammatory rhetoric from the asshole, and work to get a majority for some other party in the next election in 3 years. Problem solved.
The foreign power in question built the barracks because it was part of a peacekeeping force that was officially accredited as such by the joint commission from all sides of the conflict after the last war. Said agreement was not formally withdrawn by Georgia until September, i.e. after the conflict. Ironically, the commander of the Georgian battalion of the same peacekeeping force received orders to participate in the take-over of the city (and carried them out).
If you can't resolve the conflict internally, then an internally accredited peacekeeping force isn't going to be able to do it either. Appeal to the UN for intervent. There appear to be 189 countries willing to back that, including 3 of the 5 permanent UN security council members, and as of that date, 6 of the remaining 10 non-permanent serving members would probably voted for a resolution as well, if only to piss Putin off.
Yes, I understand the commonly held view that Russia pushes a lot of money into controlling the outcome of the elections in neighboring states - http://www.csmonitor.com/Commentary/Opinion/2012/1001/Beware-Russia-s-hand-in-elections-in-Georgia-Ukraine-Lithuania - but the answer to this is that you have to refuse to be bought, and call out those who are willing to accept the payola.
As for where I live...I live in the New Orleans area...I've been through more than my share of storms on the level of intensity that NYC got, and I do know what they are like.
I'm pretty sure the New Orleans area building codes are not up to snuff for a Loma Prieta level earth quake.
It's similarly unfair to expect the NYC codes to be up to snuff for a Sandy-like storm (although I'd expect them to be a lot closer than they were, given the 20 and 50 year storm history for the area, as you implied, I wouldn't expect them to be quite there still).
Of course, the codes were not up to snuff in New Orleans for Katrina, but it was a worse disaster than it should have been, given that the levee (redesigned) levee system was started in 1965 and was supposed to have been completed in 1978/1979 - 25 years before Katrina hit.
Government Accounting Office report of Katrina: http://www.gao.gov/new.items/d051050t.pdf
PS: A lot of the levee delays were environmentalist opposition, legal opposition, local populace opposition, and local government failures to maintain the parts of the system that had already been handed off from the corps of engineers to local authorities.
"Tskhinval or Ch'reba; Russian: ()), is the capital of South Ossetia, a disputed region which has been recognised as an independent Republic by Russia and another four UN members, and is regarded by Georgia and all other UN member states de jure as a region within Georgian sovereign territory."
http://en.wikipedia.org/wiki/Tskhinvali
Perhaps you should shell a barracks when a foreign power builds one in one of your cities. At least according to the 189 of the 193 members of the UN who agree that Ossetia is part of Georgia. I'm pretty sure if Mexico built a barracks in San Antonio Texas, if they didn't leave, we'd shell it too.
Without broadcasting the power to the airliner from a couple square miles of battery-backed array, so the airliner doesn't need to carry the weight of the power source, it's not going to work.
It was separatists, not the Georgian military, and it happened after a long list of provocations by Russia involving Abkhazia and South Ossetia. In 2008, Russia shot down a Georgian drone over Abkhazia, which they did not technically have the right to do, as it was part of Georgia. Things got worse from there.
Here's the Wikipedia account; start your editors!
http://en.wikipedia.org/wiki/2008_Georgia–Russia_crisis
The eventual equilibrium saddle for this, after everyone is done punching and counterpunching, is:
(1) The new law destroys the fair use provisions of France Intellectual and Property Code, Art. L. 122-5(3)(a)
(2) Content providers may request payment for content on what was previously "fair use"
(3) Google offers free listing to those who allow indexing of content (a cross-licensing agreement)
(4) Google considers indexing any content requiring payment to be advertising, and charges for it
(5) Net zero money actually exchanged
(6) France taxes the "listing" and "advertising" transactions
The result is a net loss in revenue for both Google and the French newspapers by the amount of the tax.
I'm pretty sure that the only news sources not opting into a cross-licensing agreement would be state-run news organizations.
One final point: Google could always just set up the advertising fees formula such that they always balance at a net zero loss to Google after the French tax, putting the entire burden on the French providers who do not opt into the cross-licensing.
Probably that he's not the right person to be in charge (sorry, Tim).
Ive is an industrial designer (make it pretty).
Forestall is a software engineer (make it work).
Cook is an industrial engineer (make it cost less).
Steve was able to balance the trade-offs in these interests because he was the 800 pound gorilla. He also had Avi (technological visionary) and Bertrand (better software engineer than Forestall (again, sorry Scott; he was much better at managing simultaneous projects with radically different requirements)) to rely upon before that.
Tim is very good at optimizing supply chain, because it's instinctual for him: control access to supplies of at least 6 key components of products to prevent copycats and third-shifting by the Chinese factories; hold a knife to the throat of key suppliers like Sharp for displays to control costs; etc.
The latest iPhone display is a bean-counter decision, not a Steve decision; changing the aspect ratio relative to all previous iPhone models because "that's what there was a lot of in the warehouse" when Apple still has a knife to Sharp's throat was a horrible mistake. Unless it wasn't a mistake, in which case I have to say "good job monetizing the App Store by requiring application rebuys": still a bean counter decision, and not a Steve one.
Personally, I fault Steve himself for never working to develop a protege within Apple, which is how the COO got turned into the CEO by default and power vacuum.
Some people have pointed to Apple's 20% increase in year-over-year profits as portending the future value of the company; however, I would have to say the rapid decline from 20% year-over-year innovation is probably a better indicator.
I have to say, I actually did expect a faster decline due to recognition of new_product = previous_product++ by the larger world, but that much money can't just evaporate overnight, and neither do good employees, despite who is at the helm (with the exception of the large option/RSU cliff timed exodus following the "Steve is stepping down" announcement).
For 10 concurrent developers it will set you back about $10,000. BattleMap (now called McCabe IQ) will set you back about $30,000 a seat, and can generate test cases for unit tests which will test every branch path, and correlate them back to line items in your requirements documentation.
Probably overkill, if you are not working on a life support system of some kind, but the tools exist.
I'm probably in a better position that you are to know what costs are and aren't.
You should also be aware that it's Samsung manufacturing the thing, and Google has only supplied software engineering resources, and a number of hardware reference designs.
Here is the correct information for the PGE smart meters:
The meter is radiating on two bands:
NAN Communications
- Frequency: 915-928 MHz
- Spread spectrum technology: FHSS
- Channels: 43
- Receiver sensitivity: -97 dBm for 1% PER
- Modulation: Binary FSK
- Transmitter output: 30 dBm
HAN Communications
- Frequency: 2.4 GHz ISM Band
- Spreading technology: Direct Sequence
- PHY/MAC: 802.15.4
- Transmitter output: 20 to 23 dBm (200 mW)
- Receiver sensitivity: -97 dBm for 1% PER
- Power, Transmit: 1.6 W (1.8 W max.)
The transmissions on the HAN band are nearly continuous, since it does station connection heartbeat broadcasts at 11 second intervals (same as anything talking to a 2.,4GHz AP with SSID enabled).
This is specifically why PGE has had to remove the "smart meters" on homes with Arlec Model PC600 "Automatic Light", which operate on ultrasonics in the 2,5GHz band, and which are capable of being triggered by the 2.4GHz "smart meter" broadcasts. Basically the damn security lights turn on every 11 seconds; time out after 5 or so, go dark for a bit, and then come back on. All night long.
Start with the Java it requires in order to run the client. Then move onto the licensing that prohibits redistribution of the client, and therefore the client can not be signed code, and then move onto the known replay attack CERT advisories for the Cisco VPN system itself.