217 karma · joined March 30, 2016
At heart, Slack is a chat app. Chat apps have existed for 40 years and don’t require a whole lot of data.
The complex part might be displaying the data, but that’s not much different than what an RSS reader does.
Even calling a chat app “complex” sounds absolutely ludicrous. It’s just that devs are now used to shipping 100MB apps in the name of fast development, so Slack is what we get.
Just because some complain about it it doesn’t mean that it’s failing.
What overhead? You don’t run any optimization step on your code? I haven’t seen a single front end project without package.json in years in all the companies I consulted for, and I don’t even deal with fancy frameworks.
If you’re gonna pull a statistic out of a shadowy place, at least explain its link to the question.
(For the record South Koreans drink twice as much alcohol as Italians)
https://www.who.int/substance_abuse/publications/global_alco...
Why create a function that shortens/clarifies nothing and is used once? If you want to explain some code, use a comment, don’t make spaghetti
Yes and no. Your CI system runs when you want it to. If you want to check the latest dependencies,
- with a lockfile you have to delete it, create a new one and commit it;
- without a lock you just press the “rerun tests” on your CI
Libraries should skip lockfiles because they are ignored by the end user and therefore any testing you do based on them helps no one.
I’ve had lockfiles being broken for no reason* so if you can avoid them, do.
* For example, multiple versions of the same package were installed after several install/updates, but nuking the lock would avoid this issue and solve the problems it caused.
I’ve found all kind of bugs just refactoring code because poor code obfuscates them.
Your way of building things will lead to debt and bug reports
There are minor code style preferences and others that affect maintainability. Just because it works now it doesn’t mean the code is done.
Why is this not clear? Airbnb is so opaque. It would be really easy to list this extra tax but they don’t, so I end up creating a new account.
What if the largest file on your drive has that filename and no tool can show it?
What’s this? You’re asking for a solution to “things that don’t work” ️
Correction: you do have 1000 discoverable actions, but you discover them in the menu bar.
What you found out with this article is that users are bad at knowing things, because there are too many things to know. I know all of those actions and their keyboard shortcuts, but I still have to occasionally "google it."
Either you have iOS 1.0 where everything is clear and easy to do — because there's very little to do — or macOS, where each app has dozens of features but can only surface some of them.
This is non-news.
The difference I’d say is that 45kph get you much “farther” in EU cities than the average US city.
It’s just a meme, used correctly, what’s the problem? This isn’t the White House’s blog.
- you tapped the “Siri suggestion” result which completely skips the SERP. I hate that “back” doesn’t bring you back to what I typed in the search/URL bar
- I regularly visit The Verge, open a story and then the back button doesn’t take me to the homepage but to the page before it. I blame their crappy JavaScript but maybe we’re experiencing the same thing.
If you add one more use case that might help the maintainer reconsider the feature, then I’d find it acceptable. Sometimes the issue opener didn’t explain the utility that well or wrote some example that made it sound like it would be a niche feature and not worth it.
It’s definitely predatory practices of people who don’t understand that, after a day of work, you should have more money than what you spent.
TypeScript is not sound; JavaScript isn’t either. The first one will catch some type errors, the second will catch none.
Syntax highlighting, linting, testing, and now type checking: every step can make you more confident about the code you ship, before it even hits the browser.
You can forgo using any help and probably you’ll code faster, but, again, you lose confidence.