Yeah that’s a complete myth and not based on actual science.

It’s definitely not faster than vim, fwiw.

There’s no feeding going on. We’re simply laughing at their expense.

What do you mean “build our dev environments around vim”? If you mean they write dev tooling in vimscript and explicitly require everyone to use it, I actually agree with you. I don’t believe employers should really ever force any particular editor or IDE if the work is getting done. I would be equally annoyed by a workplace forcing me to use vscode instead of vim. It would slow me down way too much.

If you are just complaining that they build dev tooling as a CLI, hard disagree. That is absolutely what dev tooling should use because it’s actually universal and can be used regardless of your editor choice.

At my workplace, our dev tooling is done via CLI and our developers use vim, emacs, and vscode. Because it’s all CLI, it’s easy for individual developers to add their own scripts to automate parts of their workflow as they see fit (and if such automations are deemed useful by the group at large, it will get merged into our shared devtools repo). We even have some editor-specific stuff in there people have written that they find useful, but it’s entirely optional.

Vscode definitely can’t handle large files like vim can. I can open files that are multiple GBs in vim without issue. Vscode definitely cannot.

That’s simply false. Increased length increases the entropy of a password, making it harder to brute force to gain access.

You have to go out of your way to restrict the length of passwords. There’s absolutely no reason to do it, and it is contrary to all good security practices.

xattr -d com.apple.quarantine path/to/file will remove that shit.

Though personally, I get as much software as possible on my work MacBook through Nix, and only use .dmg files if absolutely required.

It’s not that hard, technically speaking, though of course it takes skill to come up with a set of glyphs that work well together and such.

Also, there are websites that can scan your handwriting and turn it into a font file, which is pretty cool. I have a font I created of my wife’s handwriting.

1GB of files is not configuration.

1. Supposedly there’s a way to install nix without root access, but I can’t speak to it as I’ve never tried. Ofc it doesn’t require sudo to install packages or anything, though.
2. I don’t think it does this right now, largely because it’s super fucking complicated (as is basically everything Apple) and homebrew casks themselves have had a ton of headaches around it. But nevertheless, I think home-manager has some workarounds it uses itself to enable many common GUI apps on MacOS.
3. Not sure exactly what you mean, but I think it does that?

If you want to install packages purely by name, you can use nix-env -i hello or whatever. But it’s pretty janky and not really a recommended way of doing things.

Nix. I use it for everything, including all of my tools I use on my work MacBook.

There are many ways to use nix for this stuff, but personally I use home-manager in a flake-based setup. Versions of tools are all pinned in a lockfile which is committed to source control, so it’s easy to get my config and all my tools on a new machine without any breakage (it does require installing first, though).

It’s a great tool and has largely solved the pain of dealing with having to work on MacOS, for me.

So… Rust?

Not sure if serious or not, but yeah I use interactive rebases every day, many times a day (it’s nice for keeping a clean, logical history of atomic changes).

It’s very simple to recover if you accidentally do something you don’t intend (git rebase --abort if the rebase is still active, git reflog to find the commit before the rebase if it’s finished).

Never understood why this is such a trope. There’s very little you can’t recover in git (basically, only changes you never committed in the first place).

It very well could be typical corporate fuckery, but that makes me wonder if it’s actually a bug and that it’s computing the per kg price based on the single until price but dividing by the total weight of the pack.

Or perhaps it’s a “bug” that’s left intentionally until called out.

Unless you’re writing Scala or something (which is probably the one exception to the rule), if you are using a language that supports OOP, you’re not really doing functional programming. Functional-esque features that have made their way into imperative languages like map are only a tiny fraction of the functional toolbox.

There’s a bunch of features you want in a language to do functional programming, and imperative languages don’t really have them, like purity by default (and consequently, an orientation towards values rather than references) ergonomic function composition, algebraic data types, pattern matching, support for treating everything as first class expressions/values, etc.

Perhaps this is presumptious (and I apologize in advance if so), but I’d wager you haven’t truly programmed in the functional paradigm. What imperative programmers tend to think of functional programming is very surface-level and not really reflective of what it actually is. It’s an entirely different beast from imperative programming. It requires a shift of your mindset and how you think about programs as a whole.

Source: Senior software engineer writing Haskell full time for the last 4 years. Will avoid OOP until my dying breath.

It basically does. It pretends to court functional programming while actually being really antithetical to it in basically every way. Guido Van Rossum has vocally expressed his dislike for functional programming (though I’d argue he actually doesn’t really know much about it).

Its query planner is also much, much more powerful. Like it’s not even close.

There’s hardly any good reason to use MySQL today. Postgres is easier and nicer to work with, with a strong community backing it.

SQLite is completely different from both and has entirely different usecases.

Postgres, hands down. It’s far better than MySQL in every way.

For Haskell:

1. I’d say this is definitely a wtf. Tuples should have never been given Foldable instances and I’d immediately reject any code that uses it in code review.

2. I actually didn’t know, so TIL. Not surprising since common wisdom is that a lot of the type class instances for Doubles are pretty weird/don’t make a lot of sense. Just like in any language, floating point needs special care.

3. This is jjust expected syntax and not really a wtf at all. It’s very common for languages to require whitespace around operators.

4. Agreed as wtf, the NegativeLiterals should be on by default. Just would be a pretty significant breaking change, unfortunately

5. Not a wtf… What would you expect to happen? That operation is not well-defined in any language