I have been building Kreya [1] for over 6 years now as a Postman alternative. It's offline-first and privacy focused with a storage format made for git.
In all our years, Kreya "just worked" for our users without any drama or unwanted changes, unlike most of our competitors...
Sorry to hear that! That warning is unlikely the cause of the crash, it just means that some GKT3 settings are no longer supported in GTK4 and should be removed from the settings.ini, but they do not crash the app.
Please note that our AppImage does not include the required libgkt-4-1 and libwebkitgtk-6.0-4 dependencies. I just noticed that this is not documented, my bad! Installing them will probably fix your issue.
If not or if you have any other questions, you can write me at [email protected]
Mad respect.
Kreya is my go-to for playing GRPC endpoints. Basically every other tool has some whacky behaviour, got rapidly abandoned, or had janky ux.
Many may think that EDIFACT is easy to parse, which may be the case. But it is NOT easy to interpret.
There are hundreds of "substandards" per industry. For example for clothes or medicine, most vendors have custom fields outside of the standard which MUST be interpreted/sent or everything falls apart
In my corner of the world, all official grammar descriptions finish with a sentence like "or another interpretation by bilateral agreement" (where bilateral means between any two vendors using the same "standard").
I have bees myself. Beekeepers and scientists all over the world are trying to breed better bees with improved VSH. While it may work in a laboratory, it does not seem to work consistently in practice. You cannot just buy a "VSH colony/queen" and no longer treat Varroa mites. Even with careful breeding, the VSH behavior often vanishes (or is greatly reduced) after 1-2 generations.
Of course having only colonies with a strong VSH would be the end goal so we no longer need to treat our bees. But until then, better treatments are needed.
Wrangler, being cloudflare’s primary CLI tool, is a microcosm of exactly the problem GP was articulating: it’s focused way more on adding new commands than improving existing ones.
Many products, even supposedly “GA” ones, still lack basic operability via wrangler because instead of finishing building out its capabilities to manage existing services, they prioritized adding rudimentary support for new ones.
Nah, you don't get to claim they don't work on improving their products, and then handwave away actual updates to it with "yeah but those aren't the improvements I wanted". That's just life and priorities.
Abandoning something, and not making the changes you want to see are entirely different things.
You're arguing against a point I did not make. I observed that Cloudflare prioritizes expanding to new products over making improvements to existing ones. I did not claim they do not improve their products.
There are numerous examples, such as Cloudflare claiming Workflows had reached "GA" status before offering a way to delete workflows... not via wrangler, not the dashboard, not the API. They eventually added this many months after declaring it "GA", with no upfront disclaimers, just the capability silently missing.
If they want to move fast and break things (and they do, as their numerous, "CEO declares an emergency" outages have evidenced) they can — but they need to be honest in their communication about the production readiness of their new products.
That is not "life and priorities": it is poor communication/judgement from an infra company, and misleading advertising at worst. I choose to believe it's the former.
> I did not claim they do not improve their products.
Apologies that I didn't notice you weren't CommonGuy, who said "improving them in the future is not really their style". Consider my reply aimed at them. The two of you seem to be saying something quite different. I don't think I necessarily disagree with you
> ... unless it is made directly to an origin server that has previously indicated, in or out of band, that such a request has a purpose and will be adequately supported.
Even HTTP 1.0 RFC[11] is fairly clear on this, although it doesn't explicitly spell it out like RFC 9110. GET requests should only consider the Request-URI and request bodies should only be included if the method calls for it.
In all our years, Kreya "just worked" for our users without any drama or unwanted changes, unlike most of our competitors...
[1] https://kreya.app
reply