"I'm jealous with all the attention 'threads' are getting lately."
- a process, however lowly & otherwise humble
"Me too!"
- a coroutine
"Honestly, same."
- a goroutine
"It me."
- a fiber
"My people!"
- a tasklet
"Represent!"
- a greenlet, looking suspiciously like a fiber and tasklet, but colored green
#programming
#concurrency
#threading
#MultiThreading
#parallelism
#fibers
#greenlets
#processes
#threads #programming #concurrency #threading #multithreading #parallelism #fibers #greenlets #processes
as a fan of oldskool dystopic/apoc fiction & drama TV (esp from the 60s to 80s, & UK/Euro) let me just say Meta's choice of the Threads name is terrible... & PTSD-inducing
as a decades-long programmer with plenty of scars from doing & seeing multi-threaded programming at scale, well, let me just say Meta's choice of the Threads name is also terrible... & PTSD inducing
#programming
#multithreading
#concurrency
#parallelism
#threading
#fibers
#coroutines
#goroutines
#processes
#meta #threads #programming #multithreading #concurrency #parallelism #threading #fibers #coroutines #goroutines #processes
whenever I hear someone talk about using Meta/Facebook's new Threads I think, "Nah I'll just stick with Golang's channels-and-goroutines model instead, thanks!"
#Go
#Golang
#channels
#goroutines
#threading
#parallelism
#concurrency
#go #golang #channels #goroutines #threading #parallelism #concurrency #threads #facebook #meta
So, in our current world, conversation platforms are accessed by diverse clients, there are real barriers to client diversity in how #threading is handled.
This isn't just a #Fediverse issue, but applies to any protocol that can be accessed through independently developed clients.
A hypothetical #Mastodon client that approached #threading in the way that I suggest could take things a step further by automatically collapsing (hiding) subthreads, so that people can choose whether to view those replies (again, in place) or not.
Unfortunately, trying to organize a Mastodon thread with all toots as replies to a single top-level toot results in an incoherent thread view on the default web client and (as far as I know) all other existing clients.
The upshot of the #threading interface that Mastodon inherited from Twitter is that, while it is straightforward to post an essay or rant as a sequence of toots, it is not at all straightforward to follow any conversations that it generates.
To my way of thinking, the way conversation #threading works on #Mastodon and #Twitter is dead wrong.
Ok, so no #threading #posts in #IceCubes, it seems. I've only found that in #Toot!, so far.
#Toot #icecubes #posts #threading
my technical projects (underway) or interests, with hashtags, so findable:
book & blog series on software performance & scalability
#software #programming #performance #scalability #scaling #optimization #tuning #engineering #guides #HPC #BrendanGregg
my tech interests and favored tools:
#Go #Golang #Python #C #Linux #git #SQL #webdev #cloud #Internet #DistributedSystems #threading #concurrency #parallelization #EDA #queues #MessagePassing #CLI #TUI #curses #Terminals #consulting #Systems
#software #programming #performance #scalability #scaling #optimization #tuning #engineering #guides #hpc #brendangregg #go #golang #python #c #linux #git #sql #webdev #cloud #internet #distributedsystems #threading #concurrency #parallelization #eda #queues #messagepassing #cli #tui #curses #terminals #consulting #systems
@NudelnAlDente shit like this is why I can't use #Teams at all.
It's like all the worst features of #Mattermost & #Slack got combined with no redeeming qualities...
Whereas #Zulip at least is consistend and does #Threading very welll...
#threading #zulip #Slack #mattermost #teams
#tutorial #javaserver #java #server #threading
So it sure looks like #Reddit is going to eat itself in the next week or so. The recent AMA from the CEO pretty much shows they are going to Twitter route. Trying to monetize a platform in a way that's going to drive up to the users away from it.
I had hoped that #Mastodon would be the thing that could replace both Reddit and Twitter, but without a federated #groups model, or proper #threading, or similar tools, it's not going to work.
So where y'all going?
#reddit #mastodon #groups #threading
Can someone point me to a human understandable writeup of 'how to do stuff in parallel in Python'? I have no idea about it and see things like subprocess, async, threading, concurrent and I have no idea what it all means (I'm ok with some nice, linear Python) #python #threading #async #parallel #halp
#halp #parallel #async #threading #Python
By setting `nogil=True` on a Numba function, I just cut the runtime of one part in the code from 60 minutes to 4 minutes.
Feels like an okay win for essentially a single line edit.
#threading #numba #nogil #python
My book, Parallel Programming and Concurrency with C# 10 and .NET 6, is part of Packt Publishing's April #dotnet sale.
Get 20% off thru the end of April: https://packt.link/XJfsC
(Works with .NET 7 & 8 too!)
#sale #programming #async #csharp #concurrency #books #visualstudio #threading #ebook
#dotnet #sale #programming #async #csharp #concurrency #books #visualstudio #threading #ebook
Is there an effective way to thread posts on Mastodon? In my feed I see posts. Many are from the same author, replying to their own post, in a cascading series. Is there a setting I can use to put all of these posts and replies in line? As opposed to saying them randomly in my feed?
Check out my latest blog post!
#dotnet #dotnetcore #threading #concurrency #beginner #howto #tutorial #programming #coding
#dotnet #dotnetcore #threading #concurrency #beginner #howto #tutorial #programming #coding
Programming languages and memory management and #synchronization:
https://research.swtch.com/plmm
I'd noticed this PLMM paper by Russ Cox via an included reference to an #HP Labs research paper I'd previously read by Hans-J. Boehm. Boehm's paper indicating that #threading could not be implemented as a library; that the programming language and the compiler had to be involved in threading. That paper:
https://www.hpl.hp.com/techreports/2004/HPL-2004-209.pdf
There are some gnarly bits within the #OpenVMS #compilers to contend with some of the more common cases here. This because OpenVMS IOSBs, LKSBs, itemlists, and other sundry giblets are inherently asynchronous and should be marked as volatile by the developer, but probably aren't. And various programming languages common on OpenVMS don't have a volatile keyword or related support.
#synchronization #hp #threading #openvms #compilers