HN user

fireant

112 karma

https://kelin.dev

Posts0
Comments104
View on HN
No posts found.

Personally I've always found it funny that the widely used work software is called Slack which is very close to slacking (not working hard enough).

Personally I really dislike when the agents generate super long composed shell commands because they are really hard to audit. ffmpeg I'd whitelist, but if it makes a mistake in some super long chained git command it can have pretty scary consequences.

Deno Desktop 1 month ago

That's really nice. It would be really good for game GUIs too where the situation is quite poor and would work well with underlays/overlays/worldspace UIs. That said while binary size may be around 10mb, it still baloons to 500mb at runtime for your TODO list example which is more than some electron apps.

That's really nice. Have you tested if it works well with longer and more detailed prompts? For example adding more whole product specs and so on. It would be nice to generate a design system from generated UI you like instead of recreating that UI directly.

If the frontier models will take as much money to train as they do now, there is no way the wealthy are able to afford their training just for their own consumption. Financing of this whole thing rests on the models being available to companies and consumers who are willing to pay astronomical (compared to other software) sums for it.

MCP is dead? 2 months ago

Besides points already mentioned,

- remote mcps are server driven, meaning the producer can introduce new functionality without requiring all clients to update their skills and clis

- remote mcps are safe as they don't require literal code execution privileges on your system. Many times skills even bundle scripts with `npx`/`uvx` which is basically just `curl npm.com | bash` level of unsafe

Claude Opus 4.8 2 months ago

Wow that looks really impressive. Both the UI and the content looks good, the game is a bit buggy but still nice!

Googlebook 2 months ago

With AI dependence, unless you are a holdout, offline development isn't really a thing anymore. Perhaps to do some code reviews, but actually producing new code?

I have been thinking about this a lot lately. If you look at effects of geopolitical events and who profits and loses, rather than stated intentions. This global oil crisis, the Ukraine crisis, tariffs ect. It's the equivalent of the "the purpose of the system is what it does".

Oil crisis: Trumps friends profit on insider info, US oil industry (also his friends) profits, Russia profits because they are another big oil producer, USD dominance is harmed (also helps Russia), everyone else in the world eats the costs

Ukraine: Russia bleeds, Ukraine bleeds, arms industry profits, politicians in general get something to grandstand on in front of the voters. Personally I believe that this conflict has been artificially prolonged just to amplify the effects

Tariffs: US public eats the costs, Trump profits politically by appearing strong, Trumps friends profit on insider info

I don't really get how this stops captcha solving as a service, which is the actual way that scaled recaptcha solving is done? Those things are incredibly cheap and are staffed by humans anyway. Instead of selecting grainy busses, they will just scan the image with their phones.

My point is that since we have had so few nuclear incidents, but they have done massive damage, it is very possible that we don't actually know much worse it could get. We have only seen a few points from a distribution that could be much wider than we think. Compared to renewable failures for which we have a pretty good idea.

Believing we're in a climate crisis and also being anti-nuclear are mutually exclusive positions

I also used to believe that but now I'm not so sure. Nuclear carries massive and unpredictable risks on failure. We can fairly well predict what will happen on catastrophic wind turbine failure, but with nuclear it is much more difficult. And what is arguably worse is that nuclear catastrophic failures are very infrequent and so we have very hard time estimating and thinking about probabilities of them happening.

Personally I think that keeping existing reactors running is better than the alternatives, but I'm not so sure about building up new reactors compared to building more predictable green energy sources.

Open multimodel tools will start dominating as soon as frontier labs stop massively subsidising their models only inside their tools and align with api pricing. Personally I think that the inflection point is near considering the slew of recent drama with Claude Code.

Claude Code and Codex are solid, but the real reason people use these over alternatives is that they have dramatically lower overall cost compared to open alternatives.

It used to be worse, these days you can at least link between storybook and figma and have similar component naming and figma mostly uses css mental model. Before we had invision and sketch and designers and developers lived in their own worlds that were just completely disjoined.