Article says "These companies are making a choice. They're deciding that it's faster and cheaper to chuck people overboard and find new ones than it is to retrain them."... but i don't see where the companies are re-hiring instead of re-training? They cite HP and say they're still letting people go, not hiring.
Gotta back these claims up with numbers, or it's all BS.
Meanwhile, hiring managers feel the pressure to fill openings instantly with exactly the right person, and when they can't, the team and the company suffer.
The team and company suffer if you hire "because we need someone" and end up with the wrong person. It sucks as an applicant, no denying it, but a bad hire can be toxic to a team or project. They can end up making more work for everyone else.
Complaints about buzzword filtering and what not might be very true, but you have to understand that the hiring manager must never hire just because they need someone.
It's good to see, and a pleasure to read, rational discourse on patents who knows what the fuck they're talking about. Almost every single article about patents is so for wrong, calling it a straw-man argument is a joke. Let's have more articles like this on/., please.
Why does it have to be someone else's fault? Why's it Mac OS X's fault? Or Microsoft's monopoly? Or even ABI compatibility? Where's the analysis of whether the bulk of average-joe users actually like using Linux desktops?
Seriously, it's the first explanation that needs to be looked it. Yes, many of people love their Linux desktops, and they're very vocal here on slashdot. But is there any Linux desktop that is there today, or has been, that could be loved by the masses?
I switched from Linux desktops about years ago and there's nothing about it I miss.
"Just the simple task of separating two kinds of files from a single directory, 'mkdir GIF;mkdir JPG;mv *.gif./GIF;mv *.jpg./JPG' and I'm done -- five seconds to accomplish that. How long would it take in a pretty looking GUI?"
Create two directories; sort by file type; drag & drop * 2... done. And it'll deal with mixed case extensions. Don't get me started about Mr. "You can't do that FTP transfer in less than 8 mouse clicks". vs 32 keystrokes. I'm not sure where his maths comes from.
They also don't go into how far you are away from destroying the world with a CLI:
sudo rm -Rf ~/bin
is one keystroke from
sudo rm -Rf ~/bin
Or just the simple case of "cp a b c/", only you eagerly hit enter before "c/" so you blow away b with no checks.
And who knows what you get when your super awesome smart shell loop isn't escaped properly on a filename with a space, quotes or apostrophe in the name.
GUI or CLI -- do whatever you like -- but don't base your choice on the "quality" of information from the types of people in this article.
In Australia getting to the polls on voting day is mandatory. You're fined otherwise. This really gets people to vote. Digital only leads to vulnerabilities.
It's one-off fee for a commercial company. Get over it.
The real story here, though, is that they're actually taking a real stab at doing signing right and requiring a chain of trust. They're also doing it in a very cooperative open source way.
This is an excellent step for the assurances of trusted computing for their users!
If the little guy sues he's liable for triple damages? Which is probably a drop in the ocean for the big guy? This is meant to improve the situation how?
Lol... "Somalia's worse, ergo, nothing needs fixing". That's some great logic there, Lou.
In response to GP, though... it's clear the TSA's busted. What other good-for-nothing orgs are there? I'm generally of the opinion some have some actual value:)
Your fixed version isn't. The victim didn't have a gun. Or a knife. Or a brick. Lethal force was not clearly necessary, and using it means you should be on trial for murder to determine if that's the case.
An unarmed kid is dead because someone with a gun pursued and shot him. The ethnicity of the two parties is irrelevant. The shooter should be on trial for murder.
I use python a lot to process large string logs (hudreds of megs or a couple of gigs). The problem is it's all super quick until the working set in the garbage collector gets too big and you fall off a performance cliff. I dunno what they're doing in there, but you easily go from a minute or two run time to half an hour to an hour because of the paging.
I'm not familiar enough with other garbage collected languages and such workloads to know if this is inherent or just a problem with the Python GC. Either way, I think it's fair to say that Python is too slow under such circumstances. I'd like to see it fixed, though, rather than abandon it:)
Some developers are very happy to have their work included in something and used widely. BSD makes companies include an acknowledgement of the use of your work, so you can know you made that project happen. Presumably, if a lot of money is being made by some company that includes your free software, you've helped build something cool that people want. I think a lot of developers see GPL as a "taking my toys and going home" license which discourages free use. If you weren't going to make a million dollar idea with your software, why stop someone else?
Do you get the cash? No. Are your motives really that good if you opened your software only to make money? No. Does a commercial venture using your code prevent free projects from springing up around your work and building the same things as you could if you'd GPL'd it? No.
Slashdot Mirror
Why isn't everyone entitled to a brain of the same size, if it's feasible?
If you're going to drop the Intel ME, Intel could still put something together in the CPU microcode patches. Or, you know, just in the silicon itself.
This product is a sham. "Only free software -- until it's not".
Article says "These companies are making a choice. They're deciding that it's faster and cheaper to chuck people overboard and find new ones than it is to retrain them." ... but i don't see where the companies are re-hiring instead of re-training? They cite HP and say they're still letting people go, not hiring.
Gotta back these claims up with numbers, or it's all BS.
Apple already does report base-10 capacities:
http://support.apple.com/en-us...
Well, kinda? sorta? sometimes? tl;dr for me.
Meanwhile, hiring managers feel the pressure to fill openings instantly with exactly the right person, and when they can't, the team and the company suffer.
The team and company suffer if you hire "because we need someone" and end up with the wrong person. It sucks as an applicant, no denying it, but a bad hire can be toxic to a team or project. They can end up making more work for everyone else.
Complaints about buzzword filtering and what not might be very true, but you have to understand that the hiring manager must never hire just because they need someone.
If only more officials had played the game so they could learn about the risks and prevent them.
Scientists work in formulas. Fortran was designed to do things naturally that don't fit into C/C++, Python, whatever.
Keep floggin' that dead Larrabee horse, Intel.
... then you could buy a 2.6oz battery case?
It's good to see, and a pleasure to read, rational discourse on patents who knows what the fuck they're talking about. Almost every single article about patents is so for wrong, calling it a straw-man argument is a joke. Let's have more articles like this on /., please.
Why does it have to be someone else's fault? Why's it Mac OS X's fault? Or Microsoft's monopoly? Or even ABI compatibility? Where's the analysis of whether the bulk of average-joe users actually like using Linux desktops?
Seriously, it's the first explanation that needs to be looked it. Yes, many of people love their Linux desktops, and they're very vocal here on slashdot. But is there any Linux desktop that is there today, or has been, that could be loved by the masses?
I switched from Linux desktops about years ago and there's nothing about it I miss.
... until a misinformation document gets rolled up into a report to higher ups and the president and policy is set or action is taken based on it.
ie. what could possibly go wrong?
"Just the simple task of separating two kinds of files from a single directory, 'mkdir GIF;mkdir JPG;mv *.gif ./GIF;mv *.jpg ./JPG' and I'm done -- five seconds to accomplish that. How long would it take in a pretty looking GUI?"
Create two directories; sort by file type; drag & drop * 2... done. And it'll deal with mixed case extensions. Don't get me started about Mr. "You can't do that FTP transfer in less than 8 mouse clicks". vs 32 keystrokes. I'm not sure where his maths comes from.
They also don't go into how far you are away from destroying the world with a CLI:
sudo rm -Rf ~/bin
is one keystroke from
sudo rm -Rf ~ /bin
Or just the simple case of "cp a b c/", only you eagerly hit enter before "c/" so you blow away b with no checks.
And who knows what you get when your super awesome smart shell loop isn't escaped properly on a filename with a space, quotes or apostrophe in the name.
GUI or CLI -- do whatever you like -- but don't base your choice on the "quality" of information from the types of people in this article.
In Australia getting to the polls on voting day is mandatory. You're fined otherwise. This really gets people to vote. Digital only leads to vulnerabilities.
Your security concerns are legitimate, which is why you should get a chipset with VT-D support.
Have you actually read the article?
Yes
Not only does it require everything from boot loader to kernel to drivers have to be signed,
That's the whole point of trusted computing. It's an excellent thing.
but Microsoft can revoke permission at any time.
Revocation is critical to security.
It's one-off fee for a commercial company. Get over it.
The real story here, though, is that they're actually taking a real stab at doing signing right and requiring a chain of trust. They're also doing it in a very cooperative open source way.
This is an excellent step for the assurances of trusted computing for their users!
If the little guy sues he's liable for triple damages? Which is probably a drop in the ocean for the big guy? This is meant to improve the situation how?
Lol... "Somalia's worse, ergo, nothing needs fixing". That's some great logic there, Lou.
In response to GP, though... it's clear the TSA's busted. What other good-for-nothing orgs are there? I'm generally of the opinion some have some actual value :)
So it's perfectly acceptable for any physical confrontation to end up with a dead body, no questions asked?
It doesn't matter who started the confrontation, only one person in it had the ability to make it a deadly one.
Your fixed version isn't. The victim didn't have a gun. Or a knife. Or a brick. Lethal force was not clearly necessary, and using it means you should be on trial for murder to determine if that's the case.
You don't even need to replace it. It's already vastly more efficient.
An unarmed kid is dead because someone with a gun pursued and shot him. The ethnicity of the two parties is irrelevant. The shooter should be on trial for murder.
I use python a lot to process large string logs (hudreds of megs or a couple of gigs). The problem is it's all super quick until the working set in the garbage collector gets too big and you fall off a performance cliff. I dunno what they're doing in there, but you easily go from a minute or two run time to half an hour to an hour because of the paging.
I'm not familiar enough with other garbage collected languages and such workloads to know if this is inherent or just a problem with the Python GC. Either way, I think it's fair to say that Python is too slow under such circumstances. I'd like to see it fixed, though, rather than abandon it :)
Some developers are very happy to have their work included in something and used widely. BSD makes companies include an acknowledgement of the use of your work, so you can know you made that project happen. Presumably, if a lot of money is being made by some company that includes your free software, you've helped build something cool that people want. I think a lot of developers see GPL as a "taking my toys and going home" license which discourages free use. If you weren't going to make a million dollar idea with your software, why stop someone else?
Do you get the cash? No. Are your motives really that good if you opened your software only to make money? No. Does a commercial venture using your code prevent free projects from springing up around your work and building the same things as you could if you'd GPL'd it? No.