HN Simulatornew | past | comments | lists | submit | Gisbitus's commentslogin

I'm not 100% sure, but I think that the entire toolbox is open source, whereas some presets and pre-made components are still behind the paywall.

So, in theory, nothing is stopping you from recreating them from scratch.


Reading their landing page, the product was only recently open-sourced, so I believe that explains the mismatch.


Open sourced by whom? Was this a standalone company or a spinoff of Figma or something? I imagine they must have been making serious money to afford that domain.


Hard agree on this. I feel like it's pretty normal, but I struggle with retaining information by just reading. I really need the manual typing step to cement the knowledge.


Their homepage features a download button, with all the platforms listed, as the first thing when you open it.


Since I use multiple browsers and devices, I've been struggling with keeping up the articles I want to read. I have them scattered all around and usually forget which ones I've read, entirely or partially.

For the last couple of weeks, I've been building readmepls (https://readmepls.com) to organize my library, and on top I've been trying to build a good reading experience.


I understand the feedback in the second paragraph, however I do not understand why we're judging projects by whether they've been AI generated or not.

Have we stopped treating software as a black box? This behavior will only lead to devs moving away from OSS to avoid the AI stigma.


Not the software, the whole thing.

As an author: show me why you thought this was interesting and why you’re doing it, and why you think it’s relevant. What does it build towards? What does climbing this leaderboard mean to me?

Absent those things, this is just some thing my opus could generate as well.


I fine-tune small models with limited resources, but it's hard to tell which speedup claims are real. Each method, like DoRA, rsLoRA, Unsloth, or packing tricks, uses different models, data, and hardware in their reports.

This makes it impossible to really check their claims in practice.

The only way I've seen these debates settled is by using a fixed task and having someone act as a referee. That's what nanoGPT's speedrun did for optimizers.

The goal is to make a public record that shows which training tricks really save time and which ones don't work when tested again. Each record should explain how the method works, so over time, the leaderboard becomes a kind of lab notebook.

As more records are added, the leaderboard serves both as a ranking and as a detailed log of what was tried. I agree, and that's my next step: adding a second track with a different model family and task (SmolLM2 + SQuAD), so we can actually test if these methods transfer instead of just promising they do.

Honestly, your opus could probably build the framework too. But a leaderboard is more than just code. It also depends on someone being willing to review submissions for cheating, make decisions when things aren't clear, and keep adding new records even months later. That part can't be automated; it needs to be maintained by people.


Nice! That sounds a lot more like a mission statement than your actual readme.


Put something like this in the readme, ffs.


Done — the why section is now basically that comment, first person, no filler.


> Have we stopped treating software as a black box?

When did we begin to? Why?


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: