This is a pet peeve of mine and I'm glad to see it called out. That said, I haven't seen a comprehensive discussion of "here's the different factors that we think contribute to creating lift" for the general public, is anyone aware of a good source?
Yes, I am in a hybrid role, went through 5 interviews and several more check-ins, and the first time anyone saw me in person was on the first day when I picked up my laptop at the local office (which wasn't even required, I had the option of having it shipped at my home address)
I'm also 37. Two younger colleagues were complaining this week that something like `os.MkDir(..., 0755)` is extremely confusing and that they don't like and can't make sense of octal file permissions. I felt really old :)
First of all, thank you for creating this app. A couple of years ago you've finally put an end to my decade of looking for a decent HN client for Android and I haven't looked back. I actually run Harmonic in Windows Subsystem for Android and on ChromeOS to use it as my primary way of browsing HN on all devices!
That said, if you have any spare time to dedicate to it, it would be great if you could open some issues on GitHub to express what you have been wanting to do but didn't manage to. I don't have any gripes with the app as-is (other than adding Material You support, but that's likely to require some large changes) and it would be great to have some guidance on what would be useful to contribute.
Wow I never thought anyone would be so hardcore as to actually run Harmonic on windows subsystem and Chrome OS - I figured not a lot of people don't use the big screen mode and I mostly made the tablet changes for when I bought myself an Android tablet a couple of years back to use Harmonic more comfortably in the couch.
The GitHub issues is a very good point! I have a long Google Keep list with things I've been meaning to do and hadn't even thought about opening issues to guide to help. I'll try to get some of those up tomorrow :)
I've seen projects that take longer to link than a complete from-scratch build of the Linux kernel (and when bisecting, incremental builds do a lot for you on the later steps).
We have a ton of Christmas-only or Easter-only desserts in Italy, all very good. I'm guessing the short availability window increases sales, you just need to make sure you always have something in season ;) It's more of a tradition than anything else, really!
I know it's just an example, but it's really straightforward: you create a component which accepts a boolean prop and, based on that, either outputs the default slot directly or a wrapper containing the default slot via a simple v-if.
If you wanted to get fancy, you could also accept a tag prop and v-bind all other $attrs on the container to make that a general purpose component.