Earlier quoted context omitted.
tl;dr - I'm upset because the raison d'etat for Go's name doesn't exist. Correct, no -- practical, probably. No matter how many gophers swear that {searchterm} + go returns just as good of results as {searchterm}+golang, it just isn't true. Maybe I'm just bitter because the reason Go was named Go was because -- and obviously I'm paraphrasing here... "we thought Oogle would be a really cool name for a debugger." Years…
The debugger on plan9, acid, is a work of art.
Prolog interpreter in Go
21–24 of 24 posts
Re: Prolog interpreter in Go
#22Earlier quoted context omitted.
What problems are they? I'm interested in Prolog but never encountered something I thought would be a good fit (or perhaps I'm not thinking about it the right way)
Some examples: Combinatorial optimization problems, timetabling tasks, reasoning engines, rule-based systems for the medical industry, recommender systems etc.
Re: Prolog interpreter in Go
#23Earlier quoted context omitted.
Prolog interpreter is unlikely to be able to meet your performance needs although it would be a great ui. Search datalog and bdd and you should be able to find some good research and tools using bdd to support source code analysis related queries.
I thought about using datomic for this before. I've seen a Java based bdd data log tool for pointer analysis. Though it was hard to play with Iirc. I think it would be slow but good for prototypes.
Either way, email's in my profile. We should talk.
Re: Prolog interpreter in Go
#24Earlier quoted context omitted.
I thought about using datomic for this before. I've seen a Java based bdd data log tool for pointer analysis. Though it was hard to play with Iirc. I think it would be slow but good for prototypes.
Is this you? https://github.com/achambers16 Either way, email's in my profile. We should talk.