+1 for Compassion International. We've been sponsoring children through them for 20 years. We get to know the children personally with cards, letters and Christmas gifts.
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 think the comment is exactly opposite of what you are suggesting.
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.
I'm curious. Did you look into Googles AppEngine? It seems to have a lot of the benefits that Heroku offers, but is much cheaper.
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.
While it is technically true that Alferd Nobel did not provide for a prize in Economics in his will, there is The Sveriges Riksbank Prize in Economic Sciences (1). This was funded in Nobel's memory by a Swedish central banker.
It is administered by the Nobel Foundation - just like the other prizes.
I just recently found Essential Craftsman, and I absolutely love it!
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.
> About 50% of our users completely skip the onboarding altogether.
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?
It seems to me that it's a good thing for Oracle. Oracle/Sun was never going to make any headway in the mobile space. It just wasn't going to happen. So, it wasn't a loss to them, because they had already lost that market.
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.
I'd argue that instead, she should have emailed the rest of the team and asked what's going on. Raise the issue and let somebody take responsibility.
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."
This article is full of FUD, and shows a very naive understanding of how to maintain and deploy software.
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.
That was an option that he gave (towards the bottom). I have no idea if GH passes these on to the repo owner or not. GH may have just removed the repos.
Can you elaborate on what you mean by the "very large/significant complexity drawback"? From what I've seen (which is admittedly small) Rust is much less complex than either C or C++.