What is it about Obamacare that so many Americans are against such that it became an election pledge to repeal it?
I could understand a candidate promising tax cuts and then after being elected scrapping Obamacare to pay for them. But this was not the case. It was a specific election promise ...
@derobert In most things other than computing, I'm not a conservative, but when the web started blooming in 1994 I uttered the actual word "It will never catch on". I also, still, find it extremely confusing to move to base 10 from base 2 while at the same time relabelling the units. As a programmer, base 2 makes more sense...
@Kusalananda Yes, a lot of times it does. But most UIs shouldn't be designed around that. Most UIs should, I think, use 10^6. Which seems to be the general trend.
Stuff particularly for programmers (e.g., debuggers) have darn good reasons to use 1024-based units.
@derobert While I realise that Americans are (understandably) sick of the topic of healthcare (and if you don't want to talk about it I completely understand) but has the Affordable Care Act made things worse, or it is a mixed bag? There does not seem to be a concensus.
@FaheemMitha Personally, it make things better for me... But I have a friend it made worse off, too. Overall, it got a lot of extra people insured. So I think it was an improvement. But left a lot that still needed fixing.
@FaheemMitha yeah, though the amount of error grows the larger the unit is
@FaheemMitha ~5% for MiB v. MB, ~10% for TiB v. TB
I remember a lot of people being confused—and coming to false conclusions, like it was filesystem overhead (this was on Mac OS, where an empty HFS filesystem actually didn't take much room, and didn't have reserved space)
@FaheemMitha Yep. A DIMM's size is, AFAIK, always a power of two. A system though can have a non-power-of-two RAM (e.g., I have a machine with 24 GiB, from 3×8GiB).
Well, it gave them a few more customers—the Obamacare market is, I believe, actually pretty small. I'd guess that the Medicare expansion that went with it was actually more (new) people covered, and that's single-payer (government run)
But I don't have numbers in front of me, so that's a guess.
And I'm pretty sure the non-exchange market (mostly employer-provided/purchased insurance) is much larger.
@derobert Hmm. It lists India as going from 4% to 4.7%. Which is actually quite large, both as an absolute measure, and as an increase, for a country with a basically non-functional health care system.
@FaheemMitha I pay the equivalent of $10 for a checkup but is guaranteed to not have to pay more than $125/yr, and I'm is guaranteed to not pay more than $250/yr for medicines. When (if) I reach 85 years, checkups are free.
I don't code, don't know the difference between a tag nor a bag however i do have a question and sincerely hope that you may provide so insight/direction. if i have a set of numbers in a tic-tac-toe format (9) numbers, is there a program that will identify the common possible combinations of thr...
While you're absolutely right that it should be closed, it is important to choose the right reason. That had 3 migrate to SO votes and one "off topic: learning materials" vote. I don't know who had voted for what but they're all completely wrong choices :)
The first rule of migration is We don't migrate crap.
That was 100% crap, completely unclear and in the best case scenario a "give me the code" question.
The point of migration is to move a gem of a question that just happens to be off topic here to a better home. If the question is bad, we just close.
Imagine how we'd feel if SO started dumping all of their stupid Kali questions on us! :P
Then, I've started noticing a lot of abuse of the learning materials close reason. That should only be used to close requests for online tutorials and the like.
If a question is crap but doesn't fit the set close reasons, either give a custom one ("I am voting to close this question because it is completely off topic" or something) or choose too broad, unclear etc.
The reason we choose for closure is the only explanation we give to the OP so it is important to give them useful info.
So, never migrate bad questions and please choose the right close reason.
If we migrate, we edit and fix it up first. We should only send things to another site if the target site will be improved by their presence. So if it looks like you wouldn't want it in your back yard, don't send it to anyone else's.
@Kusalananda Heh, no worries. Migration is a pain. :)
My rule of thumb is that if I see something that's off topic here and would be on topic elsewhere but isn't a good question, I just close and leave a comment suggesting they ask on moreAppropriate.stackexchange but make sure they add this and that and fix the formatting etc.
3
If it's great as is, I'll migrate. But only if it's already good or can easily edited into shape.
Actually that tic-tac-toe question is probably a perfectly reasonable question, but written so poorly (and without supporting context) as to be incomprehensible. I can imagine it could be on topic on Math or something.
@terdon Let us know if you see more of these (at least if my name is on the list of voters). I need to know when I'm doing the "wrong" thing to be able to improve.
@FaheemMitha I gave up on that one, not just because memory on Linux seems to be somewhat like black magic, but also because I couldn't see where his "3713500 app" came from.
@terdon Thanks for the reminder. I was in fact keeping in mind the "we don't migrate crap" rule when I voted to close that. I was thinking that the "learning materials" reason made some small amount of sense since it was kind of a "how does programming work, generally" type of question. I admit I could have chosen a better reason (but definitely not migrate!)
What is it about Obamacare that so many Americans are against such that it became an election pledge to repeal it?
I could understand a candidate promising tax cuts and then after being elected scrapping Obamacare to pay for them. But this was not the case. It was a specific election promise ...
ZFS module not reported in buffers+cached
i update my memory analyser tool that help to find problems like that
bug-free-memory
