You can press any key to go past that screen.
412 karma · joined March 9, 2015
You can press any key to go past that screen.
> We thank all the distribution package maintainers for backporting patches that improve security, fix bugs, etc. who coordinate with upstream. Often times this means creating or pulling patches to fix issues with inactive/abandoned/unresponsive upstream projects. These distribution package maintainers are doing a tremendous job and their work is not the subject of this letter.
> This letter wants to address the cases where actively-developed features, huge changes, etc. of active upstream projects are being included without the knowledge of the project maintainers or end users.
Very smart UX choices here.
Since then, the situation has largely pretty much improved, in particular both OBS and Zoom have support for the screen sharing portals.
The effort required to implement this in practice is pretty sizable, and antivirus software ships out signature updates at a much higher frequency than Bottles would be.
> 10kb code change? re-download all dependencies and all assets!
Any unchanged files are not redownloaded.
Given that the M2 is based on the A15, which doesn't have AV1, this was kind of expected. I'd imagine that, due to their general cycle, AV1 would come to iPhones first if/when it arrives.
In terms of actual compute speed, Python is still significantly slower, and although 3.11's changes will help quite a bit, V8 is also just insane.
In terms of I/O speed, uvloop (https://magic.io/blog/uvloop-blazing-fast-python-networking/) can beat Node quite handily, so if you're more concerned with being able to handle requests than doing anything major during those requests, Python might be comparable.
There's definitely some complexity and learning curve involved, but it comes with some nice advantages for my particular use case:
- Low vendor lock-in: I actually migrated to DO from a different hosted k8s, and I was able to reuse the majority of my configuration. - Reproducibility: your projects are derived from the resources you upload, so it's hard to end up with a setup that you can't easily reproduce (or migrate!) elsewhere. - High flexibility: I can do some relatively strange things with e.g. routing without k8s batting an eye. There isn't really ever a point of "oh no, I've found something I can't really, do". - I've found it to be cheaper than cloud managed services once you're hosting as much as I am.
More generally, I like the...standardized(?) style. It feels like a sort of "build your own cloud", but the blocks you use look like everyone else's, despite the total product looking a bit different for everyone. I can use k8s managed, in a business setting, or fully self-hosted, and the essentials still work the same way.
A lot of bad experiences wrt complexity I hear come from running the cluster yourself, but nowadays, distributions like k3s make this, dare I say, pretty easy. If you want to use. VPS, DO managed k8s is very nice.
I think Keycloak 18 should use less memory? Might be worth a try.
This would be solved by PEP 681, which originates from (and is already used in) pyright: https://peps.python.org/pep-0681/
> 3. To this day, there is still no way to express optional keys. Not "Optional" keys, but keys that can be left out of your dictionary. The closest you can get is this weird hack where you can set `total=False` in your TypedDict, which makes all keys optional.
This is solved by PEP 655, which introduces NotRequired: https://peps.python.org/pep-0655/
It's implemented in mypy 0.930: https://mypy-lang.blogspot.com/2021/12/mypy-0930-released.ht...
> I really wish Python learned from Typescript, but it's too late at this point
Personally, I feel like it's partly just entirely different styles: Python relies on a mix of nominal and duck types, whereas JavaScript is much more focused on structural typing. As a result, there are a lot of things like TypedDict that are absolutely essential for JS to even function but a decent bit less so in idiomatic Python code (keeping a significant amount of dicts around uses much more memory than objects, I recall a PyCon talk explicitly mentioning this too).
> Since they want to keep new hardware support a secret, they work on it in parallel on another branch / whatever. So all the betas only include a subset of the changes going into the real release. And then when the -RC drops, they merge major changes, especially around boot/HW.
> Headline CPI in March rose by 8.5% *from a year ago*
Another notable piece:
> core inflation appeared to be ebbing, rising 0.3% for the month, less than the 0.5% estimate
which matches the other commenter mentioning that the gas prices were a massive contributor to this.
This is one of the greatest comments I have ever seen.
It's a bit overambitious IMO, but it tries taking a relatively different approach to the problem that I find to be quite interesting.
> This is an unfortunately very common misconception: you can still set GTK_THEME on libadwaita apps, it's only the gsettings configuration that doesn't work (due to implementation constraints, unfortunately).