648 karma · joined December 20, 2008
In software patents, the implementation is described in such general terms that a lot of the time, any implementation can be said to use the method described in the patent. This is my biggest problem with software patents: once you abstract your solution enough, it isn't of much use to anybody, hence the value of the patent to the general public is null while it still allows you to block out competitors that want to find a solution to the same/similar problem although your patent is of no help to them actually solving the problem.
It is this skewed relationship that drives me crazy. Licensing a software patent only allows you to come up with your own solution a lot of the time, it does not save you the development cost.
If you license a patent for some industrial process it saves you huge amounts of research cost so licensing the patent is actually attractive.
Software should only be patentable if the patent provides actual value in solving the problem it claims to solve. Since useable software implementation are so specific, this may rule out patenting software at all.
As other mentioned, the idea with patents was to offer people a limited time monopoly on their innovations in exchange for publishing them so others could use/enhance these ideas instead of reinventing the wheel over and over. I have not seen one instance where this works out for software...
Apple didn't make this move because they have some irrational religious hatred against Adobe. They are just betting that a tight control over the technology by which people produce applications for their mobile platform will be advantageous to them. They are fully aware that this is bad for people who have bet on using different technology and I guess is that they just don't care the tiniest bit.
Basically, they reserve the right to ban any sort of DSL/runtime/engine application architecture. Imagine you are building adventure games (like Money Island). You'd have a game engine and a domain language in which you describe the game. The beauty of this is, you don't have to rewrite the engine every time you finish a story for a game, you just write in your DSL. The same holds for a range of other applications such as travel guides, recipes for cooking... How can you be sure where they draw the line between data and code?
Well, it probably just depends on whether it comes from an Adobe tool or not. Let's see who's next.
Interestingly, it says "The new class action goes beyond Google’s Library Project, and includes Google’s other systematic and pervasive infringements of the rights of photographers, illustrators and other visual artists."
I wonder what else they may be filing suit over... Image search?
Were the homework assignments of a type were using a computer to prepare them would actually help? Did the computers include the appropriate software that was needed to do the homework? Had the homework to be submitted in paper form and did the computers come with printers?
One should probably just automate this. Pay $20 to istockphoto for a piece of vector art and put the company name beside it. That's an easy made $79. So if easterbunny inc. needs logo, just license http://www.istockphoto.com/stock-illustration-11054108-rabbi... and you're done. The quality would be comparable to those logo templates.
Many people obviously have started to believe that a logo is a bit of illustration plus your name.
Methinks you might have a somewhat non-standard definition of the term middleware. Please have your buzzword generator re-calibrated ;)
Thesis (established view): SQL/ACID solves all you data problems
Antithesis: Nobody needs SQL/ACID, let's throw it all out
Synthesis: By carefully considering data integrity constraints we can find a more optimal data management solution for a particular problem (alternatively: let's go to the pub!)