The giant arum is another example of beetle pollinated flowers. It smells of manure so attracts manure-loving beetles.
With more traditional pollinators, I've always found that a fascinating example of bee pollination that does not involve the plant taking advantage of the insect drinking its nectar is Ophrys Apifera, which has a distinct bee-shape silhouette and relies on the mating instincts of male bees in order to pollinate.
If it becomes a problem I would imagine that most victim plants will evolve certain defence mechanisms. For example, some insects will simply chew through flowers to reach the nectar stores - so I think in such cases a flower would just evolve a tougher skin, or secrete something that deters insects from doing that.
Whilst I think that criticism of such heavy-handed decision making is valid, I can't help but feel this blog post is littered with unhelpful and snide culture war remarks, and a smug attitude that this is the definitive end of Codeberg. If Codeberg truly has gone woke, people who espouse 'anti-censorship at any cost', like the author, will leave. But many others will remain.
I'm starting to get a bit of fatigue for these projects that boil down to just "I asked Claude to re-write this code into a new language that's in vogue right now!"
I really don't understand why this is needed outside of an opportunity to show how impressive LLMs can be when working within large codebases, but even then people in the comments are finding bizarre implementation choices that a human developer wouldn't make. I'll stick with Postgres and its - gasp - C implementation for now, thanks.
In this case it's justified because Rust allows safe implementation of threaded code. Current Postgres is per-process. Switching to threading yields performance improvements.
If you’re going to make a confident blanket claim, be ready to back it up - and asking for clarification is not trolling, by the way. You should be ready to engage in technical conversations if you want to make technical claims.
I'm not interested in a technical conversation with you; I was answering someone else. The top voted comment thread of this page, which dominates discussion, already covers everything you'd want to know.
Ah yeah, what I figured. You clearly have no idea what you're talking about. Don't get all mad when someone calls you out on it.
By the way, just so you have some concept of what the actual problem is despite your resistance to education:
Simply switching from processes to threads will not yield the claimed performance increases. A 300x improvement on analytic workflows? From a direct transliteration? Your BS alarms should be going off. They should be screaming "5 Alarm Fire".
The only way they got that increase was by breaking the synchronization mechanisms that provide ACID guarantees in Postgres, otherwise a direct rewrite would expect very similar performance.
The author was talking about eliminating memory being copied between processes. That's a performance improvement. I don't know how the 300x improvement was made or whether that's even real - you should really be arguing with the author about that. I didn't seriously put stock into it because you know, they used AI to rewrite it. I doubt their testing methodology is sound.
I appreciate the condescension though. Thanks for teaching stupid old me how a database works.
There is an expectation that threads are more performant than processes all else being equal. Obviously there is some work involved to make "all else be equal", like maybe threads have less isolation from each other etc but if you can mechanically convert code to use threads where it used to use processes I can see the claim standing up.
Threads generally have less memory overhead and context switching between them is theoretically faster, but as I suspect you know it is situational and not as simple as just s/process/thread/g. There are many tradeoffs, including the loss of memory isolation, and since Postgres is a network application which holds a rather important position in most architectures, proper memory isolation is very important.
Switching to threads doesn't guarantee weaker isolation, just like it doesn't guarantee better performance, but those nuances are why "switching to threading yields performance improvements" is over simplified to the point of uselessness. It simply reeks of the same kind of ignorance that used to drive statements like "rust doesn't have vulnerabilities" and "rewrite it in javascript for web scale performance".
I do agree, but maybe there is a valid mechanical conversion thats applicable in the postgresql codebase? I do get what you're saying but on the other hand, if he's passing tests with his conversion then this is different than some hypothetical, I'm just saying I would believe his claim on this one. I'm not going to port my erp to it yet but the performance win could actually be there.
When I was younger, bonsai always seemed to have a notoriety of being difficult to care for. I've got a ficus which I've owned for about 4 years now, and it's doing well because my apartment emulates tropical/greenhouse conditions on even mild spring days. I'm thinking about getting a large cloche for it to try and ramp up the humidity even more and encourage aerial roots. I've also got a Chinese elm next to it that's doing well, which I will move outside in the summer. The only worry with that one is how to keep it dormant over winter - I'll have to move it inside but I'm worried it will be too warm.
More recently I bought a Japanese maple shrub from a nursery. I was planning on turning it into a bonsai, but it's already re-grown its leaves for the season so best not to prune it harshly like I was planning. I think that's the main lesson to learn with bonsai - patience. It's going to be almost a year now before I can do anything major to it. Until then it will just be some extra balcony foliage.
I grow rare cactus and succulents and this is a similar lesson, patience. Also, more often than not the correct answer to anything is “do nothing”.
You also become much more appreciative of the most minute changes, noticing things that previously you would not notice. It’s a great practice for all of life, slow down, notice the small changes and sometimes the best thing to do is nothing.
I solved my problem of over-caring for many of my hardy desert plants by getting myself some more delicate plants which demanded more care, so that I was too busy with them and could give the hardier plants the neglect they needed to thrive.
I thought that was always the case. Dig as required to get your soil to the correct type for what you want to grow, then let it be and don't dig.
Digging to turn the soil seems like an old adage that has been passed down through generations, but modern scientific studies are now showing it provides very little to no benefit for yields.
With more traditional pollinators, I've always found that a fascinating example of bee pollination that does not involve the plant taking advantage of the insect drinking its nectar is Ophrys Apifera, which has a distinct bee-shape silhouette and relies on the mating instincts of male bees in order to pollinate.
reply