Preferences

jasonpeacock
Joined 4,076 karma
[ my public key: https://keybase.io/jasonpeacock; my proof: https://keybase.io/jasonpeacock/sigs/NOzvI-pClldM3QP1RUip2qPkuuH2PhR3KgLG5ng2fgs ]

  1. My house originally had a recirculating pump for the hot water but it burned out. Somehow though, it still (mostly) worked and had instant _warm_ water.

    I think it was through natural convection/circulation - the hot water expanded in the tank and pushed it through the recirculating loop?

    So maybe there's a good-enough solution that doesn't require a pump, just a return loop.

    Now I have an on-demand water heater with a built-in recirculating pump, so it's instantly hot :)

  2. Growing up (born in late 70s), all I heard was “OMG OVER POPULATION” and how the planet can’t support the projected N billion people who will be living on it.

    Now the birth rate actually slows down to correct itself and we’re not all breeding like rabbits, that’s a bad thing?

    This feels like a capitalist concern, “we won’t have enough workers to produce goods and then consume them!”

  3. OTECs are amazing, and step 1 of "The Millennial Project: Colonizing the galaxy in eight easy steps"[0]

    [0]: https://en.wikipedia.org/wiki/The_Millennial_Project

    There's a shore-based research OTEC in Hawaii, but the best is a floating, closed-loop OTEC in the ocean.

  4. This is neat, but it's not zettelkasten - it's building a browse-able knowledge DB from content.

    Zettelkasten is about about writing down your ideas in response to content, with a link to that content, and then linking to other ideas that your already logged. It's not an extraction of ideas from that content. This is a common mis-understanding of zettelkasten.

  5. > rampant monkeypatching that made the standard library hard to count on

    That was very frustrating when doing regular development after using Rails, all the "built-ins" were actually patched into the stdlib by Rails and not available without it.

  6. > What I want is a dispassionate discussion of how different language features impact code quality

    This can be difficult because code quality, productivity, safety are hard to objectively define and measure, so we always fall back to differences in interpretation and experience.

  7. Not a belief, but my experience. Maybe I've had a blessed experience with LFS? It's always "just worked" for me.
  8. > Perforce checkout requests always do the round trip to the server

    That's literally the antithesis of Git. If that's a requirement, then yeah - Git's the wrong thing.

    It's like complaining that bicycles don't have motors like motorcycles. If it had a motor, it wouldn't be a bicycle.

  9. From the user's perspective, when setup correctly Git LFS is transparent and they don't see the text pointers - the binary files are replaced on push and pull to the server.

    It's the same user experience as Perforce?

    Yes, Git is more low-level and it's possible to see those text pointers if you want to.

  10. Perforce’s binary support is basically equivalent to Git LFS, it does the same thing.

    What does Perforce binary support have that Git LFS doesn’t?

    AFAIK, the base issue that Perforce is already in use and it has enterprise support.

  11. "If productivity can be measured by throughput then it shouldn't be done by humans."

    I forget the author, or the exact quote, but basically this. Brainless jobs should be automated, nobody should be an automaton.

    This doesn't mean we give up on craftsmanship, but mass production and busy work should be eliminated from human roles.

  12. There's also the simpler/smaller git-worktree-switcher (`wt`):

    https://github.com/yankeexe/git-worktree-switcher

    It does what it says on the tin.

  13. I mean, the same thing would happen if Bash stopped writing to `~/.bash_history` and its last item was `rm`, right?
  14. > produce memory safe software with a bit of discipline

    "a bit of discipline" is doing a lot of work here.

    "Just don't write (memory) bugs!" hasn't produced (memory) safe C, and they've been trying for 50yrs. The best practices have been to bolt on analyzers and strict "best practice" standards to enforce what should be part of the language.

    You're either writing in Rust, or you're writing in something else + using extra tools to try and achieve the same result as Rust.

  15. This is why I de-Alexa'd my house.

    I was fully invested in Alexa & Echo devices to have a voice-activated computer agent in every room, but each new "feature" was launched enabled-by-default, and every interaction started including "follup-up" prompts....which is all just ads.

    I know that such devices are another sales channel (funnel?), but when you compromise the customer experience in the name of increasing sales that's a failure of the product.

    The Kindle doesn't inject ads into the books you're reading because it's a successful product that already drives increased book sales by good at what it does.

    There's an ad-supported Kindle, but that's opt-in for a discounted device price, and the ads are non-intrusive while reading a book - unlike Alexa/Echo where the ads get in the way of using the product :(

  16. It's not that slow?

    Cargo only recompiles the crates that you edit, after the first build of the dependent crates it's quick to iterate.

    Compilation is not the bottleneck, it's the human (me) in the loop that's doing the thinking and typing.

    The productivity boost comes from Rust's strong type system and ownership (much better than MyPy) which practically ensures that if it compiles, it will work. There's a lot less troubleshooting/debugging of my Rust "scripts" than when I wrote Python.

  17. What you're asking for is called "kiosk" mode.

    Here's a random app I found: https://www.mackiosk.com/

  18. I just use Rust to do any "scripting" work. I stopped using Python and write it in Rust instead, and I'm more productive than before.

    What do you need a scripting language for that's different than using Rust?

  19. New trains: padded schedule

    Old trains: padded schedule

    So really, all train schedules are padded - which makes sense, you need buffers to absorb variance in performance to have reliable schedules.

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal