Avatar

FizzyOrange

FizzyOrange@programming.dev
Joined
2 posts • 458 comments
Direct message

Very cool. To be honest most of these languages (except maybe Lisp and BASIC) are pretty awful. I can’t imagine writing anything in them. Especially K. That’s got to result from some form of brain damage…

It’s only 7 bytes of code. !10 returns a list of numbers 0 to 9. 1+!10 adds 1 to each of them resulting in a list [1, 2, …, 10]. Finally /1+!10 applies * verb with scan adverb and returns 123…*10 which is a factorial of 10.

But it processes arrays of numbers in such an elegant way what no other language can compete with it (well, maybe numpy).

Uhm yeah or maybe MATLAB? I mean I mainly like MATLAB because of its unbeatable plotting abilities, but even MATLAB can do prod(1:10). I am very happy to spend 3 extra bytes on that readability improvement!

permalink
report
reply

Only a Linux user’s answer to “how do I install software that’s not packaged for my distro” would be “don’t”.

permalink
report
parent
reply

The only Git GUIs that I’ve ever liked:

  • GitX, and its many forks. Mac only though.
  • Git Extensions. Terrible name, but this is actually a standalone Git GUI and is surprisingly decent. I think it started Windows only but maybe there’s a Linux port now.
  • VSCode’s “Git Graph” extension. It’s not quite as fully featured but it integrates well into VSCode and is pretty nicely designed.

I’ve tried almost all the others (SmartGit, Sublime Merge, GitKraken, etc.), and didn’t really like how they worked.

permalink
report
reply

It’s sooo sloooow though.

permalink
report
parent
reply

Ooo I’ve not seen this before. Looks interesting.

permalink
report
parent
reply

Impressive persuasion! I can’t imagine that ever working at any company I’ve worked at.

permalink
report
reply

Swift users… how is it? I hear compile times are bad. Worse than C++/Rust?

permalink
report
reply

It’s not just that. Debugging segfaults and UB can be an absolute nightmare.

The C++ committee still haven’t learnt their lesson. I recently learnt about C++20 coroutines, which are pretty neat, if complex (there are pretty much no good learning resources about them). However they are still putting unnecessary UB footguns in it.

permalink
report
parent
reply

It’s not moot. The Safe C++ is opt-in to safety. It has to be because otherwise it wouldn’t be compatible with existing C++.

permalink
report
parent
reply

Yeah but I have written a lot of Rust and I have yet to use a single unsafe block.

Saying “but… unsafe!” is like saying Python isn’t memory safe because it has ctypes, or Go isn’t memory safe because of its unsafe package.

permalink
report
parent
reply