Deprecated - The word I hate hearing as a software developer

Рет қаралды 1,820

Overpass Apps

Күн бұрын

Пікірлер

@FernandoJS 3 ай бұрын

I really hate the word 'legacy,' but that's where my money comes from.

@georgehelyar 3 ай бұрын

The thing I hate is that Microsoft has a tendency to provide 2 APIs, one is deprecated - do not use, and the other is preview - do not use.

@OverpassApps 3 ай бұрын

This is true. I'm currently suffering with the Xamarin Forms to Maui upgrade on a few projects. Now that XCode has upgraded to 16, it's become urgent. But Maui still has some issues.

@OghmaNano 3 ай бұрын

Always like your videos. As an open source developer really can't stand depreciation as it costs me so much of my *free* time. At some point the GTK codebase started to not be updated/changed in a strange way. The move to QT cost a lot of time.

@_DRMR_ 3 ай бұрын

Opensource is often depreciated .. but doesn't need to be deprecated ;)

@JamesMCrutchley 3 ай бұрын

I am working on a SDK where one of the projects had a dependency that was deprecated before we started using it. No further development or fixes were planned. We had no choice. The replacement for it was in another language which required a huge amount of work to port it into a format we can use. That was done by someone else and has been ready for about 3 months now. I had to go and add a bunch of fixes for various issues to that before I could use it. All of these projects are completely open source and the dependencies I use in this case are maintained by large corporations. I am just an amateur dev contributing to a project that I like. I completed the PR close to a month ago. The kicker is I need to get it reviewed before it can get pushed to main. The issue with that is I had to rewrite nearly 80 percent of the project to make it compatible with new API. So thousands of lines of code. Finding volunteers with actual authority to review it is I find the hardest part of the whole process. I have push authority. But pushing my own work as the lowest guy on the totem pole to a major project without review is kind of frowned upon. I can understand that. I have no intentions of doing that. But it can be hugely frustrating to spend months of work and then wait 3 to 6 months for someone to feel like reviewing it.

@OverpassApps 3 ай бұрын

Wow. I have to admit... I've never actually contributed to an open-source project. I rely on so many of them, I should have given back at some point. But I never have. I think I would have the same concern as you if I did.

@CallousCoder 3 ай бұрын

Just use assembly and C with just C lib and you’ll never hear the word deprecated 😉 I have software and the hardware I developed in 1993 and to my amazement 19 of the 27 devices running on Antarctica it’s still running as well as the 23 year old energy trading platform.

@OverpassApps 3 ай бұрын

Yeah. I get that. It's because we have started relying on frameworks for servers and distribution that we have these problems now. I've never been a C guy. Maybe I should have.

@CallousCoder 3 ай бұрын

@@OverpassApps I agree, it’s the frameworks that really are the issue of the immense (almost idiotic) short life cycles of most software these days. I’m baffled that IT managers and CTOs allow this to happen, it’s such a waste seeing apps being rewritten within 5 years. If a house was written off in 5 years we’d be appalled 😱 Thats usually the amount that’s thrown away working 3 to 5 years 🤣

@gruntaxeman3740 3 ай бұрын

@@OverpassApps Idea of framework is that they standardize conventions so everyone can just look framework documentation and use same convention. It is really for communication, sure everyone can write software without framework and put things together with own conventions and adding bunch of libraries, but that requires huge amount of work in documentation. Downside in framework is that they live, and require maintenance. So key thing is choosing framework that works next 20+ years, and do maintenance work, cleaning it and moving to newer versions and fixing that if something is deprecated. It requires that developer is doing maintenance work on that code base by fixing everything that breaks and cleaning up all warnings and deprecated calls. Simple software (or component) can be of course written without framework, just using language standard library or something. Language can be also standardized. That kind of software lives much longer without maintenance. For longer lifecycles it is not enough, only sane way to write very long life software is to write book about software where book describes the problem and every line of code described why they exist, because programming languages can also change.

@gruntaxeman3740 3 ай бұрын

I have quite a lot of insight into software development that I know how to avoid having things getting deprecated too early. Software do have lifecycle that need to be specified, and also maintenance costs. How project is made and maintained depends on those.

@nz_coderman 3 ай бұрын

Letter T, especially when it is between arrows, like this

@fplove 3 ай бұрын

That's one of the main reasons I appreciate the Perl ecosystem and absolutely hate web frontend development, where frameworks deprecate at the speed of light.

@OverpassApps 3 ай бұрын

I use to be reluctant of frameworks. It took a while ot accept JQuery (I'm old) but was glad I finally did. But we got to a point where a new framework was coming out every day it seemed. And the people who write them got bored with them and stopped maintaining them. But I can't believe Google and Microsoft and other huge companies would abandon devs at the rate they are.

@fplove 3 ай бұрын

@@OverpassApps It's even a question of style of development and rate of changes in projects. Too many projects have unstable APIs by choice.

@gruntaxeman3740 3 ай бұрын

I put some time ago up and running old C project. That was written in mid 80's.

@FISS007 3 ай бұрын

Wasssuuuup Eric :) glad to see you back :)

@OverpassApps 3 ай бұрын

Wassssuuuup! Dude, good to see you again!

@minikame2272 3 ай бұрын

babe wake up I think Tom Scott is back

@OverpassApps 3 ай бұрын

Haha. Nah. He had that cool deep voice. I wish I sounded that cool.

@cern1999sb 3 ай бұрын

And then you're looking for how to use an API. You find a good stack overflow post or explainer video that demystifies it, only for a strikethrough to appear when you type it into your editor, and you're back to square one

@OverpassApps 3 ай бұрын

Yeah. It's like you can't even rely on Stack Overflow anymore. And even if you want to use AI to help out, it's not current enough.

@minikame2272 3 ай бұрын

In all seriousness though, I went through this exact issue with a client of mine. Their regular developer was proving to be frustratingly slow to action fixes and their notifications system had fallen apart. Alright, easy fix for sure? Not quite. To fix it on the back-end, I had to also fix it on the front-end, which meant pushing out new versions of both mobile apps... which meant targeting the newest APIs... which meant refactoring a lot of legacy code in languages I don't even know, something which was a total non-issue when it was just a straightforward logic tweak... I had wildly, wildly mispriced that job. Never again.

@OverpassApps 3 ай бұрын

This is exactly the kind of stuff I'm dealing with. I had to turn down some upgrades because they wouldn't compile anymore. And the price I had to quote was just stupidly high. But I had others where I ate the cost and I resented every second of it.

@angrydog4379 3 ай бұрын

Literally as I am building my app I run into this all the time now especially with Android, it literally change as I am working. Something to note Android 9 to Android 13 for example it is almost day and night now depending on what you are trying to do. My Gradle broke twice in 1 hour trying to get everything going. I don't even want to look at my manifest right now it is a mess I will clean it up later today but man yea i think things are going to get harder.

@OverpassApps 3 ай бұрын

Yeah, going to Android 13 and all the permission changes were a pain. I have so much conditional code in my apps checking for the version that it interferes with code readability. And the benefits don't seem to be that great.