Think about how many columns you can fit!
Seems unlikely and frankly doesn't matter much.
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).
For Haskell:
-
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.
-
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.
-
This is jjust expected syntax and not really a wtf at all. It's very common for languages to require whitespace around operators.
-
Agreed as wtf, the
NegativeLiterals
should be on by default. Just would be a pretty significant breaking change, unfortunately -
Not a wtf... What would you expect to happen? That operation is not well-defined in any language
https://daniel.haxx.se/docs/curl-vs-httpie.html
Httpie and xh only have a small subset of curl's functionality, and IMO the claims of more intuitive UX is dubious at best. More magical and limiting is what I would say. Httpie in particular is slow as hell, too.
Daniel has a more thorough comparison of features across different alternatives here: https://curl.se/docs/comparison-table.html
My wife and I think it is. I took her last name since it meant more to her.
I was born in 1990 and remember lots of stuff.
I doubt it's what OP means, but technically Republicans did get rebranded as Democrats (and vice versa) due to the political realignment of the parties after the Civil Rights Act and the Southern Strategy.
This is something often repeated by OOP people but that doesn't actually hold up in practice. Maintainability comes from true separation of concerns, which OOP is really bad at because it encourages implicit, invisible, stateful manipulation across disparate parts of a codebase.
I work on a Haskell codebase in production of half a million lines of Haskell supported by 11 developers including myself, and the codebase is rapidly expanding with new features. This would be incredibly difficult in an OOP language. It's very challenging to read unfamiliar code in an OOP language and quickly understand what it's doing; there's so much implicit behavior that you have to track down before any of it makes sense. It is far, far easier to reason about a program when the bulk of it is comprised of pure functions taking in some input and producing some output. There's a reason that pure functions are the textbook example of testable code, and that reason is because they are much easier to understand. Code that's easier to understand is code that's easier to maintain.
Let's give it a shot. I live in the suburbs of Lincoln, Nebraska, which is an average-sized college town in the US (about 300k residents):
- Nearest convenience store: 1.1 miles/1.7km (we often do walk there, takes about 20 minutes)
- Nearest chain supermarket/big supermarket (they are often one in the same here): Target @ 1.5 miles/2.4km
- Bus stop: 1.3 miles/2.1km
- Nearest park: 0.6 miles/965m
- Nearest public library: 3.5 miles/5.6km
- Nearest train station: 9.1 miles/14.6km (we don't really use trains much at all in the US, though)
It can be nice when you successfully do a rebase (after resolving conflicts), but change your mind about the resolution and want to redo it.
Doesn't come up that much, but it's been handy once or twice, for me. It's also just nice security: no matter how I edit commits, I can always go back if I need to.
Yep. When everything about your IDE (unix) is programmable, it makes "modern" IDEs seem quite quaint.
Personally I make extensive use of https://f1bonacc1.github.io/process-compose/launcher/ to orchestrate a bunch of different shell scripts that trigger based on file changes (recompiling, restarting servers, re-running tests, etc.). Vim just reads from files as needed. It's lightning fast, no bloat, and a world-class editing experience.