I went back and found every Android phone shipped in the United States up through the middle of last year. I then tracked down every update that was released for each device - be it a major OS upgrade or a minor support patch - as well as prices and release & discontinuation dates. I compared these dates & versions to the currently shipping version of Android at the time. The resulting picture isn’t pretty - well, not for Android users.My iPhone 3G stopped being updated only a few months ago, and is now 1 major version behind. In fact, iPhones are the only devices I've ever owned that has had regular long term updates, even across major versions, for free.
Asgeir S. Nilsen tenker litt
Ymse tanker om dette og hint. Mye om Open Source, noe politikk og annet jeg er opptatt av. Follow the english label for blog posts in English.
2011-10-29
Android Orphans: Visualizing a Sad History of Support
Michael Degusta tells a sad story in Android Orphans: Visualizing a Sad History of Support:
2011-09-22
A Lock Free Concurrent Circular Buffer With Multiple Independent Readers
I wrote about a Lock Free Concurrent Circular Buffer about a year ago. This has now been updated to support multiple independent readers, so many consumers can get updates to this circular buffer.
It is still lock free, so the readers won't block. If you try to take() on a buffer with no updates a null is returned, and if you drain() a buffer with no updates you get an empty list.
The code is now on GitHub, so I recommend you give it a spin if you want a (simple) circular buffer. It does detect buffer wraparounds, but will in this case reset the reader to the end of the buffer, losing any intermediate updates. Tune your buffer size accordingly.
Take a look at the unit tests to get an idea on how to use this buffer.
It is still lock free, so the readers won't block. If you try to take() on a buffer with no updates a null is returned, and if you drain() a buffer with no updates you get an empty list.
The code is now on GitHub, so I recommend you give it a spin if you want a (simple) circular buffer. It does detect buffer wraparounds, but will in this case reset the reader to the end of the buffer, losing any intermediate updates. Tune your buffer size accordingly.
Take a look at the unit tests to get an idea on how to use this buffer.
| Reaksjoner: |
2011-09-08
Blogger has an official app for iPhone
This blog post serves as proof that it works.
Seems to do okay, but does not have rich text.
Also the labels do not auto complete.
Seems to do okay, but does not have rich text.
Also the labels do not auto complete.
2011-09-06
So it finally happened...
From "Who do you trust to tell you who to trust?":
The big security news of the past few days is the story of the compromise of the DigiNotar Certificate Authority and the subsequent issuing of fraudulent SSL certificates, leading to actual Man in the Middle attacks against Gmail users in Iran.and:
When the whole trust structure for SSL was devised, there were many people who worried that it gave too much power to certification authorities. In this instance we had one that suffered a security breach, but imagine if there were a corrupt one. With hundreds of trusted certification authorities, each with the power to issue certificates for any domain, the scope for abuse is substantial. I was one of those worriers.
It is easy to say that I don’t like the system, it is much much harder to present an alternative that works better and doesn’t burden users with the task of performing their own audits of certificates or authorities. There are a number of proposals out there, and discussion of them has certainly kicked off again over the past few days. My post here has already been long enough, so I will redirect readers to a post by Mike Caldwell who proposes an idea I haven’t seen before (as well as linking to other proposals).Well, I told you so. Basically the use of TLS to ensure trusted domain names is not trustworthy. In my opinion this problem should be solved by the Domain Naming System, not by Transport Layer Security.
2010-09-17
How to fix a NETGEAR WN802Tv2 after firmware upgrade
For me, updating to the latest 3.1.3 firmware for the NETGEAR WN802Tv2 access point had an unfortunate side effect: the access point refused to accept any password for logging in…
Resetting to factory defaults did not work. There are a few threads on the NETGEAR forums about this as well, but the only resolution seemed to be to send the unit to NETGEAR.
However – after two days of hacking I have found a do-it-yourself solution:
1. Make sure you can connect to the web interface safely
This means resetting to factory defaults, use a cable directly between your computer and the access point, and set a static IP address for your computer in the 192.168.0.x range. NETGEAR supports recommends using the address 192.168.0.210 for reasons that I don’t know..
2. Go to the address http://192.168.0.233/recreate.php
The real purpose of this file is not known, but it has an interesting side effect: When you go to the access point home page afterwards, you get access to a partly functional interface. A lot of things don’t work, but one important piece did work for me: the firmware upgrade
3. Upload the 3.1.1 firmware image
If you don’t have the firmware image here you can get it from NETGEAR support at http://kb.netgear.com/app/answers/detail/a_id/12197
4. Restore config
If you have a backed up config file, you can upload it. Otherwise, just configure settings as normal.
Resetting to factory defaults did not work. There are a few threads on the NETGEAR forums about this as well, but the only resolution seemed to be to send the unit to NETGEAR.
However – after two days of hacking I have found a do-it-yourself solution:
1. Make sure you can connect to the web interface safely
This means resetting to factory defaults, use a cable directly between your computer and the access point, and set a static IP address for your computer in the 192.168.0.x range. NETGEAR supports recommends using the address 192.168.0.210 for reasons that I don’t know..
2. Go to the address http://192.168.0.233/recreate.php
The real purpose of this file is not known, but it has an interesting side effect: When you go to the access point home page afterwards, you get access to a partly functional interface. A lot of things don’t work, but one important piece did work for me: the firmware upgrade
3. Upload the 3.1.1 firmware image
If you don’t have the firmware image here you can get it from NETGEAR support at http://kb.netgear.com/app/answers/detail/a_id/12197
4. Restore config
If you have a backed up config file, you can upload it. Otherwise, just configure settings as normal.
2010-09-13
Musikerne vinner, plateselskapene taper
Dommedagsprofetien ser ut til å ha et relativt begrenset nedslagsfelt. Som Espen refererer i Tversover: Musikerne vinner, plateselskapene taper ser det ut til at artistene har kommet godt ut av digitaliseringen økonomisk sett:
Etter 10 år med digitalisering av musikk har den gjennomsnittlige musiker hatt en inntektsvekst på 66%. De eneste som taper på digital musikk, er de tradisjonelle plateselskapene. Det viser en masterstudie utført av Siviløkonomstudentene Richard Bjerkøe og Anders Sørbo ved Handelshøyskolen BI.Det gjenstår å se hvordan inntektsmodellen til digitalt salg og streaming påvirker (påvirkes av) dette.
| Reaksjoner: |
Password Reuse
This is absolutely true. In most occasions it doesn't really matter how strong your password is, only that it's unique. My recommendation is that you use SuperGenPass to generate site specific passwords for you.
2010-08-27
Why Java needs Oracle
Chris Wong's Development Blog: Why Java needs Oracle:
For better or for worse, Oracle is now Java's champion and protector. The legal landscape is too dangerous out there for a major platform to be without one.
Abonner på:
Innlegg (Atom)
