The vacuum pressure is real. Using a system with the skip locked technique + polling caused massive DB perf issues as the queue depth grew. The query to see the current jobs in the queue ended up being the main performance bottleneck, which cause slower throughput, which caused a larger queue depth, which etc.
Scaling the workers sometimes exacerbates the problem because you run into connection limits or polling hammering the DB.
I love the idea of pg as a queue, but I'm a more skeptical of it after dealing with it in production
Because it's Afrika Bambaataa. He invented entirely new techniques for making music - which is already enough for him to be relevant here - that influences what many of us listen to daily.
I think a big piece missing from these conversations is compliance frameworks and customer trust. Of your selling to enterprise customers or governments, they want to go through your stack, networking, security, audit logs, and access controls with a fine toothed comb.
Everything you do that isn't "normal" is another conversation you need to have with an auditor plus each customer. Those eat up a bunch of time and deals take longer to close.
Right or wrong, these decisions make you less "serious" and therefore less credible in the eyes of many enterprise customers. You can get around that perception, but it takes work. Not hosting on one of the big 3 needs to be decided with that cost in mind
It's night and day. It's also about access. The labs in legal states usually just test for more things. For a while, it was one or two labs plus a Cole extraction companies that were pushing the testing boundaries. Then, relation caught up and pushed the broader testing on to everyone. Then there were managed batch sizes (though these got too small in Oregon). Hemp does not have the same regulations, and unregulated states have way less infrastructure (including access to good labs).
Nobody wants to harm their customers, but it 100% happened in the early days. A lot of harm is/was not immediately obvious. Of was repeated exposure to harmful chemicals. Good intentions are great, but resources and incentives still matter. Nobodyv wants to get hacked, but building a new feature over hardening is what stops you from getting yelled at
This is a weird one. It absolutely should not be haphazardly added as a rider. The 0.4 per container is also insane. But, this really was an unintended loophole of the 2018 farm bill. Most plants grow THCa, which turns into Delta-9 when heated. They were ignorant and straight up forgot to specify anything except Delta-9.
Cannabis is a bioremediator and absorbs basically every environmental toxin from the ground (pesticides, heavy metals, etc.). Extraction (for CBD and THC oil) increases the concentration of any present toxins.
The only way you know of the problem is by thoroughly testing every batch. Pesticides that are safe at low levels can get concentrated and become really problematic at high levels.
States where marijuana is legal require all of this testing, so the products are much safer. Hemp-derived THC does not require these tests. (Same is true for CBD, but that's a while other conversation...)
So their team is anonymous. While I understand the desire for that, trust is built through transparency. It's really hard to convince someone who's job, career, it potentially even life is at risk to trust random strangers on the Internet.
It seems like they need people willing to stretch their name to create credibility.
Ah, that's a shame they went that way. What I tell people when they're first getting into GCP is that it's gonna be a passion to set up what you want. But, the offerings are great, and once it's working, it'll just work
Oh interesting - I haven't been on their starting page in years. I'm surprised getting started with vite isn't higher up. That takes 5 minutes and doesn't require a full framework.
That said, starting with react router or expo is probably the right call depending on the project needs. Routing is not something you want to do yourself, and react native is pretty unfriendly without expo
One issue we're running into at my job: we're struggling to find entry-level candidates whoaren't lying about what they know by using an LLM.
For the tech side, we've reduced behavioral questions and created an interview that allows people to use cursor, LLMs, etc. in the interview - that way, it's impossible to cheat.
We have folks build a feature on a fake code base. Unfortunately, more junior folks now seem to struggle a lot more with this problem
This comment makes no sense. They're actively open sourcing the patent and trying to get it upstream into Postgres. They purchased another company to get this patent, and they're spending a lot of money on lawyers to figure out how to release it to the community.
Call out shady shit when companies do shady things, but the sentiment behind this comment seems to be looking for reasons to bee outraged instead of at what's actually being done.
If companies get evicerated every time they try to engage with the community they'll stop engaging. We should be celebrating when they do something positive, even if there are a few critiques (e.g. the license change call out is a good one). Instead, half the comments seem like they're quick reactions meant to stoke outage.
Please have some perspective - this action is a win for the community.
Yeah, huge props here. There's a contingent on HN that seems to assume that almost any action by a company is done in bad faith. I dislike all of the shady stuff that happens, but that's why we should celebrate when companies are doing awesome things.
This is all positive. Super appreciate what you folks have done. It's clearly hard, well intentioned, and thoughtfully executed.
Nice! I'm using DBOS and am a little active on the discord. I was just wondering how y'all handled this under the hood. Glad to hear I don't have to worry much about this issue
Do you know if people have tried distributing execution across multiple machines using Effect? That's one of the big advantages of fully immutable code execution imo, and I'm really interested if anyone has succeeded in leveraging Effect for that purpose.
That was my first thought too. I thought it was a new web framework at first, then an ETL pipeline library. It took me about 5 pages of reading before I found an actual description, and I only knew what it was trying to accomplish from the code example because I've done functional programming before
Just reading the docs, but it looks like it forces these errors into compile-time checks instead of runtime checks. It makes you a lot more confident that code that compiles with run correctly and without error.
Seems like it's mostly trying do similar things to what Haskell or StandardML does, but in Typescript.
There's an excellent essay on Anarchy Unbound about this. It analyses inter-group transactions and methods to not be cheated. Essentially, cheaters are defined as people who discount future transactions as 0. Therefore, I've easy to filter them out it's to require an upfront cost for any unknown person to transaction with you.
The thing that blew my mind was you can use non-monitary costs. E.g. if someone from an out group learns your language and your culture, that's a moderate investment. To recoup that, they need to make multiple transactions and are therefore less likely to cheat.
It's by no means a perfect metric - and it works much better in smaller, tribal settings - but it's still a fascinating analysis
That is not how the US legal system works. You can sue someone for and regardless of merit, and they will have to defend themselves. That costs time and legal fees. If they lose, they can appeal, and continue appealing. If it's baseless, they'll lose, but you still spend a lot of money and time dealing with the lawsuits.
Scaling the workers sometimes exacerbates the problem because you run into connection limits or polling hammering the DB.
I love the idea of pg as a queue, but I'm a more skeptical of it after dealing with it in production