turboponyy (u/turboponyy)

turboponyy commented on Judge hints Vizio TV buyers may have rights to source code licensed under GPL theregister.com/2025/12/0... · Posted by u/pabs3

charcircuit · 4 days ago

This doesn't make sense. If Vizo never licensed the software to you under the GPL, you can't say they violated the GPL. The court should not be able to make up contracts that don't exist between parties.

turboponyy · 3 days ago

> If Vizo never licensed the software to you under the GPL [...]

That may be true.

> [...] you can't say they violated the GPL.

That does not necessarily follow.

If they used GPL-licensed code in their product, they may be obligated to provide the source code to that product's consumer.

turboponyy commented on Ask HN: What Are You Working On? (December 2025) · Posted by u/david927

krlx · 7 days ago

If there's a demand for it to become open-source, why not? But I'll have to improve code quality first. As the presence of french labels indicates it, i18n is not properly implemented for this project.

turboponyy · 7 days ago

No, you really don't have to. Partially complete software can have a lot of value too.

Anyone can fork it and quickly add the i18n (or just translate into a different language) for their own purposes. People will likely want to contribute i18n. People may fix or improve things for you.

Of course, it's entirely up to you - but I've appreciated half-complete software countless times before.

turboponyy commented on The highest quality codebase gricha.dev/blog/the-highe... · Posted by u/Gricha

written-beyond · 13 days ago

> I like Rust's result-handling system, I don't think it works very well if you try to bring it to the entire ecosystem that already is standardized on error throwing.

I disagree, it's very useful even in languages that have exception throwing conventions. It's good enough for the return type for Promise.allSettled api.

The problem is when I don't have the result type I end up approximating it anyway through other ways. For a quick project I'd stick with exceptions but depending on my codebase I usually use the Go style ok, err tuple (it's usually clunkier in ts though) or a rust style result type ok err enum.

turboponyy · 10 days ago

I have the same disagreement. TypeScript with its structural and pseudo-dependent typing, somewhat-functionally disposed language primitives (e.g. first-class functions as values, currying) and standard library interfaces (filter, reduce, flatMap et al), and ecosystem make propagating information using values extremely ergonomic.

Embracing a functional style in TypeScript is probably the most productive I've felt in any mainstream programming language. It's a shame that the language was defiled with try/catch, classes and other unnecessary cruft so third party libraries are still an annoying boundary you have to worry about, but oh well.

The language is so well-suited for this that you can even model side effects as values, do away with try/catch, if/else and mutation a la Haskell, if you want[1].

[1] https://effect.website/

turboponyy commented on The fuck off contact page nicchan.me/blog/the-f-off... · Posted by u/OuterVale

ares623 · 14 days ago

Off topic but love the site design

turboponyy · 13 days ago

It is unique and looks cool.

When it comes to providing an enjoyable blog post reading experience, it really does creep into the "fuck off" territory for me, though.

turboponyy commented on Jujutsu worktrees are convenient (2024) shaddy.dev/notes/jj-workt... · Posted by u/nvader

spider-mario · 14 days ago

> I’ve been using Jujutsu(jj for short) as my defactor git cli frontend for a while now.

“de facto” please.

turboponyy · 13 days ago

Even better is "" since it's not really adding anything

turboponyy commented on Experiment: Making TypeScript immutable-by-default evanhahn.com/typescript-i... · Posted by u/ingve

voidUpdate · a month ago

How do immutable variables work with something like a for loop?

turboponyy · a month ago

`for` loops are a superfluous language feature if your collections have `map` for transformations and `forEach` for producing side effects

turboponyy commented on Using Emacs as a TUI blog.natfu.be/emacs-in-te... · Posted by u/NeutralForest

wredcoll · 2 months ago

It genuinely never ocurred to me that you use emacs somewhere outside the terminal.

turboponyy · 2 months ago

It's quite nice for the following reasons:

- Image previews (for file management with dired/dirvish)

- PDF viewing

- In-buffer images (e.g. profile pictures in git log with Magit)

- Browsing simple HTML pages (e.g. API docs)

There's probably more I've yet to discover.

turboponyy commented on consumed.today consumed.today/... · Posted by u/burkaman

OisinMoran · 3 months ago

Yeah, it's quite worrying. The best I'm seeing is just two eggs, which is about a tenth of the total protein they should probably be eating.

If you're reading thus, the general rule of thumb is 1.8g/kg of lean body mass. Works out as around 4 meals per day of 20-40g of protein each, depending on weight.

Wonderful website! I would like the creator to continue existing for as long as possible.

turboponyy · 3 months ago

You only need that much protein if you're trying to build muscle. The amount needed for a generally healthy diet is much lower.

turboponyy commented on Node 20 will be deprecated on GitHub Actions runners github.blog/changelog/202... · Posted by u/redbell

bramblerose · 3 months ago

I find the repeated deprecations on GitHub Actions frustrating to work with. One of the key goals of a build system is to be able to come back to a project after several years and just having the build work out of the box.

Yet with GHA I need to update actions/checkout@v2 to actions/checkout@vwhatever (or, what I'm doing now, actions/checkout@main because the actual API haven't actually changed) because... some Node version is "out of maintenance"?!

GHA is literally code execution as a service. Why would I care whether the Node runner has a security vulnerability?

turboponyy · 3 months ago

If that's something you care about, then don't define your CI build in terms of GitHub Actions steps. Instead, call your build that takes care of using whichever version of Node you want in CI.

turboponyy commented on That boolean should probably be something else ntietz.com/blog/that-bool... · Posted by u/vidyesh

Fraterkes · 4 months ago

I’m not a very experienced programmer, but the first example immediately strikes me as weird. The consideration for choosing types is often to communicate intend to others (and your future self). I think that’s also why code is often broken up into functions, even if the logic does not need to be modular / repeatable: the function signature kind of “summarizes” that bit of code.

Making a boolean a datetime, just in case you ever want to use the data, is not the kind of pattern that makes your code clearer in my opinion. The fact that you only save a binary true/false value tells the person looking at the code a ton about what the program currently is meant to do.

turboponyy · 4 months ago

I actually completely agree with both the article and your point that your code should directly communicate your intent.

The angle I'd approach it from is this: recording whether an email is verified as a boolean is actually misguided - that is, the intent is wrong.

The actual things of interest are the email entity and the verification event. If you record both, 'is_verified' is trivial to derive.

However, consider if you now must implement the rule that "emails are verified only if a verification took place within the last 6 months." Recording verifications as events handles this trivially, whilst this doesn't work with booleans.

Some other examples - what is the rate of verifications per unit of time? How many verification emails do we have to send out?

Flipping a boolean when the first of these events occurs without storing the event itself works in special cases, but not in general. Storing a boolean is overly rigid, throws away the underlying information of interest, and overloads the model with unrelated fields (imagine storing say 7 or 8 different kinds of events linked to some model).