Link to Original Source
Slashdot videos: Now with more Slashdot!
Link to Original Source
Nobody will abuse a time off policy where there are no vacation days and time is taken as needed. If it is abused it can be addressed by the performance review process.
I always understood how that will stop employees from abusing the "as needed" vacation policy.
I never understood what will stop the employer from abusing it. Until now.
You are very correct re. the difference between a RT operating system and not RT. That has nothing to do with Sync specifically or infotainment in general.
Sync does not have any control over engine management, traction control or any other safety critical system (and neither does any other infotainment system). Not sure about Sync, but typically you cannot even update safety critical systems from the infotainment system. An infotainment system may have read-only access to report "interesting" data, but that's all.
There is no need for your infotainment system beyond responding to the UI and performing the tasks you need, just like your phone, etc.
The individual officer(s) involved cannot be immune from civil lawsuits!
The individual officer(s) involved cannot be immune from criminal prosecution!
In addition to facing EXACTLY the same criminal charges that any other individual who performed the same actions would face, the officer(s) should be individually subject to a civil suit just like any other individual. Once a few officers have been bankrupted and are facing garnished wages and liens to settle court judgments then they will suddenly find a way to avoid taking the offensive and illegal actions.
And should those in charge persist, they will find their tacit acceptance and hints (never orders, because that would be wrong) are falling on deaf ears.
How do you "sign your name" is the same thing my "luddite" teacher in 9th grade asked when I was the first person in the school to turn in a paper from a word processor. I "printed" my signature and he didn't like it, but he didn't have to.
He, and now you, are the only ones to ever care.
So who is the luddite? Have you ever used a word processor?
Cursive was invented to optimize writing with a quill. A quill is fragile, so you want to put it down carefully. Even then, it tends to blob at the beginning of a stroke. Cursive minimizes lift up and put down and the number of separate strokes.
I spent a lot of time coding a good checkout solution that worked with Google Checkout, so I was pretty mad when all the work I did went down the drain when they discontinued it. I was fortunate to had already integrated Paypal and Amazon checkout before it was discontinued, so the business impact was pretty small.
But it did teach me to be 10 times more careful when investing time to integrate with a third party platform.
But this also shows an interesting trend away from APIs and "Mashups." 5 to 10 years ago, providing an API for your startup was considered an essential way to promote your platform by having it integrated all over the place. I suspect too many developers got burned in the way that I was with Google Checkout, and stopped trying to "mashup" APIs to the point where there was no longer much benefit to provide them.
Definitely a system-wide approach VS a semi-random collection of various ways to do things all tacked together (which is, frankly, what most Unix and Unixlike systems are, through survival of the fittest).
And you assume that nothing like systemd has ever been tried during that survival contest?
The systemd approach has always failed to survived. Multiple times.
Through "survival of the fittest' that collection has proven to be the fittest. It is just painful that we have to try a failed approach, again.
Henry Spencer: Those who don't understand Unix are doomed to reimplement it, poorly.
Somebody mentioned a pelican case. That (or similar eg NEMA 4 or 4x) is a good start. But if you cannot get the heat out of the case it doesn't take much power to cook a PC even at -5C exterior temperature and at 30C it takes very little added power.
It sounds like you are talking hundreds of watts. So you need to make it entirely liquid cooled. This means everything that would normally have a fan -- processor, video card, chipset, and power supply. In addition you will likely need a fan in the enclosure to prevent hot spots, and if that isn't enough you'll need to liquid cool those hot spots.
At this point you should be thinking about submerging all the electronics in an oil tank and circulating the oil thru the radiator as your coolant. (Use light mineral oil, because it will get thick at -5C and you may have to heat it so it will flow thru the lines!) Mineral oil submersion will also protect the electronics against condensation.
The radiator will need to be outside the pelican case. It will most likely need a fan at 30C, so you should use an automotive or similar fan with a proper temperature rating range. Also mount the coolant reservoir externally so you can check the level and fill without opening the enclosure.
If not mineral oil, the cooling system will need to be filled with something to provide freeze protection below your lowest low temperature. (Antifreeze, various alcohols, sugar water, etc.)
The pump will likely need to be controlled to run very slowly when temperatures are cold. But -5C should be okay for everything except perhaps fans and mechanical hard disk (so use SSD). For a less power hungry PC or colder temperatures you might need to insulate the case. If the PC must start when cold -5C is probably okay but you may need to provide auxiliary heating to warm it up to maybe 10C before powering the PC (almost certainly required if using mineral oil or at temperatures colder than -40C, but perhaps at -10C or even at -5C depending on your equipment). You can heat the air in the enclosure but heating the liquid in the cooling system is more efficient if it will thermosiphon within the enclosure. You don't want to pump coolant thru the radiator while trying to heat it.
Mount the equipment without penetrating the case. Keep all electric stuff up as high as possible off the bottom of the case. Condensation or leaks will puddle at the bottom and you want to keep the gear out of that puddle.
Make the cooling, power and connectivity lines come out the bottom of the case (to prevent puddles from slowly seeping in) thru liquid-tite cable glands (to keep out bugs and lightly pressured water). A drop tube around the exit (or each exit) will help protect against high pressure water jets except for a direct stream into the end of the tube. You might also like a valve in the bottom of the case. You can open the valve and if liquid runs out you need to take down and service the system. Do not make any other case penetrations.
I find it amusing how people continuously claim to "know" what is and isn't possible based on our infinitesimally short stint into the sciences.
When I see articles like this, and especially with a "[likely] always will be" clincher I like to imagine how the exact same tone could be (and often was) applied prior to previous breakthru advances. Such as traveling several times faster than a horse could run. (Breathing would be impossible at such speeds!) Such as heavier than air flight. (A bird can fly because its body is optimized for flight but no matter what heavier substance you add to the body of a man it only makes him heavier and thus less able to fly.) Such as supersonic flight. (The "sound barrier" isn't called that for nothing!) and etcetera.
Until we really are omniscient any claim which depends on "we didn't know then but now we know" just shows the laughable hubris of the claimant.
The PowerPC line, They were doing good until the Gigahertz range was common in Intel, Power PC was still in MHZ. Intel started to make much faster chips and PowerPC couldn't get caught up.
of course PowerPC was RISC and Intel CPUs were CISC.
Yet that makes what happened even more strange. A long touted advantage of RISC was that because of its simplicity it could be clocked so much faster than CISC that doing less per instruction would still be faster net throughput. Yet what happened was that CISC (in the hands of Intel) could and did do and even outdo all the optimizations of RISC, including clock speed.
Now ARM has been making hay with a new RISC advantage, power efficiency. We'll see...
Then as you monitor the automation you improve the scripts and your active involvement lessens over time, leaving more time for other things.
Maybe automate other parts of your job?
Self-improvement (training, education, experimentation, etc)?
Being available to consult or assist others, improving your "team player" metric?
Sell your ideas for automation, demonstrate the prototype (before it is perfected, of course)?
Entertainment? (Anything so long as it doesn't get you fired, which in a good company should be primarily based on job performance which is already covered, right?)
Just do it already...
Never said all exchanges. Nice of you to put words in my mouth to build a strawman and shoot it down.
Some exchanges were. Maybe some still are.
Fractional-reserve banking is the practice whereby a bank holds reserves (to satisfy demands for withdrawals) that are less than the amount of its customers' deposits.
from wikipedia seems like a good definition for fractional reserve banking.
A bank is a financial intermediary that accepts deposits and channels those deposits into lending activities...
ibid seems fine also.
And those definitely meet what has happened in the world of BTC exchanges. Were they officially lending? Probably not. But as soon as they start dipping into "deposits" and later reimbursing those deposits, somebody is making money by borrowing the "excess" reserves.
Financial institution? Check.
People deposit financial assets? Check.
Fractional reserves? Check.
Lending of those assets? Check.
Sure sounds like it meets at least one public definition of fractional reserve banking.