Depending on the size of the blob you might not want to use `WITHOUT ROWID`. I had a similar table with uuid keys and blobs of 40kb size on average and `WITHOUT ROWID` really tanked performance.
In Germany I spent exactly 0 dollars/euros on books in university. We got access to a huge amounts of ebooks through the university network and profs never required a specific one and would just recommend a few. One of these was always available. This free access was of course covered by the 250 euros per semester tuition…
But yes, standards and certifications are horrible.
I would understand if they didn't backup anything with FILE_ATTRIBUTE_RECALL_ON_DATA_ACCESS set (on Windows). Everything else makes their product worthless.
Since all input is run through a tokenizer, I would expect the tokenizer space doesn't change a lot between one trained on uncompressed vs one trained on compressed data.
Didn't read the paywalled article. But imo if it's not worth listening at 1x speed, it's not worth listening at all.
If it's entertainment like audiobooks, it's for my enjoyment, so why should it be faster than 1x? If it's for education, everything faster than 1x makes it hard to understand, and if there is too much filler content, I will find another source to learn about it.
I use 1.5x-2x for stuff I have to listen too, but don't enjoy.
It would be a non issue, if the options are not just allow/disallow, but also offer to provide random/fake data, so bad apps would not actually know if the permission is allowed or if the data is fake.
I would argue that most of these features (basically everything except metaclasses) are not advanced features. These are simple, but for some reason less well known or less used features.
Metaclasses are however quite complex (or at least lead to complex behavior) and I mostly avoid them for this reason.
And 'Proxy Properties' are not really a feature at all. Just a specific usage of dunder methods.
I do like the else clause with for loops. However most people are not familiar with it, and also `else:` as a keyword is confusing. I always remember it as `no break:`.
I hate Win11. It is horrible, but the first few points don't really make sense. I use it in 2 environments.
- enterprise version: no bloatware, no ads, and edge is there but never has to be used for anything
- professional version: bloatware is uninstalled in like 2min after OS install, another 2min later all ads are disabled. And it usually stays like that after updates too. Edge is never used at all.
Windows architecture is great. the WinAPI is better documented and more comprehensive than anything on Linux or Mac.
There are so many other issues.
- The file explorer gets slower and more broken with each update. context menus randomly don't show, or take literally 30 seconds to load.
- The renderer crashes randomly once a week (it's not a huge issue, but the screen goes black for 10 seconds or so)
- the settings dialog is bad. goes through like 5 different layers of Windows generations and recently makes the old dialogs hard to find but doesn't offer adequate replacements (looking at network and sound)
- and much more...
Smart TVs are the reason I haven’t bought a new tv in almost 15 years. I would like to upgrade to a fancy 4K one instead of my old 1080p one. Dumb TVs back then weren’t more expensive than smart TVs today so I don’t believe price is the reason for smart TVs. Margins maybe…