Hacker Newsnew | past | comments | ask | show | jobs | submit | jckahn's commentslogin

Please never become a product manager.

Why? We can just get 7 engineers to work on each laser in parallel and it'll be done in record time!

Why 7? Just got 1 engineer intern and 10x with AI /s

A terminal case, even

This is the most delightfully autistic response to the article.

Somebody has to have a goal and prompt them.


One person is enough for this. And even he can be replaced by simply looping the idea creation prompt.


I do. I miss practical effects; they were much more entertaining.


I don’t, they seem campy and reduce the gravitas compared to very well done CGI. Infact, I feel like it has the same effect at poorly done CGI.


Can this use local LLMs?


Yes - you can use local LLMs through LiteLLM and Ollama. Would you like us to support anything else?


LM Studio?


Yes, because LM Studio is openai-compatible. When you run rowboatx the first time, it creates a ~/.rowboat/config/models.json. You can then configure LM Studio there. Here is an example: https://gist.github.com/ramnique/9e4b783f41cecf0fcc8d92b277d...


It's all fun and games until you learn that physical media has a limited shelf life.


It’s why you archive the things you buy on physical media.


> you learn that physical media has a limited shelf life.

Their point is that physical media itself has a limited lifespan.

You need to continuously "refresh" it every 1 to 10 years, depending on the physical media you choose, or it's most likely corrupted. I've lost many HDD, SSD, SD cards, and about 50 "archival quality" DVD/CD to time, with all manufacturers having somewhere around 3x to 20x exaggerated claim of longevity. I'm guessing their numbers are based on some temperature/humidity controlled marketing BS, rather than anything resembling reality.

SD Cards are the saddest. I've seen many older members of my family shed tears when they pull out their SD cars they carefully stored in a drawer/safe, and they're junk. Charge drift be a harsh mistress.


so does digital..


Yes, React


Why would it matter what library you use? I'm using React, I do <table> whenever I need to display tabular data, React or no React as no impact on when I'd use <table>.


Just make sure to pass a subscriber to useSyncExternalStore if you decide to venture outside React and use HTMLTable.insertRow, you see react is really smart and won’t let you use this piece of outdated code without punishing you with side effects.

Thanks Vercel & Meta for protecting us.


> Just make sure to pass a subscriber to useSyncExternalStore if you decide to venture outside React and use HTMLTable.insertRow, you see react is really smart and won’t let you use this piece of outdated code without punishing you with side effects.

Huh? Why'd you involve state in this or any imperative code? You render the rows/columns as you'd render any other DOM elements in React, pass in the data as props and iterate on it, create children and pass them to render.


InsertRow updates the live DOM and React just wholesale replaces it. It’s a masterstroke footgun.


Yes, your point? Anyone who spend 15 minutes learning about React learns that you don't manipulate the DOM directly, you let the rendering engine handle that for you.


Yes that’s why of instead of learning the standard apis, you have to spend 15 months learning how to debug useEffect


Or just skip all of the newly released stuff and use React as it was originally made, like me and many others still do. Never suffer from having to debug "useEffect" because we literally never use it. You don't have to use the newest and shiniest toys, especially not those with footguns.


React is as orthogonal to DOM manipulation API as it is to letting the browser render tables from HTML.


And what does that use internally to manage tables? Just because there is layer between you and the API, it doesn't mean API is abandoned.


Are you implying that when doing DOM reconciliation, React uses these table-specific insertRow/insertCell APIs for adding and removing elements in tables instead of the regular DOM element APIs it would use for all other elements? I would be surprised if that's the case.


The funny thing is the insertRow/insertCell API just call into DOM manipulation functions like appendChild internally, they just provide some syntactic sugar around things like managing the rows/cells array. It's all the same

https://github.com/WebKit/WebKit/blob/28fa568972a4d34d867948...


Why would anyone use this outdated code over useInsertRow() and useTableColumnEffect()?


What are those and where are they in standard Javascript / DOM API?


I don't ever want to be dependent on a cloud service to be productive, and I don't want to have to pay money to experiment with code.

Paying money for probabilistically generated tokens is effectively gambling. I don't like to gamble.


Where did you get your free GPU from?


The problem is the same as owning the house vs. renting.


I just use my AMD Framework 13 and 24GB M4 Mac mini. They run gpt-oss models, but only the 20b fits on the mini.


GPUs can do other things. Cloud service LLM providers cannot.


This is one of those random internet comments that I'll be thinking about for decades. Thank you for sharing it!


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

Search: