30 karma · joined June 19, 2013
Edit: related follow up: any chance this technique is a good fit for enumeration of [Magic Squares][0] of a given order?
But not all weirdly shaped districts are bad. Between the two latino communities in that area, there is a predominately African-American community. By joining two latino communities together into a single district, it ensured that they had a representative serving their interests. This district in particular was featured in [a recent LastWeekTonight episode][2].
[1]: https://en.wikipedia.org/wiki/Illinois%27s_4th_congressional... [2]: https://youtu.be/A-4dIImaodQ?t=684
We build SaaS B2B2Cs for SMBs in the property management and legal spaces. We work with Ruby on Rails & ES6 JavaScript, including React.
I think the "obvious solution" is just not super easy to implement. If you want ACID compliance as with traditional RDBMSs but in a auto-scaling, distributed setting, it's not going to happen. Early RDMSs were built with a single node in mind, and any database-as-a-service will have to make some compromises. DynamoDB gives you the flexibility of not having to worry about scaling, and even offer strongly consistent reads, but without support for transactions, for example.
For example, take a look at problem 2.07 from the original 99-problems for [Prolog][1] and compare it to the [Java][2] solution in the linked repo. In Prolog, you're defining relations, so with GCD defined, you can compute the GCD (g) given two integers a and b, but you can also compute possible values for b, given a and g, for example. The Java solution doesn't allow for anything like that.
So, given the README information, I expected to see the implementations in different language platforms utilize some prolog-esque logic programming library (like core.logic for Clojure), but that isn't the case.
[1]: https://sites.google.com/site/prologsite/prolog-problems/2 [2]: https://github.com/shekhargulati/99-problems/blob/master/jav...
http://millcomputing.com/wiki/Instruction_Set_by_Category#Si...
> The way that LISP/c works is sort of tricky. It utilizes a lot of string manipulation and interpretation. It doesn't need to be insanely fast, though, because it's just dealing with code; the compiled result will not suffer from any slowness.
In other words, it seems that this project just allows you to generate C code from a LISP-like syntax, but doesn't allow you to `eval` during the execution of the resulting C program. There is no runtime representation of code as data as with other lisps.
I think it might be too to do a write-up. I definitely learned a lot doing it!