EscargotCult

I stand corrected! I do suppose I could also get a travel safety razor that comes apart into 3 parts (as opposed to a single piece with a butterfly opening) and pack them separately. Of course that could mean some blade wastage: I'm rarely in one location long enough to use up all 5 in a pack.

> I think that it's also important to consider that it's much easier to cut oneself when using a double edge razor.

I've actually found it to be the opposite in my case, after having used a double-edge safety razor for almost 7 years. When I use the DE razor, I know exactly where the blade is and it gives me greater control if I need to go over a spot again that I missed. With the disposable razor, I've always found it difficult to tell where the blades are on my skin, which makes me prone to errors. The multiple blades in sequence also make it much more nick-prone when going against the grain for a closer shave, or as in the missed-spot scenario I just mentioned.

But yes, you're right - it's basically impossible to travel with a DE razor without a checked bag. Even just carrying the handle without the blade in your carry-on is a risk. I have an acquaintance who lost his DE handle to a TSA agent that wasn't interested in understanding that the handle by itself poses no more risk than a toothbrush. So, if I'm flying, I'll suffer with the disposable razor and never shave against the grain.

> Fingers crossed for remote work bringing some sort of equalizer effect here.

I work at a fully-remote company, and my org had a meetup soon after I first started working here. I was surprised to see how many of the people I work with seemed to be below average height. I've never really done anything to verify it, but I have a hunch based on that anecdata that the median height at my fully-remote company might be lower than the median height of the US population and/or lower than the median height at similarly-sized enterprises that have in-person hiring and work.

Their outage heatmap is also basically a population density map too. https://xkcd.com/1138/

> Copilot is bad at accessibility because web engineers are bad at accessibility. All of the bad habits in this post were learned from its training data.

100%, and this is why Copilot is damn-near unusable for Bash scripting (yeah, the real problem is Bash scripting, use a better scripting language etc etc, but I do it, you've probably done it, and we've all definitely worked with codebases with Bash script linchpins) - there's a lot of bad Bash out there.

I'll just quote from Stevey's Google Platforms Rant

> Like anything else big and important in life, Accessibility has an evil twin who, jilted by the unbalanced affection displayed by their parents in their youth, has grown into an equally powerful Arch-Nemesis (yes, there's more than one nemesis to accessibility) named Security. And boy howdy are the two ever at odds.

> But I'll argue that Accessibility is actually more important than Security because dialing Accessibility to zero means you have no product at all, whereas dialing Security to zero can still get you a reasonably successful product such as the Playstation Network.

I'm fully aware that I'm commenting with a drive-by facetious block quote, but it is a reality that "insecure but accessible" has more users than "secure but inaccessible".

It uses the native iOS video player APIs, which (to my knowledge, it's been a while since I tried) the official app doesn't. Also overall, it follows a lot of the "recommended" iOS design guidelines and has the look and feel of an Apple-made app (fonts, long-press behaviour, slide elements to perform actions, haptic feedback, etc).

I can't imagine it being anything else in that year. That must have been a struggle-bus of a UI to work with for something this laborious, though.

This is already happening with stock "analysis" that you see on Yahoo Finance for any given symbol. For example, take a look at https://stocks.apple.com/AbKUdK1ZvSFK4NdaMwMd27w

I think they've mentioned that they expect that their generics spec will evolve, plus they're waiting to see what idioms emerge before refactoring the standard library.

Probably. Google and GitHub already support WebAuthn for 2FA so it's relatively trivial for them to ditch passwords altogether and use WebAuthn as the single credential.

Reminds me of the Stack Overflow profile badges, which themselves were inspired by Xbox achievements.

Apollo is a really good mobile app for Reddit, but I expect Reddit will eventually buy it.

As for new users, it's likely a lot of people that reach Reddit from Google - their SEO seems to have gotten loads better in recent years. They also don't remember how simple oldreddit was, so they have no reference point.

This could be crowdsourced. Imagine some sort of reporting network of volunteers, running the simple program (memory allocation and periodic checks) on any hardware they're loaning time on, and submitting their location and altitude as well.

+1 the only thing that's "surprised" me between Go releases has been their changes to build flags in 1.18, and gofmt takes care of that anyway. Now that I think of it, gofmt changes if you have autoformatting enabled is probably the only "breaking" change that might happen between minor releases, but I haven't seen any issues with this from 1.15 through 1.18. In any case, if gofmt changes are disruptive enough to block upgrading, then a team has some deeper-seated issues in how they ship.

For anyone looking, here's the comment: https://news.ycombinator.com/item?id=30779291

Sounds like Stack Overflow's early growth strategy, minus the wiki aspect

re: the Dead Internet Theory, anyone who browses the "news" sections of any stock trading app, Yahoo Finance / iOS Stocks app can see that the likes of Barron's, Zacks Investment Research, Motley Fool, Benzinga, etc have been autogenerating "analysis reports" for some time, where some basic fundamentals and options metrics are repackaged in some filler wording. I don't think it'll take much for lots of secondary content to reach this state.

> Am I being paranoid? Is it reasonable to connect my images to a random third party service like this?

Depends on your line of work I suppose

> Confluence to an extent also

without using a vendor-specific markup format, too!

> I've thought about this a lot over the past few years, and I've come to the slightly sad conclusion that Google isn't to blame.

I don't know about that, at least in the realm of programming-related searches. It's ridiculously frustrating when I'm searching for a standard library function and the top 3 results are geeksforgeeks, w3schools, and tutorialspoint, while the canonical documentation for the language is only 4th or 5th in the results.

> But it will also let good programmers write very good programs and libraries, and that's going to be a huge benefit for everyone.

I hope we can see some good examples of generics being used in the standard library once 1.18 is released.

I wouldn't be surprised if it takes years for the phase-out, if it ever gets phased out at all. There is a particular type of organizational culture that believes having the "big" option for a productivity tool is the best option. AzDO feels like the "big" option. It is quite customizable and can emulate (and in some areas surpass) GitHub's functionality, but at the expense of having more knobs. To me, AzDO feels like the inside of a space shuttle, but I'm certain that this complexity is seen as a strength to some orgs.

In CI-land, though, I think GitHub Actions and Azure Pipelines fates are much more closely intertwined. The Microsoft-hosted runners for Azure Pipelines have the same environment as GitHub Actions (or perhaps it's GitHub Actions that's standing on the shoulders of Azure Pipelines)[1].

1: https://docs.microsoft.com/en-us/azure/devops/pipelines/agen...