#chapellang — Public Fediverse posts

Actually, I forgot how much I enjoyed writing this. It’s wildly out of date but after I had fixed the race condition (in a series of errors that led to said fix never happening here) it was pretty cool to watch hundreds or thousands of log files spin up so you could watch the flow of your program across many, many compute nodes.

I even kinda still like the aesthetics I defaulted for it. I think the way channels are handled in #chapelLang is way different now, though.

lessee... do I take my concerta and write up an FM synth in python or #chapelLang because I'm sick and need something to occupy myself... or should I just give in to the sickness and rest while continuing to watch stuff and play games... hmmmm.

@[email protected] I wonder if this is one reason why #chapelLang has an unmanaged memory declaration (you can mix and match for your variables). I'm sure the major reason is performance and ease of development since it's HPC focused and you wanna make sure the hot loop is hot , but honestly getting the lifetimes right in this sort of scenario would be a biiiiiiiitch for a lot of things.

(I think there's no synchronicity guaranteed with the tasking layer in Chapel so it's all more or less async; I could be wrong but).

(also, the full set is owned, shared, borrowed, and unmanaged)

@[email protected] On the other hand, it is fun to get to play around with implementing such a basic level of functionality for the modern internet. Especially since #chapelLang doesn't have an HTTP library.

this is one thing I really like about #chapelLang, which is that you can basically tell the compiler "fuck off, I know better".

#techPosting

Weird time to throw this out there, but I’m still looking for work! #getFediHired #getFediGigs #lookingForWork #tech

Contract or permanent, part time or full time, doesn’t matter! I’ve learned a lot of Rust recently and am proficient in C++, C, Python, TypeScript, JavaScript, shell, Linux, Cloud stuff, HPC, chemistry, simulations, MPI and scaling! Mostly backend but I can, and have, done full stack work on React!

What I’m mostly looking to do is help build software that helps people, so I’m NOT interested in “AI”, defense, finance, oil+gas, startups, or anything of that sort. If you know of open positions or even if you’re looking for someone to help on a project, let’s chat! I make a mean fucking #jupyterNotebook, too.

I am also totally available to tutor chemistry, too.

Boosts welcome and appreciated!

CV on request; see my codeberg profile here: https://codeberg.org/astatide

#rust #chemistry #tutor #tutoring #cpp #rustLang #chapelLang

@crawfordsm & any other NASA folks here:

I’m giving a talk at NASA on Thursday about the open-source Chapel Programming Language! This talk is arranged by the Heliophysics division at NASA Goddard & other sites will be able to join virtually. 1-2PM.

Would love to see you there! Also, I would really appreciate it if you can invite colleagues within NASA or advertise to other groups there.

I can email details — coordinate that with me in DMs.

#NASA #OpenSource #ChapelLang

@[email protected] I like how #chapelLang handles this type of stuff (back when I was writing more of it, which was a while ago admittedly); at the time, your serialization/deserialization stuff was the same stuff used to print to stdout, for instance, so you didn't have to write multiple variants...

Like one does with Debug and serde.

It'd be nice to find a job where I could write #chapelLang or #rustLang and NOT have it violate my morals (the Rust one in particular seems to be used by a lot of dorkass violent shitlords)

#chapelLang also makes use of borrowing (in fact, I learned it there first and found Rust's borrowing/lifetime stuff much easier to understand thanks to that), but in a different way: things can either be owned, shared, or unmanaged, with the lifetime of the first two being handled by the compiler and the lifetime of the last being up to you.

Since Chapel is aimed at the HPC/scientific world, it's perhaps not so surprising that they'd want to make an easy escape hatch to allow manual memory management (when you're running on tens of thousands of cores and paying for every moment, you wanna eke out all the performance you can get). Rust, on the other hand, coming from... actually, I know it came from Mozilla so I always assumed it had a sort of "we know that it's very bad in a 'stolen website/credentials' kind of way to have memory errors" reasoning but I guess I don't know.

#techPosting

@AmenZwa I agree that the linear order can cause problems. I would like to also point out that it can cause problems for compiler courses that follow it. In particular, a course might focus significant time on parsing, when in practice the theory of parsing is unlikely to be relevant to practicioners.

I’ve been working professionally as a compiler developer for #ChapelLang https://chapel-lang.org/ . If you have not heard if it, we are trying to make parallel computing much easier.

Speaking of toolbox, yesterday morning, I took a Dockerfile I'd made as a devcontainer (using toolbox/#podman) for #chapelLang on x86_64/amd64 systems, loaded it up on my M1 macbook running #asahiLinux, and built it... and everything just worked.

I expected failures, problems... literally anything but success. But it just built! Switching architectures and to an in-development operating system and the entire tech stack didn't even bat an eye? That's awesome, and I'm maybe more excited to continue working on my little MD/BD simulator than I was before (especially now that I can have a layer of separation between my host and development environment).

Pretty excited to spend some time working on a #chapelLang project again!

(full disclosure: used to work for Cray, and I have friends on the development team)

#chapel #chapelLang #programmingLanguages #podman #asahiLinux #M1 #apple #HPC

I've created a #blog post comparing the performance of standard library 'sort' calls in different languages. Chapel's sort uses composable parallelism to be 10x faster than other popular languages for a test sort on my PC.

https://chapel-lang.org/blog/posts/std-sort-performance/

#chapellang #rustlang #julialang #golang #radixsort