RVS_ParseXMLDuration
kons-9
RVS_ParseXMLDuration | kons-9 | |
---|---|---|
2 | 50 | |
1 | 549 | |
- | - | |
1.9 | 7.9 | |
almost 2 years ago | 6 months ago | |
Swift | Common Lisp | |
MIT License | MIT License |
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.
RVS_ParseXMLDuration
-
Ask HN: Show me your half baked project
Well, these ones aren't "half-baked," but they are no longer being maintained (archived):
[0] https://github.com/RiftValleySoftware/RVS_IPAddress
[1] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration
[2] https://github.com/RiftValleySoftware/RVS_ONVIF
This project is unfinished (I just walked away from it, as it wasn't really giving me what I wanted):
[3] https://github.com/RiftValleySoftware/RVS_GTDriver
This one is "half-baked," I believe. I never really took it particularly far:
[4] https://github.com/RiftValleySoftware/RVS_MediaServer
-
Code Colocation Is King
Not completely. The way that it works for me, is that I start work on a project, and, while building, I notice that some code that I'm working on is:
1) Pretty complex, and fairly insular; and/or
2) Possibly useful, elsewhere.
If that's the case, I will then stop work on the main project, and take some time to extract and "genericize" the subproject. I'll usually set it up as a standalone open-source project; complete with tests and documentation.
This may happen before I have completed the coding in the main project, or may happen as the result of a review, after the fact.
In some cases, I very clearly need to develop a subproject before starting on the main project, or before certain milestones within that project (for example, SDKs or drivers). In that case, the timelines are completely separate.
If you look at my GH repos, you'll see a whole bunch of these projects, including some rather strange ones, like an XML duration parser[0]. These are the types of projects that I extract.
In some cases, I end up not using the extracted project in my main project (happens to some of my UI widgets). In that case, even though I am not using it, I still have an excellent project for the future. Here's an example[1]. I have ended up not using the spinner in my own work, as it was too obtrusive a widget, but it's nice to have it available for future projects.
[0] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration
[1] https://github.com/RiftValleySoftware/RVS_Spinner
kons-9
- OpenSCAD Survey - what programming language do you want to be added to app?
-
Lindenmayer Systems
Very cool. I must check this out.
I implemented some L-system features in my 3D Common Lisp system: https://github.com/kaveh808/kons-9
- Ask HN: Show me your half baked project
-
Profound Beliefs
In some small way I am revisiting the idea with https://github.com/kaveh808/kons-9
We'll see what comes of it.
- Kons-9: Common Lisp 3D Graphics Project
-
Symbolics Lisp Machines Graphics Demo (1990)
I began my 3D graphics development on a Symbolics workstation at the MIT Media Lab in the mid-80's. This was before the S-Graphics suite was released. [0]
The outstanding feature of the S-Graphics suite was the polygonal modeler which used a winged-edge structure that was far ahead of its time. It survives conceptually in the Wings3D system, which is a quite faithful copy of that modeler.
And of course you got the extensibility that came with the graphics system being built on Lisp.
But Symbolics was never, as far as I saw, a serious or popular contender in 3D production. Not only was the system expensive, but the hardware could not keep up with SGI's graphics abilities. Furthermore, the mass of CG developers at the time came from a C/Unix background, and rendering especially was so speed critical that C (and Fortran) resulted in faster systems.
Almost 40 years later, I have returned to the idea of developing a 3D system in Common Lisp [1]. We shall see where it leads.
[0] https://medium.com/@kaveh808/late-night-lisp-machine-hacking...
[1] https://github.com/kaveh808/kons-9
- Ask HN: Resources for Older Developers?
- Ask HN: What Are You Working On? (May 2023)
-
A good codebase to study as a beginner
If you are interested in 3D graphics, I have tried to keep my code simple and comprehensible: https://github.com/kaveh808/kons-9
-
Coding alone vs coding in a team
As a solo developer of my 3D system, my main focus has been to keep the enthusiasm and momentum going and to enjoy the development process, rather than worrying about how the code might not be optimal in various regards.
What are some alternatives?
laminarmq - A scalable, distributed message queue powered by a segmented, partitioned, replicated and immutable log.
clog - CLOG - The Common Lisp Omnificent GUI
typocide - Where Typos Meet Their Demise!
quicklisp-projects - Metadata for projects tracked by Quicklisp.
ukey - Simple ukulele chord reference web app
McCLIM - An implementation of the Common Lisp Interface Manager, version II
prepareprojectforllmprompt - Transform your code project into a Markdown document optimized for interaction with Language Learning Models like GPT-4, complete with dynamic file selection and token management features.
clozure-cl - Unofficial mirror of Clozure CL
speech - A tool to practice English speaking
weird - Generative art in Common Lisp
quantraserver - Distributed QuantLib
bodge-nuklear - Thin wrapper over Nuklear for Common Lisp