From an electrical engineering standpoint, that makes no sense. Thermal runaway starts when too much power is being drawn from the batteries and they begin to overheat until exploding or melting, their promixity to each other may limit the damage of an overloaded or malfunctioning cell, however the core problem remains, why are 787 electronic systems overloading the batteries?
If one cell explodes or melts, you still essentially have a fire in progress. Protecting the other cells buys you time, but how much time do you have when there is fire on a plane?
Obviously its a design issue, probably very complex that Boeing simply doesnt have the time and money to investigate thoroughly.
So this is a patch. Nothing I have read indicates an engineering approach was taken to prevent the previous result.
The worst invention since LISP is a serious contender for overdriving specious "features" of OO that noone needs or can even comprehend a use for, while remaining firmly grounded in C since you will need it because without C how could one possibly make such an abomination as C++?
Your not syncing anything your just overwriting it and making it available elsewhere, while versioning is supported in some free cloud environments, noone uses it, because they arent syncing they are just overwriting.
This is where iCloud runs into major trouble trying to do database syncing between various devices which go from being online to offline very quickly. No transactional support, messy messy stuff for consumers.
You are NOT syncing you are saving. Get it straight.
Secure boot sounds like a bunch of bullshit. Look if your OS lets a program infect the bootloader, it was your fault. If your buying systems that have been hijacked by your oppressive govt, well that sucks for you.
This is an obvious antitrust violation, MS (nor Intel) dictate the security practices of system BIOS loading.
Is it a bug or a feature? Its neither, once your MS Windows key has loaded and the BIOS boots it, your PC will still be just as infected as it was before.
This whole thing is bullshit. I call bullshit on secure boot. Its a BIOS lockout that probably disables other OSes from running, disables dual boot systems, I mean cmon.
This is why I use VMs and dont mess with the boot process, the BIOS mafia is a fucking joke.
Im not a lisper and I likely never will be, but I am encouraged to see the potential for Clojure to move away from the JVM. Its this simple really, I want a 100GB heap with no tuning. That will never happen on the JVM, Since Im not a lisper I dont know what the implications for memory management are, but having lived with JVM GC for over a decade Im done with it and hardware has surpassed JVM's ability to keep up. If it was still a 32 bit world I would have a different opinion. But Im not going to distribute tons of code to clusters just to avoid GC pauses, give me 100GB heap or give me death.
I dont do this anymore. Its too easy, and its dumb. If you want to make a point in a meeting, dont be positive or negative at all.
Instead, what I do if I feel its important enough, is to instead interject lightly and tell a story.
This story will be usually about 60-120 seconds longer than it needs to be and will be misunderstood by 80 percent of the attendees and the other 20 percent wont get it until a couple hours after the meeting.
This story will be allegorical, involve myself and potentially other actors in previous situations at another usually big company.
I will then (if necessary) paint a picture of a series of events which may or may not have unfolded as a result of making certain decisions that either led to massive success or tragic disaster.
By the time my story is over, everyone in the meeting room is spellbound, with the exception of the folks that realized I hijacked the meeting and usually the meeting ends.
None of it is personalized to anyone in the company, and I make sure its entertaining and not overly exaggerated (beating the dead horse).
No conclusions are drawn and no decisions are made.
Its that simple, tell a story, and as you walk out of the room forget the plot, because it matters not.
So let me get this straight, after all the years of talk (years ago) about how Java needed red-threads, we now want green threads again. Jesus you people are frustrating
As a java dev for 14 years, I just would please ask,
Can SOMEONE PLEASE KILL THE JVM? I dont care how many languages can generate bytecode to run on it.
I dont see how the terms of service really affect scraping when a scraper doesnt ever have to agree to them. You dont have to login or accept any TOS to read CL only to write. So what in effect he is saying is "my users gave me license to their data", therefore it is mine and not yours. Craig could protect "his data" in other ways, but he knows if he even so much as forced a login to the site, it would die overnight. That being the case, isnt this whole copyright compilation thing kind of weak? He wasnts to sue to have the courts protect him, because he refuses (in a technical fashion) to protect his data. So maybe the data is essentially worthless.
To take your idea even further, I was asked not to "reimplement" something by a new employer, but was flat out asked for the code I wrote in a previous job in the job interview. This is not a mom and pop but a huge corporation which shall remain nameless. As far as not using google, well Chrome and Search are ok with me, the rest of google's products are just data collection (about me) which I can do without.
My favorite recruiter line lately is "They interviewed (insert high number) so many candidates and they picked you!" - translation they couldnt find anyone because this is a really shitty job and your it. But let me lie to you to boost your ego enough that you'll take this horrible job.
If one cell explodes or melts, you still essentially have a fire in progress. Protecting the other cells buys you time, but how much time do you have when there is fire on a plane?
Obviously its a design issue, probably very complex that Boeing simply doesnt have the time and money to investigate thoroughly.
So this is a patch. Nothing I have read indicates an engineering approach was taken to prevent the previous result.