- cross-posted to:
- python@programming.dev
- programming@programming.dev
- cross-posted to:
- python@programming.dev
- programming@programming.dev
You must log in or register to comment.
Oh that’s sad. I was hoping for that the title of the post was misleading, and it just meant that the “experimental” flag was removed. Well, sadly no.
Little rant: My eyes hurt from reading 100% white on 100% black background… Wish sites stopped doing it. Thank god Firefox has this builtin reader view functionality.
do you know the stylus extension?
Yes off course. There are also other alternatives, but its nice to have a builtin functionality. Also each of these plugins had their own quirks in one or another form (don’t ask me what the details was, I don’t remember).
Wait, I was hinting at this because I was hoping to get noticed as the creator of the most popular style for this site 🥲 : https://userstyles.world/style/933/lwn-dark-breeze-enhanced
but I just realized I don’t have the extension on mobile yet the theme is dark. What’s going on? they did update the website and you still have light theme?
Nice! Well, I never paid attention to user created styles and was always doing it myself. From the screenshot, I have to say, it looks really good and is tempting. I’ll consider it, but really don’t want to install more extensions if possible.
I am eagerly waiting for someone to vibe code a version of Python that isn’t shit. Probably not far off I expect.
Just rewrite it in Rust
My rule of thumb: If I wouldn’t write it in bash, I won’t write it in Python. Anything more serious gets a grown up language
My rule of thumb is if it uses more than one variable, an if statement, parameter expansion, or string interpolation I just write it in python with argparse and file input.
Much cleaner, easier to reason about, and self documenting.
Bash and Python are very different. Bash uses your system as programming language, while Python offers a lot more. Python is in many cases a good solution that does not need extra work for programming languages to compile. If you don’t think that Python is a grown up language, then you seem to be misinformed.
Python may be a grown up language but it’s still a pretty awful language for ad-hoc scripting. It really wants to believe that you only use it for writing Python projects damnit! You can beat it into submission, but as soon as you start typing
importin a situation that isn’t a nice pure Python package it will say “whatchulookinatmate? Youwannafight?”Don’t believe me? Explain how relative imports work.
I write Bash, Python and Rust. And I love writing in Python. It helped me so much and prefer it over almost any compiled language. Bash is completely different beast and not a replacement for Python and vice versa. Just because import works different in the language than the ones you like, does not mean the language is crap. For any questions about the import system, have a look at https://docs.python.org/3/reference/import.html#package-relative-imports .
It depends on how you use the language, as a scripting like language or a full replacement for compiled languages. I personally don’t build packages with Python. BTW you can even compile Python scripts to binary machine code, and I don’t mean bundles, but real compilation process. It even speeds up the performance of the program.
Just because import works different in the language than the ones you like, does not mean the language is crap.
No, it means it’s unsuitable for scripting, if you need anything more than a single file. Better than Bash of course (not hard).
Python is good for scripting. If you start importing and having multiple packages involved with relative imports, that’s no longer “scripting”. We have standard library and the package manager for a reason. I think you are conflicting with full fledged applications and scripting.
my rule is much less strict: more than 3 files gets migrated. large Python projects are a nightmare to maintain, and performance is bad at scale. for quick experiments or data analysis it’s great.
but honestly Nushell has replaced Python for me for the most part, unless i need a specific Python package (and often i can just wrap that in a small runnable script with
uv)i just write the critical parts in c and glue them together with python, because if it’s one thing it’s good at it’s ffi.
Why bother with the significant pain of FFI when you can just write the whole thing in Rust?
Also “the critical parts” is mostly a myth. After a small amount of optimisation, the vast majority of programs do not have nice isolated hotspots.
Yeah anyway with AI why would you use Python for a new project? I just do everything in Rust now, including simple scripts.
Unfortunately there’s a lot of existing Python code.
Why bother with rust? Just tell it to write assembly
Assuming that’s a genuine question…
AI needs feedback just the same as humans. I would think of AI like a human that’s of average cleverness, but has a huge breadth of knowledge and basically infinite time and patience. They are going to be decent at assembly but they’re still going to make mistakes just like humans.
Using a language like Rust that has a lot of static correctness checks gives a higher quality result for AI, just like it does for humans.
i am eagerly awaiting the day when people learn to look things up again
None of those have been successful for various reasons (I think primarily because they all sound like they’d be a total nightmare to set up and maintain).
As soon as
uvprovides an alternative implementation so you can just runuv run --but-fastI think it will become popular.I would not be at all surprised if they are secretly working on a faster Python implementation. They own all of the non-shit Python tooling, they have unlimited tokens now, they aren’t afraid of vibe coding. Why not?
probably because they don’t do any themselves
