makkesk8

Running Gitlab in any kind of scale beyond a single server is a major PITA. And it's very poorly optimized.

Awesome work! A killer feature of sqlite that I would love to see in pglite would be javascript window functions.

We moved over to garage after running minio in production with about ~2PB after about 2 years of headache. Minio does not deal with small files very well, rightfully so, since they don't keep a separate index of the files other than straight on disk. While ssd's can mask this issue to some extent, spinning rust, not so much. And speaking of replication, this just works... Minio's approach even with synchronous mode turned on, tends to fall behind, and again small files will pretty much break it all together.

We saw about 20-30x performance gain overall after moving to garage for our specific use case.

Looks useful, but what baffles me is.. Why is every framework setting state or their "signals" using "setX" functions? What's wrong with the built in getter and setters that you can either proxy or straight up override?

This feels arguably cleaner: something = "else";

Than: setSomething("else");

> however beyond Windows I don't think it has neither an established presence nor ecosystem

I'd respectfully disagree with this statement based on my personal experience. Ever since .NET Core was introduced, I've noticed a significant shift in the hosting of ASP.NET apps. Many developers, including myself, now prefer hosting applications in containers on Linux systems rather than relying solely on Windows. This change reflects a broader trend among C# developers.

While I understand that my perspective might not encompass the entire developer community, I strongly believe that the adoption of Linux-based hosting for ASP.NET applications has grown considerably. It demonstrates the expanding reach and influence of .NET Core beyond the Windows ecosystem, proving its establishment in other platforms.

Please note that this is solely my viewpoint based on my experiences and interactions with other developers. Other opinions may vary, but I remain confident in the growing prominence of .NET Core outside of the traditional Windows environment.

Looked at this a couple of days ago and it looks impressive! However, it does saddens me to see the elasticsearch api compatibility being behind a license, I had hoped this was also going to be open after discovering the functionality existed in the first place.

I guess having the cake and eating it too is actually not feasible in this case.

With that said I will indeed have a go at this and test and see if I can replace elasticsearch in our stack.

Good job guys!

We do this at work, albeit much larger scale than this and I'm the only one who spends any time on upgrades, replacing failed disks and so on. Honestly, apart from upgrades every 3-ish months I don't spend any time at all on this, it's all chugging along without intervention.

Things don't fail as much as they used to, at least not from using something mature as minio and of course hardware can fail as they do specifically spinning rust, which is non trivial to replace if you have hot-swap capable servers in the first place.

I don't possess any decade worth expertise in either minio or running this kind of setup so personally I believe you are exaggerating that this is even worth calling challenge at all.

But that's just my take :)

ESD safety is an important topic, particularly in industries where sensitive electronic components are involved. However, there are many misconceptions surrounding ESD safety, especially when it comes to the use of cardboard and cotton clothing.

Cardboard, for example, is often thought of as a safe material for packaging and handling electronic components (motherboard boxes included). However, it can actually generate a significant amount of static electricity, which can damage sensitive components. Similarly, cotton clothing is often thought of as a safe material to wear in ESD-sensitive environments, but it can actually generate static electricity as well, polyester is generally considered preferred over cotton.

It is a common misconception that electrostatic discharge only causes damage if you can feel it. In reality, ESD can cause damage to sensitive electronic components even if you don't feel anything.

In fact, the damage caused by ESD can be more insidious when it is not noticeable. This is because when ESD is felt, individuals are more likely to take precautions to prevent it from happening again. However, when ESD is not felt, individuals may not even be aware that damage has occurred, leading to potential failures or malfunctions down the line.

I would advise anyone working electronics in any capacity, it's important to keep ESD in mind, as many sporadic issues are more than likely related to electrostatic discharge in some capacity.