Same, and also not kidding. I would rather have a group of three or four well-compensated maintainers who know the codebase very well (+ newer contributors they can afford to & have time to help teach/train) releasing security and bug fixes, with, maybe *one* feature release every year or two and a clear 'it's done'/feature complete state after which it's just bug fixes and maintenence/porting.
But then the boss would have fewer people to manage, and be unable to justify his job. Most software changes are about employment for engineers, not necessity. Grr.
As a software engineer I want computer languages and frameworks that stay stable for decades rather than have a new release every year that obsoletes old programs and requires a rewrite. But I don't get to have that 🙁.
@Badtux the Snarky Penguin @Eniko Fox I've written software that was "finished" only to have to update it because an underlying library introduced a breaking change. I hate that.
@me And every fifteen minutes there is a new Java release that fixes a thousand security holes and adds a thousand new features to bloat up the runtime. Meanwhile my "C" programs from the early 1990s still compile and run just fine.
@Badtux the Snarky Penguin @Eniko Fox I actually had to re-write large chunks of a program I wrote for a client because Haskell's ncurses wrapper just kind of... stopped being a thing.
Fortunately, I never liked ncurses to begin with and had abstracted much of it away. The code I'd written was fairly easy to retrofit into brick instead.
can we also get mobile operating systems that get more optimized and less resource hungry with every update so that devices can run for 10+ years before becoming obsolete?
Product: What's this ticket for, this one you're working on, it doesn't seen to be delivering any new feature? Why are we doing it?
Devs: It lets us delete a couple of thousand lines of no-longer-used code. Which will then no longer need to be maintained, tested, documented, ect ect.
The media in this post is not displayed to visitors. To view it, please go to the original post.
Hear hear! 👏
I'm pretty tired of downloading some 100 MB every week for Signal desktop for minor changes. And did you see how the changelog in /usr/share/doc looks like for Signal-desktop on Linux each time ? Yeah, whatever, Signal! 🤬 #signal
V
in reply to Eniko Fox • • •Sensitive content
Boyd Stephen Smith Jr. reshared this.
Seth Galitzer
in reply to Eniko Fox • • •Badtux the Snarky Penguin
in reply to Eniko Fox • • •But then the boss would have fewer people to manage, and be unable to justify his job. Most software changes are about employment for engineers, not necessity. Grr.
As a software engineer I want computer languages and frameworks that stay stable for decades rather than have a new release every year that obsoletes old programs and requires a rewrite. But I don't get to have that 🙁.
#software #softwaredevelopment
Jonathan Lamothe
in reply to Badtux the Snarky Penguin • •like this
Cassandrich, Eniko Fox, Em and Kirtai 🏳️⚧️ like this.
reshared this
Cassandrich and Urja reshared this.
Badtux the Snarky Penguin
in reply to Jonathan Lamothe • • •Jonathan Lamothe
in reply to Badtux the Snarky Penguin • •@Badtux the Snarky Penguin @Eniko Fox I actually had to re-write large chunks of a program I wrote for a client because Haskell's ncurses wrapper just kind of... stopped being a thing.
Fortunately, I never liked ncurses to begin with and had abstracted much of it away. The code I'd written was fairly easy to retrofit into brick instead.
like this
Eniko Fox and Alex Celeste, Princess Consort of Burnout like this.
Kirtai 🏳️⚧️
in reply to Jonathan Lamothe • • •It's like building on quicksand.
Em
in reply to Eniko Fox • • •Edvin Malinovskis
in reply to Eniko Fox • • •I'm genuinely considering starting l collection of Android apps with the ethos off "The UI does! Not! Fucking! Change!"
Any feature additions are purely optional and of be default
No nag screens to promote the new stuff
Whatisgoingon
in reply to Eniko Fox • • •Tim Ward ⭐🇪🇺🔶 #FBPE
in reply to Eniko Fox • • •Product: What's this ticket for, this one you're working on, it doesn't seen to be delivering any new feature? Why are we doing it?
Devs: It lets us delete a couple of thousand lines of no-longer-used code. Which will then no longer need to be maintained, tested, documented, ect ect.
Product: Great! That's what we like to hear!
🅰🅻🅸🅲🅴 (🌈🦄)
in reply to Eniko Fox • • •Eniko Fox
in reply to 🅰🅻🅸🅲🅴 (🌈🦄) • • •Regendans
in reply to Eniko Fox • • •Hear hear! 👏
I'm pretty tired of downloading some 100 MB every week for Signal desktop for minor changes. And did you see how the changelog in /usr/share/doc looks like for Signal-desktop on Linux each time ? Yeah, whatever, Signal! 🤬 #signal
Joan's Addiction 😷
in reply to Eniko Fox • • •Currently, my favourite app is Out-Run, and I think it's basically been abandoned by the developer.
apps.apple.com/ie/app/out-run/…
(Yes, that's probably not great for security vulnerability reasons.. 😬)
Out-Run App - App Store
App Store四
in reply to Eniko Fox • • •craignicol
in reply to Eniko Fox • • •@Meyerweb first place to start is avoiding tracking, because those are bigger, have more updates and have more code.
The challenging part is convincing your government and bank to do the same so you can still use their services.
Jhooper
in reply to Eniko Fox • • •MeaningfulBits
in reply to Eniko Fox • • •