Kivutar
My main criticism of the language is that the word are so abstract that understanding spoken Toki Pona at real speed is practically impossible. Too many possible translations. Too many ways of combining these words, and no mechanism to identify which words form a compound.
Also the good part of Go are the goroutines, the channels, the types, the safety...
The article was fun but they will find the limit as soon as they will try to support the important parts of Go.
Trying to go further will just demonstrate the opposite of their point.
The mentors I had were very passionate about their field and happy to share their knowledge.
The mentoring was not really about small details. More about seeing what technologies and concepts I was comfortable with, and telling me what things I should explore next. It was most of the time very opinionated, but this was OK, as I had more than one mentor.
Note that even if it's a traditional dish here, only a minority of people are OK to give it a try. Often to impress other people around the table.
My grandmother used to prepare it. It's quite simple to make. Put the right kind of cheese in a pot, cover it with a green cabage leaf, cover and wait for a week.
By simplicity, we mean frugality.
If you can implement something without adding a ton of dependencies, abstraction layers, and design patterns, it will be easier to understand and debug.
YAGNI is everything but abused.
Systemd is written in C and relies on kernel headers. Which means that they need to have a layer that deals with different versions of the kernel headers. I remember it was headers about network.
At the time I was working on this, I had to contribute to systemd to add support for my kernel version. Got a few patches accepted in their master. And things were working fine for a while.
Until they suddenly decided to drop <= 3.10 kernel support. Yep. Afterwhat I had to maintain patch sets for systemd, which is a great amount of job, given that my upstream was updating systemd quite often.
Now my good people, explain me how such a mess could have happen with a previous init based on shell?
The boards like Cubieboard are stuck with a 3.4 kernel (if you want to use GLES), because unlike other manufacturers, they don't pay people to ensure proper software support. Some manufacturers also claim software compatibility with the RPi images, which is impossible, but may trick some beginners in buying their hardware. Dishonest, right?
And yes, we sent a mail to the RPi foundation to ask for some free sample (we are not a commercial organisation) and they told us very politely to not expect anything from them. They ignored our request to include Lakka in NOOBS two times. Still, their hardware works and they pay enough people to work on software so if you want something that just works, go for it.