Hello Python community! There are a lot of resources online targeted at beginners that want to learn Python but very rarely do you see articles talking about moving to Python when you already have tons of experience in other languages like Ruby, and especially, many years of Perl experience and is interested in moving to Python.
I'm not looking for information on how to program in Python, that's really easy to find and most of the learning curve will be learning about the standard libraries and overcoming the years of muscle memory from other languages. I'm looking for information on the following topics:
- What's the recommended project structure for a library or a program that'll be distributed via PyPI?
- What are the general best practices to follow when writing "clean Python code"?
- What's the most commonly followed style guide for the language?
- How does import work internally and how does it perform its path lookup for local files (specifically for importing modules internal to a project)?
- How to properly set up pyenv for a project? (This one is tricky for me because the Python community loves pyenv and I'm used to having packages globally installed in Ruby and Perl)
Gnome Terminal when I'm in GNOME, Konsole when I'm in KDE, and plain old xterm for i3 and any other WM. These just feel like they fit just right into their respective DE/WM.
I've never used Google Domains, but Namecheap's solution is quite easy to use.
I won't lie, if you look at my Reddit profile you'll see that I've commented more here in the last couple of days than probably the last 3 years on Reddit. The community just feels more welcome and I feel as if my comment will get read instead of being drowned out as it happens on Reddit.
There once was a time when to make a PCB in our community was to use CadSoft EAGLE, a PCB design package which neatly filled the entry level of that category with a free version for non-commercial …
Ever since the Autodesk acquisition I've been stuck in version 7 and will probably stay in it until I retire, but it's extremely sad to see such an amazing piece of software die like this.
I would really love to see more "RPi priced" (around $30) RISC-V SBCs. It's hard to justify paying $60 to get into an ecosystem that has very little support.
Even with things like Treble the updates still have to come from the OEM, so unfortunately I don't see the situation changing any time soon.
For most of the users currently online it's extremely difficult to understand the concept of federation and how everything works, so I doubt it'll ever be as prevalent as "the big social media platforms", but for technically-inclined users, it'll definitely have at least moderate success.
It's quite sad that Google never figured out a way around this issue. The real problem is that they push the responsibility of updating to OEMs, which have no interest in updating their "old phones" (1 year old in most cases) because a new shiny one has been released.
I think the only way to really solve this is to make Android like Windows used to be back in the XP days. OEMs get a base system and they can customize it to their hearts content, but the updates to the base always come straight from the OS developer, no matter if the "OEM customizations" are ready for it or not.
There are lots of extremely useful information that has been posted on Reddit over the years, just think of how many times you've searched for things like "best X alternative Reddit" and found a great app suggestion, or when you searched for an error and someone asked about the same thing on Reddit a couple of months ago. This knowledge needs to be preserved and we do need to help the Archive Team out so that we can keep this invaluable source of knowledge.
Saldy it's very common to have this influx towards the "main server" as people that are not used to the federated aspect come to the platform.
Either way, it would be interesting to collect this information and later post some metrics about the exodus from Reddit, kind of like how Fosstodon and other Mastodon instances did when Twitter had their issues.
Nathan Campos @lemmy.ml Exploring electronics and programming one experiment at a time.
Mastodon @nathanpc@fosstodon.org Work Innove Workshop About me Nathan Campos