CLPython
ChezScheme
Our great sponsors
CLPython | ChezScheme | |
---|---|---|
5 | 27 | |
364 | 6,831 | |
- | 0.5% | |
2.9 | 9.0 | |
5 months ago | 4 days ago | |
Common Lisp | Scheme | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CLPython
-
Why Static Languages Suffer From Complexity
C++, ~haskell, python, mathematica... capisce? :)
- Common Lisp implementation in Python
-
Anybody using Common Lisp or clojure for data science
cl-python
-
Compiler in Lisp
Python
ChezScheme
-
Racket branch of Chez Scheme merging with mainline Chez Scheme
The main line of Chez Scheme is here:
https://github.com/cisco/ChezScheme
There is more work to be done before release 10.0.
-
Not only Clojure ā Chez Scheme: Lisp with native code speed
What is yakihonne? Another blogging platform? Rather confusing to use.
Anyway, would have been nice for the article to link to Chez Scheme project's page, which seems to be this one:
https://github.com/cisco/ChezScheme
Also not clear why should folks use Chez? The article barely covered the why or what successful apps have been written in Chez.
-
My resignation letter as R7RS-large chair
Who will convince Kent to come back and make r6.1rs? https://github.com/cisco/ChezScheme/issues/574
If you want a large language, isn't it a better idea to build it on top of something the makes better guarantees for the user? I prefer my program to not continue executing after reaching an erroneous state.
-
Are there any notable software projects done by traditionally non-software companies?
The link doesn't work for me but to answer the title, I found it interesting to learn that Chez Scheme (often regarded as the Scheme implementation which produces the fastest programs) is developed by Cisco, the company that makes networking hardware
-
Unable to install Chez Scheme, I'm lost š. Can you illustrate me on how to do this because I have tried for a couple hours and I don't have time to waste so I guess is better if I ask step by step the meaning of all of this
Download the exe from here
-
GitHub CopiĀlot invesĀtiĀgaĀtion
Many open source project don't allow contributions from people that have worked with similar projects with incompatible licenses. I remember https://github.com/cisco/ChezScheme/pull/376#issuecomment-45... and https://wiki.winehq.org/Developer_FAQ#Copyright_Issues
-
Building Idris2 for Apple silicon as of August 2022
This is an update on building Idris2 for `arm64` Apple silicon. My original guide was posted here a year ago: [Success building native Idris2 on an M1 Mac](https://www.reddit.com/r/Idris/comments/pc5lib/success\_building\_native\_idris2\_on\_an\_m1\_mac/) Some issues I encountered may get fixed, so these notes may best serve as guidance, as others work through this install in the future. I no longer have any Intel Apple machines in use. I am using MacOS Monterey 12.5.1, and a current homebrew installation that includes needed support such as gmp. I have successfully built idris2 on several M1 Mac minis, an M2 Macbook Air, and an M2 Ultra Mac Studio. These directions assume that you have read the install docs for Chez Scheme and Idris. ---- The official Cisco [Chez Scheme](https://github.com/cisco/ChezScheme) is still not `arm64` native. As before, one needs to install Racket's [fork](https://github.com/racket/ChezScheme/), which is `arm64` native and supports Idris2. Cloning the git repository and attempting to build, one encounters the error Source in "zuo" is missing; check out Git submodules using git submodule init git submodule update --depth 1 After these steps, the build is routine using the steps arch=tarm64osx ./configure --pb make ${arch}.bootquick ./configure --threads make sudo make install One can now confirm that `scheme` is `arm64` native using the command file $(which scheme) ---- The Idris 2 build was a delicate puzzle for me, harder than before. I got it to run by hand once, and then lost hours trying to recover what I did right by script. Here is a GitHub Gist for my install script: [Build script for Idris 2 on Apple silicon](https://gist.github.com/Syzygies/15cbaebd5d7a31630650b7a8436a8f1f) Here are the issues I encountered: Seven of the nine case statements involving ta6osx have had t `arm64`osx added, but not the remaining two. This threw me, as I imagined this had to be deliberate, and this was one of several problems that needed fixing. The bootstrap build creates a file `libidris2_support.dylib` but then can't find it later. One needs to attempt the bootstrap build twice, copying this file after the first attempt fails so that the second attempt will succeed. I copied this file everywhere needed, rather than to `/usr/local/lib` (homebrew doesn't like sharing a lane). The executable script itself can fail to find this `.dylib`, but the executable looks in the current working directory, so one could easily miss this during development. I also patch the executable so it changes into the executable's directory before calling it, where one of several identical copies of this `.dylib` can be found. `INSTALL.md` included the curious note **NOTE**: If you're running macOS on Apple Silicon (arm64) you may need to run "`arch -x86_64 make ...`" instead of `make` in the following steps. The correct way to read this is that the author isn't sure. In fact, following this instruction will create `libidris2_support.dylib` with the wrong architecture, as I verified with a matrix of experiments (this or not, edit last two case statements or not). What is the status of official Apple silicon support for Chez Scheme and Idris 2? Searching Cisco [Chez Scheme](https://github.com/cisco/ChezScheme) issues for `arm64` yields several open issues, including [Pull or Backport ARM64 Support from the Racket Backend Version #545](https://github.com/cisco/ChezScheme/issues/545) proposing to pull the Racket fork support for Apple Silicon. Searching pull requests for `arm64` yields [Apple Silicon support #607](https://github.com/cisco/ChezScheme/pull/607), which doesn't work. The author doesn't explain why they are making this effort, rather than pulling the Racket fork changes. Others note that the author also ignores prior art in their naming conventions. Searching [Idris 2](https://github.com/idris-lang/Idris2) issues for `arm64` yields [Racket cannot find libidris2_support on Mac M1 #1032](https://github.com/idris-lang/Idris2/issues/1032), noting the `.dylib` issue I address, and linking to [Clarify installation instructions on macOS (M1) #2233](https://github.com/idris-lang/Idris2/issues/2233) asking for better Apple silicon directions, which backlinks to my first [reddit post](https://www.reddit.com/r/Idris/comments/pc5lib/success\_building\_native\_idris2\_on\_an\_m1\_mac/). The other backlinks I could find are automated scrapes not of interest. There are no pull requests for `arm64`. I admire the Idris project and I want it to succeed. It needs macOS users. However, I'm unlikely to rely on Idris2 for my own work until parallelism is better supported. I'd love someone to change my mind if I'm misreading the situation.
- Chez Scheme
-
Bare Metal Racket?
Hard. Some relevant links. https://github.com/cisco/ChezScheme/issues/480 https://www.cs.utah.edu/flux/oskit/
- Private Programming Languages
What are some alternatives?
MicroPython - MicroPython - a lean and efficient Python implementation for microcontrollers and constrained systems
IronPython - Implementation of Python 3.x for .NET Framework that is built on top of the Dynamic Language Runtime.
r6rs-pffi - Portable Foreign Function Interface (FFI) for R6RS
racket-markdown-blog - This repository contains another attempt of writing a blog. The blog's "engine" is written in Racket. There is a Dockerfile which can be used to run the blog inside a Docker container, to ease deployment.
Grumpy - Grumpy is a Python to Go source code transcompiler and runtime.
PySec - OWASP Python Security Project
dumb-jump - an Emacs "jump to definition" package for 50+ languages
racket - The Racket repository
Mezzano - An operating system written in Common Lisp
ops-examples - A repository of basic and advanced examples using Ops
pylisp - A Lisp compiler targeting Python
web-tutorial - How to write web applications with Racket