Aren't skills just literal plaintext files? Why not just copy them?
Do you have any recommendations for literature on the subject of video encoding etc? I really want to learn more theory.
So you advice people to build their own framework, then advertise your own?
Maybe your actual issue is needing to mock stuff for tests to begin with. Break them down further so they can actually be tested in isolation instead.
Generics opened the floodgates for this stuff, unfortunately.
Servers taking advantage of the tendency for Americans to tip shouldn't be conflated with anyone else traveling to the US.
Python package documentation is abysmal. It tends to read like a novel and yet still only covers surface layer details with simplistic examples. It's next to impossible to just "get an overview" of what's available:…
Man, if anything you sound like a pretty shit coworker.
What's a concrete example of "concurrency power" here?
I am likely misremembering, and mixing it was something else! There definitely was something vital I wasn't able to do through just Amethyst though.
I've been there, being forced to use it for work.. I tried both Yabai and Amethyst and, frankly, neither provide a clean experience. Yabai requires disabling some OS security feature iirc, which may or may not be an…
I can recommend Runbox. It's a paid service, but I really think that's for the better.
The exact same as if npm did it.
But this can literally just be done in a simple shell script as well. The makefile ends up just being a redundant way to run a shell script.
Vendor support. Shipping with Linux is a good indicator that it's Linux compatible. Buying computers with Linux is also a way of voting for Linux compatibility - even if you reinstall your preferred distro afterwards.
How would me answering how I once "reacted to xyz" make me any more likely to "put the extra neurons in"?
And the only way to mitigate the cancer that is GitHub is to normalize contributing elsewhere.
If you truly believe it to be trivial, you should just do it rather than complain. If you don't, then you can't justify putting more work onto the maintainers of upstream for changes they may not even care about.
Then don't just send a PR: maintain your own fork. I think that's the bigger part of open source. You can fork it, change it to your needs, and not give a damn what anyone else thinks about your changes.
Is this any different from other alternate YouTube apps like NewPipe?
What would be the big gain from this, over the existing approach using multiple return values?
Most companies I've worked for (Denmark) has had a similar clause in their contracts. No clue if it holds up in court though.
How is the implementation of errors "laughable"? An error is just another result of calling a function. Seems reasonable enough.
Where do you keep up to date on what will be included in future releases?
This is essentially he default when using most CI services, however.
Aren't skills just literal plaintext files? Why not just copy them?
Do you have any recommendations for literature on the subject of video encoding etc? I really want to learn more theory.
So you advice people to build their own framework, then advertise your own?
Maybe your actual issue is needing to mock stuff for tests to begin with. Break them down further so they can actually be tested in isolation instead.
Generics opened the floodgates for this stuff, unfortunately.
Servers taking advantage of the tendency for Americans to tip shouldn't be conflated with anyone else traveling to the US.
Python package documentation is abysmal. It tends to read like a novel and yet still only covers surface layer details with simplistic examples. It's next to impossible to just "get an overview" of what's available:…
Man, if anything you sound like a pretty shit coworker.
What's a concrete example of "concurrency power" here?
I am likely misremembering, and mixing it was something else! There definitely was something vital I wasn't able to do through just Amethyst though.
I've been there, being forced to use it for work.. I tried both Yabai and Amethyst and, frankly, neither provide a clean experience. Yabai requires disabling some OS security feature iirc, which may or may not be an…
I can recommend Runbox. It's a paid service, but I really think that's for the better.
The exact same as if npm did it.
But this can literally just be done in a simple shell script as well. The makefile ends up just being a redundant way to run a shell script.
Vendor support. Shipping with Linux is a good indicator that it's Linux compatible. Buying computers with Linux is also a way of voting for Linux compatibility - even if you reinstall your preferred distro afterwards.
How would me answering how I once "reacted to xyz" make me any more likely to "put the extra neurons in"?
And the only way to mitigate the cancer that is GitHub is to normalize contributing elsewhere.
If you truly believe it to be trivial, you should just do it rather than complain. If you don't, then you can't justify putting more work onto the maintainers of upstream for changes they may not even care about.
Then don't just send a PR: maintain your own fork. I think that's the bigger part of open source. You can fork it, change it to your needs, and not give a damn what anyone else thinks about your changes.
Is this any different from other alternate YouTube apps like NewPipe?
What would be the big gain from this, over the existing approach using multiple return values?
Most companies I've worked for (Denmark) has had a similar clause in their contracts. No clue if it holds up in court though.
How is the implementation of errors "laughable"? An error is just another result of calling a function. Seems reasonable enough.
Where do you keep up to date on what will be included in future releases?
This is essentially he default when using most CI services, however.