432 karma · joined February 27, 2013
Story: I knew a lady in her 40s who started experiencing some psychosis. She started thinking that people were spying on her and reporting her activities on radio and TV, that huge gatherings were being held in football stadiums to watch videos of her which had been secretly filmed, that songs on the radio (in languages she didn't know) were talking about her, etc.
She thought that all her friends knew about this but didn't mention anything so as not to alarm her. After a couple months went by, and still none of her friends mentioned anything, she thought it was strange and decided to have herself checked instead.
After taking the recommended medication, within a day or so, the strange music she used to hear in the distance disappeared, all the people on the radio and TV stopped talking about her, etc.
Moral: Don't get stuck on the stigma of the "crazy" label. Just like anyone can get sick physically, people who are otherwise normal can start having mental problems. That doesn't mean you're "crazy". It does mean that you should have yourself checked by someone who is knowledgeable about such ailments.
Steve, what are your next 10 predictions? Obviously, you're at least 10 years ahead of me...
Abstracting out details so the "big picture" becomes clearer can make code more understandable. At the same time, more abstractions means more "layers", which a reader has to dig through to find out what is actually going on, making code less understandable. So there is a tension between allowing duplication, and removing it by adding a new abstraction, and which choice is better depends entirely on the specific situation.
Yes, there are plenty of "lowest-wage programmers" on those sites. I never bothered to compete with them on price. I simply charged what I thought I was worth, and ratcheted my price up and up as I discovered that the market thought differently. Interestingly, as my price went higher and higher, the constant noise of "crappy" job offers quieted down and was replaced by a small number of great offers.
He doesn't post often, but when he does, the articles are almost always good.
It would be very helpful if the creators made a page (linked to right from the home page) explaining their philosophy and guiding principles, and how their design differs from other languages in the same space. Don't tell us fluffy things like "we choose simplicity over complexity". #1, that is not a trade-off. #2, "simplicity" is such a vague and overused word that it's hard to know what you mean. (What I think they mean by "choosing simplicity" is: keeping the feature set and number of syntactic constructs small.)
Another point: "For the JVM" is a 2-edged sword. If I see a programming language described as "for the JVM", it would make me think twice about investing the time to learn it. The JVM is good technology and I do make use of it, but for reasons I won't detail here, I don't want to be locked in to it.
"Can run on the JVM" is a different matter. "The compiler has a JVM backend, among others" is great. "Currently runs only on the JVM, other backends are coming" is OK.
If Gosu was specifically designed for very tight integration with Java, such that it wouldn't make sense to separate it from the JVM, that is a design trade-off and should be explained on the "design rationale" page I suggested above.