Sure, it's possible to make the battery removable, but why would they do that? It was the manufacturers (e.g. Apple) who decided to make the battery non-removeable in the first place, as it allows for a more compact design and more revenue.
Also the batteries would have to be ordered as a spare part years after the product launched, and most cheap manufacturers are horrible with sustained support.
It's their first iteration and I applaud their effort. It takes at least a year to develop something like this and the sales quantities will be lower compared to the big brands, so the price is understandable.
You seem to belong to group of consumers that wants to compromise lifespan and sustainability in favor of features and price. That's fine, but it simply means you are not their target audience for this product.
I have tried all but pdn is the best software for quick editing. In the time it takes for Krita or GIMP to launch, I'm already halfway in pdn. I really miss it when using Linux.
Ageeed, and the RFC4180 you are referring to also specifies how to escape newlines.
CSV is a simple storage format for data. Its simplicity, readability and portability makes it popular. I think that any attempt to improve it will be a failure.
I must say that CSV generally suffices for table data. The only annoyance is that internationally, there are differences in the use of the column separator, as the comma is often used as decimal separator.
I think CSV should always be implemented with a comma as column separator and a dot as decimal separator, regardless of the country. But applications such as Excel do not accept this format internationally.
Many European countries already banned it in the '90s. That was decades ago and the EU is currently discussing making it obligatory to replace old asbestos materials in existing constructions.
I don't see this as a perfect solution, but CSV is not great either.
A comma is super common in both text and numbers. Here in Europe we often use commas as decimal separator and use a semicolon as value separator.
As a result spreadsheets almost always fail to automatically parse a CSV.
I do like the idea of having a dedicated separator character, that would work right worldwide. And then just standardize the use of a dot as decimal separator in these files.
It's slightly more convenient, but Vue3 is already great. I like to support an ecosystem and I want a framework to keep existing, making sure I can maintain my projects in the future. That is why I don't jump ship.
Avalonia is interesting because so many desktop apps have been made in WPF over the past decades. And now the technology is getting old and MS wants to replace it by unproven frameworks which have various drawbacks. As Avalonia is XAML based just like WPF, it is a good way to upgrade old apps and make them multiplatform in one go.
For mobile or web it would not be my first choice. And desktop apps may not sound as sexy. But there is definitely a category of applications that works best as a desktop app and shouldn't be replaced by the web.
If you don't want to deal with cookie banners, there are browser extensions you can install to automatically accept them.
However, although the cookie banners are sometimes a nuisance, it is still a good thing that people are informed and given the option to accept it or not.
And of course, it is clever marketing. Even here we are talking about it.