Kyle Isom

LISP side of things already has a bit of work toward a security model and components for robust implementation: Security Kernel https://www.kyleisom.net/downloads/security_kernel.pdf Formally-verified Scheme http://citeseerx.ist.psu.edu/viewdoc/download;jsessionid=881F8DEAC1EE1… The features could certainly be worth it. Some aspects of the Genera experience, esp productivity & holistic debugging, still aren't in modern flows: http://www.symbolics-dks.com/Genera-why-1.htm So, who knows where it will go. Betting on a semi-functional language with prior high-security and high-productivity work is a better start than most projects like this, though.

I know Kyle personally. He is super smart, incredibly humble, and willing to teach. And I always admire anyone taking the initiative to try and produce something useful. In response to Jabbles, this is from his (work in progress) book. Page 7. // Implement the standard padding scheme for block ciphers. This // scheme uses 0x80 as the first non-NULL padding byte, and 0x00 to // pad out the data to a multiple of the block length as required. // If the message is a multiple of the block size, add a full block // of padding. Note that the message is copied, and the original // isn't touched. As anyone who has written technical material knows, your drafts tend to be error prone and you rely heavily on others to help catch your mistakes. Technical editors are the normal tool utilized by the traditional publishing world. As this is a leanpub book, I feel that the responsibility generally falls on the community. Those who have paid for the book and want to see it succeed. I personally have purchased this book as well as reported errors to Kyle. I'd encourage anyone with questions or comments to reach out to Kyle. He is quick to respond. http://www.kyleisom.net

A few notes as I read through this: - Passwords are still just as broken now as they were then. - Functional programming is still widely discussed, though the focus is more on Lisp than Clojure/Haskell/etc. - Fourth post is the usual, somewhat sensationalist, this commonly-accepted thing is bad! sort of headline that makes the rounds here every so often. - This post on syntax highlighting [1] reminds me of another recent one [2]. - 37signals is there with another sage-like statement on the business. - Article on women in tech in slot #13. - Woah, is that Clojure there in #14? And on SourceForge, even. It's come a long way since then. - Fears about government invasion of privacy abound. - Hey, MySpace! That spam "epidemic" never quite subsided, it seems. - Interesting mathematical discussion in slot #24. When reading the headline, I almost expected to read "stackoverflow.com" in the domain slot. Goes to show how popular that sort of post is here nowadays. As someone who wasn't around back then, it's interesting to look back on this now and see what the site I love now was like five years ago. [1] http://web.archive.org/web/20071110115358/http://drinkbroken.typepad.c… [2] http://www.kyleisom.net/blog/2012/10/17/syntax-off/

http://kyleisom.net/blog/2012/10/17/syntax-off/ Syntax highlighting is less common in the Go community since Rob Pike called syntax highlighting juvenile :D https://groups.google.com/d/msg/golang-nuts/hJHCAaiL0so/kG3BHV6QFfIJ He also argued against keyword emphasizing: http://www.lysator.liu.se/c/pikestyle.html

Indeed, there is a small movement in the development/programming community that advocate this :) https://dev.to/huytd/turning-off-the-syntax-highlighter-8af http://www.linusakesson.net/programming/syntaxhighlighting/ https://kyleisom.net/blog/2012/10/17/syntax-off/ https://groups.google.com/forum/#!msg/golang-nuts/hJHCAaiL0so/kG3BHV6Q… https://www.robertmelton.com/project/syntax-highlighting-off/ https://news.ycombinator.com/item?id=12886067 https://www.howtogeek.com/howto/linux/disable-syntax-highlighting-in-v… https://vi.stackexchange.com/questions/8751/how-to-completely-turn-off…