The screen is the biggest battery sapper in a phone. And now you've got two of them. And twice the breakable surfaces and a fragile hinge. And more component expense. And few apps (if any) which split nicely across the two displays. And a CPU burdened with running two foreground apps at once. And a compromised design that makes the bezel freakishly large at the top and bottom edges.
That "few million" you claim is a "drop in the ocean" would be a large part of the USGS budget, or any other government agency, and it is unlikely any agency would try to get it past the funding sources given the existence of COTS solutions already available.
It's still a tiny amount of money and the US has the likes of DARPA (budget 3 billion) for handing out grants for things like this. And defeatism is hardly the correct attitude when there is a clearly identifiable problem with an achievable, remedial solution.
The funding for USGS, USACE, etc, is not there to "make a community gravitate", it is to get a job done. "A few million dollars" is a very large expenditure, and it is just not going to happen.
Agencies provide funding for all kinds of projects. Don't be so defeatist. It is clearly in the USA's interest to not use software produced by an adversary and open source is the easiest, most cost effective way they can avoid doing that.
He locked himself up because he was too chickenshit to face rape charges in Sweden. In so doing he broke his UK court bail conditions and he'll be arrested on the spot when he steps out of the embassy or is shoved out.
It's sucks to be him but frankly he'll get everything he deserves by way of the judicial system.
And any other AV software. While it's doubtful Kaspersky or any other firm would bother spying on "low value" targets and the software behaves as intended it's still intrusive, destabilizing and slows down the system. And if Russia wanted to be malicious, e.g. shutdown computers in the runup to something, I'm sure the software's AV update mechanism would give them the means to do so.
Of course if I were in Russia I would have my doubts about running US software for the same reason. As a rule of thumb, don't trust code produced by your main adversary.
DJI drones are used by the military and other government departments for surveying etc. A few million is a drop in the ocean given that a fully auditible software / hardware and aftermarket solution pops out of the end. They don't even have to drop the million in funding. They could offer prizes or some other form of incentive for drones that can do certain things, or improvements to the user experience, e.g. the control software. The main purpose is to make the community gravitate away from proprietary to open source. The benefits fall out at the end.
Yes you can
I'm kind of surprised more of a market doesn't exist actually. Governments and military shouldn't be using closed source devices from Chinese companies. Seems like it would be in their interest to toss a few million into open source projects that let them develop drones which have the feature set and reliability they're interested in without worry of the devices "phoning home" or being bricked when they're most needed.
They developed a killer product and then sat on their asses doing little to progress it until the competition surpassed them. Not enough investment in R&D, not enough marketing, not enough product refinement.
So that means a big fuck you to everyone on Ultraviolet or other industry efforts. And who's to say the same won't happen in a few years time again?
And that's the thing. You don't own your movies. You own a licence to watch a movie that's only as good as the platform it was issued on. Don't expect to donate, sell or loan your movies. Don't expect your family to have access to them if you die. Don't expect to watch movies at all if some legal fubar means the rights expire or whatever. Don't expect to play movies on a platform and player of your choice. And absolutely don't expect your movies to be there if the platform flops.
I can clear up your confusion by pointing out that this race isn't trying to prove "real life usage". These vehicles are glorified bicycle frames covered by an aerodynamic shell of panels. It's a race. Even so, the change in the rules demonstrate that solar panels have become much more efficient than even a few years ago which does have a knock on impact for the real world.
Finland is hardly representative of much either. Even if Finland has crappy dark winters due to its latitude, it doesn't mean solar doesn't work in the summer months, or in other countries. A brief google suggests Finland's renewable policy is more focused on wind turbines, hydro and black liquor which apparently is a byproduct of the wood pulping industry that can be gasified.
I don't know how they rank results right now but I do know that it really sucks particularly for topics like news.
I assume they rank based on number of subscribers, thumbs up/down, keywords, related video clicks etc. and for the most part perhaps that's fine. But for news and notable events it is a terrible way to rank results. Search on "Sandy Hook" for example and look at all the nutbar results that appear close to the top.
I realise curating everything is unlikely but YouTube / Google can certainly weight channels as more trustworthy based on the veracity of their news reporting and their track record. It can also curate certain "hot topic" items and ensure that results are reflective of the facts rather than conspiracy brain damage.
It makes sense for an island to generate its own power from renewables. However those renewables have to be hurricane proof otherwise they'll be wrecked just like the conventional power plants when the next storm passes.
Solar panels seem especially vulnerable but everything would have to be robust and capable of being secured or removed to minimize damage until a hurricane passes.
I bet the compositing code in Firefox on Windows is a mess of #ifdefs and different backends to cope with different versions of DirectX and rendering APIs. Also the same for theming support. And video / audio support. Also the same for font / canvas rendering. And for UAC / permissions work. And anything to do with the installer.
That probably amounts to a lot of noise and different code paths that somebody has to maintain and impedes refactoring and modernisation. That's reason enough to consider dropping it.
I don't see how they can claim no queues when all the experience of public transportation suggests that at peak times there sure as hell will be queues at one point or another.
Complete absence of records before Christ? Oh dear oh dear.
The Rosetta stone, Armarna letters, THOUSANDS of hieroglyphic texts on tombs, inscriptions on monuments and steles. Plus written descriptions of ships, depictions of boats in paintings, model boats in funerary goods, actual boats like the Khufu boat. Even evidence of shipyards, canals and docks. Boats were important to the Egyptians for obvious reasons.
Aside from that, the stone quarries themselves all lie next to the Nile, again for obvious reasons - the blocks were transported by river. The Aswan quarry isn't even on the same side of the Nile as Giza. So even if they dragged those blocks 500 damned miles they'd still have to be ferried from one bank to the other. And at that point why not use the natural conveyor belt they happened to be next to in the first place? And besides ALL THAT. We even have the likes of Herodotus explaining how Egyptians moved large obelisks, which are far larger than standard blocks were transported by water.
So sorry there isn't much doubt about what Egyptians were capable of or what they obviously did.
It's hard to even fathom why you reference Archimedes except as some non sequitur. One doesn't need to know how boats float to know that they do float. Egyptians built lots of boats and had thousands of years of practical experience building them and navigating them on the Nile and around the Mediterranean / Red Sea. They figured a lot out through trial, error and practical experience.
There is archeological evidence of canals from quarries in Aswan that has been known about for years. And canals and docks near Giza that granite blocks arrived. In fact virtually every limestone, sandstone and granite quarry in Egypt was situated close to the Nile for obvious reasons. Also obvious would be their desire to minimize the effort required to transport blocks which would involve bringing water closer to the quarry via canals where practicable. If you had bothered to do even a brief search before hammering out your response you might even learn that.
So no "great mystery" has been solved here. Just some TV show hyping up some recent evidence that merely confirms and adds detail to what was already known.
This "great mystery" hasn't been such for a long time. Quarries carved rocks to make blocks, the blocks were moved onto barges and then the barges were sailed to places where they were required. Evidence for canals was established long before now. The only mystery is why anybody has such trouble understanding that ancient peoples weren't idiots.
Putting aside issues of bots, Russian interference, fake news etc., if Facebook is predominantly "anti-Trump" it is because the people who use the service are anti-Trump.
I'm sure it wouldn't be hard to find groups of Trump supporters within the service if someone were so inclined to look.
Dyson is the Apple of appliances - selling the same crap as everyone else but hyping it up on the basis of some dubious feature and selling it with a 2-3x markup.
Given that Dyson typically sells vacuum cleaners and hairdryers I'm not especially convinced they have the resources to produce any kind of electric vehicle unless it is powered by washing machine motors, a la the Sinclair C5. In which case, good luck with that.
Rust is beneficial in a number of ways for security. Strings, buffers, vectors etc are far more rigorously enforced and it's extremely hard to step outside them by accident without a resulting in a panic. That means normal forms of attack such as writing beyond the length of buffers are far harder to pull off.
In addition, allocation is declarative in Rust. Memory is either allocated or it isn't, in which case it panics. So code doesn't have to worry for testing for NULL or not. So no null/dangling pointers or memory leaks.
Thread safe code is also safer because the compiler enforces access. If two threads want to share a data structure they either have to implement a send / receive pipeline or they have to protect it with a read-write lock or a mutex.
Rust doesn't eliminate all potential issues, e.g. deadlocks / memory exhaustion, or fix logical bugs but it certainly eliminates the most exploitable errors where someone doesn't check the length of a string, or forgets to account for a terminating byte and so on. And typically when it fails it does so in a way that terminates the thread rather than allow an exploit to happen. So the devs can be far more aggressive at optimizing the code.
That's the payoff for the browser. Single threaded and gnarly code can be rewritten for concurrency without imposing significant risk to the browser.
Slashdot Mirror
And by "obvious trap" you mean a situation of his own making. He can rot in that embassy for all anybody cares.
What was the point again?
That "few million" you claim is a "drop in the ocean" would be a large part of the USGS budget, or any other government agency, and it is unlikely any agency would try to get it past the funding sources given the existence of COTS solutions already available.
It's still a tiny amount of money and the US has the likes of DARPA (budget 3 billion) for handing out grants for things like this. And defeatism is hardly the correct attitude when there is a clearly identifiable problem with an achievable, remedial solution.
The funding for USGS, USACE, etc, is not there to "make a community gravitate", it is to get a job done. "A few million dollars" is a very large expenditure, and it is just not going to happen.
Agencies provide funding for all kinds of projects. Don't be so defeatist. It is clearly in the USA's interest to not use software produced by an adversary and open source is the easiest, most cost effective way they can avoid doing that.
It's sucks to be him but frankly he'll get everything he deserves by way of the judicial system.
Of course if I were in Russia I would have my doubts about running US software for the same reason. As a rule of thumb, don't trust code produced by your main adversary.
DJI drones are used by the military and other government departments for surveying etc. A few million is a drop in the ocean given that a fully auditible software / hardware and aftermarket solution pops out of the end. They don't even have to drop the million in funding. They could offer prizes or some other form of incentive for drones that can do certain things, or improvements to the user experience, e.g. the control software. The main purpose is to make the community gravitate away from proprietary to open source. The benefits fall out at the end.
Yes you can I'm kind of surprised more of a market doesn't exist actually. Governments and military shouldn't be using closed source devices from Chinese companies. Seems like it would be in their interest to toss a few million into open source projects that let them develop drones which have the feature set and reliability they're interested in without worry of the devices "phoning home" or being bricked when they're most needed.
They developed a killer product and then sat on their asses doing little to progress it until the competition surpassed them. Not enough investment in R&D, not enough marketing, not enough product refinement.
And that's the thing. You don't own your movies. You own a licence to watch a movie that's only as good as the platform it was issued on. Don't expect to donate, sell or loan your movies. Don't expect your family to have access to them if you die. Don't expect to watch movies at all if some legal fubar means the rights expire or whatever. Don't expect to play movies on a platform and player of your choice. And absolutely don't expect your movies to be there if the platform flops.
So enjoy!
"I wrote the routines for PornHub for classifying enema and adult diaper changing porn."
Have you really had issues with systemd or even pulseaudio or network manager?
The answer is 99 out of 100 cases would be "no". And that one case that said "yes" probably has other mitigating reasons.
I think it would make more sense to embed solar panels in the access roads of car parks and above the parking spots themselves.
Finland is hardly representative of much either. Even if Finland has crappy dark winters due to its latitude, it doesn't mean solar doesn't work in the summer months, or in other countries. A brief google suggests Finland's renewable policy is more focused on wind turbines, hydro and black liquor which apparently is a byproduct of the wood pulping industry that can be gasified.
I assume they rank based on number of subscribers, thumbs up/down, keywords, related video clicks etc. and for the most part perhaps that's fine. But for news and notable events it is a terrible way to rank results. Search on "Sandy Hook" for example and look at all the nutbar results that appear close to the top.
I realise curating everything is unlikely but YouTube / Google can certainly weight channels as more trustworthy based on the veracity of their news reporting and their track record. It can also curate certain "hot topic" items and ensure that results are reflective of the facts rather than conspiracy brain damage.
Solar panels seem especially vulnerable but everything would have to be robust and capable of being secured or removed to minimize damage until a hurricane passes.
That probably amounts to a lot of noise and different code paths that somebody has to maintain and impedes refactoring and modernisation. That's reason enough to consider dropping it.
No, but somebody armed with a bomb could blow the shit out of everyone in a pod and potentially cause billions of dollars of economic damage.
I don't see how they can claim no queues when all the experience of public transportation suggests that at peak times there sure as hell will be queues at one point or another.
The Rosetta stone, Armarna letters, THOUSANDS of hieroglyphic texts on tombs, inscriptions on monuments and steles. Plus written descriptions of ships, depictions of boats in paintings, model boats in funerary goods, actual boats like the Khufu boat. Even evidence of shipyards, canals and docks. Boats were important to the Egyptians for obvious reasons.
Aside from that, the stone quarries themselves all lie next to the Nile, again for obvious reasons - the blocks were transported by river. The Aswan quarry isn't even on the same side of the Nile as Giza. So even if they dragged those blocks 500 damned miles they'd still have to be ferried from one bank to the other. And at that point why not use the natural conveyor belt they happened to be next to in the first place? And besides ALL THAT. We even have the likes of Herodotus explaining how Egyptians moved large obelisks, which are far larger than standard blocks were transported by water.
So sorry there isn't much doubt about what Egyptians were capable of or what they obviously did.
It's hard to even fathom why you reference Archimedes except as some non sequitur. One doesn't need to know how boats float to know that they do float. Egyptians built lots of boats and had thousands of years of practical experience building them and navigating them on the Nile and around the Mediterranean / Red Sea. They figured a lot out through trial, error and practical experience.
So no "great mystery" has been solved here. Just some TV show hyping up some recent evidence that merely confirms and adds detail to what was already known.
This "great mystery" hasn't been such for a long time. Quarries carved rocks to make blocks, the blocks were moved onto barges and then the barges were sailed to places where they were required. Evidence for canals was established long before now. The only mystery is why anybody has such trouble understanding that ancient peoples weren't idiots.
I'm sure it wouldn't be hard to find groups of Trump supporters within the service if someone were so inclined to look.
Given that Dyson typically sells vacuum cleaners and hairdryers I'm not especially convinced they have the resources to produce any kind of electric vehicle unless it is powered by washing machine motors, a la the Sinclair C5. In which case, good luck with that.
Anyone who has ever written highly concurrent code wouldn't find it funny.
In addition, allocation is declarative in Rust. Memory is either allocated or it isn't, in which case it panics. So code doesn't have to worry for testing for NULL or not. So no null/dangling pointers or memory leaks.
Thread safe code is also safer because the compiler enforces access. If two threads want to share a data structure they either have to implement a send / receive pipeline or they have to protect it with a read-write lock or a mutex.
Rust doesn't eliminate all potential issues, e.g. deadlocks / memory exhaustion, or fix logical bugs but it certainly eliminates the most exploitable errors where someone doesn't check the length of a string, or forgets to account for a terminating byte and so on. And typically when it fails it does so in a way that terminates the thread rather than allow an exploit to happen. So the devs can be far more aggressive at optimizing the code.
That's the payoff for the browser. Single threaded and gnarly code can be rewritten for concurrency without imposing significant risk to the browser.