There was an article by Google about the security of their code base, and one of their core findings was that old code is good, as it gets refined and more free of bugs over time. And of course conversely, new code is worse.

https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html

Generally it seems like capitalism’s obsession with growth is at odds with complex software. It’s basis in property also.

It’s not too hard. There are a bunch of different platforms one might experiment with as well as instances. Some will use multiple accounts for different needs or interests. On lemmy, multi accounts are useful for have different feeds, for example. I probably have 7-10. I’ve probably forgotten about a few of them. If you’re curious, it happens.

Yea. Even nicer if it could be adjusted on a post-by-post basis (however viable that is).

By the same token Evan seems a bit self centred and egotistical about his projects. Of you look at his comments about BlueSky it seems he’s pretty bitter that someone dared to make an alternative protocol that so far has a decent amount of users, when a acceptance of multiple systems experimenting and borrowing from each other for the good of the open web is right there as a natural position.

It’s definitely an interesting and relevant idea I think! A major flaw here is the lack of ability for communities to establish themselves as discrete spaces desperate from the doomscrolling crowd.

A problem with the fediverse on the whole IMO, as community building is IMO what it should be focusing on.

Generally decentralisation makes things like this difficult, AFAIU. Lemmy has things like private and local only communities in the works that will get you there. But then discovery becomes a problem which probably requires some additional features too.

it’s the sort of tool that is really just fundamental now and should be ubiquitous and promoted and taught and talked about every where there is knowledge work. Even more so as there’s a great open source version of the tool.

Oh yea, I hear you.

What your point does though is open up the discussion about whether enforcement makes financial sense in isolation. And once you open that door, the whole becomes uncomfortable for a lot of people who are stuck in a simple black-and-white justice mentality, where “do what you’re supposed, pay what they charge, or be punished” is all there is to making the world work well. You know, “law and order” types.

You’re trying to talk about incentives. For many though that’s a very dangerous slippery slope. So I’m trying to get a head of that and wonder if the end of that slippery slop is actually a demonstrably good thing.

I remember hearing rumours during the role out that tech employees were found asking for help on forums in ways that weren’t promising for the health and talent of the people building it.

But yea, it’s the embarrassment of this sort of stuff that must be masking the real financials of PT and how viable a free system would be.

Yea I’ve kept track of how often I’ve encountered inspectors, and most of the time it’d be worth it to not get the ticket or not tap on. Sometimes though I’ve noticed an increase in the number of inspectors that would definitely shift the equation. Also train stations with gates complicate the matter.

I don’t know if it’s out there, but I’d personally like to know how the finances come out for making PT free. You obviously lose revenue, but also all the overhead of paying for inspectors and for all of the ticketing infrastructure. I also wonder if the part that makes the finances work is all the fines collected, which would be pretty fucking shithouse if true.

The catch is that the whole system is effectively centralised on BlueSky backend services (basically the relay). So while the protocol may be standardised and open, and interpreted with decentralised components, they’ll control the core service. Which means they can unilaterally decide to introduce profitable things like ads and charging for features.

The promise of the system though is that it provides for various levels of independence that can all connect to each other, so people with different needs and capabilities can all find their spot in the ecosystem. Whether that happens is a big question. Generally I’d say I’m optimistic about the ideas and architecture, but unsure about whether the community around it will get it to what I think it should be.

I don’t recall seeing ads in Netflix

Didn’t they start an ads tier ages ago?

And yea I wasn’t commenting on the shows, just that I’d been away from Netflix for so long I haven’t even had a chance to see any of these.

It’s funny how long I’ve been off of netflix … I haven’t seen any of these (even despite wanting to watch Stranger Things S4 just to finish it).

Something about netflix just burned me. I tried subscribing again after they introduced ads and the amount clunkiness and incompatibility they’d introduced through that basically burned me for good. I subscribe to some things here and there but I’d lost track of how much netflix is basically off of my radar.

Suspicion is totally fair re BlueSky IMO. The system they’ve design seems to me (and others AFAICT) to have the potential to include interconnected components or sections with various degrees of independence.

The elephant in the room, which I point out on BlueSky whenever I can, is that no one seems to really be trying to build the hard parts of that out. Which is a shame because it could be interesting.

EG, there’s a chance that a hybridised system running both BlueSky’s protocol and the fediverse’s could be viable and quite useful. Add to that the integration with some E2EE, and it finally feels like an actual attempt at building something new for the modern internet.

Fortunately there is some noise around these ideas, so hopefully their system can outlast their finances. But yea, a rug pull is definitely not out of the question.

Oh I’m with you there! And otherwise totally understandable.

I’m not close to Gaiman or the fandom or the story, at all … but I did manage to pickup on some of the whisper network through mastodon, where I read a couple of posts or blog posts by people who seemed to be close to the fandom and even be friends with him (in one case). The vibe was very much he’s likely a womanising guy and has been his whole life and likely has standards “below” what most would consider normal. There also seemed to be a bit of introspection about how much the fandom around him was kinda culty and that that clearly enabled whatever he did, as a common enough pattern seemed to be that someone would go through something unseemly, but because it was Gaiman and all their friends were fans, they presumed it was them or their fault and never wanted to open up about it.

Like I said though, this is essentially gossip, so don’t take it seriously or anything (also I don’t have any links or anything).

I think for python tooling the choice is Python Vs Rust. C isn’t in the mix either.

That seems fair. Though I recall Mumba making headway (at least in the anaconda / conda space) and it is a C++ project. AFAIU, their underlying internals have now been folded into conda, which would mean a fairly popular, and arguably successful portion of the tooling ecosystem (I tended to reach for conda and recommend the same to many) is reliant on a C++ foundation.

On the whole, I imagine this is a good thing as the biggest issue Conda had was performance when trying to resolve packaging environments and versions.

So, including C++ as part of C (which is probably fair for the purposes of this discussion), I don’t think C is out of the mix either. Should there ever be a push to fold something into core python, using C would probably come back into the picture too.

I think there’s a survivor bias going on here.

Your survivorship bias point on rust makes a lot of sense … there’s certainly some push back against its evangelists and that’s fair (as someone who’s learnt the language a bit). Though I think it’s fair to point out the success stories are “survivorship” stories worth noting.

But it seems we probably come back to whether fundamental tooling should be done in python or a more performant stack. And I think we just disagree here. I want the tooling to “just work” and work well and personally don’t hold nearly as much interest in being able to contribute to it as I do any other python project. If that can be done in python, all the better, but I’m personally not convinced (my experience with conda, while it was a pure python project, is informative for me here)

Personally I think python should have paid more attention to both built-in tooling (again, I think it’s important to point out how much of this is simply Guido’s “I don’t want to do that” that probably wouldn’t be tolerated these days) and built-in options for more performance (by maybe taking pypy and JIT-ing more seriously).

Maybe the GIL-less work and more performant python tricks coming down the line will make your argument more compelling to people like me.

(Thanks very much for the chat BTW, I personally appreciate your perspective as much as I’m arguing with you)

Funny to only ask/report on Zendaya if she’d come back after Messiah.

Yep! And likely the lesson to take from it for Python in general. The general utility of a singular foundation that the rest of the ecosystem can be built out from.

Even that it’s compiled is kinda beside the point. There could have been a single Python tool written in Python and bundled with its own Python runtime. But Guido never wanted to do projects and package management and so it’s been left as the one battery definitely not included.

I feel like this is conflating two questions now.

1. Whether to use a non-Python language where appropriate
2. Whether to use rust over C, which is already heavily used and fundamental in the ecosystem (I think we can put cython and Fortran to the side)

I think these questions are mostly independent.

If the chief criterion is accessibility to the Python user base, issue 2 isn’t a problem IMO. One could argue, as does @eraclito@feddit.it in this thread, that in fact rust provides benefits along these lines that C doesn’t. Rust being influenced by Python adds weight to that. Either way though, people like and want to program in rust and have provided marked success so far in the Python ecosystem (as eraclito cites). It’s still a new-ish language, but if the core issue is C v Rust, it’s probably best to address it on those terms.

Huh. I hadn’t really thought about it before, but it would seem to indicate that size and density are mostly independent parameters of a city.