It's time to admit Lemmy has won the "the biggest reddit alternative" award, why it's time for all of us to consider supporting it (here's why) + reopening r/LemmyMigration
It's time to admit Lemmy has won the "the biggest reddit alternative" award, why it's time for all of us to consider supporting it (here's why) + reopening r/LemmyMigration
Disclaimer: This is kind of a long write-up, but please don't downvote before reading it, put effort into this one:) Hello everyone. I’m back...
You're viewing a single thread.
I’m concerned with the amount of bugs cropping up between major updates. I looked at the repo and they have no unit tests. Eventually people will get fed up with the amount of bugs appearing.
I use a third party app and see very little. Over time it’ll get better also.
Lemmy still feels like beta (while Kbin is alpha), but it still is better than Reddit!
(no /s - I really believe that, b/c the people here vs. there make ALL the difference)
To all those who contribute code, thank you for making this micro-world a better place for us all!:-)
Which repo are you talking about? There are tests in the main rust repo. Rust puts its tests in line with the code. https://github.com/search?q=repo%3ALemmyNet%2Flemmy "%23[cfg(test)]"&type=code
I have no idea how complete these or or anything. But it's not 0
As mentioned in other comments, they have some tests in the backend repo. Moreover, its being an open source platforms means that contributions are welcome: bugs can be reported, missing tests can be added, fixes can be merged and so on...
"Some tests in the backend" would instantly get you fired from some companies. Lack of tests is a symptom of the programmers not being as experienced as they should be, when making a platform such as this.
Permanently Deleted
The issue is, if open source has any chance of competing with paid software, it needs the same standards a regular company has. It's not about "increasing productivity" as you put it. It's actually about doing less. By writing tests, you spend less time on the code that ends up in the final application. But the result of that, is that the final application breaks less. Issues that could have been avoided, are incredibly rare.
Writing regular code is fun, it's exciting. You deliver new toys that people see and are thankful for. Writing tests is the opposite of that, it's boring and dreary for most people. But it is necessary to maintain a quality product. No regular user will thank you for tests being present, they'll complain when things break. They won't adopt a new version, since there is no automatic regression testing possible, since you haven't written tests and things break in the next version. So now you have to test the entire thing yourself. Which is even more boring than writing tests, so you move onto exciting new features again. And you end up in a death spiral a few years from now, since you can't see why a certain feature stopped working, all the features depending on it break one after the other, and the only way to check what's wrong, is to go test everything there is.
I looked at the repo and they have no unit tests
Lol wut
Using an app, I’ve only had some very minor issues. Essentially, just occasional crashes.