Re: The video
If it's take-off noise, what about a hybrid? Enough battery capacity to get you in the air then fire-up a normal engine to power the rest of the flight and recharge the batteries.
2299 posts • joined 30 Jan 2010
There are several things that surprise me about this kneeling on the neck technique.
First, it's an official method of restraint. WTF? Who the heck thought that restricting the neck was a good restraint technique?
Second, this isn't the first death of a suspect from being restrained by this technique. Here's a suggestion for you: If people are dying from your restraint technique then clearly somethings wrong!
iWork is utter crap compared to LibreOffice.
I've used both iWork and LibreOffice. Sure, iWork doesn't necesarily have the same depth of features as LibreOffice, but I think the UI is better for the simple use cases. And if you're storing your documets in iCloud, then the seemless transition between MacOS and iOS for editing your documents (and the iOS apps are quite good) is very useful.
Do I use iWork as my primary office suite? No. My go-to office suite is LibreOffice - but I'll fire up iWork some tasks.
Ah Z80 assembler. I remember doing that on Spectrums & Amstrad CPCs. Once I went to Uni and discovered Intel CPUs I was shocked by the x86 memory segmentation and wondered how anyone could work with such an environment.
I have a dream of getting back into assembly programming - but with a CPU with a sane instruction set.
We had a HA system which worked fine. Then one day, the primary failed and everything jumped over to the secondary. Which promptly failed and everything failed back to the primary (which was just about getting back on its feet) Which failed, etc. , etc..
It turned out one client got into a very weird state and sent command packets to the servers which the servers couldn't handle. Once we managed to get some logs and isolate the client the system became a lot more stable.
We're not the size of Cloudflare, but we use software which tracks every server, switch, patch panel, PDU, cable (data & mains), duct, etc. in our machines rooms. Any scheduled work has to be pre-booked through the software (Which gives you a report on what you're going to do) Any emergency work has to be updated into the software ASAP.
Failure to comply with using the software is quite simple: Everyone gets to take the piss out of you for causing someone else pain. (Yes, I've been on the receiving end) No management intervention required as peer-pressure is a far more effective stick in this situation.
The initial inputing of the data was a tedious piece of work and getting buy-in took some time, but now everyone sees its value. Now, when someone says "What happens if I cut this cable?" you click a button and it immediately tells you what will be affected.
Since we rolled out Teams across our organisation we've inundated with requests for Zoom so people can see everyone in a meeting.
We spoke to our Microsoft account team and it was hinted that Microsoft just don't have the compute power to handle more video streams on screen at once at the minute.
a typical dual CPU with a decent amount of memory will support 100,000 users
Doing what? Chat? Yeah, that's probably do-able.
What about some of the other toys MS-Teams has: File sharing/syncing, voice calls, video calls, conferencing, etc.
You're not going to get 100,000 video (Or voice) users on that dual CPU box.
I'm not usually one to stick up for MS (I've sworn at them many times over the years) But the commentards here who are saying "Why don't Microsoft just expand capacity - it's just cloud". Why not consider these minor details called "facts":
Firstly, the number of users of Teams has dobuled in less than three months, from 20 million to 44 million users.
Secondly, the amount of use people are making of Teams is going to be much, much higher. I don't have a figure for this, but let's guess and say it's doubled.
So the number of users have doubled and the usage has, in effect, quadrupled. Running a service at this scale isn't going to be just a couple of virtual machines. So quadrupling the capacity in such a short space of time isn't going to be a trivial exercise. You're also going to be needing more hardware and more bandwidth - the cloud has to run "somewhere".
Yes, we will give all of you free access. What we will not tell you is the actual cost
Nor will we give you the tools to extract your data.
Files are easy: Just copy them out (Subject to rate limiting...)
Onenote: "Export as PDF" is MS's answer.
Chats & Posts? Nope. Kiss goodbye to them.
Not just Teams, Onenote & Outlook eat battery on Macs too. I found these apps have the ability to eat the battery of my MBook Pro is under an hour when they're misbehaving. My suspicion is that they don't like it when you move between network connections (e.g Wired & Wirelss)
Biting the hand that feeds IT © 1998–2020