Yeah I love my UBNT gear (6 APs, 5 switches, 2 routers, and a cloud key), but their hardware tolerances and lack of real support are painful.
EVERY device I've had from them "squeals". The APs are the worse as it increases based on what is being pumped through it and can be bad enough where I can hear it from 20' away with the TV on and between me and the AP.
My support from them started off great where they sent me a total of 4 replacement APs and a 8 port ToughSwitch (I had bought a 5 port, which also squeals). After the second round of APs they just stopped responding. The upside is that included never sending me return info for the last pair of APs and the 8 port TS so I went from 2 APs and a 5 port switch for ~$300 to 4 APs and 2 switches (5 port and 8 port) for ~$300, so it wasn't all bad;-)
I still buy their gear because the price can't be beat for the functionality. I just know that it has to be placed in a location where no one regularly goes.
The general lesson may be the same as that behind the Concorde.
Unlike others, I agree
There's not a massive market for people willing to pay a massive amount of money for travel by planes. That applies whether the increased cost is for incredible luxury or incredible speed.
But I think you went to the wrong conclusion
The biggest issue with the 380 is that not all major airports can accommodate it. Even those that could handle the 747. Remodeling an airport is not a simple affair. Especially those where communities have grown up around them and effectively limited their expansion space.
The Concorde had a similar issue where there were only a few airports could accommodate it's runway requirements and even before it started running into regulation problems there wasn't a swell of airports looking to sink the money into supporting it.
A related issue with the 380 is that many airports are already at or near capacity as it is, so the idea of more people in the same number of flights is another infrastructure problem they have to solve at the same time they are dealing with runway/traffic/gate changes. That doesn't give them much incentive to invest in letting those monsters land.
What's worse, is that the menu items were right under each other. "Missile alert" and "Missile alert Test". Both items give the same "are you sure" confirmation.
While it was certainly a bone headed mistake, it was one what was easily possible for someone in a hurry. As this fellow was just wrapping up his shift, he was clearly trying to get everything done in time.
I don't get the people calling for this guy to get fired. Like none of those assplugs have ever made a mistake on their job. How many know someone in the office that accidentally did reply to all, or forward some email chain to external Eric rather than the internal Eric.
Shit happens. Clearly the design of that system isn't the best.
I agree. Shit happens. Just was unfortunately some really bad shit in this case. I haven't made such public mistakes, but I've made some big ones. He is just a scape goat here.
The real problems I see here is that A) it wasn't blatantly obvious (through using a different workflow and by clear visual (and audio?) indicators) that he was going down the live path rather than Test and B) that having permission to use the EBS doesn't automatically carry the ability to send a "oh shit! we didn't mean to do that" message as well.
At the point where the workflow path deviates between Test and Real it should be impossible for someone, no matter how rushed/tired/bored, to get it wrong. Glaringly different color schemes. Audio prompts. Full screen dialogs so they can't be paying attention to something else. Extra steps down the Live path. Having a second account confirm the action. Etc...
Make it so that you have to be either blatantly ignorant or blatantly malicious to get to the point of sending a Live alert when you shouldn't. The timeliness nature of the system, however, does present some challenges since you want to delay getting the alert out as little as possible.
Now what I think is really being missed here is that this was a blessing in disguise. Yes it inconvenienced and scared the crap out of a lot of people, but based on all the reports I've seen no one had a clue what to do with it. Given the short time involved for a missile to get from NK to Hawaii and the devastation a nuclear warhead would do I question the point of giving warning (I'd rather die blissfully ignorant rather than in a panic or linger through injury/radiation poisoning), but if there is going to be a warning people need to know what to do and react accordingly.
They are concerned enough to spend money on the warning system, but have they spent the money on enough bunkers to hold the population of the islands? Are they located so that everyone has a reasonable chance of getting to one regardless of traffic/panic of everyone else trying to get there?
Yes personal space. Even though in most cases everything in a marriage is shared equally there is still the concept of personal space and "mine vs theirs". While not legally binding, they are still critical to being able to live in the same house together.
I don't know where you keep yours, but close friends can at any time take a 50 out of my wallet as long as they tell me
and put it give in due time.
And that is the key part left out of items 2-5 in the original list.
I completely agree with you that in a good relationship, grabbing some cash from your partner is a non-issue. The expectation, however, is that it's a good relationship so that the one doing the grabbing is going to hold up their part of the social contract and let the other know. In that context, there is neither anything wrong with or illegal about taking the money.
The offended party's opinion makes no difference (as it should not). Theft has a legal definition and just because I feel something is theft does not make it so. Except for the first example the rest all have some explicit or implicit legal access to the money in question. That doesn't make it right to take the money without asking, but it makes it legally NOT theft.
Our legal system is already a big enough mess as it is. Allowing people to define laws based on how they feel at any given time is NOT the direction we want to go.
That last one is the one that most likely will result in a legal battle.
Just what sort of legal battle do you think it would result in? That in itself is not remotely enough to justify a divorce. The police/prosecutor will laugh at you. You could probably find a low life lawyer to help you file a civil suit, but really?
In what kind of relationship that is still at least kinda-sorta working do you feel obliged to write your SO a check for money owed?
In what type of relationship do you feel it's Ok to casually invade someone else's personal space without so much as a "hey, I need to grab $50"? While most of the original list is technically legal, I'd say there are some serious relationship issues going on...
I'm not sure you understand what you just did. You claimed that the money is a shared asset but it was wrong to take the shared asset to buy food. You need to rethink that. If the money is a shared asset then it both of theirs regardless of where it resides. As a shared asset, he has a right to take and spend it regardless of whether it is in the bank, his wallet, or her purse, just like she does.
No, they are correct. Just because it's a shared asset and you have the right to use it does not mean it is the correct thing to do. You CAN take the money and you will NOT be charged with theft (assuming you are not legally separated), but it's still a pretty shitty thing to do.
Now in contrast, unless there is a problematic pattern, the wife getting too bent out of shape over a one time event also falls into the right but wrong category too.
As they said, "right" and "legal" are two totally different things. Plenty of things are right, but illegal. Plenty of things are legal, but not right. Most of the original list comes down to "just because he can, doesn't mean he should".
I developed a set of BASH scripts to automate building a GNU/Linux distribution from scratch based on Linux From Scratch releases. After creating the package build definition files you can launch the build process by running a single master script. https://github.com/gdhorne/abs...
I know a guy that wrote a Puppet/Chef alternative in KSH. Complex stuff certainly can be done, but it is almost always more convoluted than using a better language for such tasks.
OLED still has a very serious burn-in problem and that just does not seem to go away in the mid term - so no, OLED will not replace LCD in the monitors any time soon.
I've got the 2nd to the last pre-4k 55" LG (3 years old?) and I haven't seen any sign of burn in. It replaced a Pioneer Elite Plasma 50", so I know all about burn in (fuck you NBC logo!).
I read about the burn concern before buying it, but I simply couldn't stomach the piss poor LCD quality after living with true blacks on the Plasma for so long (the refresh is also far smoother on the OLED so I've never noticed that irritating "soap opera" effect either). I generally try to avoid burn in after owning a Plasma, but since every channel likes to have their logo on the screen 24/7 it's hard to avoid the "static" image issue. To my relief, however, I see no signs of burn in at all.
I also have zero dead pixels that they are complaining about above.
My only one complaint is how fragile the damn thing is. The Plasma took some good whacks in it's time and wasn't moved about all that carefully, but it too a small high velocity projectile to take it out. The first OLED had to be replaced a month in after a rather light object deflected wrong and hit the screen. At worst I would have expected a scratch, but it damaged the glass and the panel wouldn't turn on anymore (the Plasma would turn on, but it was useless). Now we treat it with kid gloves which is rather annoying with a 5yr old running around...
You can potentially code solutions in fewer lines of Python compared to bash too
For complex things, certainly and at that point you should be using something more practical than BASH anyway.
If, however, I want to simply execute a shell command (that does not have a Python/Perl/whatever builtin analog), capture it's output to a variable, and check the exit status, BASH is pretty damn simple. Those last two requirements are the biggest killer of Python as that forces you to use subprocess which makes it much more complex than BASH (especially if you want to capture stdout and stderr).
It's not that things like that are hard or not well documented, but they are more complex to write and don't read as simply. Not only does simplicity serve when writing the code, it also serves when it has to be debugged at 4am due to a Production issue.
I've done my time as an Admin and much prefer writing real code (of which I happen to specialize in automation), but I recognize that the language I may choose to solve a problem might not really be the best option when all facets of it's deployment and support are taken into account.
Now what most admins leave out of their code which would do wonders regardless of the language is error checking. I've lost track of the number of messes I've had to cleanup that simply came down to scripts that blindly carry on assuming the world is perfect without bother to check... "if [ $? -ne 0 ] ; then" really isn't THAT complicated...
"Incitement" is bullshit. Rioting is a choice. Losing your head to the mob is no excuse. Large groups of people are just as dangerous as any other animal, you should expect the worst when they become agitated, but people do it by choice, either way, the best move is to keep a safe distance.
While I agree that those in the mob are responsible for their own actions (including a panicking horde when someone "yells fire"), there is also responsibility on the one doing the shouting for recognizing the situation and the result of their "free expression".
Is the piece of shit that called in the SWAT team not culpable in the death of that innocent man? Certainly the police have responsibility for how they responded to the call and the actions they took, but ultimately they would not have been there had he not called. Additionally he clearly knew that the police would show up in force due to such a call and would have to be monumentally stupid (debatable given that he thinks swatting is "funny") to not grasp the potential outcome of such actions.
So yes, the people responding to the "free expression" have responsibility and should be held accountable, but the same goes for the expresser.
Here's a new year's resolution for you: Strap yourself to a rocket and launch it to demonstrate that the Earth is flat.
The GP isn't wrong though. As part of pushing "DevOps" my company is pushing the Admins to become "real" programmers and as such is trying to shove Python down their throats.
While I'm a firm believer in fresh/relevant skills keeps the agism boogyman away, there is also a lot of risk in such a move. What I've seen:
They can't produce the scripts as fast which leads to delays.
The scripts are more error prone due to the lack of experience.
Simple BASH scripts can typically take twice the Python code (again, delays)
BASH and KSH are "loved" because they are everywhere and predictable . While Python is everywhere, it's a damn box of chocolates! What version is installed? Which modules have been installed? Multiple versions of Python that conflict with one another is always fun. etc..
One Admin that thinks it's great to write all their scripts in Python/Ruby/whatever when the rest of their team has no experience in that language provides "fun" in emergency situations and prevents proper code reviews.
I'm sure there are more if I put my mind to it too.
Yes you should always learn new skills and keep up with technology, but you should never do just to do.
A good [insert role here] knows that while they need to keep their tool box up to date they also need to use the right tool for the right job. Any one-size-fits-all approach is always doomed to problems that should never be.
After watching the body cam, it's a bit pathetic. Maybe there should be better quality cameras on the dash. I think I've had better quality from 10year old cameras, if the intention is to show that the criminals are misbehaving, this quality really lets the police down.
Those cameras are designed for closer interactions than what happened here. Maybe 20' tops? Additionally this was video at night and not in an IR mode. Given the poor lighting conditions and distance, that's actually pretty good quality in my opinion.
Bullshit. Unless that officer was using a pair of binoculars. Stupid, panicky pigs.
Can't quite tell for sure, but it does appear that the rifle had a small scope on it. If so, even a small one would have been good enough to provide a better view than we see in the video.
What I'm most shocked about is that it wasn't the typical hail of fire where only one or two actually found the target. This was a shot by an officer that actually knew how to use their weapon!
It's absolutely disgusting that this guy lost his life over some prick half the country away being pissed off over a $1 or $2 dollar bet. The limited context of the video would seem to corroborate with the Police's version of events though (that he wasn't following commands). I've been an adult longer for awhile now than I was a child and it's always been basic knowledge that when dealing with cops in a non-friendly situation there are two basics to walking away. First and foremost, you ALWAYS move slow. Especially when raising your hands. Sudden moves will get you shot 9 times out of 10. The second rule is to follow the orders even if you believe they are in the wrong. Being alive and sorting it out later is far better than being dead and right.
Of course knowing these things in the comfort of my office behind my computer is drastically different that opening my front door at night to find my house surrounded by cops pointing the guns at me. It's very believable to me (without seeing more video context) that the guy opened the door, freaked out, and wanted to get his hands up as quickly as he could so as to show compliance and being unarmed.
There are really not enough bad things I can hope happen to the asshole that made the phone call.
Android is a BIG step backwards in operating systems.
Based on the rest of your post, the problem is more that you are trying to use the wrong tool for the job than a specific fault of the OS. You think trying to use iOS as a desktop OS would net you better results? They were specifically designed to be run on limited hardware (compared to laptops and desktops) and relatively small screens.
It isn't self hosting unless you chroot it, and then, you can't get a native windowed program running on it, unless you use VNC to open a session to the chroot.
While the idea of running Android on a real computer is cool and even somewhat useful, you're asking it to do something it wasn't designed for. This isn't some failing of the OS.
It's 2017 and Android STILL cannot do multitasking properly: My android phone has 1GiB of RAM. Why the fsck can it not put multiple windows on the screen (not just 2, but like, 10) and let me work on more than one thing at once?
Maybe because there isn't enough screen space on a phone/tablet to have 10 different applications visible in a meaningful manner?
Every app runs in fullscreen, and actually stops running (or changes to a 'background state') when you switch to another one.
You would be crying like a baby if it did what you wanted and then your phone was A) hot as hell and B) the battery was dead in 10 minutes from all the stuff you switched out of, but forgot to kill eating up the CPU and killing the battery.
Windows 95 let me put as many windows on the screen as I want
Have you considered the extremely odd possibility that this is because it was... wait for it... DESIGNED AS A DESKTOP OS???
Android can't mount NFS shares and the state of memory-card management is a mess. You can't even symlink directories without rooting it and mucking around. Why isn't that in the native UI?
Again. Phone/Tablet OS. Not desktop. Different worlds.
Every. Bloody. Thing. Is. In. Java. Why can't I write a program in scheme, and run it on Android?
Yeah I've never gotten that myself. As long as there is a tool chain to do the correct byte compiling, it shouldn't matter. Different language, but the same applies to iOS too.
Android doesn't support IPv6 properly. I'm pretty sure Windows 98 did. Maybe Windows 95 did, as well.
I don't know about Andriod's compatibility, but I know you certainly have no clue what you are talking about. Given that Win95 was released a few months before the first IPv6 RFC (1883), no it most certainly did not support IPv6. Similarly as Win98 was released a few months before 1883 was superseded by 2460 which is when it started to actually mean something to the world, it did not support it either.
Regardless, this will be the Year of IPv6! right after it's the Year of the Linux Desktop!...
Oh, and here's the biggest step back of all: 99% of all android phones don't even give root access. It's an OS that you can't become root on. How is that a step forward in any conceivable sense of the word?
100% of iOS devices don't allow you to become root. What's your point?
Oh. Wait. You're trying to use it in a manner that it wasn't really designed for.
Stop being an idiot and using things in a manner that they were not meant to be and then complaining when they don't work as well as tools actually designed for what you are trying to do.
OS development has totally stagnated. There hasn't been much forward progress since the mid 1990s, and there has actually been a lot of backward regression.
While it might seem that way, I think there are 2 major points you are missing and you are under valuing the differences between then and now.
The first is that until the late 90s consumer OSes were significantly limited by the hardware they ran on. There were very real limits to memory, disk space, and bandwidth. The "great jumps" during that time happened around significant hardware changes. The last was the time of the Pentium which unlocked the path to the resources we now have available. While we still have physical limitations, they are so high that the OS vendors are not constrained like they once where. This allows for incremental changes which are less WOW inducing than the earlier era where 2MB of RAM was something to be excited about.
Secondly, just what is really missing from an OS these days that should be at the basic OS level? The only thing I can really think of that would be really nice is to kernel updates that don't require a reboot. Beyond that peripherals haven't significantly changed in 20+ years (e.g. USB is still serial based and everything else continues to fall by the wayside). So beyond tweaks for stability and performance, what's left?
I also think you under value what has changed under the covers. I was playing with Linux back in 94 and there is no question it is a much better OS now than it was then. Hardware compatibility isn't remotely the concern that it once was. Similarly the differences in Win 95 to Win 10 or NextSTEP to the current OS X are equally significant and important. It's just that much of the change is behind the scenes and not as noticeable (usually deliberately so).
It's also worth noting that the UI is not part of the OS itself, but just an extension running on top of it. It's a distinction many don't seem to understand, but it is an important one. Similarly, however, beyond tweaks to meet the aesthetics of the day, what significant changes are needed to the UIs these days?
We as a culture cannot afford the one size healthcare for all problems.
You'll get no argument there from me just as you'll get no argument that ERs get overcrowded with those that have no business there. Your original assertion, however, was that someone's ability to drive to the ER and their decision to call an Ambulance was the deciding factor of if they are a valid ER patient. That is demonstrably not true.
One of the factors that this study doesn't seem to take into account is Obamacare. That, I think, has had far more impact in overuse of the ER than Uber. Many ERs were used in place of doctors by people that had no insurance and/or couldn't pay since most public hospitals reduced costs or simply didn't bother to chase down those who couldn't pay. In my area within a few months of OC getting in gear ER wait times dropped significantly while getting an appoint with GPs became harder (e.g. outside Urgent Care level stuff, same day appointments are just about gone). OC has a lot of problems, but it's impact to ER usage definitely seems to be a big pro for it.
I've only used Uber twice for work, though I've tried to use it more. Getting an Uber home from a major international airport takes about 5 minutes (so longer than walking right up to a cab) and costs within a few dollars of what a taxi costs for the same trip. I use Uber because my company has some connection to them so the rides feed our expense system. The local cabs don't take our corp Amex (also directly feeding our expense system), so that it's less hassle for me doing my expenses is the only reason I have opted for them so far.
Trying to get from home to the airport, on the other hand, can vary from 30 minutes to an 1.5 hours while the same cab company that can bring me home from the airport is 45 minutes and SuperShuttle (much cheaper than either) gives me a time I can count on for planning. It's not like I'm out in the sticks either. I'm in the middle of a bunch of heavily populated suburb developments and happen to be 2.5 miles (as the crow flies) from the end of said airport's runways. This area (and the county that I and the airport fall in) are one of the country's biggest Tech sectors (outside of SV) too which was an early adopter of Uber.
The point being that while taxis have problems, they are far more predictable outside of the major city areas. Uber is far from the panacea the "True Believer" want us to believe.
Not sure why you are trying to bring Communism into this since nothing about the subject or my comments has anything to do with Communism (or any particular form of government).
The problem with people going to the ED, is the fact that they are not going for a real emergency, but an urgent visit or just see a doctor without a schedule.
Obviously you are a learned doctor that knows all the the possible health conditions and how they should be managed and treated. Please enlighten us more...
There are plenty of issues that are not life threatening which can not be treated by urgent care. There are also plenty of conditions that complicate less severe issues which make having access to a full hospital's resources the better choice. There are also plenty of areas where urgent care facilities don't exist (or are run by a specific group that do not accept non-members).
There are plenty of people that waste the ER's time for things like non-critical flu/cold symptoms and the like, but to argue the patient being able to drive themselves or not is ludicrously naive.
Presented with a transportation option previously depressed by the city overlords
So these cities refused to allow taxis to operate prior to Uber? I doubt it. Even though they may be more expensive than Uber, they would still be far cheaper than an ambulance ride.
So is Uber truly the savior of humanity this study wants us to believe, or are there maybe other factors that they missed/ignored in their effort to show Uber in a good light?
Among other things, because they aren't really given the opportunity. Generally it's something like:
"Journalist": [bangs out story]
"Journalist": [calls related parties for comment]
"Journalist": [leaves message for those that don't answer directly]
"Journalist": [goes ahead and releases article without allowing messages to be returned]
Even for those where they get a real person, in something the size of Starbucks the answer will invariably be "we'll look into it and get back to you" or "let us find out who you need to talk to". There is still no delay in the publishing though.
That certainly isn't always true, but it's also not always "[insert big company] is evil and hiding things" either.
Warrant to search phone company records for triangulation data not so cut n' dry.
They are required to get a warrant to do something like attaching a GPS tracker to your car. I fail to see the difference between that and scraping nearly-as-good-as-GPS location information from a 3rd party which would bring the need for a warrant into question.
Just a reminder, the average IQ is 100 so fifty percent of the population is less than that.
The term you are looking for is median.
With an average you could have 99% with scores below 100 and 1% with higher scores. Or the 99% could be higher and 1% lower. The average is simply the sum divided by the count with no connection to distribution.
The median (or 50th percentile) is value in the center where roughly half are above and the other half are below. It can't really be half on either side though since it is actually ((count - 1) / 2). It also doesn't account for a cluster at the center where you might have multiple examples with the same value (e.g. The median of "2 3 3 3 5" is 3,
but only 1 of the 5 is actually higher...).
It trivial for Facebook to link the identities, she is using the same IP address to log in for both of them. It is then reasonable for the Facebook algorithm to guess that people logging in from the same IP address are related somehow.
More likely the simple answer is that she was clueless about how deep their tentacles are and used the same browser without logging out of Facebook first. Thus since just about every website insists on haven't FB's "like" button somewhere on their page, FB gets the details to do the math.
A smart person (can that be said of a Facebook user?) would at least go as far as using an entirely separate computer for business and personal stuff. Still not fool proof by any stretch, but every little bit helps.
Slashdot Mirror
Yeah I love my UBNT gear (6 APs, 5 switches, 2 routers, and a cloud key), but their hardware tolerances and lack of real support are painful.
EVERY device I've had from them "squeals". The APs are the worse as it increases based on what is being pumped through it and can be bad enough where I can hear it from 20' away with the TV on and between me and the AP.
My support from them started off great where they sent me a total of 4 replacement APs and a 8 port ToughSwitch (I had bought a 5 port, which also squeals). After the second round of APs they just stopped responding. The upside is that included never sending me return info for the last pair of APs and the 8 port TS so I went from 2 APs and a 5 port switch for ~$300 to 4 APs and 2 switches (5 port and 8 port) for ~$300, so it wasn't all bad ;-)
I still buy their gear because the price can't be beat for the functionality. I just know that it has to be placed in a location where no one regularly goes.
The general lesson may be the same as that behind the Concorde.
Unlike others, I agree
There's not a massive market for people willing to pay a massive amount of money for travel by planes. That applies whether the increased cost is for incredible luxury or incredible speed.
But I think you went to the wrong conclusion
The biggest issue with the 380 is that not all major airports can accommodate it. Even those that could handle the 747. Remodeling an airport is not a simple affair. Especially those where communities have grown up around them and effectively limited their expansion space.
The Concorde had a similar issue where there were only a few airports could accommodate it's runway requirements and even before it started running into regulation problems there wasn't a swell of airports looking to sink the money into supporting it.
A related issue with the 380 is that many airports are already at or near capacity as it is, so the idea of more people in the same number of flights is another infrastructure problem they have to solve at the same time they are dealing with runway/traffic/gate changes. That doesn't give them much incentive to invest in letting those monsters land.
What's worse, is that the menu items were right under each other. "Missile alert" and "Missile alert Test". Both items give the same "are you sure" confirmation. While it was certainly a bone headed mistake, it was one what was easily possible for someone in a hurry. As this fellow was just wrapping up his shift, he was clearly trying to get everything done in time.
I don't get the people calling for this guy to get fired. Like none of those assplugs have ever made a mistake on their job. How many know someone in the office that accidentally did reply to all, or forward some email chain to external Eric rather than the internal Eric. Shit happens. Clearly the design of that system isn't the best.
I agree. Shit happens. Just was unfortunately some really bad shit in this case. I haven't made such public mistakes, but I've made some big ones. He is just a scape goat here.
The real problems I see here is that A) it wasn't blatantly obvious (through using a different workflow and by clear visual (and audio?) indicators) that he was going down the live path rather than Test and B) that having permission to use the EBS doesn't automatically carry the ability to send a "oh shit! we didn't mean to do that" message as well.
At the point where the workflow path deviates between Test and Real it should be impossible for someone, no matter how rushed/tired/bored, to get it wrong. Glaringly different color schemes. Audio prompts. Full screen dialogs so they can't be paying attention to something else. Extra steps down the Live path. Having a second account confirm the action. Etc...
Make it so that you have to be either blatantly ignorant or blatantly malicious to get to the point of sending a Live alert when you shouldn't. The timeliness nature of the system, however, does present some challenges since you want to delay getting the alert out as little as possible.
Now what I think is really being missed here is that this was a blessing in disguise. Yes it inconvenienced and scared the crap out of a lot of people, but based on all the reports I've seen no one had a clue what to do with it. Given the short time involved for a missile to get from NK to Hawaii and the devastation a nuclear warhead would do I question the point of giving warning (I'd rather die blissfully ignorant rather than in a panic or linger through injury/radiation poisoning), but if there is going to be a warning people need to know what to do and react accordingly.
They are concerned enough to spend money on the warning system, but have they spent the money on enough bunkers to hold the population of the islands? Are they located so that everyone has a reasonable chance of getting to one regardless of traffic/panic of everyone else trying to get there?
Personal space?
Yes personal space. Even though in most cases everything in a marriage is shared equally there is still the concept of personal space and "mine vs theirs". While not legally binding, they are still critical to being able to live in the same house together.
I don't know where you keep yours, but close friends can at any time take a 50 out of my wallet as long as they tell me
and put it give in due time.
And that is the key part left out of items 2-5 in the original list.
I completely agree with you that in a good relationship, grabbing some cash from your partner is a non-issue. The expectation, however, is that it's a good relationship so that the one doing the grabbing is going to hold up their part of the social contract and let the other know. In that context, there is neither anything wrong with or illegal about taking the money.
it depends on what the owner thinks
The offended party's opinion makes no difference (as it should not). Theft has a legal definition and just because I feel something is theft does not make it so. Except for the first example the rest all have some explicit or implicit legal access to the money in question. That doesn't make it right to take the money without asking, but it makes it legally NOT theft.
Our legal system is already a big enough mess as it is. Allowing people to define laws based on how they feel at any given time is NOT the direction we want to go.
That last one is the one that most likely will result in a legal battle.
Just what sort of legal battle do you think it would result in? That in itself is not remotely enough to justify a divorce. The police/prosecutor will laugh at you. You could probably find a low life lawyer to help you file a civil suit, but really?
In what kind of relationship that is still at least kinda-sorta working do you feel obliged to write your SO a check for money owed?
In what type of relationship do you feel it's Ok to casually invade someone else's personal space without so much as a "hey, I need to grab $50"? While most of the original list is technically legal, I'd say there are some serious relationship issues going on...
I'm not sure you understand what you just did. You claimed that the money is a shared asset but it was wrong to take the shared asset to buy food. You need to rethink that. If the money is a shared asset then it both of theirs regardless of where it resides. As a shared asset, he has a right to take and spend it regardless of whether it is in the bank, his wallet, or her purse, just like she does.
No, they are correct. Just because it's a shared asset and you have the right to use it does not mean it is the correct thing to do. You CAN take the money and you will NOT be charged with theft (assuming you are not legally separated), but it's still a pretty shitty thing to do.
Now in contrast, unless there is a problematic pattern, the wife getting too bent out of shape over a one time event also falls into the right but wrong category too.
As they said, "right" and "legal" are two totally different things. Plenty of things are right, but illegal. Plenty of things are legal, but not right. Most of the original list comes down to "just because he can, doesn't mean he should".
I developed a set of BASH scripts to automate building a GNU/Linux distribution from scratch based on Linux From Scratch releases. After creating the package build definition files you can launch the build process by running a single master script. https://github.com/gdhorne/abs...
I know a guy that wrote a Puppet/Chef alternative in KSH. Complex stuff certainly can be done, but it is almost always more convoluted than using a better language for such tasks.
OLED still has a very serious burn-in problem and that just does not seem to go away in the mid term - so no, OLED will not replace LCD in the monitors any time soon.
I've got the 2nd to the last pre-4k 55" LG (3 years old?) and I haven't seen any sign of burn in. It replaced a Pioneer Elite Plasma 50", so I know all about burn in (fuck you NBC logo!).
I read about the burn concern before buying it, but I simply couldn't stomach the piss poor LCD quality after living with true blacks on the Plasma for so long (the refresh is also far smoother on the OLED so I've never noticed that irritating "soap opera" effect either). I generally try to avoid burn in after owning a Plasma, but since every channel likes to have their logo on the screen 24/7 it's hard to avoid the "static" image issue. To my relief, however, I see no signs of burn in at all.
I also have zero dead pixels that they are complaining about above.
My only one complaint is how fragile the damn thing is. The Plasma took some good whacks in it's time and wasn't moved about all that carefully, but it too a small high velocity projectile to take it out. The first OLED had to be replaced a month in after a rather light object deflected wrong and hit the screen. At worst I would have expected a scratch, but it damaged the glass and the panel wouldn't turn on anymore (the Plasma would turn on, but it was useless). Now we treat it with kid gloves which is rather annoying with a 5yr old running around...
You can potentially code solutions in fewer lines of Python compared to bash too
For complex things, certainly and at that point you should be using something more practical than BASH anyway.
If, however, I want to simply execute a shell command (that does not have a Python/Perl/whatever builtin analog), capture it's output to a variable, and check the exit status, BASH is pretty damn simple. Those last two requirements are the biggest killer of Python as that forces you to use subprocess which makes it much more complex than BASH (especially if you want to capture stdout and stderr).
It's not that things like that are hard or not well documented, but they are more complex to write and don't read as simply. Not only does simplicity serve when writing the code, it also serves when it has to be debugged at 4am due to a Production issue.
I've done my time as an Admin and much prefer writing real code (of which I happen to specialize in automation), but I recognize that the language I may choose to solve a problem might not really be the best option when all facets of it's deployment and support are taken into account.
Now what most admins leave out of their code which would do wonders regardless of the language is error checking. I've lost track of the number of messes I've had to cleanup that simply came down to scripts that blindly carry on assuming the world is perfect without bother to check... "if [ $? -ne 0 ] ; then" really isn't THAT complicated...
"Incitement" is bullshit. Rioting is a choice. Losing your head to the mob is no excuse. Large groups of people are just as dangerous as any other animal, you should expect the worst when they become agitated, but people do it by choice, either way, the best move is to keep a safe distance.
While I agree that those in the mob are responsible for their own actions (including a panicking horde when someone "yells fire"), there is also responsibility on the one doing the shouting for recognizing the situation and the result of their "free expression".
Is the piece of shit that called in the SWAT team not culpable in the death of that innocent man? Certainly the police have responsibility for how they responded to the call and the actions they took, but ultimately they would not have been there had he not called. Additionally he clearly knew that the police would show up in force due to such a call and would have to be monumentally stupid (debatable given that he thinks swatting is "funny") to not grasp the potential outcome of such actions.
So yes, the people responding to the "free expression" have responsibility and should be held accountable, but the same goes for the expresser.
Here's a new year's resolution for you: Strap yourself to a rocket and launch it to demonstrate that the Earth is flat.
The GP isn't wrong though. As part of pushing "DevOps" my company is pushing the Admins to become "real" programmers and as such is trying to shove Python down their throats.
While I'm a firm believer in fresh/relevant skills keeps the agism boogyman away, there is also a lot of risk in such a move. What I've seen:
I'm sure there are more if I put my mind to it too.
Yes you should always learn new skills and keep up with technology, but you should never do just to do.
A good [insert role here] knows that while they need to keep their tool box up to date they also need to use the right tool for the right job. Any one-size-fits-all approach is always doomed to problems that should never be.
After watching the body cam, it's a bit pathetic. Maybe there should be better quality cameras on the dash. I think I've had better quality from 10year old cameras, if the intention is to show that the criminals are misbehaving, this quality really lets the police down.
Those cameras are designed for closer interactions than what happened here. Maybe 20' tops? Additionally this was video at night and not in an IR mode. Given the poor lighting conditions and distance, that's actually pretty good quality in my opinion.
Bullshit. Unless that officer was using a pair of binoculars. Stupid, panicky pigs.
Can't quite tell for sure, but it does appear that the rifle had a small scope on it. If so, even a small one would have been good enough to provide a better view than we see in the video.
What I'm most shocked about is that it wasn't the typical hail of fire where only one or two actually found the target. This was a shot by an officer that actually knew how to use their weapon!
It's absolutely disgusting that this guy lost his life over some prick half the country away being pissed off over a $1 or $2 dollar bet. The limited context of the video would seem to corroborate with the Police's version of events though (that he wasn't following commands). I've been an adult longer for awhile now than I was a child and it's always been basic knowledge that when dealing with cops in a non-friendly situation there are two basics to walking away. First and foremost, you ALWAYS move slow. Especially when raising your hands. Sudden moves will get you shot 9 times out of 10. The second rule is to follow the orders even if you believe they are in the wrong. Being alive and sorting it out later is far better than being dead and right.
Of course knowing these things in the comfort of my office behind my computer is drastically different that opening my front door at night to find my house surrounded by cops pointing the guns at me. It's very believable to me (without seeing more video context) that the guy opened the door, freaked out, and wanted to get his hands up as quickly as he could so as to show compliance and being unarmed.
There are really not enough bad things I can hope happen to the asshole that made the phone call.
It looks pretty. Maybe an engineering problem.
But it sounds like the roof works fine, and the complaints are it's inconvenient for people who aren't in the Apple store.....
Sounds like another marketing/sales ploy just like their CPU slowing tactic. Don't want to get hit by falling snow/ice? Come inside and buy something!
Android is a BIG step backwards in operating systems.
Based on the rest of your post, the problem is more that you are trying to use the wrong tool for the job than a specific fault of the OS. You think trying to use iOS as a desktop OS would net you better results? They were specifically designed to be run on limited hardware (compared to laptops and desktops) and relatively small screens.
It isn't self hosting unless you chroot it, and then, you can't get a native windowed program running on it, unless you use VNC to open a session to the chroot.
While the idea of running Android on a real computer is cool and even somewhat useful, you're asking it to do something it wasn't designed for. This isn't some failing of the OS.
It's 2017 and Android STILL cannot do multitasking properly: My android phone has 1GiB of RAM. Why the fsck can it not put multiple windows on the screen (not just 2, but like, 10) and let me work on more than one thing at once?
Maybe because there isn't enough screen space on a phone/tablet to have 10 different applications visible in a meaningful manner?
Every app runs in fullscreen, and actually stops running (or changes to a 'background state') when you switch to another one.
You would be crying like a baby if it did what you wanted and then your phone was A) hot as hell and B) the battery was dead in 10 minutes from all the stuff you switched out of, but forgot to kill eating up the CPU and killing the battery.
Windows 95 let me put as many windows on the screen as I want
Have you considered the extremely odd possibility that this is because it was ... wait for it ... DESIGNED AS A DESKTOP OS???
Android can't mount NFS shares and the state of memory-card management is a mess. You can't even symlink directories without rooting it and mucking around. Why isn't that in the native UI?
Again. Phone/Tablet OS. Not desktop. Different worlds.
Every. Bloody. Thing. Is. In. Java. Why can't I write a program in scheme, and run it on Android?
Yeah I've never gotten that myself. As long as there is a tool chain to do the correct byte compiling, it shouldn't matter. Different language, but the same applies to iOS too.
Android doesn't support IPv6 properly. I'm pretty sure Windows 98 did. Maybe Windows 95 did, as well.
I don't know about Andriod's compatibility, but I know you certainly have no clue what you are talking about. Given that Win95 was released a few months before the first IPv6 RFC (1883), no it most certainly did not support IPv6. Similarly as Win98 was released a few months before 1883 was superseded by 2460 which is when it started to actually mean something to the world, it did not support it either.
Regardless, this will be the Year of IPv6! right after it's the Year of the Linux Desktop! ...
Oh, and here's the biggest step back of all: 99% of all android phones don't even give root access. It's an OS that you can't become root on. How is that a step forward in any conceivable sense of the word?
100% of iOS devices don't allow you to become root. What's your point?
Oh. Wait. You're trying to use it in a manner that it wasn't really designed for.
Stop being an idiot and using things in a manner that they were not meant to be and then complaining when they don't work as well as tools actually designed for what you are trying to do.
OS development has totally stagnated. There hasn't been much forward progress since the mid 1990s, and there has actually been a lot of backward regression.
While it might seem that way, I think there are 2 major points you are missing and you are under valuing the differences between then and now.
The first is that until the late 90s consumer OSes were significantly limited by the hardware they ran on. There were very real limits to memory, disk space, and bandwidth. The "great jumps" during that time happened around significant hardware changes. The last was the time of the Pentium which unlocked the path to the resources we now have available. While we still have physical limitations, they are so high that the OS vendors are not constrained like they once where. This allows for incremental changes which are less WOW inducing than the earlier era where 2MB of RAM was something to be excited about.
Secondly, just what is really missing from an OS these days that should be at the basic OS level? The only thing I can really think of that would be really nice is to kernel updates that don't require a reboot. Beyond that peripherals haven't significantly changed in 20+ years (e.g. USB is still serial based and everything else continues to fall by the wayside). So beyond tweaks for stability and performance, what's left?
I also think you under value what has changed under the covers. I was playing with Linux back in 94 and there is no question it is a much better OS now than it was then. Hardware compatibility isn't remotely the concern that it once was. Similarly the differences in Win 95 to Win 10 or NextSTEP to the current OS X are equally significant and important. It's just that much of the change is behind the scenes and not as noticeable (usually deliberately so).
It's also worth noting that the UI is not part of the OS itself, but just an extension running on top of it. It's a distinction many don't seem to understand, but it is an important one. Similarly, however, beyond tweaks to meet the aesthetics of the day, what significant changes are needed to the UIs these days?
We as a culture cannot afford the one size healthcare for all problems.
You'll get no argument there from me just as you'll get no argument that ERs get overcrowded with those that have no business there. Your original assertion, however, was that someone's ability to drive to the ER and their decision to call an Ambulance was the deciding factor of if they are a valid ER patient. That is demonstrably not true.
One of the factors that this study doesn't seem to take into account is Obamacare. That, I think, has had far more impact in overuse of the ER than Uber. Many ERs were used in place of doctors by people that had no insurance and/or couldn't pay since most public hospitals reduced costs or simply didn't bother to chase down those who couldn't pay. In my area within a few months of OC getting in gear ER wait times dropped significantly while getting an appoint with GPs became harder (e.g. outside Urgent Care level stuff, same day appointments are just about gone). OC has a lot of problems, but it's impact to ER usage definitely seems to be a big pro for it.
I've only used Uber twice for work, though I've tried to use it more. Getting an Uber home from a major international airport takes about 5 minutes (so longer than walking right up to a cab) and costs within a few dollars of what a taxi costs for the same trip. I use Uber because my company has some connection to them so the rides feed our expense system. The local cabs don't take our corp Amex (also directly feeding our expense system), so that it's less hassle for me doing my expenses is the only reason I have opted for them so far.
Trying to get from home to the airport, on the other hand, can vary from 30 minutes to an 1.5 hours while the same cab company that can bring me home from the airport is 45 minutes and SuperShuttle (much cheaper than either) gives me a time I can count on for planning. It's not like I'm out in the sticks either. I'm in the middle of a bunch of heavily populated suburb developments and happen to be 2.5 miles (as the crow flies) from the end of said airport's runways. This area (and the county that I and the airport fall in) are one of the country's biggest Tech sectors (outside of SV) too which was an early adopter of Uber.
The point being that while taxis have problems, they are far more predictable outside of the major city areas. Uber is far from the panacea the "True Believer" want us to believe.
Not sure why you are trying to bring Communism into this since nothing about the subject or my comments has anything to do with Communism (or any particular form of government).
The problem with people going to the ED, is the fact that they are not going for a real emergency, but an urgent visit or just see a doctor without a schedule.
Obviously you are a learned doctor that knows all the the possible health conditions and how they should be managed and treated. Please enlighten us more...
There are plenty of issues that are not life threatening which can not be treated by urgent care. There are also plenty of conditions that complicate less severe issues which make having access to a full hospital's resources the better choice. There are also plenty of areas where urgent care facilities don't exist (or are run by a specific group that do not accept non-members).
There are plenty of people that waste the ER's time for things like non-critical flu/cold symptoms and the like, but to argue the patient being able to drive themselves or not is ludicrously naive.
Presented with a transportation option previously depressed by the city overlords
So these cities refused to allow taxis to operate prior to Uber? I doubt it. Even though they may be more expensive than Uber, they would still be far cheaper than an ambulance ride. So is Uber truly the savior of humanity this study wants us to believe, or are there maybe other factors that they missed/ignored in their effort to show Uber in a good light?
How come corporations never respond???
Among other things, because they aren't really given the opportunity. Generally it's something like:
Even for those where they get a real person, in something the size of Starbucks the answer will invariably be "we'll look into it and get back to you" or "let us find out who you need to talk to". There is still no delay in the publishing though.
That certainly isn't always true, but it's also not always "[insert big company] is evil and hiding things" either.
Warrant to search phone company records for triangulation data not so cut n' dry.
They are required to get a warrant to do something like attaching a GPS tracker to your car. I fail to see the difference between that and scraping nearly-as-good-as-GPS location information from a 3rd party which would bring the need for a warrant into question.
Just a reminder, the average IQ is 100 so fifty percent of the population is less than that.
The term you are looking for is median.
With an average you could have 99% with scores below 100 and 1% with higher scores. Or the 99% could be higher and 1% lower. The average is simply the sum divided by the count with no connection to distribution.
The median (or 50th percentile) is value in the center where roughly half are above and the other half are below. It can't really be half on either side though since it is actually ((count - 1) / 2). It also doesn't account for a cluster at the center where you might have multiple examples with the same value (e.g. The median of "2 3 3 3 5" is 3, but only 1 of the 5 is actually higher...).
It trivial for Facebook to link the identities, she is using the same IP address to log in for both of them. It is then reasonable for the Facebook algorithm to guess that people logging in from the same IP address are related somehow.
More likely the simple answer is that she was clueless about how deep their tentacles are and used the same browser without logging out of Facebook first. Thus since just about every website insists on haven't FB's "like" button somewhere on their page, FB gets the details to do the math.
A smart person (can that be said of a Facebook user?) would at least go as far as using an entirely separate computer for business and personal stuff. Still not fool proof by any stretch, but every little bit helps.