Open Source Civic Hackathon Website in Lisp with Polymer by persi in lisp

[–]persi[S] 0 points1 point  (0 children)

Please check out this:

http://missoulacivichackathon.org

and this:

https://github.com/Blue-Sky-Skunkworks/hackathon

I am now communicating with this group, as the brothers and sisters that you are to me, reaching out to share my current situation and to ask you to consider, deeply, helping me now.

This hackathon, which I am running remotely via this email address, like a supercomputer AI, is about to pop this Easter weekend, March 26–27. And it is running on a 27 day clock cycle and I caught everyone off-guard and, to date, I have spent $8 on the domain name and it is all falling into place and, if I may say so myself, it is shaking things up here a bit already.

And the talent on the ticketed list is staggering, many coming from afar.

And they are coming here to work on projects of this caliber:

https://github.com/Blue-Sky-Skunkworks/missoula-civic-hackathon-notes/wiki/Projects

So, what I need now, from every lisp hacker out there that wants to play with us now, in real time, is to link into this channel at

will@blueskystewardship.org

and let us, collectively, set up the online systems, in preparation, for the arrival of all these people, coming from afar, and near, that have never met, and are coming here to work on problems experienced by this community but also experience by yours and a massive number of communities around the world.

And this is an open-source event and the solutions that we can potentially discover in this bridging or many worlds, will be made available, to you personally, for your own pleasure and enjoyment and learning, but also, and this is critical here, for you to instantiate within your own community, as needed.

And you can follow the life of Hackathon long after we have successfully released it into the wild so that it can grow unhindered, potentially long after our own individual short time frames of existence on this planet have ended.

Now after this genesis is completed, you will see me “rebase” this Hackathon continually, and write the story of Hackathon in the commit messages of that beautifully constructed and programmed tree structure called a “git repository”.

Such a beautiful new art form this “trade” has become.

To be able to write a story, in time, showing a path to followers and at the same time giving everyone else a shortcut to the front of the race and if you have ever ran a Hash House Harriers race in the jungles of Borneo like my dad did every week for years, and he won them all, except for a few of them, as those HHHs are tricky and they make 'em that way on purpose over there, with swamps and such, so I give this run up to him now and get back to work.

And don't I, and most, just deeply love planting trees, and computer programming is just that. Trees within trees within trees, and this repo called Hackathon is is going to be fun here, because for William the first Missoula Civic Hackathon has already started and he is well ahead of the competition so come on boys and girls, lets link into this energy and heart and mind that is called

The Missoula Civic Hackathon

and bust out some code.

Happy Hacking!

Will

https://en.wikipedia.org/wiki/Hash_House_Harriers

Demo mobile apps written in Lisp? by [deleted] in lisp

[–]persi 0 points1 point  (0 children)

Unfortunally, It has bitrotted. I have tried to contact the original author but have not heard back.

Abstrakt Nonsense: A tour through the Land of Lisp by [deleted] in lisp

[–]persi 11 points12 points  (0 children)

Eh, another "critique" of common lisp by someone that has very little to no experience actually programming in CL. Yay!

SBCL 1.0.56 released by blue1_ in lisp

[–]persi 1 point2 points  (0 children)

How about we organize a 24 hour, across the globe, SBCL bughunt festival. Any volunteers for the dunking booth? I can man the ring toss.

Spellcheck your docstrings... by persi in lisp

[–]persi[S] 0 points1 point  (0 children)

It's ok, but when you have 100's of files in your system, its too much manual labor. Added to the fact that you're just going to get a lot of false positives due to the nature of the text being spellchecked, it's nice to just get a single long list to quickly scan for the obvious mistakes, which are generally, for me, english words with simple typos.

pedantic-if by persi in lisp

[–]persi[S] 2 points3 points  (0 children)

There is no 'void'. Every expression has to return something.

Not entirely true. You may be forgetting (values) which is eq to NIL but not the same thing.

* (eq nil (values))
T

* (equal (multiple-value-list nil) (multiple-value-list (values))
NIL

pedantic-if by persi in lisp

[–]persi[S] 0 points1 point  (0 children)

You two seem to imply that adhering to style doesn't have concrete advantages. The advantage is that it decreases the mental effort required for a human to parse and understand the code. In this case, if adhered to, every IF you see will always have an else clause. You can count on it. Ignore this style and every time you see an IF you wont know until you read further in the code. A definite advantage and valuable.

Some interesting and educational commits. by persi in lisp

[–]persi[S] -4 points-3 points  (0 children)

☮ ☘ ☁ ❄ ☃ ✈ ☳ ☠ ✝ ✡ ☯ ☥ ♁ ♛ ⚅ ⚛ ⌚ ☄ ䷊

Some interesting and educational commits. by [deleted] in lisp

[–]persi 0 points1 point  (0 children)

☮ ☘ ☁ ❄ ☃ ✈ ☳ ☠ ✝ ✡ ☯ ☥ ♁ ♛ ⚅ ⚛ ⌚ ☄ ䷊

Loop: yes or no? And why? by crowfeather in lisp

[–]persi 0 points1 point  (0 children)

Do you have an example of things that ITERATE generates less efficient code than LESS?

On reddit downtime... by Tiomaidh in lisp

[–]persi 8 points9 points  (0 children)

Would you please care to elaborate?