A bit late, but Ceylon creator Brian Krig answered the following question in an interview posted today:
Finally, going forward, do you think that going forward, Red Hat will start coding more in Ceylon?
The first step for us will be to bring some of our pieces that we have in the JBoss ecosystem that we delivered as pieces of the application server, and repackage them, and make them modular, and make those modules for the Ceylon platform.
At the same time as that, we're taking Ceylon, and we're enabling deployment to Openshift. Once we have then the capabilities that we have in JBoss, also for Ceylon, then it's going to be a lot more interesting - what can we do in Ceylon that we can currently do in JBoss?
People often ask me, does RedHat use Ceylon to build internal projects, and I'm always kind of like, I don't quite understand, we don't have internal projects, we're a product company!
People do not think in types.
Piaget would disagree with you.
It doesn't help that a lot of sites use policies that make it harder to practice good password habits. Examples:
- Unnecessary limits on password length or allowed characters. These make passwords weaker and serve no purpose that I am aware of. They also make it harder to use consistent conventions between services.
- "Security Questions" that would be easy for others to know if answered honestly.
- "Password Hints". I don't think I even need to explain why these are a bad idea.
- Requiring users to change their passwords regularly. Such rules often result in users picking weak passwords or taping them to their monitor or keyboard, and so in my opinion, reduce rather than increase security.