DuncanvR / arnold

A Recurring Neat Occasion Likelihood Decider
0 stars 0 forks source link

POWEERRR!! #3

Open dhessing opened 9 years ago

dhessing commented 9 years ago

Seeing that I'm the only one with +/- 16 hours a day to program, I will take on me the responsibility to create the first implementation.

To stay true to the original intent of the application, I will build it using Clojure for the backend-end, Datomic as database and ClojureScript as front-end. This will ensure that the project will be completely over-engineered and never to be completed.

I leave all design-documents, documentation and architectural decisions to be written by people with actual CS degrees, and to be completely ignored by me.

Also I recommend changing the application name to the: Clojure Language Amazing Recurrent Known Scheduled Occasion Notifier, or CLARKSON for short.

Love, Dzjon

DuncanvR commented 9 years ago

Good to hear from you!

I love the completely over-engineered and never to be completed thought, as I imagine this entire project to be basically that. Since it's more of a sandbox for trying out stuff, we can make it as enterprisey as we want. And I'm pretty sure we'll be able to come up with some crazy things that are both hauntingly beautiful and needlessly complicated.

I've been meaning to try out git submodules for some time, and I think this project will be a pretty good occasion for it, with every implementation of the server or client as a module. That has the added benefit of the author being the owner, not needing pull request to merge in stuff, etc..

So may I ask you to do the development of CLARKSON in a separate repository? Maybe even separate ones for the client and server? And then of course another one for the common code shared between them as submodule --- We need to go deeper! I'll be sure to check it out and make silly suggestions from time to time!

Cheers, Duncan

jankramer commented 9 years ago

Yo dawg