VectorScriptTools
p50em
| VectorScriptTools | p50em | |
|---|---|---|
| 1 | 3 | |
| 0 | 40 | |
| - | - | |
| 10.0 | 0.0 | |
| over 11 years ago | about 3 years ago | |
| PowerShell | C | |
| The Unlicense | 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.
VectorScriptTools
-
What is the most interesting thing you have created that you are still proud of?
The Kludgeomatic.
https://github.com/brudgers/VectorScriptTools/tree/master/Kl...
Vectorworks 2008 was scripted in a Pacal variant that required compiling. Creating a script required many "bureaucratic" operations.
More bureaucracy to load the script to test it.
Looking back, I think in all seriousness that punchcards were the point of reference for the programmers who came up with it...that the development tooling was designed to digitalize a punchcard workflow.
Coming from Autocad, I wanted a scripting workflow that looked like its. Put a list of commands in a text file and they would be run through in order.
That's the background...well that and the sub-prime mortgage meltdown bringing about a future with no work -- be careful what you ask for.
The Vectorscript documentation allowed scripting Vectorworks "tables" -- a spreadsheet like data structure.
Vectorscript also had an evil...I mean eval. [1]
Thus, Kludgeomatic.
From within the drawing I could open one those internal "spreadsheets" and create an ordered list of API calls to Vectorworks commands, and run that list with the click of a button.
Since the spreadsheet was a drawing object, it would be saved with the drawing and could be externalized into a library like an other drawing object for use in other projects.
I thought I was on the road to fame and fortune.
I was wrong about that, but it is still really cool.
[1] Later I wrote a script that could execute arbitrary code the users computer. Digitalized punch cards, like I said.
p50em
-
What is the most interesting thing you have created that you are still proud of?
Emulator for a Prime minicomputer system from the late 70's to early 90's:
https://github.com/prirun/p50em
-
Ask HN: What is the most complex topic you understand?
The Prime minicomputer architecture, from the 80's. Competed with Dec VAX, Data General Eclipse, etc.
The Prime architecture was based on the Multics design from a group of guys hailing from Honeywell and MIT. I worked on Primes for around 12 years, worked for Prime briefly in the 80's, and wrote an emulator that runs many versions of Prime's OS, Primos: https://github.com/prirun/p50em
Prime systems are very much the opposite of RISC, with instructions for:
- process exchange and task scheduling
- procedure call, incl arguments, ring crossing, stack handling, register saves
- decimal arithmetic, incl picture editing for COBOL & PL/I
- string instructions and picture editing
- 6 CPU modes for compatibility with older processors
- DMA, DMC, DMT, DMQ I/O modes for controller access to memory
- 32, 64, and 128-bit floating point
- 2.3k Patch Would Improve Linux Build Times 50~80% & Fix “Dependency Hell”
What are some alternatives?
nand2tetris-fpga