I am a daily IRC user and I think you are exaggerating the problems. I can count on my one hand the number of times I have seen an attack on my nick or the channels I hang out in, in the last 15 years. Those attacks pass without much disruption (sometimes requiring staffer intervention). Nick squatting is solved by Nickserv these days. Splits do happen occasionally but they resolve on their own automatically without much disruption.
It is ok if it never gets adopted as mainstream communication. But for the target audience (like opensource support communities being the target audience of Libera), it works quite well.
Survival is not the issue. Mastodon will survive. Tumblr survives. Even MySpace survives. But major disruptions tend to lose users.
(And yes it's true that the potential Twitter acquisition is a potential major disruption. But it's not going to be shut down after a $44 billion investment.)
The staffers setup the new servers and did all the heavy-lifting.
As a user, I only had to point my client from Freenode to Libera (exactly one line change in my client config), run /msg nickserv register to register myself, run /msg chanserv register to register the channels I op-ed, and it was all done.
Total time spent was less than 30 minutes. The next few days, others did the same and the community started trickling in to the channels in the new servers. Seems seamless enough to me. I doubt such an easy migration is possible if Twitter disappears suddenly.
And yet userbase got decimated for most channels when moving from Freenode to Libera. Just because it was only 30 minutes (for you or for anyone) doesn't mean people will go through the effort.
The active userbase was not affected very much. (Note that some channels moved to OFTC, not Libera.) The lurker userbase was more than decimated – I think it about halved – but they were barely part of the communities, and there might not even have been anyone sitting behind the IRC clients.
anecodote only, but #ardour lost precisely zero users when moving from freenode to libera. just because people on channels you joined weren't willing to go through "the effort" doesn't mean that other people feel that way.
It's not $44B that twitter will have available and can spend. Most (all?) will go to current investors to buy their stocks at a set price, which is where the $44B comes from
It's probably more about how much the new owners will want to drop into it and how long before it moves to x.com (?) and becomes an everything app
> It's not $44B that twitter will have available and can spend. Most (all?) will go to current investors to buy their stocks at a set price, which is where the $44B comes from
Why did you feel the need to mention this 100% obvious fact?
Of course I meant that the new owners wouldn't shut down something they just spent $44 billion on, thereby throwing their investment in the trash, not that Twitter would magically get a $44 billion operating cash infusion.
We stopped capitalizing each letter in Lisp since Interlisp (sometime around 1960ies). I might be just making shit up, but I think the idea was to use "Lisp" when referring to the programming language dialects, and "LISP" when talking specifically about McCarthy's original thing. But don't quote me on that.
Anyway, Lisp isn't acronym anymore (or abbreviation, initialism?, mnemonic? I don't know what you call that). It doesn't always mean "LISt Processing" anymore.
So "that guy" is right. It's Lisp, not LISP. Well, most of the time it is.
Quite a few authors, including good ones, used LISP in the 1980's and into the 1990's.
Some examples:
Stuart C. Shapiro: LISP: An Interactive Approach (1986), Common LISP: An Interactive Approach (1992).
Robert Wilensky: Common LISPCraft (1986).
W. Richard Stark: LISP, Lore, and Logic: An Algebraic View of LISP Programming, Foundations, and Applications (1990)
Winston and Horn: LISP (1981-1989, 1st-3rd ed)
Steele's ClTl2 doesn't capitalize Lisp throughout the work per se, but the cover styles COMMON LISP in all caps. This leads to mistakes, like Amazon listing it as "Common LISP, The Language".
Well, yes, in the past, sure. But seasoned, contemporary Lispers, actively using Lisp to write programs don't usually do that these days, unless they are referring specifically to things like CLISP, XLISP, AutoLISP, etc. Even Common Lisp is no longer capitalized in each letter anymore.
You can use whichever style you like. But just so you know, some Lispers may get annoyed.
But then again Lispers often get easily annoyed. Some of then get annoyed when you say "Clojure is a proper Lisp".
While that is all true, those old books are still useful and good, and by and large much better than newer books.
That could be one reason why newcomers still keep using "LISP".
Come to think of it, there must be people using "LISP" who were not even born prior to the first time (or even the umpteenth) someone was corrected in this matter on the Internet.
People who will one day write "LISP" into an online comment are not yet born, or still in diapers.
Maybe we need to target preschools and kindergartens?
I have done IT for small businesses. Every small shop I worked for had to use many different and incompatible assortment of software tools to set up the IT for the business: Windows system for a proprietary billing software, OpenBSD system for routing, proprietary intercom tech. I envied my friends who worked for proper software companies. They could build everything for Linux, dockerize everything and done!
Is there anything like Kali-Linux but for business tech? I would love it if I can find one Linux bistro for business tech that rules them all!
I'm lacking details from your wish of course, but if you need to run several, disparate different software....Could not one of the common linux distros like Ubuntu, Redhat/Fedora, SUSE, etc. suffice, and of course have a powerful enough machine to run virtual machines or maybe WINE? Obviously this depends on whether you were asking for client side or server side...And if on the client side, things - as you know very well - can get very tricky because you then have to deal with training and general acceptance.
When i used to have my IT side hustle company, whenever i supported software for small businesses, i often found that nuding them to web equivalent software made things alot easier. For example, some users get comfy with software faster when its within context of a web browser...Of course, this is different for every user/org and with different software, it depends. But it lessens your support away from conventuional desktop supporot. However, if the web softeware is managed hosted then its much easier, but if you have to manage the hosting, then you would need web management sort of skills. for me that was my forte, so it was easy for me.
As to your wish to find a linux distro for business tech, there are platforms like Odoo (see wikipedia: https://en.wikipedia.org/wiki/Odoo)...but they're not lightweight, and back to my earlier point, you'd have to build up your skills administrering web apps, server, etc. I'm sure there are plenty of other options beyond Odoo. Try a couple of searches against odoo; the old google hack of "odoo vs..."
Good luck!
EDIT: Sorry, i meant to direct my comments aboive to @importgravity :-)
Came here to say this. I use org-mode to do what OP's package is doing. But OP provides some features like
> one keystroke executes all specially-marked lines from a
buffer and inserts the results inline
Not sure if we can make such specially-marked lines using org-mode. Never needed this feature myself. But for those who want a workflow like this the new package could be useful. But again maybe there is a way to do this without an external package with a little bit of elisp?
It is ok if it never gets adopted as mainstream communication. But for the target audience (like opensource support communities being the target audience of Libera), it works quite well.