@jasonkoebler > People have a right to use third-party parts under the Magnuson Moss Warranty Act, for one thing, and it's hard to square this contact language with that basic consumer right.
It's not hard, it's impossible. The contract is not legally enforceable on its face. More corporate overreach where they believe contract is king.
@thomasfuchs "Without fear of being shamed or shunned" has literally never been the deal. You are free to say your piece, and others are free to tell you that you're fucking stupid.
Sometimes my motor cortex invents user-interface features completely by accident.
Just now I wanted to edit a particular shell function 'download_foo()' in my .bashrc. So I went to emacs, hit the keystroke to open a file, and before I quite realised what I was doing, my fingers had typed in the pathname
~/.bashrc/download_foo
as if download_foo were one file in a subdirectory, rather than one function in a source file.
Of course it doesn't work. But it might be kind of handy if it did!
One year ago, I started a bi-weekly nerdy podcast with a few friends called Linux Matters. The goal was to make a show for our wider circle of Linux nerds who like to hear what we've been up to every couple of weeks. We just released episode 27, where we read and discussed feedback we've received since we last looked in the 'mailbag'. 🧵
Given how Pydantic 2 broke compatibility with Pydantic 1 in a way that's still shaking out - you can't use 2 in a project that has dependencies that use 1 without making changes to those dependencies...
... I wonder what the downsides of releasing Pydantic 2 as a new package called "pydantic2" such that it could be installed in the same namespace as the original pedantic would have been?
Presumably this is how Jinja ended up as "jinja2" forever?
@ubernostrum I generally run unit tests in a Python environment (pyenv locally, GitHub Actions pipeline remotely). My approach is: if there's something that I need to dockerize for a unit test, then it's probably not actually a unit test (e.g. end-to-end test, etc.) or there's something I'm not mocking that I should be.
I went to book a flight with Wizz Air last night and the absolute shocking web performance made me feel better about my own work.
It takes ~30s to process the #JS and render the search, literally the primary function of the site. I like the DX of #VueJS but is this kind of performance really worth it?!