Nevermind that it's also (effectively) a fossil fuel since cracking water is prohibitive from an energy standpoint so they steam crack natural gas instead...
and actual use case for dual licence needing to be consistent: (each line is a release step)
FOO - proprietary only sell for $$ BAR - proprietary only sell for $$; FOO converts to GPL BAZ patch shows up, creator ignores? BIN - proprietary only sell for $$; BAR converts to GPL
where you run into trouble: create app, version FOO licence under GPL && proprietary licence. modify app, version BAR, no issue with either licence. someone puts a patch against BAR in the GPL version out on GitHub (or anywhere else). BAR + patch is version BAZ.
Unless you get permission from the patch creator you can't pull BAZ back into your proprietary trunk. You can make BAZ not part of your GPL tree, just to keep the two versions consistent, but then you're letting potentially cool features go unused.
Even worse, it is possible that you independently create BAZ not knowing about the community version, and end up being sued for it. (assuming your source is different enough from the community version you'd likely prevail, but it's still a costly hassle.)
So sure someone can dual licence, but it can really be a PITA, and thus just going MIT licence is so much less headache.
Mal and crew leave the Serenity and it goes back in mothballs. They go their separate ways. Could be done with narration and CGI or later as a flashback. New crew finds an old Firefly class in a mothball fleet and picks her up (the more echo of the initial series pilot the better here). As they are refitting the ship they discover one of the smuggler holds (no surprise to anyone since these were popular ships for that); and find something (plot device) epic that starts them on a quest to figure it all out.
blah blah blah, ships plate was missing, is found, "Hey her name is Serenity!" "I remember a ship with that name, owned by a Browncoat that wouldn't give up" blah blah blah and off you go with a series reboot. Allows to bring in former cast as cameos, accounts for them being older, etc.
not true. While I was at intel we had several CPUs that had issues with older Windows (and Linuxes). We *mostly* papered over those issues with uCode updates in the (BIOS|UEFI)/ME firmware but sad fact is anything after ME5 had zero Win98/2.2 support and only halfway okay WinXP/2.4 support. Lion's share of the issues were integrated LAN and Graphics though, so as long as you used a PCIe LAN and GFX card you were okay.
There's a handful of engines that are still out there like this. I have an 04 5.7 Hemi. That beast is good for at least 300K, but the rest of the truck is falling to bits already.
I *lived* with a BPD for a decade before I successfully extricated myself from that disaster area.
Trump displays so many hallmarks of this that I actually get mild anxiety attacks from watching him. There is *no* timing the cycles of "up on a pedestal" to demonization and back... none.
I'm not. I think most here on/. are of this general opinion. It's machiavellian for sure, but really does have the whole "Ends justify the means" feel to it.
Hopefully (though doubtfully) the OEMs will be eating a lot of warranty returns. It is only if this costs the OEMs money that the problems will be fixed. If it only costs the end users money then not a ton will really happen.
You are correct. My statement was more along the lines of how I feel about being asked to forfeit my vacation.
If you're only going to offer me straight pay if I am giving up vacation time, then I'll just take the vacation. Obviously the same goes for if I lose it outright.
If, however, you're going to compensate me at time and a half then I'm much more amenable to not taking every day of vacation I've earned. -nB
That's true, but if this gets adoption rates up, then even if they switch to another vendor they still have cameras. They'll find it hard to justify discontinuing cameras once they have them.
Actually, even with a scope you can't reverse an entire design these days.
The dopant wells are too small to reliably measure, and there's just too much going on in the interconnect above the poly layer to actually capture it all correctly. It's like OCR where you read an e as an o or an l as a 1 or I.
Conceptually you can reverse an entire chip. Pragmatically you can only really see the overall structure of the die layout and maybe home in on how they're making their gates and oxide layers.
As to what he stole: * Itanium VLIW instruction decoder logic and specification. * VLIW to x86 code manipulations * Cache coherency algos and other stuff I don't remember anymore.
It caused a *huge* change in how internal sensitive docs were handled: - cube searches, if you left red or orange covered docs out (even to go take a piss) you could be written up - physical IP had to be accounted for at a much more detailed level (though I think that was more related to a guy selling engineering samples on eBay) - New on-line format for PDFs of documents using "authentica" application that killed the ability to screen cap (a print screen had the Authentica logo sprayed all over the place where the document was) - printed copies had non-obvious watermarking applied (in addition to the big red watermark across each page diagonally with your name on it) to catch OCR or scan and remove red layer attempts at copying.
This is why I have *no* work contamination of my personal machines. I only bring my phone to work, and I concede they can search the filesystem if they want (it's really no different than a USB drive afterall).
If they expected to search my home machine I'd refuse and lawyer up when they tried to discipline me for it.
On a related note: Uber is handling this all sorts of wrong.
This happened while I was at Intel, an employee grabbed a stack of confidential and top secret Itanium docs and *while on sabbatical* got a job at AMD. When AMD found out he stole the IP (to help him get a leg up at his new employer) they called Intel, and the FBI; obviously sacking the guy as well.
There is a story (I don't know if true) about a guy getting the formula for Coke and offering to sell it to Pepsi. Pepsi called Coke and asked how they wanted to handle it. The decision was that Pepsi would offer to buy the formula. When the guy came in to sell it, the Pepsi exec accepted the envelope of docs, handed them to a waiting Coke lawyer, and nodded to the waiting FBI agent to arrest the guy.
In both these cases the company potentially receiving the secret sauce for a competitor made great efforts to inform said competitor and distance themselves from *any* question of impropriety. How is it that Uber saw no need for verifying poached employees brought nothing but what was in their heads with them from the competition?
I tried getting out from under one and was retaliated against and ultimately was terminated (with 17 years of good to outstanding reviews behind me) by a railroad job from said psychopathic asshat.
Slashdot Mirror
Nevermind that it's also (effectively) a fossil fuel since cracking water is prohibitive from an energy standpoint so they steam crack natural gas instead...
https://en.wikipedia.org/wiki/...
and actual use case for dual licence needing to be consistent: (each line is a release step)
FOO - proprietary only sell for $$
BAR - proprietary only sell for $$; FOO converts to GPL
BAZ patch shows up, creator ignores?
BIN - proprietary only sell for $$; BAR converts to GPL
where you run into trouble:
create app, version FOO licence under GPL && proprietary licence.
modify app, version BAR, no issue with either licence.
someone puts a patch against BAR in the GPL version out on GitHub (or anywhere else).
BAR + patch is version BAZ.
Unless you get permission from the patch creator you can't pull BAZ back into your proprietary trunk.
You can make BAZ not part of your GPL tree, just to keep the two versions consistent, but then you're letting potentially cool features go unused.
Even worse, it is possible that you independently create BAZ not knowing about the community version, and end up being sued for it. (assuming your source is different enough from the community version you'd likely prevail, but it's still a costly hassle.)
So sure someone can dual licence, but it can really be a PITA, and thus just going MIT licence is so much less headache.
Loved Ice Pirates!
https://xkcd.com/566/
A Firefly reboot is even easier than that.
Mal and crew leave the Serenity and it goes back in mothballs. They go their separate ways. Could be done with narration and CGI or later as a flashback.
New crew finds an old Firefly class in a mothball fleet and picks her up (the more echo of the initial series pilot the better here).
As they are refitting the ship they discover one of the smuggler holds (no surprise to anyone since these were popular ships for that); and find something (plot device) epic that starts them on a quest to figure it all out.
blah blah blah, ships plate was missing, is found, "Hey her name is Serenity!"
"I remember a ship with that name, owned by a Browncoat that wouldn't give up"
blah
blah
blah
and off you go with a series reboot.
Allows to bring in former cast as cameos, accounts for them being older, etc.
not true.
While I was at intel we had several CPUs that had issues with older Windows (and Linuxes).
We *mostly* papered over those issues with uCode updates in the (BIOS|UEFI)/ME firmware but sad fact is anything after ME5 had zero Win98/2.2 support and only halfway okay WinXP/2.4 support.
Lion's share of the issues were integrated LAN and Graphics though, so as long as you used a PCIe LAN and GFX card you were okay.
There's a handful of engines that are still out there like this.
I have an 04 5.7 Hemi. That beast is good for at least 300K, but the rest of the truck is falling to bits already.
good luck with that:
https://en.wikipedia.org/wiki/...
I *lived* with a BPD for a decade before I successfully extricated myself from that disaster area.
Trump displays so many hallmarks of this that I actually get mild anxiety attacks from watching him.
There is *no* timing the cycles of "up on a pedestal" to demonization and back... none.
that's what makes it the best kind of sarcastic troll.
A hat tip to the GP post indeed!
depends, did she submit a bad review on Amazon?
I'm not. /. are of this general opinion. It's machiavellian for sure, but really does have the whole "Ends justify the means" feel to it.
I think most here on
Hopefully (though doubtfully) the OEMs will be eating a lot of warranty returns. It is only if this costs the OEMs money that the problems will be fixed. If it only costs the end users money then not a ton will really happen.
citation?
If your fraud scheme falls apart in 5 days you set it up wrong.
Longest death march I've had was 36 days.
zero days off, 12 to 16 hours per day.
I took two (comped) weeks off after that.
You are correct. My statement was more along the lines of how I feel about being asked to forfeit my vacation.
If you're only going to offer me straight pay if I am giving up vacation time, then I'll just take the vacation. Obviously the same goes for if I lose it outright.
If, however, you're going to compensate me at time and a half then I'm much more amenable to not taking every day of vacation I've earned.
-nB
Cut me a check for the *overtime* value of the lost vacation.
Pretty simple.
Good to know!
The article did not say it streamed to the cloud, but did imply it.
That's true, but if this gets adoption rates up, then even if they switch to another vendor they still have cameras. They'll find it hard to justify discontinuing cameras once they have them.
Actually, even with a scope you can't reverse an entire design these days.
The dopant wells are too small to reliably measure, and there's just too much going on in the interconnect above the poly layer to actually capture it all correctly. It's like OCR where you read an e as an o or an l as a 1 or I.
Conceptually you can reverse an entire chip. Pragmatically you can only really see the overall structure of the die layout and maybe home in on how they're making their gates and oxide layers.
As to what he stole:
* Itanium VLIW instruction decoder logic and specification.
* VLIW to x86 code manipulations
* Cache coherency algos
and other stuff I don't remember anymore.
It caused a *huge* change in how internal sensitive docs were handled:
- cube searches, if you left red or orange covered docs out (even to go take a piss) you could be written up
- physical IP had to be accounted for at a much more detailed level (though I think that was more related to a guy selling engineering samples on eBay)
- New on-line format for PDFs of documents using "authentica" application that killed the ability to screen cap (a print screen had the Authentica logo sprayed all over the place where the document was)
- printed copies had non-obvious watermarking applied (in addition to the big red watermark across each page diagonally with your name on it) to catch OCR or scan and remove red layer attempts at copying.
That's fine with me.
The more cops wearing body cameras that stream to the cloud for storage (ending the missing SD card issue) the better!
There are tons of reports where adding body cameras has decreased both actual and claimed police abuses.
This is why I have *no* work contamination of my personal machines.
I only bring my phone to work, and I concede they can search the filesystem if they want (it's really no different than a USB drive afterall).
If they expected to search my home machine I'd refuse and lawyer up when they tried to discipline me for it.
On a related note:
Uber is handling this all sorts of wrong.
This happened while I was at Intel, an employee grabbed a stack of confidential and top secret Itanium docs and *while on sabbatical* got a job at AMD. When AMD found out he stole the IP (to help him get a leg up at his new employer) they called Intel, and the FBI; obviously sacking the guy as well.
There is a story (I don't know if true) about a guy getting the formula for Coke and offering to sell it to Pepsi. Pepsi called Coke and asked how they wanted to handle it. The decision was that Pepsi would offer to buy the formula. When the guy came in to sell it, the Pepsi exec accepted the envelope of docs, handed them to a waiting Coke lawyer, and nodded to the waiting FBI agent to arrest the guy.
In both these cases the company potentially receiving the secret sauce for a competitor made great efforts to inform said competitor and distance themselves from *any* question of impropriety. How is it that Uber saw no need for verifying poached employees brought nothing but what was in their heads with them from the competition?
+1 for the jumper!
It's NOT THAT HARD to add a jumper for the WE# signal.
*THIS*
I tried getting out from under one and was retaliated against and ultimately was terminated (with 17 years of good to outstanding reviews behind me) by a railroad job from said psychopathic asshat.
I disable WiFi at work. LTE only, and anything I want private (banking, FB, etc.) is done exclusively on my phone.
-nB