@lebronjames75@shitposter.club oh right, open it in instance pleromafuck
@lebronjames75@shitposter.club come over to misskey you three headed freak
we don't cotton to weirdos around these parts
@emilis @lebronjames75 Misskey is a fad.
I’ll believe it’s better when @alex writes a pleroma to misskey migrator
And @p uses it to convert fse.
@shebang@freespeech.group @lebronjames75@shitposter.club @p@freespeechextremist.com ironic, considering how mad you were about mastodon being bad and not supporting the cool features 
@emilis @lebronjames75 @p Mastodon is bad and missing cool features. But by design.
Pleroma has fallen behind a bit, but not by design, merely developer resources. That can change any time.
@shebang@freespeech.group @lebronjames75@shitposter.club @p@freespeechextremist.com >that can change any time
ah yes, elixir, very popular, likely to attract swathes of developers any moment
> swathes of developers
What Elixir I know, I learned because I wanted to hack around the edges of Pleroma. (I cheated a little by knowing Erlang, but it's not Elixir.)
But "swaths of developers" aren't needed. That's some Mythical Man-Month shit.
@p@freespeechextremist.com @lebronjames75@shitposter.club @shebang@freespeech.group Clearly not, that's why pleroma is hot in development and is just getting shit fixed and features added.
Yeah in fact the part of Pleroma which entirely felt apart is MastoFE.
Which is in React with all the usual webshit stuff.
And no one else but me and someone else at random ever dared to touch it.
In fact PleromaBE is quite easy to pick up. I had no knowledge of Elixir at first, only had vague notions of Haskell before, I knew my C and Shell and fe other languages.
Just except stuff to not be as fast as before and for devs to be more centered around their own interests.
My lazy-ass way to get by in a new language in basically few hours:
- Read the language introduction to get a feeling of it's design on the basics
- Walk around the standard/common libraries a bit
- Look at simple existing code for known algorithms (Rosetta code ♥)
- Play with the language a bit, REPLs are neat to have
- Make sure you have the documentation on your machine, this way you can easily search in it
And for annoying things like C where some libraries tend to have bad to no documentation, stuff like public repos of well-established and https://codesearch.debian.net/ are neat when you're blocked.
That said, always try to doubt third-party code snippets.
I'd add that doing a few toy problems can help. YMMV but I usually do "Hello, World!" (mainly a smoke test for the compiler/interpreter, a feel for what boilerplate might be required), 99 Bottles of Beer (loops, conditionals, and string-mangling), and then Project Euler #31 (lends itself nicely to different implementation strategies, gives you a very good feel for the language).
Reminds me that before I had this "itch driven development" I tried few languages by trying to write an IRC Bot.
It's a quite easy thing to do in most languages, it takes a bit of time though but it touches enough parts of a language (network, parsing, loops, events, …) that you'll be aware of the limitations it has.
Like it made me learn that python (back in 3.6) feels like it sucks as much as C for string manipulation but is quite good for web scraping.
This was one of the books thrown at me by fedi when I was looking at Elixir, perhaps useful.