Is this where some dirty IT laundry is still yet to be hidden away, even from the grave?!


Apple's $1bn anti-competition trial might collapse

... The case is considering whether the hardware giant abused its dominant position in the digital music market.

The lawsuit covers iPods purchased between September 2006 and March 2009. During that period Apple used software that meant only music purchased from its iTunes store could be played on its devices...

... By 2007 Apple's software had got more sophisticated and restrictive.

In the trial it emerged that, between 2007 and 2009, if an iPod owner tried to sync their device with iTunes and had music from another digital store on the device, they would receive an error message telling them to restore their iPod to factory settings. This effectively wiped all non-iTunes music from the device...

... If the case continues it will hear video testimony from Steve Jobs, filmed shortly before his death...



IT is what we allow it to be...
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

I think that we can all agree that your

Such an "ism" means you must be an "ist."

Now as to licenses remember you rail against lawyers, but they are just shills for the fiduciary duty to the shareholder. So rail against the real problem.

---

Technology heading down a dangerous road?

Aircraft v Drones

"Investigators were unable to identify the drone, which did not appear on air traffic control radar and disappeared after the encounter."

"They are expected to be very popular as Christmas presents.
Only a very small minority of people operating drones have attended training courses in how to fly them.
A spokesman for the CAA said it had to depend on people using their common sense when they operated drones.
"People using unmanned aircraft need to think, use common sense and take responsibility for them", he said.
"There are rules which have the force of law and have to be followed.""

Force of law will be farcical should one bring down an aircraft!

Steve Wozniak reveals that 'the Apple Garage' was a myth.

http://www.theinquirer.net/inquirer/news/2385264/wozniak-reveals-the-apple-garage-was-a-myth

[edit] Apple pulls Safari update after a lot of users find that it actually removes the browser all together and reinstalling the OS is needed to bring it back. :-O

http://www.theinquirer.net/inquirer/news/2385351/apple-pulls-failing-safari-update-after-it-forces-users-to-reinstall-os-x

Cheers.

For those waiting for the new smart phones and tablets containing the new Snapdragon 810 SOC to come out, then you'll be waiting a bit longer due to a few problems, the main 1 being overheating.

http://www.dailytech.com/Qualcomms+Snapdragon+810+is+Reportedly+Delayed+by+Serious+Overheating+Woes/article36967.htm

Cheers.

Steve Wozniak reveals that 'the Apple Garage' was a myth.

http://www.theinquirer.net/inquirer/news/2385264/wozniak-reveals-the-apple-garage-was-a-myth

[edit] Apple pulls Safari update after a lot of users find that it actually removes the browser all together and reinstalling the OS is needed to bring it back. :-O

http://www.theinquirer.net/inquirer/news/2385351/apple-pulls-failing-safari-update-after-it-forces-users-to-reinstall-os-x

Cheers.

That's a bit of a let down. I'd be surprised if Wozniak wasn't required to sign a paper giving HP the rights to anything he designed while in their employ, especially since he did it using their facilities. I guess that is why the garage myth was started in the first place.

---

Bob DeWoody

My motto: Never do today what you can put off until tomorrow as it may not be required. This no longer applies in light of current events.

I've got to agree with Tim Berners-Lee here.

http://www.news.com.au/technology/online/tim-berners-lee-inventor-of-the-world-wide-web-hates-apps/story-fnjwmwrh-1227151905656

Cheers.

I've got to agree with Tim Berners-Lee here.
http://www.news.com.au/technology/online/tim-berners-lee-inventor-of-the-world-wide-web-hates-apps/story-fnjwmwrh-1227151905656
Cheers.

“Everything you can do an app you can do on a web page,” he said.
Maybe, but many applications are not suitable for web solutions.
For instance, a database administrator would go mad when updating several records in the database because of the low latency in web solutions.
As an analogy. If you want to converse with some other person you can use email.
But it's more easy to use the phone.

As an analogy. If you want to converse with some other person you can use email.
But it's more easy to use the phone.

That's all good & well if you have that person's direct contact number, otherwise it could be quicker to use e-mail...

"Thank you for calling. We now have 5 options for you...
Press 1 for...etc

Thank you, we now have 4 options for you...
Press 1 for...etc

Thank you, we now have 3 options for you...
Press 1 for...etc

Thank you, we now have 2 options for you...
Press 1 for...etc

Thank you, Sorry, the person you are trying to contact is unavailable at this time. Please try again later.
Goodbye"

I've got to agree with Tim Berners-Lee here.
http://www.news.com.au/technology/online/tim-berners-lee-inventor-of-the-world-wide-web-hates-apps/story-fnjwmwrh-1227151905656
Cheers.

“Everything you can do an app you can do on a web page,” he said.
Maybe, but many applications are not suitable for web solutions.
For instance, a database administrator would go mad when updating several records in the database because of the low latency in web solutions.

To be fair, he's talking about the distinction between an "app" and an application, with the former being anything lightweight and portable that can be run on the relatively limited power of a cell phone, whereas an application typically is any (somewhat more) advanced application requiring the power of a full PC.

I have not seen any "apps" that are a database, but I have seen apps that communicate with a web server that in turn communicates to a back-end database. Conversely, a web page could do the exact same thing as that app, just like Tim said. In fact, I've seen some pretty poorly written apps that are nothing more than web pages designed for a small screen.

So in your analogy, that database admin would simply enter their data in a website, which would in turn queue the entries and feed them to a database backend, masking any latency. And yes, you could do that function in an app as well, but that's precisely Tim's point.

I've got to agree with Tim Berners-Lee here.
http://www.news.com.au/technology/online/tim-berners-lee-inventor-of-the-world-wide-web-hates-apps/story-fnjwmwrh-1227151905656
Cheers.

“Everything you can do an app you can do on a web page,” he said.
Maybe, but many applications are not suitable for web solutions.
For instance, a database administrator would go mad when updating several records in the database because of the low latency in web solutions.

To be fair, he's talking about the distinction between an "app" and an application, with the former being anything lightweight and portable that can be run on the relatively limited power of a cell phone, whereas an application typically is any (somewhat more) advanced application requiring the power of a full PC.
I have not seen any "apps" that are a database, but I have seen apps that communicate with a web server that in turn communicates to a back-end database. Conversely, a web page could do the exact same thing as that app, just like Tim said. In fact, I've seen some pretty poorly written apps that are nothing more than web pages designed for a small screen.
So in your analogy, that database admin would simply enter their data in a website, which would in turn queue the entries and feed them to a database backend, masking any latency. And yes, you could do that function in an app as well, but that's precisely Tim's point.

Well. I'm a system developer and I think for many applications it cannot work.
Your idea about queuing transactions is bad.
That's the 70's way of doing it. Batch processing.

And there are no distinction between apps and applications!

I've got to agree with Tim Berners-Lee here.
http://www.news.com.au/technology/online/tim-berners-lee-inventor-of-the-world-wide-web-hates-apps/story-fnjwmwrh-1227151905656
Cheers.

“Everything you can do an app you can do on a web page,” he said.
Maybe, but many applications are not suitable for web solutions.
For instance, a database administrator would go mad when updating several records in the database because of the low latency in web solutions.

To be fair, he's talking about the distinction between an "app" and an application, with the former being anything lightweight and portable that can be run on the relatively limited power of a cell phone, whereas an application typically is any (somewhat more) advanced application requiring the power of a full PC.
I have not seen any "apps" that are a database, but I have seen apps that communicate with a web server that in turn communicates to a back-end database. Conversely, a web page could do the exact same thing as that app, just like Tim said. In fact, I've seen some pretty poorly written apps that are nothing more than web pages designed for a small screen.
So in your analogy, that database admin would simply enter their data in a website, which would in turn queue the entries and feed them to a database backend, masking any latency. And yes, you could do that function in an app as well, but that's precisely Tim's point.

Well. I'm a system developer and I think for many applications it cannot work.
Your idea about queuing transactions is bad.
That's the 70's way of doing it. Batch processing.

You're missing the point entirely. When he said "anything you can do in an app you can do on a web page" - he wasn't talking about databases because they're not apps - they're applications. So in essence, you're agreeing with Tim and at the same time not even offering a counter argument against him.

Remember, app != application. Database != app. Database == application.

Well. I'm a system developer and I think for many applications it cannot work.
Your idea about queuing transactions is bad.
That's the 70's way of doing it. Batch processing.

Some applications require the DB be in a consistent state, some allow for a fuzzy state. Take for instance a DB with bank balances. Fuzzy?

---

Remember, app != application. Database != app. Database == application.

Nonsense!
app == application. Database != app. Database != application.

As to app vs browser ...

Frequently the app is just a url and a special display that general HTML doesn't do a pretty job of rendering. Or it may be a real database such as a contact list that never leaves the phone.

I understand his point, but I don't think it is universal.

His other point about allowing all to make changes, well, social media perhaps, but I don't think he wants others to be able to change his bank balance in his bank app. There are authorized users in the world still.

---

Well. I'm a system developer and I think for many applications it cannot work.
Your idea about queuing transactions is bad.
That's the 70's way of doing it. Batch processing.

Some applications require the DB be in a consistent state, some allow for a fuzzy state. Take for instance a DB with bank balances. Fuzzy?

Fuzzy:) Hope not.
My bank when doing transactions take hours to be confirmed.

Remember, app != application. Database != app. Database == application.

Nonsense!
app == application. Database != app. Database != application.

??? What you just wrote is "an app is an application. A database is not an app. A database is not an application". It would seem your education is outdated here, which would explain why you're confusing what I'm talking about with 70's era understanding.

An app, in modern terms, is any application you can run on your cell phone. Most apps that retrieve data, do so by contacting a web server, which in turn retrieves the information from a transactional database. This is different than batch processing as you remember it.

An application is the traditional piece of software you run on a computer. My World of Warcraft game is one such example. It is an application, it is not an app.

A database is another such application. It is not an app; most are not designed to run on cell phones.

Tim Berners-Lee is saying that any "app" that runs on a cell phone (which traditionally isn't a database) can also be done in a website - and in his opinion should be done in a web-based interface.

Again, he is not saying that all applications should be run in a website (though many can now thanks to SaaS). He is specifically referring to apps only.

Remember, app != application. Database != app. Database == application.

Nonsense!
app == application. Database != app. Database != application.

??? What you just wrote is "an app is an application. A database is not an app. A database is not an application". It would seem your education is outdated here, which would explain why you're confusing what I'm talking about with 70's era understanding.
An app, in modern terms, is any application you can run on your cell phone. Most apps that retrieve data, do so by contacting a web server, which in turn retrieves the information from a transactional database. This is different than batch processing as you remember it.
An application is the traditional piece of software you run on a computer. My World of Warcraft game is one such example. It is an application, it is not an app.
A database is another such application. It is not an app; most are not designed to run on cell phones.
Tim Berners-Lee is saying that any "app" that runs on a cell phone (which traditionally isn't a database) can also be done in a website - and in his opinion should be done in a web-based interface.
Again, he is not saying that all applications should be run in a website (though many can now thanks to SaaS). He is specifically referring to apps only.

For heavens sake.
I have done both apps and applications for years.
There is NO difference between them.
And calling a database for an application is simply ridicolous.
Yes you can create triggers in a database handler for many things.
The end user still have to suffer time latency.
Not because of the database handler but to the web protocol.

Remember, app != application. Database != app. Database == application.

Nonsense!
app == application. Database != app. Database != application.

??? What you just wrote is "an app is an application. A database is not an app. A database is not an application". It would seem your education is outdated here, which would explain why you're confusing what I'm talking about with 70's era understanding.
An app, in modern terms, is any application you can run on your cell phone. Most apps that retrieve data, do so by contacting a web server, which in turn retrieves the information from a transactional database. This is different than batch processing as you remember it.
An application is the traditional piece of software you run on a computer. My World of Warcraft game is one such example. It is an application, it is not an app.
A database is another such application. It is not an app; most are not designed to run on cell phones.
Tim Berners-Lee is saying that any "app" that runs on a cell phone (which traditionally isn't a database) can also be done in a website - and in his opinion should be done in a web-based interface.
Again, he is not saying that all applications should be run in a website (though many can now thanks to SaaS). He is specifically referring to apps only.

For heavens sake.
I have done both apps and applications for years.
There is NO difference between them.
And calling a database for an application is simply ridicolous.
Yes you can create triggers in a database handler for many things.
The end user still have to suffer time latency.
Not because of the database handler but to the web protocol.

There is a difference contextually. When someone is talking about an app, such as their flashlight app or their Youtube app, they are talking about something different than an application, and most people would not make a mistake about that.

Yes, an app is an application. The term app is short for application. But in the context of discussion they are referring to two different things. Tim was specifically referring to mobile "apps" in the context of his discussion - not applications such as databases.