Many people argue that some #programming language is too slow for a task, this is often true, but what they don't realise, my language of choice isn't my bottleneck.
For example, writing a #Mastodon bot like @Python. Currently, the webscraping and processing of posts to Python Discuss takes a few seconds, but a simple bot like @3dprinting has no such processing.
So running the bot with #Rust would give me mo added benefit. Ok, cool, it now processes a new follower and sends a welcoming message within 0.1s instead of 0.11s. Cool, but you forget, we are using the same API, and this response time is negligible.
In the space race industry, they have a thing where if it is not feasible in the next 20 years, wait 5 and you'll be able to do it in 10 years, winnig 5 years in the end.
A company has limited resources, especially a startup type thing. Doesn't help that you bankrupt yourself for a POC. Build an MVP and then innovate from there.
But don't put it off too long. Otherwise, as you said, you get stuck.
#Programming is like a relationship. It needs constant work, and you need to be happy. If you start slacking, you'll wreck the relationship beyond repair.
Because we often say, "Why pay a C++ developer for something a Python developer can do in a week?"
Don't get me wrong, I do embedded, so I know my C++ and Assembly. I am a degenerate assembly lover and would use that before an Arduino because I can.
But doing so takes so much longer.
What you say is 100% true, and it is an easy thing to fall into. I think it should be determined by the lifetime of the code and the usage.
If it is a once-off use for database migration, just do it in Python. Yes, #Rust can do it faster, but should I spend so much more time to code this once-off problem?
The other thing is, again, where is your bottleneck? If my servers can only handle 10k users, Python can handle 100k users, but only 5k users will use it, go Python.
But you should always evaluate your solution and look at the ROI of upgrading now or in the future.
Recently watched this video by #ThePrimeTime on #Youtube, and his hot-take 🔥 was that they were using #Ruby, and half of their pain was caused by this.
I have no experience with Ruby at all and most probably won't even recognize it if I were to read it.
If Ruby is such a bottleneck and inefficient, why did #Mastodon :mastodon: use Ruby for its implementation?
I know Ruby is often praised for servers and backends, especially APIs, but we have many solutions for this in #Python :python: , which I wouldn't recommend, but #Go :golang: and #Rust.
Does anyone have opinions or sources for this statement?
I like #Rust and #Go :golang: for backends. For simple personal prohects, #Python :python: and #Flask are great. The development process is fast, I can push it out under hours. But I wouldn't use it for mission critical systems!
I'm really proud of myself for returning after work after an extensive absence due to what was most likely autistic burnout, but now after being made redundant I'm job hunting and every time I mention that I want to work 30 hours a week it immediately shuts down the conversation.
So if you happen to know of any jobs in tech for someone with a background in #Linux device drivers working mainly in #C and some experience with #DevOps working in #Python, remote in the UK but preferably with an office in the north that does allow working less than full time please let me know.
I started working on the next iteration of #image2sound which was inspired by the idea that sculptors simply reveal what is hidden within the stone. What if the image itself determines the key, the tempo, etc. rather than the user passing arguments to the utility?
Version 0.5 of #image2sound is out! This is a #Python utility I wrote that converts images to sound. This version adds a "reveal" mode, which allows the utility to derive the key, tempo, and track length from the image data itself instead of depending on user specified arguments.
And Sam Gross has submitted PEP 703 (Making the Global Interpreter Lock Optional in CPython) to the steering council for consideration for Python 3.13!
"Thank you, everyone, for responding to the poll on the no-GIL proposal. It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details."
You already know about 🐍 Snakes on a Plane, but how about Planes on a Serverless? At @pythonfrederick, @pierson_pat showed off the openly available plane data from 1090MHz and how he maps those flights on the web with a #Python lambda. https://www.youtube.com/watch?v=dMFWMTIyEgU
Just finished giving the closing keynote for Women Who Code Python Dev Summit: Block Data Py🎙️💁♀️
Such a wonderful and supportive community. Thank you so much for having me, and letting me talk about bots, APIs, and about my Raspberry Pi aquarium/potato-cam.
Video will be out soon, in the meantime you can check out my slides here:
ICYMI: @Posit and Databricks are partnering to provide #RStats and #Python developers with an easier way to connect workspaces, access data, run code, and interact with other resources. 🎉
What does this entail?
• Enhanced access to your Databricks Workspace from Posit Workbench
• Support for #Spark Connect in R via sparklyr
• Posit Workbench in Databricks Marketplace
Jupyter + Quarto = easy scientific and technical publishing!
At #JupyterCon, J.J. Allaire shared how the two work together to easily create and share the output format (HTML, PDF, Microsoft Word, reveal.js) and the styling you need for any situation.
There are so many features that make scientific and technical publishing an actual joy. Check out his talk to hear more! #Python#Quarto
🐍 On this Building SaaS with #Python and #Django, we continued the work to make school breaks work for individual students. There was a lot of design and test philosophy discussion along the way. https://www.youtube.com/watch?v=yL8qn3-nLO8
Yesterday, with the launch of @Python, I decided to have the #PythonDiscuss cross-posting as follower-only posts.
This was intended to not flood the #Python hashtag and because we tested in production🥳
The problem with this however is, now followers can't boost a cross-post, and their comments will also be private. So, I will be making it as unlisted posts.
This way, it won't show up in public timelines, but people can view, interact, and reply to it without following the bot.
I think I have dived into more practical #Python code (of my own making) in two weeks than in 10 years running python code here and there without ever really grasping what it was really doing... But this is how I learn.. I use it before I cook it.. Sometimes for years until what was "Chinese" to me becomes not just readable but also understandable and guess what.. It feels damn great!
Oh I'm not going to publish it just yet but it works and it does boring things humans shouldn't have to do!