It's more a move to counter LG - who are building TVs around the entrails of Palm's webOS. Both platforms are built around HTML5, so any 'apps' running on LG TVs might easily be ported to Panasonic's.
You might want to check Google Earth there, mate. WA's coastline is huge, stretching thousands of km.
It's not just city folk from the Perth region that sharks find tasty. The latest fatality, RIP, occurred 6 weeks ago off a coastal community of less than 400 people, in Gracetown, some 269km from the state capital. If it's not cost effective to put sonar on every beach along the coastline then the next small town attack would produce the outcry of "we should have used geotracking".
I'm not saying the current system is foolproof but the expanse of coastline may have made your solution unviable cost-wise.
Some of the blurbs sound interesting, with the accompanying videos but some of them don't offer enough detail without clicking enrol.
So enrolling is more akin to turning up to the first week's lecture. A more reliable metric would be to exclude those who, like me, unenrolled before completing an assessment - i.e. how many actually submitted a homework or two before "dropping out" or indeed went through to the end of the class without achieving a passing grade...
If the Surface Pro and Galaxy Note can steal thunder from iOS devices then Apple may be forced to react. But don't hold you breath; Jobs was no fan of the Newton.
There's a scope for both and shared knowledge can be beneficial.
Part of the automated build process can be running QA scripts via a robot. e.g. QA person files a bug report with steps to reproduce the issue. A VNC script is attached to the bug report, which is then translated to, say, a junit script. Programmer inserts asserts in the junit code to verify expected conditions. In this way regressions are fewer and don't escape to the QA people in the first place.
In the case of test inputs, we're largely talking unit tests here, which form part of the code base to verify the functional code is correct. The 'customer' shouldn't have such fine grained control over the development process.
(As distinct from a black box tester who never looks at the source code etc)
As far as not using xUnit/TDD, that's often a generational thing where development practices stem from the previous millenium before Kent Beck and others popularised its widespread adoption. I've worked on several projects where senior managers were resistent to adopting unit tests but at the same time had serious problems with unmaintainable code and regressions etc, with many hours wasted sitting in front of a debugger trying to work out the cause of a coding flaw.
A problem is, a fair % of programmers don't care for code maintenance and unit tests.
Documenting expected behaviour (e.g. javadoc) as to what exceptions will be thrown and writing unit tests to verify these trivial cases may seem pedantic to some.
Typical reponses above: (a) DB operations aren't CPU intensive (b) Servers don't come with dedicated graphics cards of any note (c) Loading each server with a AMD or Nvidia card would increase power usage
So in summary, certain operations may benefit using GPUs but there's not a cost-effective solution to warrant such experimentation.
I'd be surprised ARM if haven't sponsored cloud research into OpenCL on the Mali GPUs.
Meanwhile in Australia, we've had several of the hottest years on record this past decade and our weather service had to add a new colour to the heat map last summer.
Just because 'warming' isn't happening in your area with your eggnog, gluhwein and white Christmases doesn't mean climate isn't fluctuating globally.
Slashdot Mirror
Huh?
Mozilla has some catching up to do, FFOS 1.2 was only released a month ago.
Subterranean railway like they have in bike friendly cities like Montreal?
Because it's the law in civilised nations such as Australia and New Zealand.
You're nearly 2 centuries behind, dude. Joseph Smith discovered ancient golden plates back in 1823, in nearby new york state.
Only if you use Oracle's binaries. linux distros switched to openJDK years ago, whose source is available under the GPL.
Maybe it's just your spelling.
According to wikipedia at least.
Waiting for the next Indiana to thus discover a two thousand year old computer! Evidence of those time travellers we heard recently about on /.
It's more a move to counter LG - who are building TVs around the entrails of Palm's webOS. Both platforms are built around HTML5, so any 'apps' running on LG TVs might easily be ported to Panasonic's.
Which is why clojure is the lisp all the cool kids use.
You might want to check Google Earth there, mate. WA's coastline is huge, stretching thousands of km.
It's not just city folk from the Perth region that sharks find tasty. The latest fatality, RIP, occurred 6 weeks ago off a coastal community of less than 400 people, in Gracetown, some 269km from the state capital. If it's not cost effective to put sonar on every beach along the coastline then the next small town attack would produce the outcry of "we should have used geotracking".
I'm not saying the current system is foolproof but the expanse of coastline may have made your solution unviable cost-wise.
Some of the blurbs sound interesting, with the accompanying videos but some of them don't offer enough detail without clicking enrol.
So enrolling is more akin to turning up to the first week's lecture. A more reliable metric would be to exclude those who, like me, unenrolled before completing an assessment - i.e. how many actually submitted a homework or two before "dropping out" or indeed went through to the end of the class without achieving a passing grade...
If the Surface Pro and Galaxy Note can steal thunder from iOS devices then Apple may be forced to react. But don't hold you breath; Jobs was no fan of the Newton.
A comparison of San Francisco and Melbourne would be more apt - both 37 degrees adrift of the equator.
There's a scope for both and shared knowledge can be beneficial.
Part of the automated build process can be running QA scripts via a robot. e.g. QA person files a bug report with steps to reproduce the issue. A VNC script is attached to the bug report, which is then translated to, say, a junit script. Programmer inserts asserts in the junit code to verify expected conditions. In this way regressions are fewer and don't escape to the QA people in the first place.
In the case of test inputs, we're largely talking unit tests here, which form part of the code base to verify the functional code is correct. The 'customer' shouldn't have such fine grained control over the development process.
(As distinct from a black box tester who never looks at the source code etc)
As far as not using xUnit/TDD, that's often a generational thing where development practices stem from the previous millenium before Kent Beck and others popularised its widespread adoption. I've worked on several projects where senior managers were resistent to adopting unit tests but at the same time had serious problems with unmaintainable code and regressions etc, with many hours wasted sitting in front of a debugger trying to work out the cause of a coding flaw.
A problem is, a fair % of programmers don't care for code maintenance and unit tests.
Documenting expected behaviour (e.g. javadoc) as to what exceptions will be thrown and writing unit tests to verify these trivial cases may seem pedantic to some.
shame about the browser. if this thing came with a detachable touchscreen it'd be a great Firefox OS device!
It's spelled 'arse' :-)
yes, sorry. I only watched 1 episode.
So is it true a dead person's retina retains the image seen at the moment of death?
copyright has been a problem for a least 400 years since an unauthorised sequel to Cervantes.
70 years sounds about right but I do wish Hollywood would stop remaking films from 30 years ago and create some new material.
They attempted to resolve the orientation question for conservative US audiences by casting Lucy Liu as Holmes in Elementary.
They already ruined Star Trek for me by casting Sherlock in the role of Khan, who looks nothing like the previous Punjabi-Mexican...
Typical reponses above:
(a) DB operations aren't CPU intensive
(b) Servers don't come with dedicated graphics cards of any note
(c) Loading each server with a AMD or Nvidia card would increase power usage
So in summary, certain operations may benefit using GPUs but there's not a cost-effective solution to warrant such experimentation.
I'd be surprised ARM if haven't sponsored cloud research into OpenCL on the Mali GPUs.
Meanwhile in Australia, we've had several of the hottest years on record this past decade and our weather service had to add a new colour to the heat map last summer.
Just because 'warming' isn't happening in your area with your eggnog, gluhwein and white Christmases doesn't mean climate isn't fluctuating globally.