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.
codeq
-
Codebase as Database: Turning the IDE Inside Out with Datalog
This is a well composed idea. This reminds me slightly of (Rich's?) (Codeq)[https://github.com/Datomic/codeq] although this is really outlining code and scm logic and not syntax trees etc. I think I was always codeq would add something like this (for doing what you are doing to validate forms) but the input mechanism probably needed more hammock time
- The Database Inside Your Codebase
-
What comes after Git? It's been 15 years since it was created
He is referring to codeq: https://github.com/Datomic/codeq which has a last commit on 2014. But there have been recent rumours (https://medium.com/@sfyire/can-codeq-2-solve-clojures-weakne...) that Hickey is working in a new version of it. Fingers crossed!
restore
-
Pro-tip: TextEdit can restore previous versions of text files (including code)
I made a GUI version of that command-line utility called Restore.
-
I made a few Mac utilities
https://gitlab.com/jcfields/restore (download)
-
What comes after Git? It's been 15 years since it was created
Mac OS has a built-in file versioning system (separate from Time Machine) that works with any program that uses the standard document saving APIs. Most Mac users probably aren't aware that their computer stores potentially hundreds of previous versions of their documents (in evictable space, of course). The interface for it is kind of trash and isn't accessible in every app, though.
(Over the summer, I made a command-line (https://gitlab.com/jcfields/versions) and a GUI program (https://gitlab.com/jcfields/restore) for accessing this system outside of the standard UI, if anyone's interested, though the binaries are not notarized so the OS will show a scary warning the first time you use them.)
Granted, it's not exactly the same thing since you're not making commits at discrete and meaningful points like in a software version control system and since it works on an individual file level, which might not be ideal for every workflow, but it's still really useful when you realize you need to roll something back to an earlier state.
For Windows, I think modern versions use the Volume Shadow Copy service stores backups of files at given snapshot points (such as when your computer runs a scheduled backup or creates a System Restore point), which can be pulled up in the file properties. I use to use NTBackup to do basically the same thing in a more crude way back in the Windows XP days. This isn't as nice as the Mac Versions feature since it requires setting up periodic backups, but it's something.
I'd be curious if any of the free desktops have come up with a simple and user-friendly solution to this.
What are some alternatives?
semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
jedi - Awesome autocompletion, static analysis and refactoring library for python
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
dupver - Deduplicating VCS for large binary files in Go
wcag - Web Content Accessibility Guidelines
Glean - System for collecting, deriving and working with facts about source code.