Those costs are never taken into account. It's always the "low" price of licensing/use/dev that is looked at, and then... you have the regret phase. Which never end because "we already invested so much", and the famous "in the long run it will be cheap... oh wait, we have a newer offer"
How long ago was that a thing? I got in in the 2000s and there was only a single email system for the entire Army. 10 years ago they moved the whole DoD to DEE.
As an employee of a company where about 1/3 of our workforce have migrated to Google Workspace and the rest have not, I have a (pretty long) list of things that are a pain. Anything to do with sharing is awkward. Google Chat vs Teams is a headache. Lack of calendar integration is annoying.
Obviously YMMV, but I don't think it's as simple as you're making it out to be.
How do your Office users share files? At a previous employer they refused to migrate away from an ancient companywide network share, combined with people emailing each other QuarterlyReportQ42021_final_Fixed (7).docx. There was absolutely no interest from IT (which the company had recently outsourced) to actually facilitate migrating to a sane sharing model a la Office 365.
OneDrive. Enterprise deployments have something similar to consumer-grade OneDrive, but more enterprisey with compliance controls built in. And of course all the regular Office apps work well with it — it’s not just browser based.
It’s honestly pretty good. All the usual features are there — importantly, version history (no more Contract v15 FINAL.docx).
The key thing is it works with Teams and SharePoint and has collaborative editing, works in browser, desktop app, or phone.
They had an on-premises version of OneDrive too, not sure if that’s still a thing.
It’s not all a bed of roses. Gmail still feels nicer than Outlook web, but Outlook web is catching up. Collaborative editing feels much more robust in Google Docs. But the OneDrive client is way nicer than Google Drive (for me, at least).
I’d definitely say Google’s and Microsoft’s “online business collaboration” offerings are comparable. I suspect users will have preferences based on what they’re used to.
Of course, if your org uses both you’re in for a world of hurt. Email works well enough, but even calendaring has friction. Filesharing / chatrooms? Doesn’t interoperate well at all.
Which neither side supports fully. So now you're paying a software dev to integrate the two. And of course, they're not going to get recurring events implemented correctly, especially when some events are exceptions due to holidays or other scheduling conflicts.
Or protecting people from being killed. Taiwan, Philippines, Vietnam, and many others, mainly in Asia and Africa rely on the U.S. for their security. Not to mention the protection of international trade routes that feed billions of people.
Ukraine is certainly thankful for the weapons they've been getting from the West, primarily the US. I don't think their offensive would be even half as successful without the precision strikes enabled by HIMAR and the US's stockpiled ammo.
Yes definitely. However, in the case of the Ukraine invasion, I see a lot of the fault in the West too. Very much reminds me of the first US-Iraq War in the early 1990s.
So everyone is going to have to switch from Workspace to O365 email when they get promoted from E-3 to E-4? Migrate all the saved messages and presumably switch addresses? Isn't that a low level enough that it will apply to basically all enlisted?
No, they will just claim for months that they will automatically migrate your e-mail and then instead of doing that, they'll cut you off from your old account one day and you'll lose all 10 years of mail in it.
Halon being tagged out wouldn't have influenced the outcome here. Lower V is not Halon protected. MMR1 below it is, but not V. The next closest Halon compartment would have been FWD EDG, which would have been beyond too late once the fire reached it. The AFFF system would have made short work of the fire, had it not been tagged out / in IEM -- definitely affected the fire attack.
I did two years on Iwo, and BZ to the Bonny crew. They did all they could have with those fire trees with plastic nozzles until help arrived.
BTW were you aboard the Iwo in 2005? I was a Marine deployed w/ SPMAGTF Katrina down there and we got “evacuated” on the Iwo Jima when another hurricane was bearing down on the area. It was a Marine battalion along with a lot of civilians. Don’t remember how long I was aboard but a few days certainly, before disembarking in norfolk or somewhere thereabouts.
This happened to me too. I rented a Hertz vehicle while on a trip to San Diego in 2005. I had to exchange the car at their airport location due to a flat tire. Two days later while driving from Coronado to Imperial Beach, I was stopped. About four additional officers showed up and had me exit the vehicle at gun point and lay flat on the road, and that's when I was informed the car had been reported stolen. Thankfully I wasn't arrested either, but spent about an hour with the Coronado police on the side of the road getting this mess resolved. I avoid renting whenever possible to this day.
> As for if they will get paid afterward, well legally the government cannot promise that. Legally it's possible that the new budget may even disband something like the TSA and all of the workers who have been working for free would be even more screwed. But historically every shutdown ended with giving back pay to the workers who had to work for free. They just can't guarantee it.
Yes and no. Excepted service employees, which includes most of the TSA, are guaranteed to receive back pay for time worked during the shutdown, as agencies are required to pay for services performed. However, Congress and the President must pass and a sign a bill explicitly paying workers who were furloughed (i.e., non-essential and non-excepted employees).
As the shutdown continues, excepted and essential workers may be entitled to double pay due to the Fair Labor Standards Act.
AWS' Customer Agreement[1] essentially has the same language. I wouldn't be surprised to see similar language from other cloud providers as well. Seems rather prudent on their part.
I would suggest the inference I was alluding to would also apply amazon.
Note how I never stated the inference. This is because I wanted to share a way of thinking without feeling the responsibility to reply to people attempting to force me to prove some prescriptive, arbitrary inference rule by exhaustion. I do not participate in such practices casually. I also consider it rude to subject people to such practices without consent. I also believe it is a practice that kills online discussion platforms. See this community’s thought provoking guidelines :)
> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.
While carriers are certainly used in this role, I've taken part in two such missions while deployed with the USS Ronald Reagan, there are ships that are more capable in handling humanitarian and disaster relief, and non-combatant evacuation efforts, such as LHDs -- which also have a larger complement of helicopters/V-22s and ground-troop support than a carrier.
Except in this case, I'd argue it's fairly obvious. One tends to make a conscious decision to change their DNS server from that provided by their ISP to a public DNS service such as Google's.
The First Amendment. The Free Exercise Clause requires Congress to make religion available to all servicemembers regardless of where they are stationed if one of their denomination is not available. Courts have found that not providing that opportunity for religious guidance would be prohibiting the servicemember's free exercise of religion.
Chaplains typically spend more of their time counseling and mentoring than on religious services.
