Sounds more like a you problem, probably due to unfamiliarity. There are endless options for local dev on a Mac, and a huge share of devs using one.
But it's a fair point. If you truly have no option it's better then absolutely nothing. I really wish people would stop writing mission critical production code in Python.
For example I work on a python codebase shared by 300+ engineers for a popular unicorn. Typing is an extremely important part of enforcing our contracts between teams within the same repository. For better or for worse, python will likely remain the primary language of the company stack.
Should the founder have chosen a better language during their pre-revenue days? Maybe, but at the same time I think the founder chose wisely -- they just needed something that was _quick_ (Django) and capable of slapping features / ecosystem packages on top of to get the job done.
For every successful company built on a shaky dynamic language, there's probably x10 more companies that failed on top of a perfect and scalable stack using static languages.
But it's really valuable documentation! Knowing what types are expected and returned just by looking at a function signature is super useful.
I've worked on large python codebases for large companies for the last ~6 years of my career; types have been the single biggest boon to developer productivity and error reduction on these codebases.
Just having to THINK about types eliminates so many opportunities for errors, and if your type is too complex to express it's _usually_ a code smell; most often these situations can be re-written in a more sane albeit slightly verbose fashion, rather than using the more "custom" typing features.
No one gets points for writing "magical" code in large organizations, and typing makes sure of this. There's absolutely nothing wrong with writing "boring" python.
Could we have accomplished this by simply having used a different language from the beginning? Absolutely, but often times that's not a option for a company with a mature stack.
TL;DR -- Typing in python is an exception tool to scale your engineering organization on a code-base.
Other than the podcast thing of course which is unique.
Mostly curious about perspectives of folks who used both and can compare them.
I try starting my morning with learning, lately having a podcast to listen to while I start my day has been awesome.
Some advantages for me:
1. I don't touch your credit card or personal info. I don't want to know those things. I don't want to be responsible for keeping them secure.
2. Integration with the post office for generating shipping labels is seamless.
3. I think people are more confident to buy something from a little known business if they feel that PP is protecting them. The increase in sales probably covers the PP fee.
4. I can run my business from a passive web page. All of the other services require me to manage some kind of server, running code, that I become responsible for maintaining. I love coding, but don't want it to be part of this business.
From reading articles and forum posts two main sources of horror stories seem to be:
1. People who just seem to be "accident prone" in terms of getting into disputes with others.
2. Selling non-physical goods, which I can only imagine has its own pitfalls that I don't know about.
Works perfectly well for us, we don't handle any PI or CC details and clubs can connect their PP account to our platform for their registration / event management needs.
Literally all the time? Every single month?
I am struggling to understand your perspective. In my existence, the bottleneck is always the coding.
The development team has a backlog that could keep them busy for years. Meanwhile, everyone else -- QA, localization, whatever -- operates at whatever pace the code gets delivered.
Never in my entire life have I been in the situation where the engineering manager said, "well folks, localization is backed up so we've got no more code we need to write. Go home and check in next week to see if we have any work?"
The only exception I can think of might be videogames where the bottleneck is the art and then maybe the testing loop. But gaming isn't representative of software development generally at all.
Initially I didn’t mind it because my team focused on technical debt, but it pretty quickly turned sour. Having to scrape up “work” for the team of 6 engineers each morning to appear productive to management was dreadful
Not really the same since Claude didn’t deploy anything — but I WAS surprised at how well it tracked down the ingress issue to a cron job accidentally labeled as a web pod (and attempting to service http requests).
It actually prompted me to patch the cron itself but I don’t think I’m that bullish yet to let CC patch my cluster.
I buy extensively from Amazon across a number of product categories. My order history shows purchases as far back as 2005 (though I cannot be sure given I remember buying things in 1998 while in college, probably on a different account). During the intervening 20 years I can count on one hand the number of products I ordered which weren’t legitimate, matched my—admittedly moderate expectations for any commercial product—or included overhyped reviews.
I’d be interested in a service like yours if I could understand how the cost would cover itself in benefits.
It makes sense on paper, if the service helps confirm legitimate reviews for you and convinces you to purchase said product, they should receive attribution revenue for helping generate the purchase.
The reality is much much messier though, because often times the people who award attribution revenue have a conflict of interest against any service that could even potentially expose bad practices happening on their marketplace.
I once worked for a popular deal site that developed a price tracking extension, a certain marketplace threatened to completely ban us from attribution revenue and we had to kill the extension over night despite our users loving it.
Like Claude not being able to generate simple markdown text anymore and instead almost jumping into writing a script to produce a file of type X or Y - and then usually failing at that?
[1] https://github.com/obra/superpowers