I wonder if when people move to 2 year or 3 year cycles with phones
Wait, what? People change phone more often than once per two years. Most people I know, keep them for about two years or longer.
I basically live on the hand-me-down phones from my wife. Why? Because she gets the "everything included" plan which comes with an iPhone (and when we renew each two year, we get a new iPhone). She gets the "everything included" plan because that way she doesn't have to think about anything when using it (Am I on wireless? How much volume do I still have this month? Roaming? Those kind of questions that are hard for non-tech users).
When she gets a new phone, I get her two year old phone and continue to use that on my cheap-ass-phoneless-plan. At this point, I am using a iPhone 5 (just the number) and it works fine. I'm even pondering continuing on using it until Apple stops support, because I'm not keen on getting the bigger iPhone 6 (just the number) my wife currently uses. Refresh is in March next year.
Phones already have a long longevity... I do admit, I went to Mr Minit to get a new battery for the iPhone 5. Cost me something like 50€ and that was worth it.
Given that this case has gone on for six (6) years, a $3 million verdict probably won't even cover MobileMedia's legal fees (which, I suspect, the judge will not grant to them on top of the aware; it's unusual for the plaintiff/patent owner to get legal fees on top of damages in these cases). Patent litigation is very expensive, especially if you go to trial; I remember being staggered at what the cumulative per-hour billing rate must have been for one such trial where I testified as an expert.
There's a lot of useful PDP-11 programs, too; but most people can't run them, either.
Really? You might even be able to run them in your browser...
VueScan? Just works.
I have no stake in this. I am just a happy customer.
Not to be an old programming fart (but, hey!), but this comes up about every 5-10 years. Someone has created a system for automatic program generation that is going to replace programmers (4th generation languages, anyone? How about "The Last One"?), and it turns out to have only limited usefulness.
Of course, code generation programs exist. They've existed almost as long we've been programming computers. The most common are assemblers and compilers, which take in text specifications and generate running code (or sometimes bytecode to be interpreted). And if you stop and think about the difficulties that most of us who code have with making source code that we write produce running code that meets our needs, you can immediately see the issues with replacing or bolting on top of that system a 'source code generation' system. It can work very well as long as you don't exceed what it can actually do and only if the code generation system itself is well-written and reliable. (This is why developers feel a sense of betrayal and anger with compiler bugs more than any other kind of tool bug.)
So, yeah, like strong AI, self-coding systems are always 5 to 10 years out and have been for half a century.
Maybe the underlying libraries now catch these things, but back in the day it didn't. Even with Java, writing platform independent code does require some care.
When speculation has done its worst, two plus two still equals four. -- S. Johnson