HackerTrans
トップ新着トレンドコメント過去質問紹介求人

earcar

no profile record

投稿

Founding a company in Germany: €9600, 152 days and I still can't send an invoice

paolino.me
608 ポイント·投稿者 earcar·17 日前·756 コメント

RubyLLM 1.16: concurrent tool execution, Rails-style instrumentation, and more

github.com
2 ポイント·投稿者 earcar·先月·0 コメント

Rails has overtaken Next.js in a dataset of 3,658 profitable startups

twitter.com
3 ポイント·投稿者 earcar·2 か月前·1 コメント

Kamal Backup: Scheduled restic backups for Rails apps

kamal-backup.dev
1 ポイント·投稿者 earcar·2 か月前·0 コメント

Engineering Is Not Dead, Because Accountability Isn't

paolino.me
3 ポイント·投稿者 earcar·2 か月前·3 コメント

Production experience cannot be hallucinated

paolino.me
2 ポイント·投稿者 earcar·2 か月前·0 コメント

Kamal-Backup: Scheduled Rails Backups for Kamal Apps

paolino.me
2 ポイント·投稿者 earcar·2 か月前·0 コメント

Show HN: Kamal-backup – Rails backups with restore drills and audit evidence

kamal-backup.dev
1 ポイント·投稿者 earcar·2 か月前·0 コメント

Ruby Concurrency: What Happens

paolino.me
2 ポイント·投稿者 earcar·2 か月前·0 コメント

Jekyll can be as fast as Vitepress by using Turbo Frames

jekyll-vitepress.dev
1 ポイント·投稿者 earcar·3 か月前·0 コメント

NodeLLM: RubyLLM in JavaScript

github.com
3 ポイント·投稿者 earcar·3 か月前·0 コメント

Making the Rails Default Job Queue Fiber-Based

paolino.me
1 ポイント·投稿者 earcar·3 か月前·0 コメント

A new chapter for Ruby Central

rubycentral.org
3 ポイント·投稿者 earcar·3 か月前·1 コメント

Ruby AI News – April 16th 2026

rubyai.beehiiv.com
1 ポイント·投稿者 earcar·3 か月前·0 コメント

Buttercut: Edit Videos with Claude Code

github.com
2 ポイント·投稿者 earcar·3 か月前·0 コメント

Your Agent's Context Window Is Not a Junk Drawer

paolino.me
1 ポイント·投稿者 earcar·3 か月前·0 コメント

André Arko: Towards an Amicable Resolution with Ruby Central

andre.arko.net
2 ポイント·投稿者 earcar·3 か月前·0 コメント

Show HN: Hyprmoncfg – Terminal-based monitor config manager for Hyprland

paolino.me
11 ポイント·投稿者 earcar·3 か月前·4 コメント

Comb Shaped Slices: Why I'm not picking a vertical

paolino.me
2 ポイント·投稿者 earcar·4 か月前·0 コメント

Show HN: Jekyll VitePress – VitePress-Style Docs for Jekyll

jekyll-vitepress.dev
1 ポイント·投稿者 earcar·4 か月前·0 コメント

コメント

earcar
·16 日前·議論
Thanks for litigating every layer of a bug I fixed 27 minutes after your comment, more than a year ago.

> Also, the same PR was reverted a bit later, IIRC

No. Your #151 was merged. The regressions it introduced were patched the next day in #157/#159.

Cheers!
earcar
·16 日前·議論
We have an extensive model registry with cost and capability tracking:

https://rubyllm.com/available-models/
earcar
·16 日前·議論
Your PR #151 was opened May 4, 2025 and merged 2 days later.

The repeated `chat.to_llm` message bug was reported Apr 30 2025, and fixed May 6, 2025, about 27 minutes after your comment.

It only showed up when reusing the same Rails chat object for multiple turns in the same Ruby object lifetime, e.g. `chat.ask("first"); chat.ask("second")` inside one controller action or one background job.

The usual flow is one turn per request/job, where the record is reloaded each time. Also, it did not overwrite records; it duplicated messages in the in-memory request context.

Gemini tool calling shipped in 1.0, schema support landed in 1.4, and observability landed in 1.16.

As for "the most trivial of applications": check the docs. RubyLLM goes well beyond that, and several multi-million-dollar companies use it in production every day.
earcar
·16 日前·議論
I checked whether you or anyone from Wistia, your company, opened PRs.

I found one: #813, opened June 16, 2026. Last week.
earcar
·17 日前·議論
Thank you!

Since a few mentioned Responses API: the reason why it wasn't implemented in 1.x is because RubyLLM 1.x effectively assumes a 1:1 mapping between provider and protocol. That assumption no longer holds since OpenAI has 2 protocols with different capabilities, and to access all VertexAI models we need to support a bunch under that single provider.

Therefore, a major refactoring to split Protocols and from Providers was needed, as well as a way to route different models to different Protocols under the same Provider, transparently.

That's one of the many things that's gonna ship with RubyLLM 2.0.

If you're curious: https://github.com/crmne/ruby_llm/commit/d398354da493570b050... https://github.com/crmne/ruby_llm/commit/0875ce2dfeae9d28a3a...
earcar
·17 日前·議論
Interesting! What were you guys trying to achieve by running them in your own tool harness?
earcar
·17 日前·議論
Glad you like it.

Rails-style instrumentation landed in 1.16.0.

https://rubyllm.com/instrumentation/
earcar
·17 日前·議論
Not yet. I'll do a series of blog posts and tweets in the next weeks.
earcar
·17 日前·議論
Thank you!

I love how MINASWAN Hacker News is when talking about Ruby!
earcar
·17 日前·議論
Thank you!

Responses API is now implemented and it's coming in RubyLLM 2.0

https://github.com/crmne/ruby_llm/blob/main/lib/ruby_llm/pro...
earcar
·17 日前·議論
RubyLLM author here.

I'm not sure where you got that.

`chat.with_temperature(0.2)`

https://rubyllm.com/chat/#controlling-response-behavior

`chat.with_thinking(effort: :high, budget: 8000)`

https://rubyllm.com/thinking/#controlling-extended-thinking

Max tokens is the only one of your list that require provider specific params:

https://rubyllm.com/chat/#provider-specific-parameters

I'm one guy doing it for free. Happy to see your contribution!
earcar
·17 日前·議論
I have founded a UG and upgraded to a GmbH before.

It had got us "more credibility" with our clients, and 12,500EUR less in each other's bank accounts.

Thanks for your insults.
earcar
·17 日前·議論
Can't agree with you more.
earcar
·17 日前·議論
It should be possible to move within Europe, then when the liquidity event happens tax me from the countries where I've lived, proportionally to the time I've lived there.

If you want to move out of Europe, you get the exit tax as before.
earcar
·17 日前·議論
I'm not 100% sure, but I believe there was an issue with the "place of effective management" or perhaps the company address not being in your federal state.
earcar
·17 日前·議論
> there are specialized lawyers that maintain a pool of freshly founded GmbH's for you to buy

It doesn't sound easy nor cheap to buy a company and change the company name.

UG & Co. KG has a couple of advantages and while it did add some money and time to the table, it doesn't change the story.

Notaries in the US are the price of a dinner. Many people have waited up to 6 months to receive their VAT ID from Berlin.
earcar
·17 日前·議論
Well said!
earcar
·17 日前·議論
I have yet to find the mythical efficiency everyone was talking about.

Trains, Berlin Brandenburg Airport, this.

It's rules and adherence to rules, more than efficiency, that I've found in my experience.
earcar
·17 日前·議論
That sucks, my fellow Italian. I haven't looked into our country since I live abroad for a long time, but I'm also paying health insurance here which is not cheap at all, and haven't added it to the post since it's not necessarily a company spend.

Cordiali saluti!
earcar
·17 日前·議論
That is refreshing to hear. Unfortunately I can't get out because of exit tax, an unrealized capital gains tax for the privilege of leaving the country. That is way worse than what I mention in this post and will get its own post soon.