sullyj3

12 ms·

91.
by sullyj3 5y ago
> 1- There is excessive white-space everywhere (like every other modern web-app). I feel like it was designed as a mobile-first solution. So many programmers have this obsession with interfaces having every available piece of information
92.
by sullyj3 5y ago
One key difference is that usually the captured values in a closure can't be mutated.
93.
by sullyj3 5y ago
I hate to be be the one to tell you this, (just kidding, I get a little sadistic thrill out of it) but if you think the best way to defend science is to shy away from searching for truth, you may possibly have missed the entire point of the
94.
by sullyj3 5y ago
Understanding the fundamentals of public key cryptography is a worthy pursuit. Memorizing the idiosyncratic flags of yet another command line tool (or looking them up in the man page every damn time like most people do), instead of having a
95.
by sullyj3 5y ago
> What do you expect? That people without prior knowledge or experience just pick up source control in seconds? I mean, ideally, that'd be great. I don't think there's any fundamental reason things can't be this way,
96.
by sullyj3 5y ago
This seems like exactly the sort of issue the Unison language is trying to tackle. They want straightforward execution of distributed computations using the same language, with no friction across machine boundaries, no sacrificing composibi
97.
by sullyj3 5y ago
Maybe a rundown of the different strcpy variants or something
98.
by sullyj3 5y ago
If you could give a concrete example of a problem to be solved, I could try to convince you that the method using Either won't actually be all that unwieldy.
99.
by sullyj3 5y ago
For the moment, you have to create a function with the appropriate IO ability, and execute using the `run` command from inside the codebase manager. I don't think there's a way to create a standalone executable just yet.
100.
by sullyj3 5y ago
Agreed, I think calling them enums is an example of trying a little too hard to make the language seem comforting and familiar to c/c++ programmers at the expense of clarity.
101.
by sullyj3 5y ago
It's true that here the data type was just a tag. There's always a decision to be made about how much structure you want to enforce by the construction of the data type. You'd still consider it to be "parsing" becau
102.
by sullyj3 5y ago
It's true that you can't extract a value obtained from the outside world from the IO type by design, but, I don't think I'd characterize that as a problem. For any piece of code someone thinks they want to write that inv
103.
by sullyj3 5y ago
I don't really know much about this area, but there's a language literally called Lawvere. https://github.com/jameshaydon/lawvere
104.
by sullyj3 5y ago
It's not entirely clear what you want to happen here with `f` and `g`. It's trivially easy to apply `g` to the `b` in the result of f. You just use `fmap`. -- suppose we have some x :: a fmap g (f x) :: IO [c] Of cour
105.
by sullyj3 5y ago
There's no apology they could have written that would not result in some people saying it was insincere.
106.
by sullyj3 5y ago
This demonstrate countability, not finiteness. If by "world" you mean universe, there's no guarantee that you can "take everything in it", because it might be infinite.
107.
by sullyj3 5y ago
The point about the AWS console being thoroughly un-delightful is well made, it's a nightmare.
108.
by sullyj3 5y ago
https://www.michaelwest.com.au
109.
by sullyj3 5y ago
Yeah, I'm a neovim user, and I enjoy that feature. There are just times when multiple cursors would be ever so slightly more ergonomic.
110.
by sullyj3 6y ago
Copyright may or may not be a good idea, but arguing its merits isn't relevant to the question of its current legality.
111.
by sullyj3 6y ago
Very cool, has some interesting ideas! Things I love: - Many common operations are a single keystroke - saving, switching buffers, opening a new buffer. Simple design choices like this make the editor feel incredibly fluid. - Jump mode is v
112.
by sullyj3 6y ago
The installation dependency list is missing libxcb.
113.
by sullyj3 6y ago
That's definitely a killer feature for me.
114.
by sullyj3 6y ago
Agree about the second one, that seems weirdly specific, but , and m for scrolling seems reasonable enough and p/P for pasting is the same as the vi family.
115.
by sullyj3 6y ago
The difference is the interactivity and instantaneous feedback. I don't want to have to blindly write a regex substitution when I could instead be seeing what is happening at each step, right in front of me.
116.
by sullyj3 6y ago
Ah, thanks haha.
117.
by sullyj3 6y ago
What's the intuition behind the name?
118.
by sullyj3 6y ago
> How is case different from the elif pattern? Pattern matching is often conflated with switch-case by people who are unfamiliar, because pattern matching subsumes switch-case, but they're very much not the same thing. Structural pa
119.
by sullyj3 6y ago
1. You can use that style as well. You're free to return early in the error arm of the match, and make use of the Ok value in later straight line code. I've done that in fallible_function in this example: fn main() {
120.
by sullyj3 6y ago
Yeah, I'm familiar with the ML derivatives, I'm a haskeller, I was musing specifically about imperative languages, because I doubt go programmers would be interested in that much of a switch up.

More ›