Companies don't hire people because they're making a profit. They hire people when, despite the threats & floggings, the existing workforce can't do the work needed.
That's the same thing as paying for the extension, except instead of paying for it directly, you're paying for it indirectly via a higher electric bill.
I'm running it on my machine at the office.
What? If the company made bigger profits it would pay me more?
You mean separating the "internal" gibletty stuff from the "external" pretty stuff? What next, splitting the "external" stuff into "inny things" and "outy things"? And then deciding that the last two are sort-of-nearly-almost the same and sticking them partially back together?
You're absolutely barmy. No way could that catch on.
This just in: the next release of Firefox will have an extension that contains an embedded JavaScript library in the extension's code that mines for the Monero cryptocurrency using users' computers and without getting their consent.
I almost put "nearly" in italics. Probably should have done.
Incompatibility per se[1] isn't the issue. It's this #smegma or whatever it is that doesn't work for the *minority* of code. In what way does it not work? Compiler warning[1]? Compiler error? Just do random shit?
Slashdot Mirror
Companies don't hire people because they're making a profit. They hire people when, despite the threats & floggings, the existing workforce can't do the work needed.
I'm running it on my machine at the office.
What? If the company made bigger profits it would pay me more?
Of course they would!
You mean separating the "internal" gibletty stuff from the "external" pretty stuff? What next, splitting the "external" stuff into "inny things" and "outy things"? And then deciding that the last two are sort-of-nearly-almost the same and sticking them partially back together?
You're absolutely barmy. No way could that catch on.
This just in: the next release of Firefox will have an extension that contains an embedded JavaScript library in the extension's code that mines for the Monero cryptocurrency using users' computers and without getting their consent.
I almost put "nearly" in italics. Probably should have done.
Incompatibility per se[1] isn't the issue. It's this #smegma or whatever it is that doesn't work for the *minority* of code. In what way does it not work? Compiler warning[1]? Compiler error? Just do random shit?
[1] Who takes notice of those?
Comprehend Python? I can't even see it!
Yeah, I'd totally take financial advice from you.
Don't you just love things that nearly always work?
One. After that the hardware will break anyway.
That's absolute fucking rubbish.
All slashdotters have a maid. She lives right upstairs!
Source? Other than yourass.com or thinair.org
I guess that explains it.
Not that for each speak? WTF is that supposed to mean?
This is a Java thread, don't go bringing Python into it.
You using for cleaning your fingernails. No shame in that, sweetie.
They might not now, where you are.
They did when - and where - I went to school. And it wasn't the only dangerous thing. We were taught evolution too.
No, you'll have 100% water.
I thought that was Werner von Braun?
Hang on, he parabolised them. My bad. As you were.
The key word was "fresh".
Why?
That's pretty common round here.
Good thing too - you're unlikely to catch anything that way.
Strip off the i and they won't be complex any more. Do I have to do all the thinking round here?
If a garage even displays a BMW logo they'll get hammered for trademark infringement unless they're actually a BMW approved dealer.
So yes, they can do it. Once.
... but we don't want the Irish.
Whatever the level is, almost half of American voters have it, with slightly more than half in certain key states.