Path: ...!news.mixmin.net!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Mild Shock <janburse@fastmail.fm>
Newsgroups: comp.lang.prolog
Subject: Re: Is Rust the culprit? (Was: What about the Holy Grail?)
Date: Mon, 22 Jul 2024 22:38:57 +0200
Message-ID: <v7mg10$6vai$1@solani.org>
References: <v32hjd$s3qh$1@solani.org> <v7g0du$475u$1@solani.org>
 <v7j9g9$643u$1@solani.org> <v7mem6$6uld$1@solani.org>
 <v7mf8r$6utd$1@solani.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 22 Jul 2024 20:38:56 -0000 (UTC)
Injection-Info: solani.org;
	logging-data="228690"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.18.2
Cancel-Lock: sha1:LSf9o65/hvqcctIKbkRLolARUN0=
In-Reply-To: <v7mf8r$6utd$1@solani.org>
X-User-ID: eJwFwQcBACAMAzBLg305O9S/BBJlOzYupiYKRaCoIzh4jBuvEuyPaCcCPYW8c1Fnb3fVPhNO50hyGsmVD3uQFlw=
Bytes: 3551
Lines: 82


Most likely Rust has not high performance computing
on its mind. This here looks horrible, and is the
same nightmare as in Go:

https://jondot.medium.com/errors-in-rust-a-formula-1e3e9a37d207

I would never port or realize a Prolog system on a
programming language and runtime, that doesn't offer
clever and efficient exception handling.

You don't get clever and efficient exception handling if you
shuffel around tuples. Althoug some of recent nodeJS
async programming had a similar flavor.

But still JavaScript has solid exception handling,
and so does Java and Python.

Mild Shock schrieb:
> If Rust is the culprit, I guess it isn't
> due to this speculation:
> 
> Imagine Rust failed, why did it fail?
> https://www.reddit.com/r/rust/comments/c93upr/imagine_rust_failed_why_did_it_fail/ 
> 
> 
> "climate change causes massively increased methane
> offgassing in the Arctic, causing a runaway greenhouse
> effect that eventually turns Earth into Venus,
> destroying the biosphere before rust
> can gain widespread adoption"
> 
> There are other signs that Rust is a failure, like here:
> 
> Why Rust is Making You Fail. --> 1.1k Claps
> https://medium.com/@ChadJohnsonOfficial/why-rust-is-stopping-your-success-use-c-and-c-instead-586dc7e2edbc 
> 
> 
> And here:
> 
> Should we call Rust a failed programming language? --> 10.5 views
> https://www.quora.com/Should-we-call-Rust-a-failed-programming-language
> 
> Mild Shock schrieb:
>> Maybe Scryer Prolog is a failure, because Rust
>> is a failure. Building Scryer Prolog on my machine,
>> after a git pull of a small change, did just
>>
>> take this much time:
>>
>> $ time cargo build --release
>> [...]
>> real    6m52.663s
>> user    7m39.043s
>> sys     0m3.241s
>>
>> What did Rust do? And this tabling test case,
>> 2000 shuttle, hangs:
>>
>> /* Scryer Prolog 0.9.4-107 */
>> ?- use_module(library(tabling)).
>>     true.
>> ?- [user].
>> :- table c/1.
>> c(X) :- c(Y), 0 =< Y, Y < 20000, X is -Y-1.
>> c(X) :- c(Y), -20000 < Y, Y =< 0, X is -Y+1.
>> c(0).
>>
>> ?- time(c(_)).
>> %%% hangs ? %%%
>>
>> It is solved in a blink in SWI-Prolog:
>>
>> /* SWI-Prolog 9.3.8 */
>> ?- time(c(_)).
>> % 540,077 inferences, 0.047 CPU in 0.051 seconds (92% CPU, 11521643 Lips)
>> true .
>>
>> The test case is from here:
>>
>> https://github.com/JanWielemaker/tabling_benchmarks/tree/master
>