The author just push LLM nonsense. PWA's are great for field app where internet is scarce and without the need to rely on google to keep side loading possible. Not to mention the nightmare if you even want to deploy the side loaded app to a fleet of phone without needing to use google play store to publish it as an internal app.

One of the best manhwa IMHO

It matters for longer runs and higher speed. The twist provides noise cancellation effect

For the kind of supported data, one looks at the README and it supports a lot of different kinds of metadata, hence the generic description. A jpeg (or other image) metadata editor cannot edit metadata for geospatial surveys for example. But this application can. And manage it like any other CRUD application works. By providing users a way to enter a new entry, edit it, remove it, query it, all kinds of things really.

...can you post your monitor setup?

Nothing? I'm pointing out another way to "attack" some LLM?

So, you know LLM has a context window right? That means context overflow is a valid LLM attack strategy if you are somehow able to send more stuff than what is allowed.

I am so proud of this community

Wait, fable has a feature to create our hero? I thought the hero was predetermined. Forgive my ignorance since I only ever played The Lost Chapter. I hope MS will give fable the Halo treatment so I could play the other series too.

Seriously asking, what is The Pack community? I've seen their memes are basically like this and talking in CAPS.

At least virus have different genetic code which suggest they are different something. Prion is just normal protein gone rogue.

I do think everything has its place. For example, you can do offline PWA with SPA since a page load doesn't need a call to the server for rendering it. It also saves processing time/bandwidth by offloading the server from the burden of rendering the page. Once the page has loaded, the web app only needs data, not markup nor style. And last is that it is great since it only requires a browser without needing to write native apps in myriad of languages. Distributing and installing it is also not limited by the Apple/Google tax.

For clouds, there are certain workflows that can surely benefit from it. Maintaining your own infrastructure 24/7 with minimal downtime can be overwhelming for SMALL teams, especially one man show. Even more so when the product/web apps suddenly blows in popularity and now need to scale. Even more so when it is being DDoSed. The point is, many things can go wrong. And when you are deploying it for 24/7 use, down times can be costly. Deploying to cloud early and then slowly building towards on-premise after the team gets bigger is a viable route IMHO

And last is container devops. I think it also solves a lot of problems in multi-tenancy or even when running multiple services. Not everyone will use the latest-and-greatest version of a shared library. If the library is somehow conflicting with other tenants/service, you will have a bad time. Also, developing inside a container or virtual env can make testing and messing around safer since you didn't affect your system installation.