Double boogers. 5/10.
I voted for this and would do so again. The state had no business to be in the liquor business in the first place. State run liquor is merely a remnant of prohibition. The argument you made is framed under privatization, but it doesn't make sense here, because liquor is a retail business, not a function of government. If my taxes went towards universal intoxication for all citizens (human rights violation to have to confront life's problems sober) and that got more expensive when privatized, then you would have an argument.
Even if Freddie's does a huge markup, I can shop elsewhere. Prices will come down when more players get in. Why be limited to making special trips to dirty stores with lame hours and surly employees.
So, this is an example where privatization costs the public much more in the short run, AND increases the likelihood of an income tax, which will cost the public much more in the long run.
We need to confront the need to feed government, not just look for ways to satisfy the beast whenever it is hungry.
Why was parent modded troll? Yes, he took took the flamebait, but his opinion is shared by many. It's a legitimate complaint against the party that promised "to be the most transparent administration [in history]" (Obama) and "dredge the swamp [of corruption]" (Pelosi). The trolls here are too busy correcting each others grammar.
This is to prevent spammers from being able to send mail from *.onmicrosoft.com. This is the online service, not to be confused with Office, the desktop app.
That's a good idea. They should do it for each category and also include an "average number of days between stories". I felt like we were overdue for a Bitcoin story.
Thanks for telling us about slushdot.
It's like a cheap knock off brand.
It's like a little brother who tries to hard to be like his big brother.
Instead of "news for everyone...", its moto should be "News for a subset or nerds, subsets of stuff that is anecdotal."
The full.Net framework has a lot of hacks to support COM. Your STA running managed code can get preempted at any time to Release COM objects behind RCWs that get garbage collected. This can cause interesting stress bugs. It gets even worse when an RCW around an STA gets finalized on the finalizer thread. That blocks the finalizer thread, because it waits for.Net to Release the COM object on the original STA thread. If the STA thread is in a wait state, you can hang the finalizer thread. Another big issue is around supplying alternative credentials for DCOM..Net has no exposure of the CoCreateInstanceEx API that allows you to specify alternative credentials. Even if you wrap it yourself, you have to make sure you call CoSetProxyBlanket before you do any calls - and.Net does QueryInterface under the hood for you, and you have to make sure CoSetProxyBlanket is called again, then the simple programming interface of.Net becomes more of a hindrance than a help.
They were supposed to get away from COM in the Silverlight versions. Now the waters are even muddier, because WPF is still supported on the Full version of the CLR.
That movie Tommy Boy comes to mind. The quote was something like this:
I can take a dump in a box and mark it guaranteed. All that I've done is sold you a guaranteed piece of shit.
Slashdot Mirror
His analysis is superficial, and his conclusion makes everyone dumber. "And then they ate ice cream," might as well been the result. Talk about s
What reliability? I had to reboot my iPhone 3G more often than my WP7. Cite sources measuring reliability of WP7 or 8 compared to iOS or STFU.
In my experience, comments make sweeping generalizations while the articles promote cognitive dissonance.
So, this is an example where privatization costs the public much more in the short run, AND increases the likelihood of an income tax, which will cost the public much more in the long run.
We need to confront the need to feed government, not just look for ways to satisfy the beast whenever it is hungry.
Why was parent modded troll? Yes, he took took the flamebait, but his opinion is shared by many. It's a legitimate complaint against the party that promised "to be the most transparent administration [in history]" (Obama) and "dredge the swamp [of corruption]" (Pelosi). The trolls here are too busy correcting each others grammar.
en-US is open source. TJ had his own branch. Just sync to his branch, and you'll be fine.
This is to prevent spammers from being able to send mail from *.onmicrosoft.com. This is the online service, not to be confused with Office, the desktop app.
brotip: Use magnetz for faster fluid. http://trollscience.com/
That's a good idea. They should do it for each category and also include an "average number of days between stories". I felt like we were overdue for a Bitcoin story.
You must not be talking about setting it up with Windows. Worst experience ever.
It'll be like 911 * 7.
How do you know Ben Franklin didn't dream about sharks with frickin' lasers?
http://www.utzsnacks.com/store/ There. Fixed that for you.
That cloud ought to be accessible by anybody's computer and through any sort of information sitting out on the Web.
As long as the server has the right crossdomain.xml file...
Thanks for telling us about slushdot. It's like a cheap knock off brand. It's like a little brother who tries to hard to be like his big brother. Instead of "news for everyone...", its moto should be "News for a subset or nerds, subsets of stuff that is anecdotal."
However, once one gains the enlightenment of mathematics, one realizes that shoes are beneath them.
Good idea, but I think half the fun of /. is getting incredulous reading comments that you think are overrated or underrated.
Long ago, in a thread tangentially related...
Buzz feels a bit... unfinished to me. It's just one box to put status updates in, and not much else.
Yup, it needs Farmville. Like anyone cares about what their friends are doing.
My point exactly. Why deal with this crap when there are more straightforward alternatives to do interop?
The full .Net framework has a lot of hacks to support COM. Your STA running managed code can get preempted at any time to Release COM objects behind RCWs that get garbage collected. This can cause interesting stress bugs. It gets even worse when an RCW around an STA gets finalized on the finalizer thread. That blocks the finalizer thread, because it waits for .Net to Release the COM object on the original STA thread. If the STA thread is in a wait state, you can hang the finalizer thread. Another big issue is around supplying alternative credentials for DCOM. .Net has no exposure of the CoCreateInstanceEx API that allows you to specify alternative credentials. Even if you wrap it yourself, you have to make sure you call CoSetProxyBlanket before you do any calls - and .Net does QueryInterface under the hood for you, and you have to make sure CoSetProxyBlanket is called again, then the simple programming interface of .Net becomes more of a hindrance than a help.
They were supposed to get away from COM in the Silverlight versions. Now the waters are even muddier, because WPF is still supported on the Full version of the CLR.
You can always use FireBug or programs like Wireshark to inspect your traffic. It's not as bad a XSS attack surface as using iframes for AJAX.
ActiveX didn't exactly take the web by storm on a large scale.
Except for that whole XmlHttpRequest ActiveX component in IE5 that later became standardized and part of AJAX.
Fair != Tough Shit.
That movie Tommy Boy comes to mind. The quote was something like this: I can take a dump in a box and mark it guaranteed. All that I've done is sold you a guaranteed piece of shit.