Since this has turned into a "giggle about fans" thread, one of my favorite company names is Big Ass Fans [1]. They make really large fans for warehouses, etc. And their logo is a donkey.
I got three of their house fans from Costco a few years ago. Great fans - low power draw, good looks, includes a nice light, good noise profile, etc.
The fans didn't include wall panels, which I wanted rather than only remotes. No problem, I figured I'll order 3 of them from their site. However, there's an obvious bug in the shipping calculator, where the cost to ship three little wall boxes came out to $40+$40+$40 = $120. (And where the shipping page called this a "flat rate".) If I wanted to order 50 wall boxes, the shipping would be $2,000! The shipping cost was completely incongruent with other items in their shop - e.g. I could order 100 branded mugs for a flat shipping charge of $40. (And this is on top of the wall controllers that where already $123 each for some pretty simple electronics.)
I had probably a dozen support interactions over a couple weeks over both phone and email trying to get Big Ass Fans to fix their broken website and/or just put the wall controllers in a $30 flat-rate shipping box for me before we finally settled on a $55 shipping charge where I still felt like I was getting ripped off.
OnlyFans lost its purported audience years ago, when they made the decision to include human adult content in addition to fan-related content only. The adult content quickly took over and now you can barely find anything relating to fans on there.
Reddit is a much better place for that now, and if you aren't particularly precious about documentary-style fact reporting, you're much better off browsing r/fanfiction.
I think there were plenty of signs for the reader. My pet theory is that overly verbose llms have trained people to skim text instead of reading it. I've certainly noticed more cases than usual of people not reading HN comments thoroughly enough in the last six months
I’m sorry too. my stupid jokes in response to yours earlier were just me taking advantage of bad fan puns but others seem to have jumped on the downvote bandwagon.
I thought "when they made the decision to include human adult content in addition to fan-related content" in the first sentence was already pretty obvious
Ok well that at least has examples of the syntax. But not a single example of actually using the language to do anything. That is, no examples of actual code.
It took a while to click through a link to an actual implementation on github, which had some test examples. None of which were documented.
So idk? I'm not going to buy the ebook for $41 to find out.
So to answer your original question: Liskell, despite being 13 years old and unmaintained, does actually have an accessible document that _explains what it is_.
What are the reasons why PyPy hasn't caught on? I know about PyPy for ages, but I still haven't given it a try, I still feel the aftertaste of anaconda...
The biggest issue has been that CPython exposes its internals to native libraries, thus since many Python libraries are actually thin bindings to native libraries, this reduces the interest in using PyPy.
There is now new ABI proposal that should work across Python implementations, proposed by PyPy, but the uptake seems slow.
> rest of the post is me trying to make sense of the tutorial on borrowing. It has fried my brain and negatively affected my skills in modern Rust, so be wary
I think that tutorial discouraged me from really getting into Rust
I’m no expert in Rust, but have done a couple of very minimal weekend projects. In the time I’ve read up on Rust, I’ve always looked at the borrow mechanism like an extreme/overactive implementation of RAII from C++, that is triggered with every context change.
Would be interested to hear where this analogy breaks down from someone more experienced than me.
Borrowing and RAII are basically separate features, though they do interact.
RAII in Rust is like C++, but simpler: there are no constructors, only destructors. The Drop trait gets called like in C++, except that in Rust, moves are the default, and destructors don't get called on moved-from objects, that is, your destructor only runs once.
References are, at runtime, the same as a pointer in C++, except they cannot be null. We also say that they "borrow" what they refer to, which means that the compiler keeps track of the lifetime of the referent. This ensures that the referent always outlives its reference, so that its reference is always valid. This is a compile-time analysis on the control-flow graph of your program.
One of my favorite RSS readers is https://vore.website - river of news, no unread indicators, simple. It's a website, as the domain suggests, so no need to install anything.
Yeah, after the appropriate layers of VPN/Incognito/Tor/muted phone/etc I braved the link, and it turns out it's actually real, but that is still not a hostname I want connected to me in anyone's access logs more than once.
It's under the NON-VIOLENT PUBLIC LICENSE v5, which is probably not open source, but should be fine for personal use if you're not an arms dealer or prison warden.
There's more RSS readers than you can count. No need to pick a proprietary one with a sketchy license when there are tons of great open-source options.
https://www.youtube.com/playlist?list=PLHLn2U7i45M_EXIsnqUyI...
reply