This is a massive commercial product with a serious issue (everyone knows about the flickering) that hasn't been solved for months now. I don't think leeway is warranted.
There's no garage, and the only driveway-facing outlet is at the front door - opposite where my parking spot is allocated (an extension cord would have to go under/through the landlord's cars.) I have to drive 60km to work every day.
Only laws (accommodate EVs and/or WFH) or spending time sitting at a gas station will help me here. No landlord is interested in accommodating an EV unless it's a net benefit to them (and thus a net negative to me, who already spends 40% income just to have a place to work.)
I would love to have gone electric (bought a car in September) but I rent and don't have any way to charge at my residence. How do we solve the renters-that-cant-charge-their-cars problem?
> Android does provide a WiFi suggestion API [1], but it has several limitations and doesn’t behave quite as expected.
Can you expand on this? I read the linked doc, and it looked like a separate API should be used to used to "persist a network connection" (my words), but as someone with no Android dev experience there don't seem to be any obvious limitations.
You did mention in another reply that only certain root apps can do [what we expect]. Is there a link where I can learn more about that?
Just to add some (unprovoked) additional info here: I'm a 26 year old Canadian. We covered early Canadian history, abuse of the aboriginal peoples of Canada, war with America, and WW1/WW2/the Holocaust.
I don't think we were really taught at all about European/Asian history or the Soviet Union. I think I could have taken some classes related to those in highschool (secondary school), but for anyone working towards a non-history bachelor's degree those courses were generally not something that you could fit in your timetable.
We ran into this, informed our users to reinstall Docker (we use Homebrew), and seemingly have had no further issues. I guess we're the minority?
I would be more inclined to blame this on Apple than Docker, but I haven't looked too deeply since things are working for us. Curious about you folks' opinions.
Will Anderson, another Scrabble champion/grandmaster, uploaded a video talking about Nigel's win here. The win is a lot more impressive than memorizing bingoes - Spanish scrabble has different letter distributions and point values, resulting in different metas. He didn't just memorize the Spanish Scrabble dictionary - he learned how to play Spanish Scrabble and dominated the first Spanish tournament he participated in.
We do development/builds in containers to make things easier on the devs. These are the Python build containers, so we have to rebuild every time there's a new version of Python or one of its dependencies.
This is fine until you're working with hundreds of other developers. I believe the reason solutions like this exist is to abstract git away from most devs, because in (my experience) many enterprise devs have only rudimentary git knowledge.
Sure, the devs should "just learn git" - but the same argument applies to a lot of other tech nowadays. Ultimately most folks seem to want to close their ticket off and move to the next one.
Git submodules and git subtrees generally do not fit my org's needs - we have internal tooling similar to this. Happy to expand on that if you have questions.
GHES is a massive monolith running dozens (hundreds?) of services in Nomad, so it's not surprising to me that GH has a hard time supporting it and wants folks to move away from it.
I'm tired of slow, risky, late-night upgrades to the appliance. I'm tired of sending support bundles and being told to run a customized string of MySQL commands to resolve peculiar issues. I'm tired of checking the roadmap and telling folks "yes, they announced that feature, but it won't be available to us for at least 12 months." I'm tired of a feature eventually being in the GHES release notes, only for GitHub to have made a mistake and it not be available for another two versions.
We're moving to GHEC. I'm concerned about the semi-frequent outages there, but we're not running HA GHES so it has become a liability for us.