248 karma · joined October 28, 2019
> The CDC recommends using boiled, sterile or distilled water.
Flesh eating bacteria? Yeah, no, thanks.
https://www.pbs.org/newshour/health/what-to-know-about-anoth...
" System-agnostic setting making the unnamed clipboard register act like
" clipboard in any other editor. Copy with y commands, and paste with p or P.
if has('unnamedplus')
set clipboard=unnamedplus,unnamed
else
set clipboard+=unnamed
endif
Beside this, there is also the issue of setting paste when pasting in insert mode.One thought regarding the quantification element. I’ve grown to appreciate the uniformity of Go’s solution, where you always import an entire namespace, optionally aliasing it to avoid conflicts.
This small restriction makes some naming decisions simpler (for example sticking to config.Parse, and not the stuttering config.ParseConfig). Additionally it sprinkles the namespaces over the code so you get at least _some_ feel for them.
On another note, on some occasions I have thought to myself that it’s easy for the import section to get to little scrutiny on reviews, and wondered if there’s something that could make us wonder „should x depend on y?” more often.
I moved from Linux to M1 MacBook recently. I know my greps and vims, but I was tired of audio glitches during high CPU usage, system not waking up from sleep, total OS freezes, super loud fans, and so on.
Now I get none of that. I don't think I've ever heard the fans. Audio just works, everything is super snappy. It always wakes up. I'm no longer afraid of bluetooth.
And on top of that, setting my $DAYJOB VPN took three minutes and it just works, where on Linux I had constant problems with DNS breaking, and setting it up was always an hour of work, praying I got the config files right this time.
It really seems to be "unixy desktop with working sound", the best of both worlds.
Type systems in general reject some programs as invalid, but this claim is usually made with powerful type systems in mind; think Haskell, Idris, Rust. I only played with these casually, but it is true that you can write some code, and then let yourself be guided by compiler in fixing all the errors. It's often the case that the resulting program just works.
Rust's borrow checker is a part of its type system, based on some flavor of linear types if I remember correctly. Think about it: the type system can protect you from double frees. This is powerful.
In Haskell, for starters, you can't do any side effects outside of IO monad. You can express precisely what a given function is allowed to do.
In dependently-typed languages you can express that, for example, a function concatenating lists of length n and m returns a list of length n + m.
And aside from these above there is a lot of other, less magical things: no nulls, exhaustiveness checks for ADTs, some focus on immutability, lack of exceptions, and so on.
Now, I doubt we are all going to write Idris in five years, and even there bugs do happen obviously. But the idea compiles==works is not entirely out of this world.
It's a meme title, I've seen it a couple of times on HN: https://hn.algolia.com/?q=Unreasonable+Effectiveness
Also see: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
I always die a little hearing the flying rat thing. I get that they can be really annoying, waking you up, trying to lay eggs everywhere. But—having helped to care for many injured, sick, and unwell animals, pigeons _and_ fancy rats among them—I can't help but to feel sorry for how they are treated.
The drummer essentially plays two rhythms at once. His hands mostly do 4/4, but feet play a shorter phrase that only lines up with hands every couple of bars. It's like simultaneously counting to four on one hand and to three on the other hand, but using four limbs on a full drum kit, adding accents, ghost notes, changing time signates, and not skipping a freaking beat.
And their every song is like this. I also think on "Combustion" he plays 1/16 note off from the rest of the band.
Shameless plug: I've recently written a blog post about how set -e suddenly ceases to work when using function calls in flow control (what you refer to as "disabled errexit quirk"): https://snails.dev/posts/set-e.html
Your comment made me interested in Oil, thanks!
I see a single advantage to these frameworks though. They force you to write a test in a specific way that looks like a real-world scenario with clear delineations between setup stages, assertions, and so on. Not that it's impossible to achieve with regular programming language, obviously.