throwaway43234

Users can be free or paid. When I open up support tickets backed by a paid account they're always very quickly resolved. I'm not sure how much GitHub needs to support people who won't even pay for the product...

Visited June 29 for a number of hours, visited protests at the police line after it was dismantled approx. Jul 1-4.

The area proper on 29 was generally enjoyable to be around. Observed lots of drifter types, no visible violence, some good musical performances, nice community gardens, free food tent. Saw very little public drinking, some weed, lots of tobacco (mainly self-rolling, which I thought was interesting). A few circles of older folks smoking weed in circles out front their tents and hammocks on the outskirts of the habitation.

The protests at the police line were very disheartening. The militarization of police was of course frightening (not for my own life so much as the state of the nation). The protesters themselves had a fair amount of infighting, some of them seemed unstable (these ones were often the ones with guns).

Overall I found the CHOP area pleasant to be around, however the fact that CHOP armed guards killed more black teens in that ~2 week period than SPD in the past 6 months made me question if it was possible to logically consistently support both CHOP and BLM -- it's concerning there hasn't been more coverage of the disconnect there.

And those are just the failures you see! Friends in the industry tell me there are many more failures behind the scenes where shows can get arbitrarily far down the production pipeline only for studio execs to come in and scrap the whole thing.

We're not so different from those 1000 monkeys writing shakespeare :)

For a sufficiently large project (let's say 100k issues+), I think it's totally reasonable for some vanishingly small percent (say 0.003%) of issues to be really quite hard to reproduce/debug/fix without breaking other things. I don't think that in any way implies the maintainers don't care, and to not submit reports because you fear you'll end up in the 0.003% rather than the 99.997% is a bit silly if you ask me.

I maintain such a project, and most bug reports I can fix in a few minutes. Others take a few days. Still others need to be deferred until some large refactoring is completed in coming months. Others still are involved to the extent that I'm not sure I'll ever fix them. But I value them all, and there are many more in the former categories than the latter.

They need TS incremental compilation for their TS problems. Which exists. And is used by other large projects to achieve milisecond compiles. But I guess they couldn't figure it out, not clear to me why.

There's much less volume of copper in a RPi than a 486, so if you recycle your 386 to get a Rpi, the net copper reserve increases.

> At least, command line interfaces have the merit of often being documented (that feature is documented line 91 of my offline `man git commit`)

By default, pressing "Enter" in VS Code adds a new line. I don't think that needs to be documented. And the input box for the commit message says as its placeholder "Cmd+Enter to commit on [branch]", which is a whole lot more discoverable than going to line 91 of some man page. Plus, every keybinding can be searched and configured using the built in keybinding editor.

>> but using Shift+Enter to get a newline is fairly common and easy to try and guess.

> How on Earth is that intuitive? User interfaces (coomand line, GUI, web, voice) typically rely on common patterns

You'll find many "Enter to submit" boxes across the technosphere have some way of adding a new line, typically shiftenter, ctrlenter, etc. So this is a common pattern.

Protip: store bought salsa makes a better pasta sauce than store bought pasta sauce.

(Controversial) protip: home made salsa makes a better pasta sauce than home made pasta sauce

For some resources such as copper, it might actually be environmentally net positive to recycle to old copper and buy new.

If I spent my weekends flipping burgers instead of kayaking/backpacking/etc, I'd have more money too. But why on earth would I want to do that? This person clearly has some source of income sufficient to let them "waste" hundreds of hours, I don't think they need to be in a rush to dig up more money.

This seems to be from an org that has a variety of different highly-starred template/education repos in Portuguese. Maybe part of some education program? See https://github.com/Rocketseat/react-native-template-rocketse...

GitHub Codespaces was announced at Satellite and it's basically what you say - a way for developers to skip the "setting up" step (often the most annoying step and single biggest blocker for OSS contributions) in a new repo. https://github.com/features/codespaces

Disclaimer, I helped make these :)

I wonder how they're computing total effective monetary value, especially when it comes to 401k contribution. For instance, it has MSFT as 50% up to 19500 (it should actually be 100% up to 20000, but I digress), but a total effective benefit of just over 10k. I'd put the 401k contribution multiplier at >=1, but they clearly have it much less than that.

Really what would make more sense is allowing customization of how much you value particular benefits (i.e. free dinner means nothing to me, if not negative, because it also means you're "expected" to stick around for it)