When I was teaching Prolog are the university, I always introduced it as a niche language. “Prolog makes you unbelievably fast at very specific tasks, but don't try to implement a web server in it.”
Mercury, which is Prolog inspired, is actually a very interesting underrated language!
I think languages need to lean harder in the direction of doing more with functions than just evaluating them. Unification is one example, but you can imagine more.
Straightforward searching through combinatoric spaces for planning and optimization, including robotic and eg. discrete investment planning for models where solutions can't be described by a finite number of variables (see [1] for in-browser container logistics planning).
Composition of programs with complex rule-based semantics and large specs (the Prince CSS renderer is written in Mercury).
Diagnostics, capturing legal, medical, and other taxonomic knowledge in executable form, possibly as implementation, extension, or replacement for semantic web stuff and description logic.
All of the above with easy and powerful DSL capabilities ranging from built-in customizable operator precedence parsing, over natural recursive descent parsing with backtracking, to attribute grammars and arbitrary logic (Prolog started out as a 70's natural language understanding approach employing logic grammars).
Define a model of your program’s state, as if you’d define a model in a database. There, that’s your program! It is actually a database. You can’t create invariants in the program. It’s entirely defined by how you modeled it. Your program is correct.
IIRC (it's been years), a highly-conformant Perl5/Perl6/python/javascript regex engine core in SWI Prolog was concise and performant. Like "wow, it just one short file" concise. And "KISS competitive-with-little-optimization" performant. Modulo memory halo. IIRC, far more effort went into bootstrapping grammars and creating testing infrastructure. It helped warped my perspective on how concise and pretty compiler guts could/should be.
I agree something like that would be really cool. If you have any ideas for the API, feel free to make an issue on the php or trealla-js repos to discuss.
I'm in the Prolog Discord (invite code: https://discord.gg/pUFm3Tjq), if you're OK with that. I understand if you prefer IRC but I don't currently have a good setup for it unfortunately. I'll add that to my TODO list :)
<!-- is this a quine? -->
<section>
<h2>Source Code</h2>
<pre><?=Source current_file(File), read_file_to_string(File, Source, []) ?></pre>
</section>
No but it’s cute! Sorry if I butchered the indentation, I meant to preserve the tabs (tabs rule!), but I don’t know how to do that on my phone (spaces suffice).
Hey, this is mine. Thanks for submitting it. I'll answer some questions.
> Why?
I ported Trealla Prolog to WASM (WASI) and I was looking for something useful to test it against. I found Spin, which can run WASM+CGI, and landed on this. Making this project exposed a number of bugs in my port that have now been fixed, so consumers of more useful projects[1][2] benefit as well. Also, PHP style templates are just fun! There's something valuable to just being able to shove a little bit of code inside some HTML and get it up on the internet.
I started my webdev journey with PHP many many years ago, and it's nice to revisit it from a different perspective. I don't use the real (elephant) PHP anymore, but I've gained a newfound appreciation for how fun its quick & dirty development style is.
I hope this project can serve as an example of how to use Prolog for fun things. It does showcase some of the cooler dynamic aspects of the language, and the PHP parsing code is like 10 lines of DCG.
> Is it a joke?
Yes and no. The name is certainly a joke. I was pondering what 'Prolog on Rails' might be and thought calling it PHP would be funny. This led to the PHP-style templates which were quick to implement and pretty powerful. Despite the humorous presentation, it does actually work.
I would like to support persistence somehow. I think it'd be really cool if you could use Prolog's dynamic database[3] as a persistent store. Spin has components for Postgres and Redis so it shouldn't be too hard to implement, but I lose the WASI compatibility if I do that... which means I can't use the binary from WAPM, etc.
I would also like to experiment with running Trealla on Cloudflare Workers. I have another project, worker-prolog[4], which uses Tau Prolog (a Prolog written in Javascript) on Workers.
On a somewhat related note, I've also been playing around with Cosmopolitan libc[5]. I got Trealla to compile to an APE executable but there's some issues with the embedded Prolog libraries getting garbled, so I need to improve my GDB skills and figure out what's going on there.
Finally, I'd like to say thanks to Andrew Davison (@infradig on GitHub), the author of Trealla Prolog, for letting me add WASM support to his project and helping me with lots of things. For example, PHP led to Andrew implementing improvements for using DCGs to parse Prolog terms, which is now super fast[6]!
A rather annoying one at that.The "PHP, a fractal of bad design" blog post is completely, hopelessly outdated and yet people still quote it. PHP 8.0 got released in 2020 and people still cling to a post from 2012. It's mighty annoying. It's like lambasting JavaScript for all the things ES6 fixed eight years ago.
I think you're reading too much into it. This project is more of a love letter to PHP than an attack on it. Some of the criticisms from the "fractal of bad design" post apply equally to Prolog, like the stuff about inconsistent naming and argument positions.
It's indeed easy to shit strings into HTML pages without consideration for context, escaping, and quoting, also known as injection attack vulnerability when sourced from user content, and plaguing PHP sites to this date.
A better approach (and like processing instructions also from SGML's tool box) would be to use entities/text macros.
I was so wrong! :-D