First day of the #GPGPU course at #UniCT. Class is small, but students seem curious, gave me the opportunity to discuss in more details some things that usually go unmentioned. Hopefully it'll hold.
Only negative side, I had to take a longer route home because the park between my house and the university was closed 8-(
So I found https://github.com/tracel-ai/cubecl which allows #gpgpu in #rust. Already using it to calculate some determinants for triangulations. Wondering if it can be leveraged to build a numeric #pde solver
@enigmatico @lispi314 @kimapr @bunnybeam case in point:
#Bloatedness was the original post topic and yes, due to #TechBros "#BuildFastBreakThings" mentality, #Bloatware is increasing given that a shitty bloated 50+MB "#WebApp" with like nw.js is easy to slap together (and yes I did so myself!) than to put in way more thought and effort (as you can see on the slow progression of OS/1337...
Yes, #Accessibility is something that needs to be taken more seriously and it's good to see that there's at least some attemots at making #accessibility mandatory (at least in #Germany, where I know from some insider that a big telco is investing a lot in that!) for a growng number of industries and websites...
And whilst one can slap an #RTX5090 on any laptop that has a fully-functional #ExpressCard slot (with #PCIe interface, using some janky adaptors!) that'll certainly not make sense beyond some #CUDA or other #GPGPU-style workloads as it's bottlenecked to a single PCIe lane of 2.0 (500MB/s) or just 1.0a(250MB/s) speeds.
Needless to say there is a need to THINN DOWN things cuz the current speed of #Enshittifcation and bloatedness combined with #AntiRepairDesign and overpriced yet worse #tech in general makes it unsustainable for an ever increasing population!
Not everyone wants (or even can!) indebt themselves just to have a phone or laptop!
Should we aim for more "#FrugslComputing"?
Is it realistic to expect things to be in a perfectly accessible TUI that ebery screenreader can handle?
That being said the apathy of consumers is real, and very frustrating:
People get nudged into accepting all the bs and it really pisses me off because they want me to look like ab outsider / asshole for not submitting to #consumerism and #unsustainable shite...
It's out, if anyone is curious
https://doi.org/10.1002/cpe.8313
This is a “how to” guide. #GPUSPH, as the name suggests, was designed from the ground up to run on #GPU (w/ #CUDA, for historical reasons). We wrote a CPU version a long time ago for a publication that required a comparison, but it was never maintained. In 2021, I finally took the plunge, and taking inspiration from #SYCL, adapted the device code in functor form, so that it could be “trivially” compiled for CPU as well.
One of the reasons why I still haven't done my long-promised mini-thread on #GPGPU is that every time I find some time to brainstorm the thing I get indescribably angry at vendors, and I realize that the tone of the thread would really take a bad turn I would rather not have it have.
Mind you, I love the field, but I have a lot of pent-up frustration due to how much vendors keep (intentionally or not) making things much harder than they should be.
Now that our instance has a higher size limit for toots, time for a re-#introduction. This time with more hashtags!
Hi! I'm Jeff. 
I've been a software engineer since around 1999 I guess. I started with #WebDev back in the early days of applets, DHTML, and Flash. I've since moved on to #FullStack work on just about anything that has a compiler or an interpreter. I've even recently dabbled in #PCB design and #3DPrinting.
My software specialties are in high performance computing #HPC, #GPGPU, and #ComputationalChemistry. Although I usually enjoy any programming problem with a good challenge to it. I spent waaay too much time in school and got all the degrees in computer science. I still work in #academia part-time writing research software.
My favorite programming languages at the moment are #Rust and #Kotlin. Although, I've spent a lot of time writing #Javascript lately. With the right tooling it's not completely terrible.
More recently, I've been interested in online #privacy, #cryptography, and #SocialNetworks.
