pori
Before doing so, I closed myself off from all manner of emotion, creativity, and honesty. I tried to be invisible. I closed myself off from people. I lived in my own mind. Being closeted led me to compensate by leading a double life that hurt a lot of people.
But now it's different. I am now doing my best work, I am exploring new things to try and learn, and I have many wonderful relationships that makes me happy to be alive. For the first time, I really feel like I'm living life.
Racket - wide support, ease of use, etc.
GNU Guile - extending GNU applications or building your own robust ones.
Chibi - embedded applications. (My personal favorite.)
If you mean "Lisp" as in more general than Scheme, then the main two are:
Common Lisp - most used, advanced, etc.
Clojure - most popular of all the lisps today, arguably. It has the largest ecosystem thanks to JVM interoperability.
> Effort put into rhine: 1 year, 1 month
Props for the effort put into this! I came across rhine-ml a while ago and thought it would have been a nice, native alternative to Clojure. Both of these projects look very well thought out.
Curious, is this a learning project? It seems that way considering you go into detail about the inner workings.
Still, I can't help but feel that the game industry is always a bit behind in FOSS. They don't usually open source anything until a decade or two after the tech is irrelevant. Perhaps it's to prevent competition.
Another thing that bothers me with these releases is how little documentation there is. They put up a repository without much intention of helping/building a community around it, which is a shame.
All that said, they still have the right to approach in this manner. It is their property and they are still generous when making releases like this.
https://en.wikipedia.org/wiki/Quake_II_engine#Games_based_on...
That said, Butterfield's move to raise more money simply to be attract more recruits sounds completely crazy. But hey, it's only crazy if it doesn't work.
He seems to understand the awkward position his company is in. As covered in a TC article, Butterfield is prepping his company for the public markets even though there are no real plans to do so. This is evidenced by the near profitability Slack has now.
Link to relevant article:
I have a fear that this trend among large companies is going to trickle down to smaller ones and independent devs. Considering these "Cloud Wars" I can see stories like continuing with different providers. Ultimately, a scenario could occur where one year, one provider is king. Then the next, everyone decides they need to migrate to the next big thing. That would be irritating for us contractors. We would have to learn new interfaces and apis at the same rate of JS frameworks.
To be quite frank, I am not an expert in npm's underlying architecture. But this post has inspired me to actually do some research. The fact that there is an alternate package manager shows there is a huge problem.
Writing a Brainfuck interpreter is a good idea! (I'm aware of the language.) Perhaps I could also try ArnoldC. :3
Recently, I began working with HHVM, I've been very interested in the subject of compilers and interpreters. I would certainly love to build such a thing for JS one day.
I had forgotten about Rust. Are there major projects being used for this yet? I've heard it's picking up quite a bit.
Personally, I prefer to write code in a functional manner. While I've always thought Go looked like an amazing platform for programming in general, I haven't been keen on moving to another imperative language.
It seems the landscape for functional alternatives are mainly Scala and Clojure which are both based on the JVM and require a bit of time to learn the tooling. I am not a Java or JVM export, so I haven't been too inspired by this either.
Albeit, I am little disappointed because I have finally started getting into open source and being active on GitHub, and now it seems the development community is vying for a way out. GitHub may not be open, it may be centralized, but it does offer the advantages of uniformity and easy discovery.
Hopefully this will reduce the necessity to have a non-Windows machine around. That aspect has made things tedious for us.
All that said, Koa is pretty great and teams should adopt it.