929 karma · joined September 20, 2012
IMO it's an open question. There is not much statically typed lisp AFAIK.
Performance, macros are executed at compile time. Also, sometime the macro is easier to write that the equivalent non-macro code.
1) Guile has no Global Interpreter Lock.
2) Guile is a scheme, so it is homo-iconic cf. https://en.wikipedia.org/wiki/Homoiconicity
3) Scheme (and lisp in general) are nice to write Domain Specific Languages.
4) Guile doesn't have a particular overhead for calling simple functions which makes it possibly as fast as C.
5) Guile has a very powerful object oriented programming framework beating by far Python and Ruby OO systems.
6) Guile is optimised for immutability which makes it for safer code.
7) Guile has Guix which has 'guix pack' command which is awesome cf. http://git.savannah.gnu.org/cgit/guix.git/tree/doc/guix.texi...
8) Guile has a lot of supporters cf. https://lists.gnu.org/mailman/listinfo/guile-user
9) Guile has awesome maintainers
Also, there is not a lot of packages. But programs written in Guile or using Guile tend to be of higher quality, cf. http://guildhall.hypermove.net/ and http://sph.mn/content/3e73
(define (create-app+ container init view)
(let ((state (init)))
(letrec ((spawn (lambda (proc)
(set-timeout (lambda () (proc state spawn)) 1000)))
(make-action (lambda (action)
(lambda args
(let ((new (apply (action state spawn) args)))
(set! state new)
(render)))))
(render (lambda ()
(set! container (patch container
((sxml->h* make-action) (view state)))))))
render)))
Basically it says that instead returning two values (first value being the new state and the second value being the intended side effect) it will only return the new state. But, it will take another argument with the state called spawn. The signature of actions is now state -> spawn -> dom-event -> state. Spawn will schedule the lambda passed as argument. I will change spawn to look more like apply, so that it takes the arguments of the lambda as argument. This will make testing easier.Also nowdays, word2vec is unrelated to the understanding of grammatical constructs in natural languages. It's simply said a coincidence or co-occurance of words. Grammartical interpretation of a sentence must be seens as a general graph whereas word2vec operate on the linear structure of sentences (one word after the other). If word2vec had to work on grammatical constructs it should be able to ingest graph data. word2vec works on matrices where the graphical representation of the grammar of sentence (POS tagging, dependencies, anaphora, probably others) is graph otherwise said a sparse matrix or a matrix with a big number of dimensions. (It seems to me machine learning is always about dimension reduction with some noise).
I am quite ignorant about the literature on the subject of machine learning operated to/from graphical datastructures.
It statistic based.
The project aims at making stackexchange website available offline.
Fix the memory leak that was found in wiredtiger branch.
Python
GPL3+
There is. «TIP: When there is something that people are asking for, and you don't know how to do it yourself, announce publicly that it is impossible." Or, propose a solution that is so awkward hopeless that it annoys real experts into stepping up.»
> Why are frameworks considered such a good thing
The only thing nice about framework is that they make the main workflow obvious. But things becomes scary when you walk on the wild side (backed by experience with Django and Django RESTframework)
The problem with reactjs is that facebook was using reactjs and its "architecture" for big apps and now they try to make it work in a more general context.
> in web UI programming that widely used and admired libraries end up being called "frameworks" as a term of respect?
Backbone is framework, saying it's a library because you can use only the collection model and use whatever method you want to fetch your data or whatever template language or bind events yourself is like saying you can replace the URL routing or template language of Django on your own. Doable but not recommended.
I think backbone is framework not a library it tackles several issues (class system, views, and middle end) and it does it badly but that's a topic of ~another post~ the past.
Historically Javascript community has favoured the do-it-yourself framework hence or because there is a lot of libraries you can choose from or because the needs of everyone are so different that's it's difficult to create a miningful framework. Mind the fact that Google previous "framework" named Google closure was a stdlib kind of framework compared to the competition of MV* framework like emberjs or angular it did not force a given workflow.