HN user

TkTech

1,288 karma
Posts3
Comments294
View on HN

For many companies (country-dependent) that's not really why they use cloud services vs purchasing. It's tax shenanigans and business process overhead. OpEx vs CapEx, and a small (%) bump in the huge AWS bill no one will even notice or a $30k+ invoice for hardware that has to go through rigorous review and 3 departments.

Same reason people pay for things through the AWS marketplace (like Vanta) instead of having to go through their invoicing process.

This continuing trend is going to do a fantastic job of ensuring fewer and fewer individuals can launch casual projects and gating (non-VC) startups to those who already have the means.

No, those search engines will simply stop being used by people that care. Google's "AI results" have already wrongly accused people of being sex offenders and make up gibberish constantly. They are a blight and a scourge. There are already many lawsuits against the garbage it invents.

The "quality" of your prompt is irrelevant when you're feeding it to something that just imagines things.

Webalayzer! I'm not sure there were really any other options at the time other than writing your own. Parsed the apache logs and gave you pretty detailed results and you could see the usage (in kb, which tells you how long ago this was!) broken down by date and IP.

Once you added a redirect rule for the IP to apache you'd just check your log and see the IP that was hitting you every couple of minutes poofed for a good few hours.

I used to just start giving any IP downloading way too much a redirect to multi-tb NASA images. This was a long time ago but it was surprisingly how many would follow redirects and never time out. Wouldn't see a request again for hours and then its right back to downloading a new part of the sky.

Those images also used to crash all the early GUI irc and chat clients that showed inline images without size checks...

No, not usually. Few ISPs are willing to risk blacklisting.

Just like scrapers (and a lot of VPNs are quietly using their custom VPN clients to sell your own IP [and data] to scrapers) it's mostly a "don't ask don't tell" situation for IP sourcing. You use a multitude of IP providers and if a scandal happens you just say "We didn't know!" and move on to the next. Almost always grey-market, very rarely through legitimate providers.

It's very unfortunate but a significant amount of the most damaging stuff in this is from the underprivileged and those with minimal means who were trying to find help they could afford. Non-profits trying to get website help, confidential reports for charities trying to get translations, children seeking therapy (fiverr has a therapy category!?) for some truly dark stuff.

Utterly inexcusable that this is still up after so many hours.

Support only options aren't going to cut it in our experience; but maybe that'll be different with Python.

That's totally fair, and I can only speak from the sidelines. I haven't had a chance to review the architecture - would it possibly make sense to swap from async as a free feature to the process pool, and make async a pro feature? This would help with adoption from other OSS projects, if that's a goal, as the transition from Celery would then be moving from a process pool to a process pool (for most users). The vast, vast majority of Python libraries are not async-friendly and most still rely on the GIL. On the other hand, Celery has absolutely no asyncio support at all, which sets the pro feature apart.

On the other hand, already released and as you said it's much harder to take a free feature and make it paid.

Thanks again for Oban - I used it for a project in Elixir and it was painless. Missing Oban was why I made Chancy in the first place.

A combination of LISTEN/NOTIFY for instantaneous reactivity, letting you get away with just periodic polling, and FOR UPDATE...SKIP LOCKED making it efficient and safe for parallel workers to grab tasks without co-ordination. It's actually covered in the article near the bottom there.

Celery + RabbitMQ is hard to beat in the Python ecosystem for scaling. But the vast, vast majority of projects don't need anywhere that kind of scale and instead just want basic features out of the box - unique tasks, rate limiting, asyncio, future scheduling that doesn't cause massive problems (they're scheduled in-memory on workers), etc. These things are incredibly annoying to implement over top of Celery.

The Oban folks have done amazing, well-engineered work for years now - it's really the only option for Elixir. That said, I'm very confused at locking the process pool behind a pro subscription - this is basic functionality given CPython's architecture, not a nice-to-have.

For $135/month on Oban Pro, they advertise:

    All Open Source Features

    Multi-Process Execution

    Workflows

    Global and Rate Limiting

    Unique Jobs

    Bulk Operations

    Encrypted Source (30/90-day refresh)

    1 Application

    Dedicated Support

I'm going to toot my own horn here, because it's what I know, but take my 100% free Chancy for example - https://github.com/tktech/chancy. Out of the box the same workers can mix-and-match asyncio, processes, threads, and sub-interpreters. It supports workflows, rate limiting, unique jobs, bulk operations, transactional enqueuing, etc. Why not move these things to the OSS version to be competitive with existing options, and focus on dedicated support and more traditional "enterprise" features, which absolutely are worth $135/month (the Oban devs provide world-class support for issues). There are many more options available in the Python ecosystem than Elixir, so you're competing against Temporal, Trigger, Prefect, Dagster, Airflow, etc etc.

I might have missed it, but no mention of _where_ data is stored in the FAQ and seems critically reliant on Cloudflare.

In a changing world, what's the selling point for those outside of the USA? Why would our company pick this over self-hosting when our country is threatened with American annexation almost weekly? If I go with Zulip, mattermost, rocket.chat, matrix, etc I introduce maintenance overhead but I don't have to worry about unstable politics or a disliked tweet getting us sanctioned and banished from American-hosted services. The chat platform we use internally is critical business infrastructure and so we're required to ask these kinds of questions for business continuity.

Hard to understate just how expensive. Here in Montreal where ice storms kill and cause billions in damage, we still don't bury the main transmission lines. We been burying almost everything _in_ the city where having to repair millions of individual connections (again) would be impractical, but it's relatively simple to repair the limited major lines into the city.

From CBC:

Current estimates are that it would cost five to 10 times more to distribute electricity to a big city via underground cables, and that not all of nature's problems would be alleviated even if that were done.

Can you explain what part of that is "communist nonsense"? Appropriate taxation (and leaving them with billions still even after that)? Or was it feeding hungry children you're against?

America had a tax rate of 91% on the obscenely wealthy for decades and around 70% until the 80s. Reducing this to historical lows has universally, by both bipartisan and nonpartisan[2] parties, been found to have been the primary driver of inequality[1].

At even an absurd 99% tax rate, applied equally instead of tiered, Michael Dell would have $1.5 billion dollars.

[1] https://publicintegrity.org/inequality-poverty-opportunity/t... [2]: https://sgp.fas.org/crs/misc/R42729.pdf

It's a tiny pittance of what would have been owed had they been taxed appropriately, and seems conveniently timed to bury the news of Dell (via Dell Federal Systems) funding ICE (it's completely erased it from the first page search results for "dell funds ice" in less than 24 hours).

This isn't badass, it's a disgrace. They've hoarded an incredible amount of wealth generated by others and returned a sliver of it. You've been so conditioned to accept this system that you're even grateful for the scraps.

If they gave $100 billion, they'd still have over $51 billion in the bank. That's roughly $7 million a day for every day he's been alive, or enough to feed every child in America for over a decade. Imagine the regional economic stimulus if instead of being hoarded for nearly half a century that money was paid out in salaries to those actually earning that money. _And_ they'd still have billions.

(I'm biased, I'm the author of Chancy)

One of the major complaints with Celery is observability. Databased-backed options like Procastinate and Chancy will never reach the potential peak throughput of Celery+RabbitMQ, but they're still sufficient to run millions upon millions of tasks per day even on a $14/month VPS. The tradeoff to this is excellent insight into what's going on - all state lives in the database, you can just query it. Both Procastinate and Chancy come with Django integrations, so you can even query it with the ORM.

For Chancy in particular, retries are a (very trivial) plugin (that's enabled by default) - https://github.com/TkTech/chancy/blob/main/chancy/plugins/re.... You can swap it out and add whatever complex retry strategies you'd like.

Chancy also comes with a "good enough" metrics plugin and a dashboard. Not suitable for an incredibly busy instance with tens of thousands of distinct types of jobs, but good enough for most projects. You can see the new UI and some example screenshots in the upcoming 0.26 release - https://github.com/TkTech/chancy/pull/58 (and that dashboard is for a production app running ~600k jobs a day on what's practically a toaster). The dashboard can be run standalone locally and pointing to any database as-needed, run inside a worker process, or embedded inside any existing asgi app.

If you like Procastinate, you might like my Chancy, which is also built on postgres but with a goal of the most common bells and whistles being included.

Rate limiting, global uniqueness, timeouts, memory limits, mix asyncio/processes/threads/sub-interpreters in the same worker, workflows, cron jobs, dashboard, metrics, django integrations, repriotization, triggers, pruning, Windows support, queue tagging (ex: run this queue on all machines running windows with a GPU, run this one on workers with py3.14 and this one on workers with py3.11) etc etc...

https://tkte.ch/chancy/ & https://github.com/tktech/chancy

The pending v0.26 includes stabilizing of the HTTP API, dashboard improvements, workflow performance improvements for workflows with thousands of steps and django-tasks integration.

Germany most certainly covers treatment for aggressive adenocarcinoma, and it's covered at 100%. Germany is literally one of the best places in the world for all levels of oncology.

This isn't just with the hope of curing someone, even when you're terminal things like palliative chemotherapy are covered which can drastically ease your suffering.

I hate every part of this. The pain and suffering and the struggle for money that family had to go through because the richest country on Earth can't be bothered to provide for its citizens. Rebecca should not have had to use a damn gofundme to get health care while struggling with cancer. Her family should not have been forced to publicize her care in the desperate hope that strangers might help her live. Utterly inhuman.

RIP Rebecca.

I don't really believe this to be an issue - Valve directly contracts CodeWeavers, they developed Proton together, and they've been pretty clear from recent hiring bursts that it was specifically to work on Proton. I have to imagine the income from Valve is exponentially higher than the relative niche of CrossOver. They're basically a subdivision of Valve now.