I don't think this is really about ship to ship combat, I think this is a replacement for the big guns of the Iowa class in their fire support role during an amphibious assault or supporting ground operations otherwise. It would be substantially cheaper to replace smart munitions dropped from airplanes, which is what primarily fulfills that mission now, with equally-accurate cheap projectiles rapidly fired from ships offshore, over the horizon, reserving the airplanes for special situations.
They don't seem to care much about their users. I had an account I hadn't used in years, long enough that the credit card associated with it was expired. This resulted in my account being locked in a way that required me to contact their helpdesk. After telling me to do the equivalent of power cycling my machine by going through their password reset screens, which I'd already tried, they told me that to restore my account I'd need to email them a picture of my driver's license. This leads me to believe that their support database is probably a goldmine for identity thieves and generally those databases are not exactly Fort Knox.
XSLT definitely has its flaws and I'm not currently using it, but I am currently building an app whose UI is heavily data-driven, meaning a screen might display a dynamic list of items, each with a totally different editing/viewing/previewing experience. You can dance around the edges of this with current templating engines to the point where you have a workable solution for a specific case, but honestly nothing really compares to the generalizing power of template matching where all you'd need to do is wire up the appropriate XPath selector to a new template and there you go. This level of abstraction does not even appear to be on the radar of the templating libraries I'm familiar with but I'd love to hear about those that do support it if they exist.
I've been in situations where it basically boils down to hierarchy and reinforcement of the status quo. I once had a request for a new laptop refused because it would've meant mine was newer than the president/owner's machine and that wasn't tolerable to the corporate ego.
With the exception of Amazon, who evidently weren't interested in cooperating, Tivo does a great job of this. You get some Amazon content but it's not the good stuff. For Hulu and Netflix you get unified search and you can do things like come across an in-progress movie in the guide, see that it's available on Netflix, and start watching it right away. I really wish Amazon would let Tivo have a decent app with Prime support.
Hopefully this doesn't mean they won't be showing up in padmapper and other apps like that. It's a pretty useful service while apartment hunting, although it would be awesome if they could find a better data source than CitySearch.
I'm curious how much water the various water projects in California lose to evaporation. The All-American Canal goes through the desert and is uncovered, for example. It seems like people have talked about covering them with solar cells, but it might be valuable just to cover them with anything.
He can do whatever he wants with his property, within the law of course, but at the same time, I find it hard to believe that he won't have moved on to the next thing within a few years, ultimately having done this for nothing.
It's also about poor consideration of the varying circumstances of real world use. Ideas about a full screen start menu that work well in small form factors can't just be assumed to work on a desktop display. I think the new start menu is great on a small touchscreen device like a tablet, but my workstation has a pair of 30'' monitors and it's ridiculous.
We have a number of one-click deployments running in TeamCity. It's honestly very straightforward. If you're deploying to Azure you can use either the Powershell or node.js libraries to talk to their API. We use powershell. Basically, we compile using msbuild, package the artifacts into an Azure package, and deploy it via the API. Doing zero-downtime deploys to Azure is a matter of how you use the API. You can substitute EC2, another cloud, or traditional hosting and while the tools and APIs get progressively less powerful, it's all doable. At the simplest level you may just use msdeploy as your "API."
I'm a huge believer in this kind of automation. We make extensive use of TeamCity to drive it. In addition to builds, automated tests, and deployments, we also use it for release promotion and doing other housekeeping tasks like cleaning up data from QA environments, restoring testing databases, etc.
I'm not sure that the states have any power here. If there's a federal law legalizing it, it doesn't matter what the state laws are. It's basically the reverse of the medical/legal marijuana scenario.
Yeah, I don't get that approach at all. I started with that, ran into a case where I wanted a route resolve, couldn't figure out how to do it without a huge amount of hassle, and ended up reorganizing around screens. I do still have global services, directives, and filters, but I define them as close to screens as I can and only pull them up to a global scope when necessary. The module-per-screen approach makes a lot of sense from both Angular and Require's perspective, I think.
We use the optimizer as well, during our build process, so you can use require to load everything during development and then optimize everything down into a single file later. The optimizer is pretty powerful and supports several different scenarios for doing this.
I use require.js for this. There are a number of seed projects out there to get you started, but I suggest not following them too closely. Once you understand the basic technique it's easier to figure out your own organizational structure. My main suggestion is to discard the seed project's suggestions of organizing things into directories like /controllers, etc., in favor of organizing the files around specific screens. This reduces friction when it comes to using things like route resolves, which are a huge pain if you have the routes in a routes.js and the controllers in controllers/MyController.js.
I don't remember this particular issue either, but I do remember that an optimal layout for one of the early games (it was either SC2000 or the one that came out for SNES at about the same time) consisted of small patches of roads, just large enough to join 3 zone types.
SimCity has always had its quirks like this, but I think this version really does take it to a new level.
If your connection strings are set in .cscfg config files, remember that they are editable through the Management Portal and you can swap them to HTTP.
Edit: Maybe not such a great idea. It looks like this relies on Storage under the hood as well. Now my instances are recycling.
Later: It appears doing so actually corrupted the instance and required a redeploy, which is of course not currently possible. Awesome.
I'm not 100%, because I do audio-only rather than video, but I think Trillian will handle that for Skype, and its a little bit more stable. I agree that Skype is one of the worst apps out there.
I am right near the 101 myself, so I hear you on the love/hate thing. I figure, at least it isn't the 710.
Even the medium sized midwestern city I am from has problems with road widening. I think it's basically a scourge wherever it goes on. There are some freeways in LA that almost seem impossible to shut down under any non-catastrophic circumstances, such as the 5 downtown (or anything downtown, probably) so it'll be interesting to see how they approach that over time.
It's also a really big deal when you shut down a freeway, even if it is for maintenance that'll improve it. Not many cities make national news with road closures like LA has done with the 405. The cost of this maintenance goes way beyond time & materials.
You could handle withdrawals out of a float fund, without actually reconciling against the user funds until an offline process completes. This way, at most, your float is at risk, and it's your money, not the customer's.
I agree with you about Nancy, and I also use ServiceStack alongside it, but I don't think the linked article has anything to do with ASP.NET specifically. The author does seem to be an ASP.NET MVC guy though.
It's usually because it's tied to some sort of OS-level new feature. In the case of IE10, it's the rendering engine for (some kinds of) Metro style apps. If you're providing infrastructure for some new features, it's easy to rely on other new infrastructure, and pretty soon you can only run on the new OS. It probably was a serious effort to back-port it like this, although it's also possible IE10 represents a new model that changes things.
I would probably do the stick approach via something like a translucent overlay. I'm not sure the carrot approach makes sense to me personally because the rewards (no neck pain, etc.) are pretty intrinsic already.
I will definitely throw it up on github if I don't end up finding something else that already does it.
On a similar note, I have also been looking for something I could use to move my cursor between my monitors. I have a sort of a half-hexagon arrangement using 3 displays and it would be nice to be able to center the cursor on whatever one I am looking at.
I think there are applications out there that sort of do this, though, so I am hoping I luck out.
I'm moving soon and will be setting up a new home office and one of the things I was thinking about is using Kinect as a sort of posture sensor at my desk, so if it detected me leaning forward, etc., it'd be able to throw a warning on the screen. Is there anything along these lines I should be looking at? I certainly don't mind writing it if I need to but I cannot be the first person with this idea.
Yeah, it's the 1366x768, same as the Air. I saw better options from a few different vendors but it always came at the price of low end components elsewhere.