<div dir="auto">The backend compile process is horrifyingly slow. But when the eventually approved and compiled code will be run every hour or so for the next 3-5 years, and that code requires MPI interconnection to 100-800 other nodes to run on every hour, devel/compile time starts looking to be less of a problem.<div dir="auto"><br></div><div dir="auto">Pretty sure the heat generated to predict the weather has small but non-zero impact on the weather :-)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 17, 2024, 6:04 AM Jon "maddog" Hall <<a href="mailto:jon.maddog.hall@gmail.com">jon.maddog.hall@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">It all depends on the implementation, but some interpretive languages are fairly fast at execution. The interpreter takes the source down to atoms (or "beans" if you go that way) and then feeds them to a very optimized run-time system.<div dir="auto"><br></div><div dir="auto">Interpretive vs compiled also needs to be looked at the ratio of run time vs development. In a learning situation you may only run a program once for every time you compile it. An interpretive language is much "faster" (and less of a resource hog) than running an edit/compile/link/execute cycle.</div><div dir="auto"><br></div><div dir="auto">md</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 16, 2024, 21:36 Jim Kinney via Ale <<a href="mailto:ale@ale.org" target="_blank" rel="noreferrer">ale@ale.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Compiled code. Still do FORTRAN when it has to be fast. Still do C if I need to burn up a monitor (oops!). But you can't learn it if you can't see it, touch it, and change it. The scripting languages are easier to learn and definitely have a place. And they are now the gateway to programming. They're not perfect and they slurp down hardware. I can't imagine python trying to run in the days of BASIC on an early pc jr. :-)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 16, 2024, 8:33 PM jon.maddog.hall--- via Ale <<a href="mailto:ale@ale.org" rel="noreferrer noreferrer" target="_blank">ale@ale.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<div style="font-size:12pt;font-family:helvetica,arial,sans-serif;color:#333333">
<span style="font-family:helvetica;font-size:12pt">Chuck,<br><br>Many people did not recognize the benefit of pulling down the source code and typing it in by hand.<br><br>"Wow! What does that error mean? I typed it in just like....oh...I made a mistake!"<br><br>You had a syntax error, and BASIC showed it right away (most of the time anyway).<br><br>But maybe your syntax was correct and your program still did not work. Maybe the error was that you meant to type "2" and you typed "3' by mistake....a "run-time error".<br><br></span>You do not get to create or fix these problems if all you do is pull binaries off the web or load them from a CDROM.
<br>
<br>This was EXACTLY why the professors at Cambridge University started the Raspberry Pi project. They realized that the freshmen of today often knew less about computers than the freshmen of 20 years ago...the ones who 20 years ago downloaded source code and (in some cases) even had to COMPILE it and LINK it in order to run it.
<br>
<br>Happy Birthday, BASIC!
<br>
<br>md
<br>
<br>
<br>
</div>
<blockquote type="cite">
<div>
On 05/08/2024 8:10 AM EDT Chuck Payne via Ale <<a href="mailto:ale@ale.org" rel="noreferrer noreferrer noreferrer" target="_blank">ale@ale.org</a>> wrote:
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
I am surprised that this one didn't get an email. Happy Birthday BASIC, it turned 60. It only three years older than me, and has more functions than me too.
<div>
</div>
<div>
<a href="https://www.tomshardware.com/software/programming/the-basic-programming-language-turns-60-dartmouth-basic-started-it-all-in-1964" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.tomshardware.com/software/programming/the-basic-programming-language-turns-60-dartmouth-basic-started-it-all-in-1964</a>
</div>
<div>
</div>
<div>
As a kid, I got into BASIC because it was the way to get games. I forgot the name of the magazine, but I would buy it every month and sit at my VIC 20, trying the code in, playing such games and Oil, where you drill to get oil hoping to hit a pocket with a devil in it. Or trying to understand what the data fields were doing.
</div>
<div>
</div>
<div>
Since I missed the 4th as well, here some BASIC Code for you guys
</div>
<div>
</div>
<div>
<a href="https://www.goto10retro.com/p/star-wars-theme-in-basic" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.goto10retro.com/p/star-wars-theme-in-basic</a>
<br>
<br>Yes, I was one of those kids that would type some weird messages on the computers tha would repeat, like
<br>
<br>10 print "Long live ALE, bring more beer"
<br>20 goto 10
<br>
<br>Happy Computing guys
<br clear="all">
<div>
</div> <span class="gmail_signature_prefix">-- </span>
<br>
<div class="gmail_signature" dir="ltr" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
Terror PUP a.k.a
<br>Chuck "PUP" Payne
<br>-----------------------------------------
<br>Discover it! Enjoy it! Share it! openSUSE Linux.
<br>-----------------------------------------
<br>openSUSE -- Terrorpup
<br>openSUSE Ambassador/openSUSE Member
<br>skype,twiiter,identica,friendfeed -- terrorpup
<br>freenode(irc) --terrorpup/lupinstein
<br>Register Linux Userid: 155363
<br>
<br>openSUSE Community Member since 2008.
</div>
</div>
</div>
</div>
</div>
</div> _______________________________________________
<br>Ale mailing list
<br><a href="mailto:Ale@ale.org" rel="noreferrer noreferrer noreferrer" target="_blank">Ale@ale.org</a>
<br><a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a>
<br>See JOBS, ANNOUNCE and SCHOOLS lists at
<br><a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a>
</blockquote>
</div>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" rel="noreferrer noreferrer noreferrer" target="_blank">Ale@ale.org</a><br>
<a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" rel="noreferrer noreferrer" target="_blank">Ale@ale.org</a><br>
<a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>
</blockquote></div>