Not according to the State of California.

According to the State of California, if I go out on the Internet to the web site of a company in Texas and purchase an item, and have it shipped to me in California, the transaction took place in my home. This is their legal rationale for being able to collect sales tax on the transaction without violating the Interstate Commerce Clause of the US Constitution.

Therefore, if I "hack back" someone who has hacked me, their initial hacking took place wherever they are located, but my "hack back", in defence of the computer located in my home, took place in my home.

So this is precisely the same as if someone broke into my house and tampered with my machine to steal bank account and other information, and during the tampering, I, in my home, shot them.

It really doesn't matter that the bullet landed somewhere in Taipei, the transaction happened in California in my hose, just as if I had purchased something.

It's a way to short-circuit your lawyers brain, since then you are not held harmless from damages arising from the use, misuse, or abuse of the software.

To the people who might want to use the code, their lawyers see it as a nifty scapegoat, should damages arise from use, misuse, or abuse of their product which incorporates your software. When apportioning damages to the plaintiff, should they win their case, it'd be up to your lawyers and their lawyers to argue about it, only their layers get to see your code, and your lawyers don't get to see their code.

Seriously, you can not disclaim association with the code, unless things were amended so that declaring something to be "Public Domain" transferred the liability to the public at large, and there was an implicit "hold harmless" clause for the author of the work.

So effectively, only stupid people declare things to be "in the public domain" these days.

If you hack back, just remember to follow the 11th Commandment:
THOU SHALL NOT GET CAUGHT.

http://en.wikipedia.org/wiki/NB-36H

I believe this is the aircraft you are referring to.
If the article is to be believed, it did fly ( although not on nuclear power )

I starting to fell like a broken record here but seriously Slashdot, I would have thought that this Myth that x86 ISA somehow makes it impossible to build a low power part would be dead by now. ARM is a rather complex instruction set now that they have added SIMD and floating point support. If you look at the number of op-codes it has versus x86 they are roughly equal. Both ISAs have variable length instructions (all recent ARM designs support THUMB) so the decode logic complexity is actually pretty comparable. Also much of the decode logic is implemented in software via microcode on both ISAs.

There is nothing magical about ARM that makes it lower power. The real reason why x86 implementations are so much hotter is because designers of x86 processors have been targeting high compute performance for decades, whereas ARM has been targeting low power for decades. A quick look at Medfield benchmarks show that it is comparable in performance to ARM processors that were current when it was released. Medfield is ~4W active TDP... same as a Exynos 5 Dual ARM CPU. From what we have seen from Merrifield/Bay Trail/Haswell the next gen x86 parts are continuing along this trend.

It causes bad drivers.

The place I see this effect is driving home from the AMC 20 in Santa Clara on 101, and the idiots in the rice rockets who (A) thing they are playing a video game, (B) think that video game physics perfectly mirror reality, so things that work there work in the meat word, and (C) think everyone else drives the same way they do, so it's OK to drive that way because the only people who will get in accidents are the people who don't play the game as well as they play it.

Personally, If I were a CHP, I'd fill my monthly no-such-thing-as-a-quota on Friday and Saturday night, and maybe Sunday, if it was a 3 day weekend, and then take the rest of the week off and windsurf. Instead, these guys simply don't get pulled over.

The reason professional race car drivers don't drive like assholes on the freeway is they realize that not everyone is a professional race car driver.

If by "stupidly", you mean it as a synonym for "using Microsoft products in such a way that Microsoft could yank the rug out from under them in the first place", then yes. If by "slipshod", you mean "thrown together by idiots", then no. It was the best available component technology of its day.

It's also why so many companies don't want to give up using XP, and are giving the finger to Microsoft, HP, and so on, for as long as they can get away with giving them the finger.

Most of the businesses with these attributes were acquired with the business systems in place as charity to keep them afloat, and the people who work there employed. So it's not like my father personally made the decision to use the Microsoft products.

The only people who profit from building the same vertical market business practice solution over and over and over are the assholes of the world, like Oracle, EDS, and IBM Global Services, whose business model is predicated on giving the customer exactly what they ask for, as opposed to solving their business practice problem for them. Then they iteratively charge them a fortune to make changes until they get to a successive approximation that's still mediocre but "good enough" for the business to limp along. Both the accounting and moving industries are famous for having systems like this.

Frankly, I'd rather see the SMBs use commercial components and glue code than tithe to those assholes.

Also you should realize that the VB involved is compiled VB, in as much that Java or Dalvic or Go or C# apps can be said to have been compiled: interpreted bytecode is interpreted bytecode, so if you were going to do something dumbass and suggest Java as an alternative, VB is no worse than Java, and is in many ways better, since there's no Larry Ellison involved with doing things like dropping timezone patching to keep the license fees for new runtimes flowing in.

Finally, you should know that Google, Twitter, Facebook, and so on are all using JavaScript and Python and, yes, occasionally ActionScript interpreted bytecode (read: Flash) to run their businesses, because it allows them to make changes to business logic quickly. Only when *they* do it, you'd probably call it "being agile", right?

So those "stupid" people using VB are in pretty damn good company.

Bottom line is that these SMBs have no fucking way of affording updating all their systems at once just so they can hire a new employee, and anyone who says otherwise, including an asshole who thinks they should be exposed to second system syndrome in the process, is a pretentious prick.

Have a nice day.

The last time CO2 levels were at 400ppm was a very long time ago, way before neanderthals, at the time of homo erectus. Maybe it's not unreasonable to worry.

Fortunately coffee is a C3 plant, and should respond well to a CO2-enriched atmosphere.

Its purpose is to approve warrants and provide oversight.

Yes, indeed, its purpose is to approve warrants. Not to decide whether they should be approved, just to put the "genuine judicial branch seal of approval" on them. It has the form of a court, but none of the substance.

Coffee futures are down, supplies are up. This is just another warmist scare story.

So in 6 years, the FAA expects 167,000 aircraft owners to swap the engines in their aircraft for an unleaded engine?

As far as the FAA is concerned, general aviation can just dry up and blow away and save them the headaches.

"You're forgetting about that whole Windows software compatibility thing."

My fathers businesses continue to use XP precisely because of software compatibility.

The business systems in place have business logic built in Visual BASIC which glues together a bunch of (mostly Microsoft) components. Change a component, and the component breaks; change the OS, and the glue breaks, and EVERYTHING dies.

HP is looking at a cash cow of significant reinvestment in hardware; Microsoft, by EOLing XP in the first place, is looking at a cash cow not only new OSs, but new component sales. SMB (small and medium business) is looking at astronomical costs to keep their workflows running. I have no idea why Microsoft, HP, et. al. think that SMB is the cow from which they are going to be able to get milk, given that larger businesses have established a regulatory environment in which most SMB is barely scraping by as it is.

Personally, I can think of at least three companies where my father will just close the doors, rather than facing a significant reinvestment. At best, he will not grow them or hire new employees to run the XP machines which he can no longer purchase in order to incrementally add the next new employee. In fact, thinking of it that way, as hardware slowly fails, it's more likely he will just lay off one employee per one dead XP machine, at least in the most marginal of these businesses.

HP may not be smiling as brightly as they think.

They have it backwards... as humans get unhealthier, the trees suffer.

So exercise and eat right... remember for every mile you jog, you save a tree!