Nothing to do with PC, it has to do with the fact that I'd want to teach my daughter how to solve problems through coding not how to sell her body. She wants to dress provocatively for her enjoyment, that's all on her, but I'd make damn sure she could use her mind to earn money. If anything I'd want her to redefine booth babe as the hot developer making the big bucks.
And even when you do, you can't get a job because everyone wants a rockstar developer who can do it all when in reality it'd take a team of 6 specialists to do what they expect 1 person to be able to know/execute perfectly and quickly.
Be inspired to code by dressing really slutty and letting a bunch of geeks you'd never go out with ogle you.
Your Loving Father
That's about 1/10th of the lowest estimate of the subprime crisis, 1/26th at the top end.
Not only is it not punitive, it's laughable.
What is the "nexus principle"? A basic definition: "A place of business or employee is evidence of “physical presence” and thus constitutes a nexus" (grabbed from the abstract here: http://www.igi-global.com/article/principle-nexus-commerce-tax/66052 )
If you are paying an in-state 3rd party to direct individuals seeking to buy products to your site that is really no different than hiring a sales employee, 1st or 3rd party to do the same. While there is no "employment" contract between Amazon and it's affiliates, there is a contract and remuneration for sales related actions.
The court ruled that their relationship with these in-state 3rd parties was enough to constitute a presence which makes sense - otherwise companies could just 3rd party their sales force and not pay tax in a state. The description states that this somehow conflicts with the Quill ruling where Quill had no 1st or 3rd party presence in the state in question. If Amazon terminated it's relationship with these 3rd parties, in theory the Quill ruling should apply and any 1st party sales would be exempt.
As it stands Amazon's 3rd party partners are no different than dealerships are to a car company.
That doesn't make any sense. A car dealership buys cars from Ford or whoever and sells them locally. Amazon affiliates own and sell nothing and do nothing more than recommend people shop at Amazon.
While the nature of the relationship is different each acts, as the court put it, as a nexus for consumers to buy products from the company they have a relationship with.
SCOTUS fails to act against government's financial overreach! We could NEVER have predicted THIS!
Ruling seems pretty reasonable to me. If Amazon ditched it's local 3rd party partners then Quill Corp vs North Dakota would apply to the products Amazon itself sells. As it stands Amazon's 3rd party partners are no different than dealerships are to a car company.
There's a much simpler way: For general shopping keep 1 easily folded bag available for use. For shopping cart level shopping, keep everything in the cart as is. Take it out to your car and bag stuff there instead of in the store.
It doesn't fit every situation (those without cars, -30C weather, etc) but for most of the time it works great. We keep about 20 reusable bags in the trunk at one time.
The thing with plastic bags not degrading for 100s of years though - that seems highly suspect to me. I've had some disintegrate in a matter of 3-4 years
It should come as no surprise to anyone that there has been a number of right wing cyber attacks on the healthcare.gov site. It seems that there has been a concerted effort on several fronts in an all out Republican led war to kill and destroy the Affordable Care Act, also known as Obamacare. One has to ask if this war on Obamacare has been an intentional and coordinated effort.
Link to Original Source
Even if they do exist you've got to go hunting for the right one, then learn how to use it properly or you'll fuck up the system even more.
Because you didn't have to learn how to use the tools in Windows? Because misusing Windows tools won't fuck up Windows?
You're arguing that you were born knowing how to use Windows and that you should never have to learn anything, ever, you know that? An argument *for* ignorance.
Gott im Himmel.
Misusing Windows tools is a lot harder to do because they actively warn/outright prevent you from doing something stupid. Linux community opinion is much like yours "it's not our fault you didn't research it fully" - which, while accurate, is a complete copout because not everyone has the time/inclination to do so. It's great that you've got the time to be a Linux geek - I don't, nor do the majority of people who use computers.
> whether by crash or failure to resume the result is the same.
No it's not. Language has a use. While being a stickler for precision is not always productive or possible, being kind-of accurate in a broad sense helps people help you.
I was accurate in my description: Linux repeatedly ran into issues which prevented it from booting to the desktop for 4 distinct reasons. I'm not going to detail every freaking issue here but the end result was always the same: I was unable to access the desktop.
(without an "EventViewer" to make it easy)
>participated in launchpad thread
Lets look at the processes:
Event Viewer: Load it up, create a custom view -> select the time frame, the level of detail/type of error, the source(s) or log file type(s) you want to search, and if you want more detailed limitations (keyword/eventid/etc). It creates a nice report, very easily readable.
grep? sure that gives me keyword search. head/tail, sure that'll give me the first/last 10 of 1 log file, pico/vi/emacs sure they're great text editors but won't generate a report across multiple logs. System Log Viewer is the same deal, it'll view one log at a time but forget trying to isolate a needle in a haystack unless you know exactly what you're searching for.
Yes? And? Your failure to describe the problem correctly even in broad terms means that your participation in such threads just muddies the water.
The problem was described quite clearly but here's one just for you: My experience has been that, when you run into a system breaking or unusual problem with Linux you must either spend an inordinate amount of time researching the resolution, devising a fix yourself, or re-install the OS; ether for expediency or because no resolution can be found.
I want to like Linux, I really do, it's just not there yet. Add to that, there's too many people like you who expect everyone to become a linux geek/want to use a command line. Command lines are great, they can be very efficient, but they also require preexisting knowledge to operate. GUIs allow users without that knowledge to simply process the information and discard it when done. I'll freely admit that there are several in Windows that I've mentioned in this thread which do require preexisting knowledge, however, the number required to remember is tiny compared to Linux - the rest are available in GUI form.
There's a great quote which goes something like this: "If you were to learn 10 new methods in Java every day for the rest of your life, you'd be dead before you learned them all". While intended for programers, the same principle applies here. grep alone as 22 different flags, not including special characters/pattern matching/expressions, that's one command among hundreds. Then there's the combinations of commands like cat
Until I can sit down at a Linux system and be able to diagnose/fix most common issues in under 30 minutes without the need to research commands, as I can with Windows now, you won't convince me it's better. The underlying tech of Linux is better without a doubt, it's refinement for casual geek/non-grandma use has a LOT to be desired. The worst part is though, Windows keeps getting worse and people want to move away but there's no Linux option that can fill the gap between Win8 idiocy and OSX walled garden.
Probably because they know it's borked so they're doing a slow rollout, fixing the problems the early adopters find before they push it via update. That or they're just stupid which is entirely possible.
File recovery issue with chkdsk - you're absolutely right it's a pain and useless in many cases. That is a failing. However, it's rare that you ever get those files most of the time it's fixing indexing/journal issues and don't have to chunk files.
>number of command line tools
There are orders of magnitude more of these in Linux than under Windows, and they actually work. Your argument is specious at best. You are using your ignorance of the tools themselves to argue that they don't exist.
You're making my point for me. Even if they do exist you've got to go hunting for the right one, then learn how to use it properly or you'll fuck up the system even more. With 3 commands (chkdsk, sfc, nfc) and a couple GUIs (msconfig, services.msc, etc) I can diagnose/fix most common non-malware issues with Win7. Sure I may be ignorant of some of the Linux equivalents but in my experience 99% of the problems I've run into on Linux require specific knowledge of specific files/flags which quite frankly I don't have time for. In my youth I may have, like I used to have time to mess around with autoexec.bat, but now I need the system to work so I can work.
> I couldn't even find anyone who'd even heard of the issue before.
What, that X crashes?
No, boots to a terminal with no error message, I have to go hunting through various log files (without an "EventViewer" to make it easy) to figure out why it's booting to the terminal instead of to the desktop. When I finally did find the right log file, the error message was too generic for anyone to help me, it was just a non-descript problem with the theme files which, instead of just gracefully failing to display the theme I'd selected, it failed outright.
>One I was able to track down to a problem with specific laptops refusing to resume from hibernate
So now it's not X crashing but resuming from Hibernation? So which problem is it really?
I never said "crashing", I said refusing to boot to the desktop - whether by crash or failure to resume the result is the same.
>The other the only advice I could get was "reinstall".
This is blatantly false or you were not even asking in Linux fora, or you were calling up the useless HP or Dell tech support.
Fuck you - I participated here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568711 as well as a few forums/lists where ultimately it was found to be a kernel issue
I should rephrase that - "Windows was the only thing that did what I needed it to and didn't fail in such a way that it wasn't quick and easy to recover from". There were a few chkdsk
I triple booted a MacBook Pro for 18 months to try all 3 systems. OSX does what it does well but it doesn't do much. Ubuntu failed 3 times during that period. Windows was the only thing that did what I needed it to and didn't fail. Ultimately the hardware failed at 18 months (couldn't handle the video processing load I was putting on it and seemed to have issues with the PMC drivers which resulted in excess heat even on idle)