Rusts verbosity (and thus, harder to read syntax) is there on purpose and it's nice you do not have to worry about a lot of things because the compiler does for you.
You are right with the updating part. I think what annoys me the most is that you often have to update (because you need feature x, just now released) and you will also get a new api. It feels (highly subjective here) as it is not yet so stable as in other languages.
I also scrolled over some commits from the UUID repo. You are right, the maintainers seem to be doing a good job publishing a good crate with great documentation and the required maintenance work.
Maybe I haven't used Rust enough (still at the very beginning of the learning process) but the post fits my experiences.
When first starting a project with a REST interface (using axum and axum-login for auth) everything worked until like 1-2 month later when the login crate changed the interface completely. It wasn't much work to adapt but it feels like many crates are still in pretty active development and the recommendations on whats the current way to go change often.
Also regarding the syntax, it is often very verbose and if you start using async it gets even worse.
I know it's still in development and as far as I know the async part is still far away from a full blown stable implementation but that doesn't make it more usable.
The syntax isn't meant to be precise/easy to read but to encapsulate everything which otherwise might be a trap and fall on your feet later so I think a lot of the verbosity comes from the borrow checker.
Regarding the UUIDs, its a nice anecdote, it feels like it might point to something. On the other hand UUIDs do change (or at least get new features or versions) and the interfaces can be enhanced if the way the library is used changes. So I see why they would need many releases/commits but (without checking the GO library) I would expect it to be a fully functional UUID library with a good interface also.
But are they? Not asking for the contract side here but for the technical aspect.
If DDG relies mostly on Bing and it fails forever in the future, they can "simply" make a contract with google and continue whatever they were doing.
Same for OpenAI. Its not that Bing is the only search engine index on the web is it ?
So yes, it would mean they have to spend a lot of manpower in a short time.
On the other hand, how likely is it that Bing just goes offline?
Do you always have a second datacenter in case your provider fails? Not everyone does it and as long as you have a way of putting things back up in reasonable time you are good to go.
I myself did a lot of exercising during the last 1 1/2 years using an apple watch for measures and I would also go with the previous comment:
Even thought the VO2max is not accurate (especially not compared to actually lab data) it is a nice graph with a tendency which REALLY helps.
High differences might come from different estimation techniques and thus this value is not comparable among different brands but it seems to be for your own value and progress.
During a lazier time it depleted a bit, now its going up again.
Most other graphs don't show it that nice. E.g. your avg hearth rate will not make huge changes (and drop which, even if its good, doesn't feel that good).
Edit: I actually did a Lab test (not VO2max) but an exercise ecg with lactate measurements. I couldn't choose between running and cycling. The problem is: if you choose the bike they can measure the values while you continue riding. If you choose running you have to stop now and then while they take a blood sample. Even there it isn't 100% accurate and might yield different results based on the used method.
From the german chaos computer clubs yearly meeting.
Linus talks about what to do and who ransoms work, how "well" the service is and briefly pros and cons of paying.
Wouldn't it be more interesting to have this as an external tool?
You input your create table statement and it issues you back the migration statements? Then you can check it against your development database or whatever and if you feel fine use it?
This way you could check and modify the migration path without writing the alter statements.
This is one of the most frustrating thinks with sqlite for me. Changing a table doesn't always work with an alter statement but sometimes you need to drop and recreate it with the new columns. Why can't they do the magic for me. It's really frustrating and was often enough the sole reason I used postgres for private projects.
Why would you think so?
The PostgreSQL developers didn't stick out by delivering bad software/features so far. If they would implement this I would actually expect a pretty good way with even better documentation.
I tried using ChatGPT (4) for format conversion.
I had a draft yaml file and needed some differently structured json.
Mainly with the same content.
If you just want to change the format it works. If you need more than programming skills it seems too fail duo to the amount of text.
E.g. if you have a list of items and want ChatGPT to generate a meta field which it cannot generate using simple python code it stops after 10 to 20 elements.
Thus at least the cloud version doesn't work so well here.
I also wanted it to help me fill out my i18n file with translations and plural forms. Even thought he got every word correct i needed to split it into multiple requests. Not sure if the api would have worked better (used the web frontend).
For the plural forms I finally added them myself as it was way faster for my natural language than copy pasting all the small chunks. Really hoped for more help there.
Rusts verbosity (and thus, harder to read syntax) is there on purpose and it's nice you do not have to worry about a lot of things because the compiler does for you.
You are right with the updating part. I think what annoys me the most is that you often have to update (because you need feature x, just now released) and you will also get a new api. It feels (highly subjective here) as it is not yet so stable as in other languages.
I also scrolled over some commits from the UUID repo. You are right, the maintainers seem to be doing a good job publishing a good crate with great documentation and the required maintenance work.