[1] https://www.theguardian.com/books/2016/jul/18/against-electi...
224 karma · joined February 5, 2010
[1] https://www.theguardian.com/books/2016/jul/18/against-electi...
One person is missing and the whole world is deserted.
I would say my reflection to achieve this would be to define
- what is the product perimetre
- what architecture/design principle will bring you capabilities and useful abstraction
- what are the best interface/extension points for allowing user to extend the usage easily
Then hard work, iteration and pivot
I think the framework/product should propose some configurability or some extension points. Then your product can stay pure and people can still adapt it to fit their need. If you propose an API then it can be integrate with other product/tools/developmnent. If it embark scripting ability then the user can modify it's behaviour...
So if your usecases would benefits from caching, discoverability... then you may want to choose REST.
I think it's smart to know a little about the literature; enough to know what battle you don't want to fight. It is not smart to try to develop an engine on the basis that it will need to beat the law of thermodynamic to be possible.
But also, “They did not know it was impossible so they did it”, Mark Twain
The Curie institut reacted to the patent as a research institution, here we have the impact on a practical health issue.
[1] http://www.institut-curie.org/sites/default/files/myriad-gen... [2] http://www.institut-curie.org/press-release/by-type/377
Thanks!
[1] http://patentlyo.com/patent/2012/12/suing-the-uspto-for-issu...
The RFC says at the point 9.1.1 that: "Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request; in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the effects, so therefore cannot be held accountable for them."
I m still a intellij user at home but at work we use yoxos and it is very good to customize and maintain eclipse configuration.
I think it would be in the interest of the public that you have a more limited in time copyright and after a certain delay an obligation to let other creator reuse assets with a compensation schema that allows new creations.