canpolat @ canpolat @programming.dev

Mastodon: @canpolat@hachyderm.io

---

Read more

Posts

60

Comments

74

Joined

2 yr. ago

I'm not sure it's that simple, really. And I definitely don't think this is limited to Windows. I agree with other comments that this is mostly related to complexity. The more complex the domain the more difficult it is to implement/maintain a good solution. Delivering the new shiny feature is more exciting for all people (product management, development, users, etc.) than to fix bugs. And if you don't have the resources/maturity to keep technical debt under control, the software quality will suffer over time. Free software may be the exception here as profit is not always the primary concern.

I no longer look forward to updates.
[...]
It seems to me that some software is actually getting worse, and that this is a more recent trend.
[...]
Why does this happen? I don't know, but my own bias suggests that it's because there's less focus on regression testing. Many of the problems I see look like regression bugs to me. A good engineering team could have caught them with automated regression tests, but these days, it seems as though many teams rely on releasing often and then letting users do the testing.

The problem with that approach, however, is that if you don't have good automated tests, fixing one regression may resurrect another.

Every time I see a new update, I think: "I wonder what will break after this update" and postpone them as much as I can. Software updates shouldn't cause anxiety. But they do these days...

!learn_programming@programming.dev

Works fine on Android (Firefox).

I think you have a better chance if your instance focuses on a topic instead of being general purpose. That's the reason I chose programming.dev. All communities there are related to programming so when I sort by "local" I see something interesting even though I haven't subscribed to that community. And that increases my interaction with those communities.

Looks like this problem has been solved now. Do you still experience it?

That may be due to "the Hacker News hug". This link had a high score in HN a few hours ago. High traffic may have caused scalability problems.

I don't know if you have seen it, but programming.dev has a "community request" community: https://programming.dev/c/community_request

You can suggest one for F# there, if you want.

To be honest, I cannot be sure that session invalidation actually worked. I could use the session from the day before as well. But the vulnerability was in lemmy-ui, and people not using the web site directly should be fine, I guess. If you want to be on the safe side, you can log out and log back in. It takes only a few seconds.

Where are you seeing this happen?

It's at the top of the page when you visit programming.dev in a browser. I tried to explain what I know about it in a sibling comment.

Here is my understanding:

Recently, a security vulnerability of Lemmy has been exploited by some malicious actors. This lead to some instances going down. The vulnerability has been fixed with version 0.18.2-rc.1 of lemmy-ui. But due to the way Lemmy issues and uses access tokens, the sessions has been invalidated in the database. So, the admins are recommending the users to log out and log back in if they haven't done so after the upgrade to version 0.18.2-rc.1 of lemmy-ui.

But I may be wrong. Perhaps others can provide a more accurate description.

Ok, maybe I misunderstood your question. I though you were proposing # instead of $ sudo and I meant to say that being explicit is better.

That sounds cool. Thanks for the recommendation.

What about the packages that are not available in flatpak? I assume there must be some packages that are only available in certain corners of the internet?

Thanks

Are there any other distros that are flatpak-only?

I don't work much with Linux systems these days, but I would vote for $ sudo over #. Two reasons:

1. It's easy to overlook the prompt. That part is basically "some characters before the actual command", so I don't normally pay attention to it.
2. # is also used for comments. I think it would be confusing to use the same character for two wildly different things.

Would love to see a browser based implementation of this.

Unflushable Cache

[...] Other implementations, such as hand cranks in memory caches or even caches provided by mainstream frameworks will not expose any cache management tools. This leaves ops with the only option, to restart the service to flush the memory. (Or worse, know enough about the cache implementation to find it’s location on file system and clear it out manually.)

This is a mistake I have made. It's easy to overlook during development but difficult to handle afterwards if restart is not trivial.

Here is another implementation: Another Blog Resurrection, the Fediverse, and a New Comment System