shadytrees
From what I understand, PTACs started as a convenient way to retrofit apartments with air conditioning. You don't need ductwork, which I believe is more expensive in the concrete buildings around here. Also, I think you need protected refrigerant sleeves to meet code here, but only if the sleeves go from one floor to another (someone just told me this fact today, and i haven't verified this).
BTW that PTAC's thermostat dial in the link doesn't have numbers around the dial, which I think is honest. No A/C unit I've ever owned has managed to have a thermostat that read the temperature I was feeling consistently. It makes me think the apartment was built before the late 2010s though -- still feels new but a generation ago in HVAC terms. Mini-splits seem to have arrived, even for <1M condos. Talking to the mini-split contractors I had over recently for a squeaky noise, I got the feeling that business was booming. They had every day in the summer booked months in advance.
https://github.com/SerenityOS/serenity/graphs/commit-activit... https://github.com/SerenityOS/jakt/graphs/commit-activity
If Cloudflare wants to defend the future of the web, maybe they could also throw a few dollars towards projects with better governance and aren't helmed by a BFDL with a spotty record and are written in a more future-proof language than C++ [0]. (For example, Servo.)
[0]: In Kling's own words! https://web.archive.org/web/20250819053816/https://awesomekl...
+1. I spent hours lovingly sanitizing and prepping and waiting for habaneros to ferment; in the end, they added a bit of funky tang, but I didn't feel like it was worth the time. I realized that vinegar-based hot sauce recipes are quicker to iterate on and perfect and taste closer to what I prefer.
However, it's all subjective! Watching something ferment in a container is inherently fun, in the way a terrarium with a small creature in it can be. YMMV.
> Lucy’s father was not as pleased with his new quarters. Two days after the Johnsons moved in, he told West, “Mr. West, if you can’t get that shower of mine fixed, I’m going to have to move back to The Elms.”
> “He didn’t sound as if he were joking,” West was to say. And after the President explained that the water pressure was inadequate, and that he wanted the same elaborate, multi-nozzle arrangement that he had had at his former home, he repeated his threat to move out. Then, “without a smile, he turned on his heel and walked away.”
> A few minutes later, Mrs. Johnson asked West to come by the room she had chosen for her once, a small sitting room with one door. “I guess you’ve been told about the shower,” she said, with a smile, and repeated to West what she said to all Johnson employees. “Anything that ... needs to be done, remember this: my husband comes first, the girls second, and I will be satisfied with what’s left.”
> As he became acquainted with the Johnsons, West was to write, “I soon could see that had been her life’s pattern.” Nothing, he came to see, could “faze her.”
I'm kind of astounded the article didn't talk about Paul Singer at all. It seems like a massive oversight to not dig into the money behind Barnes and Noble.
As a result, raising and catching exns in OCaml is cheap. List.fold_until in Base, for example, is implemented with exceptions: https://github.com/janestreet/base/blob/ae169dc8097b3da8e99d... (With_return is internally implemented by raising an exception in a try-with.)
Implementations of functional programming languages often have powerful, yet fast!, non-local control-flow primitives. GHC recently sprouted delimited continuations (https://ghc.gitlab.haskell.org/ghc/doc/users_guide/9.6.1-not...), for example, and Lisps have had that for much longer. It's easy to program in an imperative language for a long time and think that straight-line control flow is the end-all, be-all for performance—but it doesn't have to be the case.
In case you were looking for more examples of "open source being held together by one tireless person somewhere" (obligatory xkcd comic link omitted).
Cool comment
Cocoa also lets you two-way bind a state object with the view as long as the state object (whether it's a controller or a model or a view model) implements key-value coding; notably, the blessed data framework (Core Data) is KVC-compliant, so apps that use Core Data sort of get all this for free. Core Data also has fairly good support for undo/redo. That being said, Core Data is a fairly idiosyncratic relational data layer. It's sort of a double-edged sword: it's easy to do 90% of what you want, and the last 10% will involve some deep dives into Apple's documentation. But it's been a long time since I've written an app on OS X -- someone will have to correct my errors.
I've long thought that the inverse of what the OP suggests, bringing reactive UI programming techniques to Cocoa, would be much more interesting. Making native apps just as easy and as fun to build as web apps would be great! ReactiveCocoa/ReactiveSwift are promising, but the underlying, mutation-heavy Apple APIs still peek through. SwiftUI also seems promising, but still relatively immature to the, gosh, decades-old OS X platform.