dlanouette
We were just contacted by one of our first children from Nigeria. She "aged out" of the program, and we hadn't heard from her in years. She found us on FB (unique last names have an advantage). It's been great catching up with her again. Watching her go from a little girl to a mid-twenties woman has been wonderful.
I can't recommend them enough.
The comment is saying that Lambda has limitations and works best when considering those limitations. If those limitations don't fit your use case, you shouldn't be using Lambdas - or, at least, don't expect it to be an optimal solution.
Granted that it does impose some limitations, and therefore isn't right for all apps. But it does seem like it would work for a large percentage of web apps and REST api's.
It is administered by the Nobel Foundation - just like the other prizes.
This video (https://www.youtube.com/watch?v=qP1AmDRhoas) popped up on my YouTube feed about a month ago and really spoke to me. I encourage everyone to spend 13 min and watch/listen.
Great stuff!
How is this different than when you had no onboarding? (serious question) Did you make other changes that made the onboarding process less important to end users?
But, with Android, Java got a boost that bled over to the server, and to a lesser extent, the desktop. It can be argued what the size of that boost was, and if it had any real impact (I would argue that it was not significant), but it was still a boost that they never would have had.
Anyway, that's the opinion of some random guy on the internet.
A potential side benefit is that you can teach more people the "right" way to do things.
Also, the comment about the docs was a really poor choice of words. A better comment might have been "Yah, they need work. Feel free to update them to make them better."
Your comment seems to imply that java hasn't been successful for db development. HBase, Cassandra and ElasticSearch would all disagree.
Yes, there are situations where GC is not appropriate. But I think those situations aren't as common as they are made out to be.
http://dave.cheney.net/2014/09/01/gos-runtime-c-to-go-rewrit...
The "problems" he talks about are caused by so many other problems he has (no version control, not knowing what's in production, making breaking changes as part of a small bug fix, not testing changes, etc, etc).
And, his proposed fix - use a scripting language - would break too if he made a backwards-incompatible change.
But, the original author did give that option.
> I'm 20 now.
So, you had a Blackberry when you were 14? Your post has a luddite like quality to it, but this fact is quite the opposite.