139 karma · joined June 29, 2018
$ sudo wc -l /var/log/syslog
4982 /var/log/syslog
$ sudo cat /var/log/syslog | bash -c "time gonzo"
real 6m13,359s
user 6m42,317s
sys 0m28,946s
Six minutes on my virtual machine for 5 thousand lines.https://github.com/rybbit-io/rybbit/blob/master/server/GeoLi...
<link rel="icon" href="data:image/png;base64,iVBORw0KGgo=">> The reverse predicate from this section should not be used in practice - most Prolog implementations actually provide a built-in version which is a lot more performant than our implementation.
I think it can be read as: If you care about speed do not use Prolog, instead write a "built-in" solution.
On the other side Go's errors are more work for the programmer and they clutter the code. But if you consequently wrap errors in Go, you do not need stack traces any more. And the advantage of wrapped errors with descriptive error messages is: they are much easier to read for non-programmers.
If you want to please the dev-team: use exceptions and stack traces. If you want to please the op-team: use wrapped errors with descriptive messages.
> A great standard library is a cornerstone of your PL success.
{def PAIR {lambda {:a :b :c} {:c :a :b}}}
What is :c if called with two arguments? And what is its application?
> Arm says it wants all Snapdragon X Elite laptops destroyed
Not so useful.
Suggesting that the macros of C and Rust may be the same is an insane failure.
BTW: meta-programming means "code which generates code" and not "code which runs earlier than other code".
The cheapest HP desktop in Germany costs more than 500€: https://www.hp.com/de-de/shop/list.aspx?fc_form_mini=1&fc_fo...