> React is the worst thing to happen to the Javascript ecosystem. The idea is good, but the execution is just piss poor. I mean look at Vue and Svelte, they managed to do it right.

As a previously big React dev I agree 100%. If anyone feels this way please spend some time on doing Sveltekit project (e.g. rewrite a personal React project).

It's a breath of fresh air.

Also in the US (probably due to lack of training and the customer too embarrassed to complaining) tend not to fill it the brim (and so not even 16''). I've seen 2-3 inch heads and asked them to top it up. They look at me as if I've just insulted George Washington.

Well, depending on the type of beer, that's intentional. It's not always the faux-pas that it would be to do this when serving cask ale in the UK.

But usually when that is the case they will use glassware that has a 20oz line on the glass with room for the head.

First thing I always look for is screenshots.

https://www.arcanoae.com/arcaos/arcaos-screenshots/

I still struggle with the fact that I was (or delusional) an effective C programmer "back in the day" (before google etc) and all we had was "man" to look up std/x11 system calls.

Now I am dismayed with juniors who can't even be bothered to use google (or llms) to look up stuff on their first hiccup.

#include <old-man-shouting-at-clouds>

That’s not a builtin, so wouldn’t it be:

   #include <old-man-shouting-at-clouds.h>

And it's kinda old, so maybe

  #define _POSIX_C_SOURCE 1
  #include <old-man-shouting-at-clouds.h>

Well played good sir, well played

Wouldn't tree-shaking take care of this? i.e. If I only use 'Button' (from the UI library), nothing else should be included in the (production) bundle.

Not in practice, because these UI libraries usually have many intertwined interdependencies. <Button /> probably still imports all of the context providers, which also import their own dependencies, etc. So you end up including half of the library if not more just for a button, but if you use multiple components from the library the cost is amortised.

And typically if you're just using a single component it's one that is more complex than a button, like a popover or colour picker. Which then pulls in other components, etc.

Try: XDG_CURRENT_DESKTOP=sway QT_QPA_PLATFORM=xcb flameshot

Thank you. I tried that. Having the interface run under Xwayland caused a ton of problems with my monitors. I also don't use a lot of QT apps so not being able to paste was a problem.

This works for me on PopOS Cosmic (Wayland). Please lmk if my flags are incorrect.

XDG_CURRENT_DESKTOP=sway QT_QPA_PLATFORM=xcb flameshot

Can you mind elaborating further how this would work? I am somewhat familiar with both of them.

Are you suggesting some sort of app store or web page to send money/bitcoin?

Nostr is a decentralized social protocol where people can send btc tips, called zaps, directly to creators.

I believe what you're saying is the benefit of Bitcoin (or other crypto) to get around gatekeepers.

I don't believe Patreon at this time supports any crypto. If they wanted they could open this up. Not sure if Apple would allow this (on an store app) without their 'slice' of the pie.