Python has Interfaces in the form of protocols, but those are explicitly duck-typed
Python has Interfaces in the form of protocols, but those are explicitly duck-typed
Thank you for sharing your experience, those points are exactly what I’m worried about. Let’s hope the situation improves over the next couple of years!
Would you say the technology is developed far enough?
I’m definitely interested, as the phone screen size is often a bit too small. But any mechanical movement makes me nervous on a small device that should last multiple years.
Yes, they can be written in maintainable ways, I didn’t disagree in my original comment. That doesn’t change that most of the projects I come across to this day are absolutely unmaintainable messes. I’m not talking about Python from 10 years ago, I’m talking about the projects I encounter now.
The biggest issue is that you have to limit yourself to a mostly non-dynamic subset of Python if you want type checking etc. to work, and you have to write your own type definitions for many dependencies. Most projects don’t do that, they instead lean into the dynamic nature of Python, which makes them unmaintainable after little time.
Python is by far one of the worst languages I’ve ever seen in relation to maintainability, second only to Javascript (due to missing types, which are fixed by Typescript).
Seriously, it’s rare for a Python project with more than 1,000 lines to not turn into an absolute mess thanks to the layers upon layers of meta programming, weird edge cases and so on. There are whole bad patterns I’ve never seen beyond Python codebases.
Things are improving slowly thanks to type hints and so on, but they are still far from where they need to be. Python is used in even more dynamic ways than JS, so the type system needs to be more expressive than TS. You can’t even define a function that appends two tuples with proper type hints!
They apparently like making memes shitting on people & things without really understanding why, like the one for the NVidia CEO
Actually the Red Star developers seem very serious
What are you referring to by “OSI”? Not the 7 layer model, but that’s all I can find. It’s good to explain abbreviations when they’re not the most common usage of that abbreviation.
If they don’t have my contacts, they can’t spoof a number from my contacts. If they just spoof local numbers, the chance of them choosing one of my contacts is incredibly slim.
And how does a scammer get my contacts?
Well yes, you didn’t get first ads. But what about second ads?
Well if it were closed source, it would be harder to repackage proprietary apps because you would not know how the snap “root filesystem” translates to $DISTRO root filesystem.
Only if all the other tools (like Snapcraft) were also made closed-source and obfuscated, but that’s besides the point. What if, for example, Snaps start costing money, and you can’t legally turn them into Flatpaks and distribute them? What if the only legal way to get some software for Linux will be the official Snap repository? This approach will make for a far worse user experience than simply using the already working, already open-source and non-enshittifiable alternative.
Because some apps are only packaged as snaps so if you want them to be accessible to users, you have to install snapd. Flatpak can still be the default which on non-Canonical distros already is. Which why I don’t even worry about snap becoming the standard.
And by promoting Snap to the same status as Flatpaks on other distributions, you’re opening the gates for enshittification and a worse user experience tomorrow. Again, why support it as an equal option if we all know the price?
Don’t forget that macOS literally contacts Apple server for every binary you execute. When there was an issue with those servers, only Apple software was launchable.
I’m aware, it was mostly a joke about these “features” making Notepad worse. Nevertheless, thank you :)
More like Notepad–, amirite
Okay, and how does snapd being open source help with that? It literally has no effect on it.
And when your best argument is “if it gets enshittified you can switch off of it”, why help it get popular in the first place?
Though you’d get the same speedup if you used SIMD intrinsics. This is just comparing non-SIMD to SIMD.
My guy. There is no open backend for Snap. If Ubuntu enshittifies Snap, nobody can host an alternate backend for them. How does the client being open source help you?
Honestly, why enable this kind of behavior in any way? Any user is free to make an informed choice by installing it themselves.
We all know how this goes. Once a critical mass is reached, enshittification begins to milk everything dry. By making it an installer option, you’re legitimizing it and supporting a worse future for the Linux desktop.
The system would have to be built so that the government can’t connect the user to the website, as you don’t want the government to build profiles on website usage by person. Though the bigger challenge here is trust - even a technically perfect system could be circumvented by the operators.
A good example for this were the COVID tracking apps. The approach was built so that as little information was leaked as possible.