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.

I used to use Manictime[1] to achieve something similar, although, that was for time tracking purposes. But I can admit I've used it multiple times to find websites and documents that I forgotten the name of using the screenshots. But in essence, It suffers from the same flaws as Recall.

[1] https://www.manictime.com

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");

Someone at Azure thought of this[1]

[1] https://github.com/Azure/fetch-event-source

Having gone down the rabbit hole of creating printable media/pages from html/css, I also discovered paged media. Generating printable pdfs using only the standard is very cumbersome but thankfully pagedjs[1] exists, which makes this a breeze.

[1] https://github.com/pagedjs/pagedjs

After working with Keycloak for a couple of years I honestly got fed up with all it's quirks and started to look at alternatives, Authentik and many more looked promising but Zitadel[1] caught my eye and I've never looked back since.

[1] https://zitadel.com/blog/zitadel-vs-keycloak

Netmaker[1] is another player in the space

[1] https://www.netmaker.io

> 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!

Interesting idea. However I do like the approach bankid did using qrcode [1] this does not however match a domain but matches a particular vendor that shows up after you've scanned it and asked to enter your security code. This way you can always verify the vendor is actually the website you are trying to log into.

[1] https://www.bankid.com/en/utvecklare/guider/teknisk-integrat...

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 :)

This is simply not true, it's negotiated between the client and server and defaults to 100 usually. 6 is the limit for http 1.1 not http/2.

Source: https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...

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.

The way pdf has become a standard in everyday life is truly disgusting.

One is expected nowadays to have a pdf reader installed on your device, this is a problem in it self because most of the software short of just reading the pdf, that are "free" does not include most of the features one would come to expect to utilize the standard. Now I don't have to sign pdf's daily but when you start a new job for instance and have to sign a pdf it becomes troublesome.

As a developer the ecosystem is pretty terrible too, in order to utilize said functions such as signing you'd need to fork out a huge chunk for a subscription to some library. Don't get me wrong, paying for software I'm all for but forcing your users to pay for some third-party software to interact with your documents is not fine.

To me, this is simply disgusting that you'd have to buy into this "standard" in every aspect, both as a user and as a developer.

We've come a long way over the years of having more options to both users and developers but honestly, it's simply not enough. And pdf as a format being very complex it's more than understandable that it would be a challenge to make it more available.

I've used it with much success, it works pretty well but there's a lot of quirks and gotchas, nothing major but it can be cumbersome.

if only there were an open source and easy to use pdf library with pdf/a support :/

That's what semantic versioning is for, breaking changes are inherently allowed in major version bumps.

I highly doubt you can count minified as "compiled" Minification is a form of compression. Compilation is a form of conversion from a high level to a lower level interpretation and that is fundamentally different.

But then again I'm not a lawyer :)

Seems like this could have been better handled by suspending you from commenting and creating issues instead. Best bet is probably appealing like you've tried already.

My isp don't offer ipv6 either but I've worked around the issue using tunnelbroker.com from hurricane electric (free) to get a /64, it works really great. Route48 is another such free service.

I would love to see something like dbaclone [1] but for postgres which in principle creates a new database and redirects reads to the source db and writes to your clone.

This works very well in unit testing for us but there are situations where we use postgres and not sql server.

[1] https://github.com/sqlcollaborative/dbaclone

Keep in mind that every vendor defines TDP differently, linustechtips have highlighted this many times and even has a video on it [1].

So comparing TDP across manufactures is not a fair comparison.

[1] https://www.youtube.com/watch?v=yDWO177BjZY

The bookmarks feature of pdfs doesn't exist in chrome's pdf engine which means paged.js don't support it either last I checked.

We solved this by post processing the pdf generated with paged.js + puppeteer with itextsharp (LGPL) to add the bookmarks.

We captured the toc using the paged.js "after" hook and put that into a variable which our backend could then grab from puppeteer.

We too had this problem, we solved it using the 3 letter country code instead.

At the company I work for we used chrome headless paired with https://github.com/pagedjs/pagedjs to fill in the gaps and it works very very well.

How do you even have logs for something like this? I feel like the log level to see the raw cookie responses would be a no go since you'd easily have hundreds of gigabytes of logs every day.

If it turns out it's the upses that caught fire, one can't help but wonder if it would be a better idea to house the upses/backup power solutions in an adjacent smaller building outfitted with sprinklers perhaps?

One big drawback of postgres when updating data in a jsonb column is that it needs to rewrite everything even when you update the value of a single key, this gets very expensive if you need to update many rows. As far as I can tell, Mongodb handles this better. Other than this I also prefer postgres despite this limitation.