> Stewart Butterfield has talked about the pressure Slack faced from large organizations in its early days wanting features that would have fundamentally changed what Slack was. The requests were reasonable on their face: more administrative controls, different permission structures, audit logging. Each one seemed like a logical extension. Taken together, they were a blueprint for a different product aimed at a different user. Butterfield’s team had to repeatedly decide what they were actually building.
I'm pretty sure Slack has those things by now. So the question is, what did the team actually end up building? What features were prioritized over the enterprise compliance features? Would Slack have less revenue had they gone with the enterprise stuff first?
The short version is, the DOS-era Japanese character sets had replaced \ with ¥, and modern Windows still shows paths as C:¥WINDOWS if you're using the Japanese locale.
You need a separate UI to handle things like entering the file name and filtering for appropriate files. Windows was designed so that the same file browser component is used in the Explorer and in open/save dialogs (but with Windows 7-era UI), but on Linux, which file manager should GTK use? GTK sometimes likes to pretend it’s separate from GNOME.
> Packaging can be irritating although uv takes the sting out a bit.
uv proves the OP’s point. Why couldn’t the core team and the core-adjacent PyPA make a tool as liked as uv, and why is the Python package manager uv written in Rust and not Python?
The standard library is full of dead batteries. If the stdlib is so good, why does everyone install requests instead of using the stdlib http client? And why requests or something like it hasn't been adopted into stdlib after so many years of stability?
Yeah, mostly slop. I wonder why the slop slingers never disable Claude's self-attribution, and are too lazy to commit themselves, are they proud that they're delegating everything to a slop machine?
Taking notes in class is akin to making a transcript of what the teacher said in class so you can remember and refer to what was said in class. The encyclical is a written document, so there is no need for a transcript, and "notes" implies commentary and analysis.
> Around 22:20 UTC, our Google Cloud account was placed into a "restricted" status hence removing all of our cloud overflow VMs, our CloudSQL instance, and our API.