The thing with unity is that it's almost so easy to grasp that when you sit down with it, it's almost not necessary. You can spend time thinking about actual implementation details while Unity does all the "boring" stuff. That said - when I started searching for specific problems I had the community had all the answers and then some. Another awesome thing is that you can do really complex stuff, like intricate shaders, if you want. Completing a full featured 3D-game have never felt so close to me.
Wow, this must have taken a long time to put together. I think he makes a very fine point when he says browsers must have a part to play in fixing this.
The author left out the most important part, which is the controller. The HTTP methods match controller verbs without requiring any attribute markup. The Get method responds to /controller (all) or /controller/5 (ID of 5), the Post method responds to a POST on /controller, the Delete method responds to DELETE on /controller/5, etc.
It's very elegant at this level. Adding additional methods requires more work, as does managing routing and the other support infrastructure in a more complex application, but it provides a great starting point.
One of the things that isn't great is that they, of necessity, have a different base class. Instead of Controller, it's ApiController. That makes sense. However, the differences pervade the entire stack, down to things like the Request and Response objects, and even AuthorizeAttribute (same class name in a different namespace with different parameters).
All in all, though, it's great. It certainly beats using WCF for simple REST APIs and it beats trying to repurpose MVC to implement an API.
But any such app is just an UI for presenting the data available for everyone. What if this app is just a open source UI with instructions on how to fit your own API key ? Finding and penalizing such apps would serve nothing.
The only solution to this is awareness on the users part and nothing else.
But every application has a specific action. See data is just well, data. What you do with it defines your application. Take something non-intrusive for a change, say the books a bookstore sells most. There's a wealth of information there. We could predict locally trending topics or the most common problems students face. But you could also predict what kind of audience the bookstore receives. It may not sound that creepy unless you find that the store gets a lot of depression related sales. That could get creepy very fast.
> The only solution to this is awareness on the users part and nothing else.
Awareness is extremely important even vital. But that is not it. Thousands of Girls Around Me apps probably exist and it is fairly possible though tough to find them. All I am saying is that efforts should be made in that regard as well.
This is just an example of how not to do an April fools day joke. These guys are posting the feedback they collected back to their server which I think is immoral.
You're not allowed to point out deficiencies in something you like and advocate? That's a fairly dense position..
The nice thing about Open Source is that it tends to be a little bit more immune to that corporate drum beat since there are less full time salesmen and marketeers. The void seems to fill with fanbois though.
I would have loved to see what these guys have to say about Scala critically, but that's not what they are doing, this is a half baked unfunny joke that does not inspire any debate, only flaming and bashing. Is good that you talk about fanboyism because that's what this article is about, clojure fanboyism to be precise
I love Scala and have been using it for a couple of years but I've been through nearly all the stages described in the article. Eventually I got so frustrated I gave up and learned Clojure !!
