Thanks for the info. I went through what I had thought was enough Show posts to find it, but apparently not enough :-( I haven't been on Hacker News in a few years and forgot how it works - I should have checked my submissions section. Though some websites mention that it can be hard to detect shadowbanning, so perhaps even checking submissions wouldn't have been enough. Good to see my post is still public.
Thanks for the info. I went through what I had thought was enough Show posts to find it, but apparently not enough :-( I haven't been on Hacker News in a few years and forgot how it works - I should have checked my submissions section.
I usually don't put a license in my repos, sometimes because I never really know which one to put in, and other times because I don't really know what I would want to allow or disallow, etc. I put a license on my vec-mat-comp-quat repo but that was because it was essentially a library so by its nature, it would have to be used in other people's code. The license I chose required (IIRC) or perhaps requested, that the users let me know how they use my library, but to this day, no one has - so that's another reason I don't usually put a license (people will probably ignore it anyway).
In regards to your story of essentially the path not taken: in general when I create a version that either doesn't work or doesn't work as well as I wanted, I keep the file around (renamed usually). Sometimes, much later I figure out how to make it work or some part of it becomes the basis of another project. Unless I didn't spend much time on it, I don't like to waste effort. The PDF addition was kind of an example of that - I kept the file around, but then when I was prettifying things up to upload to github, I figured I would add the PDF code to my file and put it within #ifdef's in case someone would want it. And also, in case you haven't noticed, I provided many different versions of the search system - it's harder to maintain, but allows the user to pick the option they like the most. So, in your case, you never know if the paths not taken might someday be paths you will want to go down.
For my own selfish purposes I would like to have a license that allowed me to reuse parts of SearchEngineSuite as if it was a library, for instance Apache 2.0 which I used for my C preprocessor at https://sentido-labs.com/en/library/cedro/202106171400/
I am preparing a pull request adding the Apache license in case it is acceptable for you.
I hope this post isn't against some written or unwritten rules (I know it doesn't meet the requirements of Show HN).
This is a modified version of my CPU design which was a homework assignment in one of my college classes 32 or so years ago. I originally drew the design on paper (homework), and a few years ago, I put it in Logisim. Since I don't have an FPGA board, I gave my design to Dr. Kevin Walsh, and he ran it (with his modifications (mostly cosmetic)) on his FPGA.
If you want to see the progression of this project, you can view my playlist:
If you want to learn basic x86 assembly language or Win32 API (Windows) programming, here's a relatively simple program which would likely be helpful (especially combined with the tutorial videos listed on the github page). Or just enjoy some nice fractals. In short, I haven't left Windows users out in the cold.
a bit late to the party, but how hard would it be to adapt it to linux or mac? The assembly part should be the shame, isn't it? (ignoring non-intel macs)
I already ported it to Linux... Here's a link to my hackernews post: https://news.ycombinator.com/item?id=27565708
I decided not to use inline assembly for the linux version (since I absolutely hate how gcc does inline). So the assembly routines are in .asm files which are assembled by nasm and linked in.
I don't know about Mac. Mac OS (not original Mac OS though) is based on Unix/Linux, so it might not be hard to do, don't know. Someone told me Macs now typically have x86 based CPUs (though that will probably change soon), so the assembly shouldn't be a problem.
I don't know if I would recommend it, but I've noticed that in the past, whenever I moved to a different type of computer/OS (Amiga, MS-DOS, Windows, etc.) or language (Java, Javascript, etc.), I ported my biorhythm program to the new system/language. It starts out simple - just strings, math, file/screen input/output, then progresses to graphical plotting of the biorhythm curves. It's a simple algorithm. Disclaimer, I don't know if I believe in biorhythms, it's just something interesting and a flashback to my childhood in the 70s.
Basically, I would say the easiest way would be to choose something you've already conquered in a language/system you already know. That way, you're only tackling one new thing.
BTW, it wasn't always biorhythms for me - I originally wrote my Mandelbrot program in Pascal, and taught myself C in order to convert it to C so it would run faster.
Coincidentally, my biorhythm program would tell you various things about yourself (birthstone, zodiac traits, yin/yang, Chinese animal, numerology, but also the phase of the moon the day you were born). Yeah, I threw in everything I could find/calculate.
If you want to learn basic x86 assembly language or XWindow / Motif programming, here's a relatively simple program which would likely be helpful (especially combined with the tutorial videos listed on the github page). Or just enjoy some nice fractals.
reply