In a fully managed enterprise environment, using OneNote to take handwritten notes in meetings - including creating quick To-Dos to send to Outlook, using handwriting to mark up Excel, Word, or PowerPoint files stored on a collaboration server so everyone's changes are synchronized, then go back to your desk and dock it so you have a full keyboard, mouse, external monitors (I have two), auto-switch from corporate WiFi to corporate LAN without losing mapped drives.
Or you could take a laptop, and not have to do the work twice.
I'm not sure why that post was modded down. Clearly anyone who suggests that we should all move close to where we work is a retard.
No-one wants to pay the huge transaction costs of moving every time they change jobs, and most of us have wives or girlfriends who WORK IN DIFFERENT PLACES, so there's no way we can both move close to where we work and still live in the same house.
It's the most common, and most retarded, suggestion that always comes up in discussions about transport. It's made by retards who think we still take a job at fourteen and keep working in the same place until we're eighty, and our wives stay at home to look after the kids.
Yes, you're right. In my experience, the middle-class left love pushing the working class onto buses through high car and fuel prices so they can feel superior every time they drive past a bus.
Also, if I take the bus to work, it takes an hour. If I drive, it takes fifteen minutes. So bus passengers may be on the road far longer than motorists.
I can't think of anywhere I've lived where the bus took less than twice as long as driving.
Wow, I must just be imagining running VLC on my Android tablet to play files on my NAS server. And Google must be quaking in their boots at the threat from Windows tablets and phones.
As for a few weeks of uptime supposedly being impressive, we reboot our Linux servers once a year, just because (or when we upgrade to a new OS release). I reboot my Linux desktop every few months because, by then, it's got a few kernel releases out of date. Damn it's a crappy OS.
In my experience, closed source software comes with much less bugs to begin with. With OSS, even some essential features can be glitchy or partially implemented.
While I'd agree that much open source software is just hacked together and shipped when it does everything the developers care about, most of the bugs in our software (not open source per se, but our customers get all our source so they can modify it if they want) are caused by third-party, closed-source libraries that we use because licensing them was much cheaper than writing the same code from scratch. I haven't seen a single crash in a year that wasn't due to third party, closed source code.
And, financially, it still makes sense, because developing workarounds for their bugs is still cheaper than writing the code from scratch.
Even if you could rent, what's wrong with financing a home via mortgage?
Easy availability of mortgages makes housing more expensive.
In saner countries, people build small houses on their own land and expand them as they need more space. They and their neighbours work together to build each others' houses, so they're only paying materials costs, and won't need to borrow vast amounts of money to do it.
In rent-seeking nations, the government requires you to hire anointed ones to build the houses a particular way, and the banks take much of your lifetime income in a mortgage to pay for it.
Have you never driven behind a diesel that's belching out a cloud of black smoke in your face every time it accelerates?
Of course, now they've spent years pushing Europeans to drive diesels with high fuel taxes, good luck convincing them to switch to petrol engines that cost far more to run.
I have a far more important question. What do you propose we will find in the wreckage of MH370 that will be worth the $100million we have spent looking for it?
The reason it disappeared.
Is it worth spending $100m to make the safest form of transportation even safer?
Again, this crash will probably end up costing around a billion dollars once all the compensation is paid out. Spending $100m to avoid something that would cost a billion is definitely worthwhile, if there's a significant chance of it happening again.
Let's say the Malaysian and Australian governments said 'sorry, we're stopping now', and another airliner vanished next year. What do you think they'd be saying then?
I would think a few countries must be monitoring for heat signatures all over the world, just to detect ICBM launches. Couldn't those satellites be used to figure out where MH370 went?
ICBMs produce a heck of a lot more IR than airliners. I would presume they also use software on the satellite to look for launches, rather than downlinking all the data to the ground, so there'd be no way to go back and look at the old data to try to spot MH370.
However, I believe the airlines currently operating 777s are mostly in countries which frown upon them using spare parts from ebay with dodgy serial numbers.
No, I was just trying to say that they've been searching for months. The chances of finding it are growing slimmer constantly.
No, the chances are improving, as they search more of the seabed. If it's in the search area, with some luck, they'll find it. Even if something does turn up on a beach, they'll still have to conduct a similar search, though possibly of a smaller area.
Airlines have insurance, which should be enough to carry out reasonable search and rescue (well, recovery at this point) efforts. The reasonable period has long since passed.
The insurer is probably on the hook for the best part of a billion dollars of compensation payouts if this turns out to be the airline's fault. If it was a hijacking, they're probably not. I would imagine they have a very strong incentive to keep the search going until the real cause is determined.
And people still don't know what or why the app is asking for permissions and the vast majority will click yes anyway, resulting in exactly the same condition.
Not if my girlfriend is anything to go by. Her default when some app asks for an unexpected permission on her iPad is 'no'.
Most people can tell that Happy Fluffy Kitty Screensaver doesn't really need to send SMS messages, know your location, or access the Internet.
Asking people to keep an eye on the beach is cheaper than flying planes around the ocean for days.
Also, I have a hard time believing there was a controlled ditching. The southern Indian Ocean has some of the worst weather in the world, and you're comparing a river to an area that may have had thirty foot waves at the time (I'm not sure what the weather actually was, but I very much doubt it was flat and calm). Besides which, it seems likely that the aircraft was out of fuel when it crashed, and why would you wait until the fuel was gone before making a controlled ditching? You'd have a much greater chance of success if the engines were still running.
OK, so I want to use their taxi service, but their app demands permissions it obviously doesn't need. Android gives me an option of installing it or not installing it.
Now what do you suggest I do?
Android's permission model is completely broken. It's the Windows of the modern world.
We had a program which located jets via afterburner IR signatures in the 1970s, I realize commercial jets aren't using afterburners but you'd think we'd have this problem licked by now.
So you're going to launch satellites which can find every airliner in the sky with IR over the entire world? Just in case one disappears again?
And note that underwing engines are probably going to make IR detection particularly hard as it will block a direct view of the exhaust.
Even if they managed to find the wreckage and black boxes, they will yield little or no data. The is very different from the Air France crash.
We don't know that.
Even if there's nothing in the black boxes, the positions of circuit breakers may tell us how the electronics was turned off and then turned back on. A big hole in the fuselage near the cockpit would tell us that there was a fire on board, similar to the previous 777 fire. The positions of passengers and crew would tell us whether someone hijacked the plane, and whether anyone knew about it. Personal phones and tablets may contain messages from people on board.
If we can find it from a few satellite pings, we can probably figure out what happened from whatever we recover.
We do know where our jets are. So long as they tell us.
In this case, it wasn't telling us. You can't ensure it tells us unless you build in hardware that can't be turned off, and then you find the next airliner loss is caused by an electrical fire in the thing you just added that can't be turned off.
MH370 had numerous ways to tell us where it went. But none of them were working, either because someone turned them off, or some electrical failure shut them down.
Or, you know, actually give us actual app permissions control so we can prevent it from retrieving this information in the first place, rather than having to agree that Happy Fluffy Kitty Screensaver can send text messages and read all my contacts or not install it at all?
How can you hope to write a drift model that with any accuracy when you have no clue where the plane crashed?
We do have 'clues where the plane crashed': that's why they're now searching a relatively small area of ocean, which is the most likely place for it to have crashed.
Doesn't mean that is where it crashed, but if they follow the currents from that area and find debris on a beach, it would certainly help to confirm they're looking in the right place.
In a fully managed enterprise environment, using OneNote to take handwritten notes in meetings - including creating quick To-Dos to send to Outlook, using handwriting to mark up Excel, Word, or PowerPoint files stored on a collaboration server so everyone's changes are synchronized, then go back to your desk and dock it so you have a full keyboard, mouse, external monitors (I have two), auto-switch from corporate WiFi to corporate LAN without losing mapped drives.
Or you could take a laptop, and not have to do the work twice.
I'm not sure why that post was modded down. Clearly anyone who suggests that we should all move close to where we work is a retard.
No-one wants to pay the huge transaction costs of moving every time they change jobs, and most of us have wives or girlfriends who WORK IN DIFFERENT PLACES, so there's no way we can both move close to where we work and still live in the same house.
It's the most common, and most retarded, suggestion that always comes up in discussions about transport. It's made by retards who think we still take a job at fourteen and keep working in the same place until we're eighty, and our wives stay at home to look after the kids.
Yes, you're right. In my experience, the middle-class left love pushing the working class onto buses through high car and fuel prices so they can feel superior every time they drive past a bus.
Also, if I take the bus to work, it takes an hour. If I drive, it takes fifteen minutes. So bus passengers may be on the road far longer than motorists.
I can't think of anywhere I've lived where the bus took less than twice as long as driving.
Wow, I must just be imagining running VLC on my Android tablet to play files on my NAS server. And Google must be quaking in their boots at the threat from Windows tablets and phones.
As for a few weeks of uptime supposedly being impressive, we reboot our Linux servers once a year, just because (or when we upgrade to a new OS release). I reboot my Linux desktop every few months because, by then, it's got a few kernel releases out of date. Damn it's a crappy OS.
In my experience, closed source software comes with much less bugs to begin with. With OSS, even some essential features can be glitchy or partially implemented.
While I'd agree that much open source software is just hacked together and shipped when it does everything the developers care about, most of the bugs in our software (not open source per se, but our customers get all our source so they can modify it if they want) are caused by third-party, closed-source libraries that we use because licensing them was much cheaper than writing the same code from scratch. I haven't seen a single crash in a year that wasn't due to third party, closed source code.
And, financially, it still makes sense, because developing workarounds for their bugs is still cheaper than writing the code from scratch.
Even if you could rent, what's wrong with financing a home via mortgage?
Easy availability of mortgages makes housing more expensive.
In saner countries, people build small houses on their own land and expand them as they need more space. They and their neighbours work together to build each others' houses, so they're only paying materials costs, and won't need to borrow vast amounts of money to do it.
In rent-seeking nations, the government requires you to hire anointed ones to build the houses a particular way, and the banks take much of your lifetime income in a mortgage to pay for it.
Have you never driven behind a diesel that's belching out a cloud of black smoke in your face every time it accelerates?
Of course, now they've spent years pushing Europeans to drive diesels with high fuel taxes, good luck convincing them to switch to petrol engines that cost far more to run.
I don't give a rats ass about piddly crap like light saber hilts, I just want a movie that has actual dialogue, plot and acting.
In a JJ Abrams movie?
This will have explosions, lens flare, and time travel. And the ending will suck.
I have a far more important question. What do you propose we will find in the wreckage of MH370 that will be worth the $100million we have spent looking for it?
The reason it disappeared.
Is it worth spending $100m to make the safest form of transportation even safer?
Again, this crash will probably end up costing around a billion dollars once all the compensation is paid out. Spending $100m to avoid something that would cost a billion is definitely worthwhile, if there's a significant chance of it happening again.
Let's say the Malaysian and Australian governments said 'sorry, we're stopping now', and another airliner vanished next year. What do you think they'd be saying then?
I would think a few countries must be monitoring for heat signatures all over the world, just to detect ICBM launches. Couldn't those satellites be used to figure out where MH370 went?
ICBMs produce a heck of a lot more IR than airliners. I would presume they also use software on the satellite to look for launches, rather than downlinking all the data to the ground, so there'd be no way to go back and look at the old data to try to spot MH370.
However, I believe the airlines currently operating 777s are mostly in countries which frown upon them using spare parts from ebay with dodgy serial numbers.
Which part do you disagree with?
No, I was just trying to say that they've been searching for months. The chances of finding it are growing slimmer constantly.
No, the chances are improving, as they search more of the seabed. If it's in the search area, with some luck, they'll find it. Even if something does turn up on a beach, they'll still have to conduct a similar search, though possibly of a smaller area.
Airlines have insurance, which should be enough to carry out reasonable search and rescue (well, recovery at this point) efforts. The reasonable period has long since passed.
The insurer is probably on the hook for the best part of a billion dollars of compensation payouts if this turns out to be the airline's fault. If it was a hijacking, they're probably not. I would imagine they have a very strong incentive to keep the search going until the real cause is determined.
And people still don't know what or why the app is asking for permissions and the vast majority will click yes anyway, resulting in exactly the same condition.
Not if my girlfriend is anything to go by. Her default when some app asks for an unexpected permission on her iPad is 'no'.
Most people can tell that Happy Fluffy Kitty Screensaver doesn't really need to send SMS messages, know your location, or access the Internet.
Too late. Facebook has all your data already. So can just as well continue using it.
It has some of my data, but I stopped updating it when it started demanding permissions I wasn't willing to give it. It doesn't have any future data.
We should check ebay, and see if any used 777s show up cheap.
If you think that's bad, don't look at what Facebook Messenger wants access to.
I did. That's why I uninstalled the Facebook app some time back.
Asking people to keep an eye on the beach is cheaper than flying planes around the ocean for days.
Also, I have a hard time believing there was a controlled ditching. The southern Indian Ocean has some of the worst weather in the world, and you're comparing a river to an area that may have had thirty foot waves at the time (I'm not sure what the weather actually was, but I very much doubt it was flat and calm). Besides which, it seems likely that the aircraft was out of fuel when it crashed, and why would you wait until the fuel was gone before making a controlled ditching? You'd have a much greater chance of success if the engines were still running.
OK, so I want to use their taxi service, but their app demands permissions it obviously doesn't need. Android gives me an option of installing it or not installing it.
Now what do you suggest I do?
Android's permission model is completely broken. It's the Windows of the modern world.
We had a program which located jets via afterburner IR signatures in the 1970s, I realize commercial jets aren't using afterburners but you'd think we'd have this problem licked by now.
So you're going to launch satellites which can find every airliner in the sky with IR over the entire world? Just in case one disappears again?
And note that underwing engines are probably going to make IR detection particularly hard as it will block a direct view of the exhaust.
Even if they managed to find the wreckage and black boxes, they will yield little or no data. The is very different from the Air France crash.
We don't know that.
Even if there's nothing in the black boxes, the positions of circuit breakers may tell us how the electronics was turned off and then turned back on. A big hole in the fuselage near the cockpit would tell us that there was a fire on board, similar to the previous 777 fire. The positions of passengers and crew would tell us whether someone hijacked the plane, and whether anyone knew about it. Personal phones and tablets may contain messages from people on board.
If we can find it from a few satellite pings, we can probably figure out what happened from whatever we recover.
We do know where our jets are. So long as they tell us.
In this case, it wasn't telling us. You can't ensure it tells us unless you build in hardware that can't be turned off, and then you find the next airliner loss is caused by an electrical fire in the thing you just added that can't be turned off.
MH370 had numerous ways to tell us where it went. But none of them were working, either because someone turned them off, or some electrical failure shut them down.
Or, you know, actually give us actual app permissions control so we can prevent it from retrieving this information in the first place, rather than having to agree that Happy Fluffy Kitty Screensaver can send text messages and read all my contacts or not install it at all?
How can you hope to write a drift model that with any accuracy when you have no clue where the plane crashed?
We do have 'clues where the plane crashed': that's why they're now searching a relatively small area of ocean, which is the most likely place for it to have crashed.
Doesn't mean that is where it crashed, but if they follow the currents from that area and find debris on a beach, it would certainly help to confirm they're looking in the right place.