HNHacker News
TopNewBestAskShowJobs

edfletcher_t137

615 karma · joined April 18, 2020

submissionscomments
edfletcher_t137··on I couldn't find a free, no-login, no-AI checklist app–so I built one
That's a great question! And fortunately, one where you can use human behavior as a guide: if someone is actively using a checklist it seems reasonable to presume they're at least accessing it once a day. So as a quick first-pass, double that time period to two days. Also start collecting usage metrics and mine those in the future to further refine this number.
edfletcher_t137··on I couldn't find a free, no-login, no-AI checklist app–so I built one
You may want to consider a keep-alive strategy based on usage and not an arbitrary static timeout. What if I need my checklist for 7.5 days? A corollary is that this may reduce your overall data usage as a lot of people may create a list and immediately abandon it. If you can expire those in less than 7 days, you're saving.
edfletcher_t137··on Rust solves the problem of incomplete Kernel Linux API docs
> The day I stopped believing in the possibility of "self-documenting code" was the day I started writing more readable code.

"More readable" is self-documenting! Doesn't matter how you get there (though it's a bummer you've lost faith), just matters that you did.

> No type system will replace docs or even comments. No type signature will give you the why, the big picture or the context.

Types are just one small part of the picture: did you read even the first full message, much less the full post? Are you aware of the other non-type-related benefits Rust provides?

OP helpfully gave an illustrative list I'll reproduce here for you since I'm not sure you saw it:

> When a callback is called are any locks held or do you need to acquire your own? What about free callbacks, are they special? What's the intended locking order? Are there special cases where some operations might take locks in some cases but not others?

> Is a NULL argument allowed and valid usage, or not? What happens to reference counts in the error case? Is a returned ref counted pointer already incremented, or is it an implied borrow from a reference owned by a passed argument?

> Is the return value always a valid pointer? Can it be NULL? Or maybe it's an ERR_PTR? Maybe both? What about pointers returned via indirect arguments, are those cleared to NULL on error or left alone? Is it valid to pass a NULL * if you don't need that return pointer?

Only a few of those are concerned with type safety. You really should read the whole thing.

edfletcher_t137··on Rust solves the problem of incomplete Kernel Linux API docs
Another perspective which makes it clear this is The Way: it brings the promise of fully self-documenting code much closer to fruition, if not all the way!
edfletcher_t137··on Micro-libraries should never be used
The fact that we're even debating it shows that they do. And I didn't ask for "an exact line". I asked for anything. What is your qualification for a "micro" library? I'm betting it's different from 9 other respondents. That's a problem.

Furthermore, that's not even the main contention I was highlighting. Without a proper definition, the advice of "just copy/paste these" is dangerous. Someone will draw their line at something too large, copy/paste that in and inherit bugs/vulnerabilities they never fix. That's a big problem.

edfletcher_t137··on Micro-libraries should never be used
Where do you draw the line: is 10 lines "micro"? 50? 100? It is never quantified within, yet the very click-bait-y title relies on the term. How many bugs can hide in 50 lines or 100? And you really want to copy-paste that code at a static point in time?!
edfletcher_t137··on I kind of like rebasing
> - Somehow reviewers never seem to like the stack of PRs, my experience is they always react with disdain and/or confusion.

Are people sending multiple branches of the stack for review at once? It should only ever be the "bottom" branch out-for-review at any time.

> - Namely there would be review comments on the first PRs that then cause a cascade of merge conflicts in the follow-on PRs

This can still happen in the model above of course as you need to make changes to the bottom branch in response to review comments/requests.

However, as I noted elsewhere, `--update-refs` is an absolute god-send in those situations: https://andrewlock.net/working-with-stacked-branches-in-git-...

It reduces a ton of manual work (scaled by how many branches you have stacked!) to one operation.

edfletcher_t137··on I kind of like rebasing
> I find merging to be extremely tough to work with -- I don't think I actually got good at git until I learned to rebase entirely.

> Also, cherry-picking (effectively an atomic rebase-type) is underrated.

This this this, all of this.

I never really "got git" until I finally committed to learning how rebase works.

+1 to cherry-picking. Also patch-add (`add -p`).

edfletcher_t137··on I kind of like rebasing
Sure you can! In fact you can do magic on stacked branches with `rebase --update-refs` that you can't do with merge: https://andrewlock.net/working-with-stacked-branches-in-git-...
edfletcher_t137··on British Nuclear Warning System
Came here to say this. I was genuinely interested in reading this page, but the blue-on-gray promptly gave me a legitimate headache. I cannot understand the person who thinks this is OK.
edfletcher_t137··on ICQ will stop working from June 26
I can't remember what I did yesterday but I will remember my ICQ number until the day I die.

RIP to an absolute legend.

edfletcher_t137··on The creator of 'Magic: The Gathering' knows where it all went wrong
"This wasn't just nostalgia talking. There seems to be something objectively more magical, more infinite-seeming and treasurable about this smaller, more limited version of Magic."

Not that I ever had the chance to play the pre-release version of the game, but the explosion of complexity has made me yearn for exactly this, a "smaller, more limited version"... so much so that I wrote https://twmtg.computerpho.be/ to try and capture it (and also, admittedly, as a bit of a joke/dig)

edfletcher_t137··on I joined landlord groups to persuade them to be better people to their tenants
OP isn't the hero we wanted, they're the hero we need.
edfletcher_t137··on Meta Horizon OS
Subtitled "Not an actual product render."
edfletcher_t137··on Introducing rcompat
Excellent project, well done!
edfletcher_t137··on Apple to wind down electric car effort after decadelong odyssey
> The two executives told staffers that the project will begin winding down and that many employees on the team working on the car — known as the Special Projects Group, or SPG — will be shifted to the artificial intelligence division under executive John Giannandrea.

It sounds like this means the official end of SPG, the group that Tony Fadell took over to eventually build the iPod (among other things). A storied history, to say the least.

RIP SPG.

edfletcher_t137··on Rye: A Vision Continued
> The PyPA should shut down or merge some duplicate projects, and work with the community (including maintainers of non-PyPA projects) to build One True Packaging Tool. To make things easier. To avoid writing code that does largely the same thing 5 times. To make sure thousands of projects don’t depend on tools with a bus factor of 1 or 2.

-- https://chriswarrick.com/blog/2024/01/15/python-packaging-on...

edfletcher_t137··on Rye: A Vision Continued
I included it because the author did, and irked me by openly admitting they recognize the argument but went against it anyway. There is good reason that particular XKCD hits so hard.

Chris Warrick has done a ton of thinking - and a lot of writing [1] - on the subject and has very sage things to say about it. But unlike the author, he didn't decide to write another one. Because there are many good reasons not to. Thanks for letting me know you didn't bother reading that follow-up though: pretty clear who is providing zero value here :shrug:

[1] In fact, here's more he has to say about it: https://chriswarrick.com/blog/2024/01/15/python-packaging-on...

edfletcher_t137··on Rye: A Vision Continued
LOL I surely did, it even explicitly says:

"I did not feel well throwing yet another Python packaging tool into the ring.

Yet it exists now and has user. (sic)"

TL;DR: I knew it was a bad idea, but I did it anyway.

But I wouldn't have had to, anyway. Because I know how names work: "Rye" is not in the set of current named tools. Doesn't matter that it wraps them. It becomes one by doing so, and now we have 15.

edfletcher_t137··on Rye: A Vision Continued
This is an impressive effort, no doubt. And Python packaging is in a woeful state. But I'm sorry, the last thing the ecosystem needs it another alternative!

https://chriswarrick.com/blog/2023/01/15/how-to-improve-pyth... https://xkcd.com/927/

edfletcher_t137··on Lowercase letters save data
Yes but they greatly enhance readability and are carriers of information. Don't throw the baby out with the bath water. Just because you can doesn't mean you should. There are so many cliches that apply here.
edfletcher_t137··on Simple Lasts Longer
> They can only last if they’re simple to maintain, otherwise keeping them working becomes tedious and the author eventually gives up.

This, x1000.

I cannot count how many hobby projects I have outright abandoned at the first failure, never to return. The fix may have been simple too! I'll never know, though: the startup effort required to re-contextualize myself with the complex mess I'd made was never worth it at the time, and the longer you let them languish the less-likely you are to return. RIP, projects.

Simple Lasts Longer.

edfletcher_t137··on Waiting on Tests
> So in my opinion, the primary purpose of automated tests is not to avoid failures, but to speed up development.

Such a juicy premise, let's dig in. In my opinion the primary "speed up" to development comes in allowing changes - especially sweeping refactors - to happen without worry. As a corollary, they provide "primary source documentation" on the inner workings of the code so that less-experienced developers can approach such tasks without worry. The value of these are exactly the same regardless if your tests take 10 seconds or 10 minutes to run. The only difference is that we've sped up our critical path development work by not focusing on hyper-optimizing tests. And to start out the gate with such a premise but then fail to provide any data related to the effects on developer cadence, in a data-heavy writeup!?

edfletcher_t137··on Making small games, which is fun in itself
This is a lovely book, thank you for putting it together! Immediate bookmark.

They really are fun. In fact making small games was my pandemic challenge: I decided that it was finally time to try these things. I ended up building a tool for cutting up and annotating tile maps first - https://tmt.computerpho.be/ - then used it to create a minimal browser city simluator, https://pc.computerpho.be/. These also served as experiments into building single-file "apps" for the browser, which was fun as well!

edfletcher_t137··on Brickception
Frustratingly difficult: I love it! The cleverness here is excellent. Well done!
edfletcher_t137··on Show HN: A Dalle-3 and GPT4-Vision feedback loop
A clever idea that I'd love to play around with, but not without a source link so I could feel better about trusting it and host it myself.
edfletcher_t137··on Peredvizhnikov Engine: Lock-free game engine written in C++20
> At the moment, the only supported platform is Linux.

Regardless of your feelings on the status quo, there is one thing you must do when building a game engine if you want it to succeed: support Windows.

edfletcher_t137··on DOS Game Club
The style for this site is fantastic. Is it available as importable source somewhere?
edfletcher_t137··on Phone.wtf
Haha wow, thank you for this: I had no idea! It's a good word, deserves more exposure than that :)
edfletcher_t137··on Phone.wtf
Not to mention many of us live like this already without needing to proselytize it. Just Do It.
← PreviousPage 2 of 5Next →