Lack of available staff, and a CEO who is probably mostly focused on finding some way to salvage advertising and has no time to spare on thinking about anything else because the advertising situation is just abysmally dire…
I mean I think fully a quarter of the community notes I see directly on things in my timeline (not people sharing screenshots of particularly funny/interesting community notes) are people putting community notes on overpriced drop shipping scammers.
The advertising situation seems completely doomed and when the CEO was picked to remedy that and the owner is in a nebulous executive role as “product owner” and simultaneously a hyper emotionally invested product user (based on credible reports and the publicly verifiable behaviour)… what can she really do besides do a good enough job for long enough that it won’t seem weird when she quits/takes another position.
Because erlang is “weird” and not enough programmers learn it for it to have breached the cultural ramparts regarding what concurrency is in a programming language. I learned Erlang and Elixir and I’ve never been happy with any other languages’ concurrency mechanisms and primitives since then. Between multitasking features that let you avoid concurrent tasks causing CPU starvation, message passing allowing proper decoupling of concurrent tasks in both an asynchronous and synchronous ways and all the other little ways it does concurrent programming right… nothing holds a candle to it. There are some nice libraries in other languages but it’s not the same because it’s not built into the language at the same level.
Async/Await, asynchronous IO, none of this is really the same kind of “concurrency”… it’s why I wish I had more chance to use the Erlang/Elixir+Rust combo… low level safety and high level concurrency are a match made in heaven.
Isn’t the entire language designed explicitly to prevent programmers from building their own sophisticated abstractions that could confuse other programmers who don’t understand that other persons code… as I understand it, if you can read go and understand basic programming you should be competent with go, and if you know your algorithms you should be proficient.
I hated old Java but the modern language isn’t as bad now some people have added some better syntax shortcuts the libraries are nearly twenty years more polished, and the IDE can nearly half write my code for me so the boilerplate and mind numbing aspect isn’t so bad… I loathe go because using it feels like programming with my hands tied behind my back trying on a keyboard with sandpaper keycaps, despite that, I didn’t bother “learning” go, I could just read it based on my Python/C/Basic/Java/C# experience instead of needing any extra learning.
Don’t forget the multiple severs multiple logins hassle, I wasn’t particularly bothered until I got to about the dozen mark at which point I started to resent any new slack I had to interact with, because even with a password manager it was a shitty interaction, because your likely matching on the slack TLD not the per slack unique FQDN, and given that owners can rename the slack and change that it’s not a bad thing to have the slack TLD be the login domain… anyway some people found this a problem immediately (likely not using password managers) and you can tell that it’s been an issue given that Slack really pushed the Magic Link logins pretty quickly, they obviously felt the pain.
Speaking as someone with similar feelings… “Well enough” and “decent” are not how I would describe something I’m thinking of investing significant mental time and effort learning and familiarisation building on. I’ve done the basic tutorials and generally like the language ergonomics, it’s not bad, and I kinda like it for the little bit of Apple platform dev I’ve done with it. But it’s basically a different language on any non Apple platform.
IntelliJ has arguably one of the best subscription models for tools. It works offline and they have fallback licenses so if they doubled the price and I cancel I’m still legally entitled to a recent version that I’ll probably be happy enough with until I find the motivation to replace it with something else.
If Adobe worked like that I’d be like 75% pissed off at their products and pricing.
Yeah. It’s like how one of the growing YouTube monetisation avenues is basically kept in a strait jacket. YouTube Membership or more specifically channel memberships, are a one way street, it all has to start with Google, YouTube is the video platform, the the point where I would pay a the damn extortion money, App Store style, to be able to sync a user that signed up off YouTube to a membership platform like Memberful or Patreon, over so their YouTube account has appropriate permissions… it’s a one way street though, they have a discord integration, and that’s basic the only useful feature that goes outside the weirdly hidden YouTube channel member extras pages that I continue to find people who join a channel to support it but don’t actually discover the extras! That’s how badly managed this is.
Theres a small issue that you overlooked here which is that once it has contributions from several other people, anything AFPL becomes impossible to relicense, how do you get 6 random GitHub users to sign a contract, without robust copyright assignment/management mechanisms ahead of the very first outside contributor, AGPL effectively kills the ability for anyone too pay you for your own work on terms you might want to agree to.
By using aggressive open source licenses like AGPLv3 you have to do more work to keep the door open for yourself to profit later if you so choose, it’s a bad personal economic choice, and while some view it as the ultimate in altruism to prevent this, it’s also an act of denial, everyone who could have used it inside companies or projects that can’t change their license to be compatible are denied the ability to use the code.
The "twisted problem" is often summarised as "I know Twisted is great for asynchronous Python... If only it was the kind of Python I want to write"
It's not that Twisted is bad. It's just that many Python developers are not "fluent in the Twisted dialect" like how some people find a thick Scottish accent hard to understand and other more familiar with it can understand every word.