wizhi

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: just show me the modules, classes, functions, etc. Don't make me spend 30 minutes trying to find an explanation for that one function which just takes a kwargs, which ends up only being covered in thr footnote of some random page in the documentation on something otherwise completely unrelated.

It's madness.

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 issue for you. I seem to recall having issues with it, and switching to Amethyst pretty soon after. It might also only support BSP layout, which I dislike - stacks all the way.

Amethyst feels a little half baked. It works well enough, but configuration is through a GUI and saved in some non text format, making it not difficult friendly. It also doesn't support things like moving windows between workspaces, meaning you need to have additional bindings for that through the MacOS command center or whatever it's called.

Overall, I managed with Amethyst for close to 2 years, so that's the one I'd recommend of the two. Luckily I'm back on a Linux machine and can use river now. :)

Good luck!

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.

Do you have some writing on this? I'd love to read it.

I think the needs you listed there would be considered the niche.

Most people just want something to display their windows. Those things are cool, sure, but they probably come at some cost.

> we are still a small/medium sized company

Sorry this is somewhat off-topic, but _why_ do you have virtual development machines?

Yeah sure, be a part of the problem, that'll solve everything!

Now where does the average person find the initial capital, such that they can enter the game of capitalism..

Because otherwise, we'd all still be writing FORTRAN. I get your point, but it's as equally hindering of progress as it is valid.