doc
semver
doc | semver | |
---|---|---|
8 | 727 | |
17 | 7,044 | |
- | 0.9% | |
6.6 | 0.6 | |
3 days ago | 24 days ago | |
Common Lisp | ||
GNU General Public License v3.0 or later | - |
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.
doc
-
How do you think about version number management?
- it is possible to subscribe on the changes using RSS (this is a feature of the 40ANTS-DOC documentation builder).
-
From Common Lisp to Julia
So, the article is harsh on CL: YMMV. Also, your goal may vary: I want to build and ship (web) applications, and so far Julia doesn't look attractive to me (at all). Super fast incremental development, build a standalone binary and deploy on my VPS or ship an Electron window? done. Problem(s) solved, let's focus on my app please.
The author doesn't mention a few helpful things:
- editor support: https://lispcookbook.github.io/cl-cookbook/editor-support.ht... Emacs is first class, Portacle is an Emacs easy to install (3 clicks), Vim, Atom support is (was?) very good, Sublime Text seems good (it has an interactive debugger with stack frame inspection), VSCode sees good work underway, the Alive extension is new, usable but hard to install yet, LispWorks is proprietary and is more like Smalltalk, with many graphical windows to inspect your running application, Geany has simple and experimental support, Eclipse has basic support, Lem is a general purpose editor written in CL, it is Emacs-like and poorely documented :( we have Jupyter notebooks and simpler terminal-based interactive REPLs: cl-repl is like ipython.
So, one could complain five years ago easily about the lack of editor support, know your complaint should be more evolved than a Emacs/Vim dichotomy.
- package managers: Quicklisp is great, very slick and the ecosystem is very stable. When/if you encounter its limitations, you can use: Ultralisp, a Quicklisp distribution that ships every 5 minutes (but it doesn't check that all packages load correctly together), Qlot is used for project-local dependencies, where you pin each one precisely, CLPM is a new package manager that fixes some (all?) Quicklisp limitations
> [unicode, threading, GCβ¦] All of these features are left to be implemented by third-party libraries
this leads to think that no implementation implements unicode or threading support O_o
> most of the language proper is not generic
mention generic-cl? https://github.com/alex-gutev/generic-cl/ (tried quickly, not intensively)
Documentation: fair points, but improving etc. Example of a new doc generator: https://40ants.com/doc/
Also I'd welcome a discussion about Coalton (Haskell-like type system on top of CL).
-
Kons-9 update β 3D Common Lisp system now on MacOS and Linux
Great news! Feedback: I guess it's time to start working on documentation ;) The readme doesn't say what the system does. I guess you could maintain a high overview "manually", and in parallel set up a documentation system (40ants doc is kinda cool). Best,
-
Favorite Lisp project? Shameless plugs welcome & encouraged!
- and 40ANTS-DOC builder.
-
Why Turtl Switched from Common Lisp to JavaScript
That is why I've put about half of this year into the Common Lisp documentation generator for all of my libraries.
If you are interested, please read it's docs and join the effort of making good documentation for CL projects: https://40ants.com/doc/
-
CL-TAR Project
And the doc is built with the new https://40ants.com/doc π Really cool.
- Does everyone here manually specify the entire project's dependency tree in .asd files?
semver
-
The right development flow: Better than Agile
We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-releaseβ¦
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
What are some alternatives?
wookie - Asynchronous HTTP server in common lisp
react-native - A framework for building native applications using React
woo - A fast non-blocking HTTP server on top of libev
semantic-release - :package::rocket: Fully automated version management and package publishing
cl-lsp - An implementation of the Language Server Protocol for Common Lisp
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
weblocks - This fork was created to experiment with some refactorings. They are collected in branch "reblocks".
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
cl-permutation - Permutations and permutation groups in Common Lisp.
helmfile - Deploy Kubernetes Helm Charts
LispSyntax.jl - lisp-like syntax in julia
Poetry - Python packaging and dependency management made easy