It was well mixed in with references and analysis of some pretty amazing visualizations though. I agree it could have been more grounded, but I still found it a pretty great article. Which statements do you view as too grandiose?
Implementing OAuth 2.0 client and server code in a .NET stack this summer for a job makes me inclined to agree that OAUTH has confusing points. It definitely is not precise enough to be called a specification, but more just guidelines. I am quite impressed with how the author overblew the whole thing to show off their solution, it was an interesting fusion of technology and selling their idea.
It seems that striking a balance between these traits is best. You have to do things and learn from your mistakes to keep from doing stupid stuff. But you also don't want to go so far that you look like a total idiot.
Wanting things to be ad free can be a strong response to the overwhelming amount of ads that we are presented with every day. These advertisements program us unconsciously and often to our detriment, so yes it is important for there to be an option to remove all advertising for a price.
It really depends on the company, there are some like that. It definitely has been like that at Microsoft in the past, but they are changing so who knows where that is going. On the other end of the spectrum at DocuSign many of the engineers would try to find potential places customer data might be handled wrong so the data could be secured. It depends on the company and even the department, but some do have that openness. It helps that it is really easy to find another job in software engineering these days so the downside of standing up on ethical matters is fairly small.
Caching is simply keeping a response that hasn't changed so you don't have to recompute it. There can be many levels of cache. Varnish is one useful type of cache, but there are many others too.
It will be particularly interesting to see if Thync tries to get studies from third parties. It looks like tDCS hasn't been solidly proven or disproven, so it will be exciting if this gets more researchers to look into the effectiveness of tDCS.
Thanks for the perspective. Right now I am still just in the experimental phase of building things and even an early beta is 6 months out for my project. Like you said there definitely are a bunch of useful tools on AWS. This article definitely convinced me to actually spin up an AWS instance and see how well it works before just going with Linode or DigitalOcean.
That is very true, time is quite valuable. It appears that for my use case AWS would be at least 5x as expensive though. I won't know for sure until I actually try running some benchmarks. Have you had experience showing AWS to be significantly faster to deploy and administer than Linode, DigitalOcean, etc?
Good point, it becomes clear that if you are operating at the scale of a large company the large scale and rich ecosystem are important. It was just a bit surprising to me that for smaller scale instances AWS is so much more expensive. It would seem they should be cheaper due to economies of scale.
Thanks for all the replies. I am just researching all of this for my own startup and it is important to understand all the tradeoffs. And it is clear from your article that AWS has a very deep feature set. Its a good article!
Really? I know reserved instances lower the price but they still have shown themselves less performant for the dollar in the benchmarks I have seen. Are there any good articles you could recommend with benchmarks showing AWS to be more cost effective?
Out of curiousity, why go with AWS when Linode, Digitalocean, etc appear to be so much more cost effective? Is the simplicity of spinning up AWS instances really great enough to counterbalance what appears to be a significantly greater cost? Is it the flexibility of different AWS services?