There's plenty of people on masto saying they have accounts on both but prefer bsky due to difficulty managing replies.
As I say I don't really understand it but it's a real thing big accounts experience.
FarceOfWill
joined 2 years ago
The tagging sounds great. One of the problems with masto is showing the hashtags in the body making posts that use them look awful, and of course being entirely set by the author
I think there's a fairly serious problem for large accounts on mastodon but I will never have one so I can't quite understand it myself.
Something like dealing with replies / scolds without spending all day blocking is too hard. It doesn't help that "no algorithm" means "show first reply at the top" so quick replies can dominate comments.
The bit I don't understand is why this is fine on blue sky. Is it just different users? I can't quite believe that but I can't see why blue sky would be less annoying.
It does have keyword blocking.
Not sure what nuclear block means but I can't think of any way a blocked person could be seen again. It even has above nuclear blocking where you block their entire server.
It has custom feeds but the implementation with lists is very fiddly and I wish it would be improved.
There is a trending posts section but I think you want a personalised discover feed? Which will never happen of course.
Over 50% approval rating.
Higher than the leader of many other countries, like, er, USA.
Despite my drive-by shitposts in the rest of this thread I want to make a serious point here.
There's a large part of software engineering that thinks languages are chosen based on the problem, as a tool for a job.
They aren't. They're chosen based on the team, on how well the team knows and can use the tool. On how many people can be hired with the knowledge of the tool to work immediately.
Sometimes, even if the team knows C well, there can be a problem so different it's worth using another tool. say python for some testing scripts on a C project.
But rust and C are too similar for this to apply. If you want rust to be used for the kernel you have to push for it to be more well known and used, so more Devs come into teams already knowing it well. Anyone agreeing to work on a team using rust is making a career decision that will be stay on their CV forever and you need them to feel good about this, that it will give them more opportunity in future.
It'll take 20+ years because that's how long legacy code is often maintained for and we already have 20+ years of future legacy code for C teams to deal with. We're all making more future legacy C code than future legacy rust code too.
I'm trapped in C++ so I'm doomed but good luck C and Rust coders.
C++ is a semi automatic shotgun with 200 barrels pointing in all directions.
It owns too much of Africa to be a regional power. It's a superpower even if by a web of alliances/dependants rather than its own military projection
It wasn't quite so much what she did as the way it was done.
The spending plan looked bad and lack of confidence in it caused a technical issue where pension funds had to make it worse to protect themselves from the consequences, which made it even worse and they had to protect themselves from bigger consequences. But this is boring and not why she had to go imho.
The real problem and cause of the whole lack of confidence was that she got rid of senior people and refused to talk to independent government orgs who are there to check the plan isn't shit.
She removed all the arse covering checks the British government has for budgets thinking she knew better, and as is clear with every mad interview she knows nothing.
Good user name too
Junior Devs could never code, yes including us
Tom's the best you goddamn ingrates