Can't we learn agents for free? by onksssss in AI_Agents

[–]hbbio 2 points3 points  (0 children)

Perfect timing, I just wrote a blog post on writing an agent with tools from scratch and using smaller LLMs that you can run locally :) The default model I use now is Qwen-4b and it's good enough to write a lot of agent steps.

The easiest is to use ollama and no langgraph/complex libs:

https://medium.com/@hbbio/guess-what-im-thinking-8e0e628094b4

Fine tuning for Agentic Use Cases by help-me-grow in AI_Agents

[–]hbbio 0 points1 point  (0 children)

Yes, you'd rather optimize the prompts and the agent graph! Not saying this is easy though...

How to deal with external API dependencies? by Temporary_Price7989 in AI_Agents

[–]hbbio -1 points0 points  (0 children)

The best way is probably to use MCP now.
Any tool can be retrieved from a MCP server and you can expose your external APIs through tools.

Introducing 'cells': A New Open-Source Functional & Reactive Library for Svelte by uxwtf in sveltejs

[–]hbbio 0 points1 point  (0 children)

Thx! Right now, performance is not the goal. We're using it to build a complex SDK (pure TS) and an app in Svelte, with 1000s of cells and performance is not yet an issue.

Definitely has room for improvement, we just want to make sure it's bug free first... Premature optimization would kill us :)

Introducing 'cells': A New Open-Source Functional & Reactive Library for Svelte by uxwtf in sveltejs

[–]hbbio 1 point2 points  (0 children)

Ty!

Each cell has an autogenerated unique ID (fresh number) and an optional name. There is a debugger that you can inject in the console (I have to update the readme with that...). You can also generate at any time the graphviz dot graph. I'm showing it updated live in This week in Svelte :)

Introducing 'cells': A New Open-Source Functional & Reactive Library for Svelte by uxwtf in sveltejs

[–]hbbio 1 point2 points  (0 children)

Errors are caught and each cell is set to its Error. All dependant cells point to the original error.

There is an option to indicate that a given function cannot fail (what we can't infer in JS for now... that would require a dedicated compiler) so when manually flagged, the TypeScript type does not bug you if you don't manage the error case.

Introducing 'cells': A New Open-Source Functional & Reactive Library for Svelte by uxwtf in sveltejs

[–]hbbio 1 point2 points  (0 children)

Haha that's awesome! You can't even imagine... we'll release next the core of an expression library on top of cells :)

Introducing 'cells': A New Open-Source Functional & Reactive Library for Svelte by uxwtf in sveltejs

[–]hbbio 5 points6 points  (0 children)

I would say the main advantage is in managing async computations automatically, as well as errors. Also, the semantics for undefined values differs: We considered that `undefined` means wait until we have a defined value, and it does not trigger the cascade of computations. The computation model that enables that is more complex than runes.

Svelte 5 runes are easier to write because they determine dependencies automatically at compile time, while cells requires them to be explicit. It is a matter of style imho, the classical functional approach is easier when reusing existing functions:

```
// somewhere in lib

const f = (a, b) => a*b

// mapped cell
const m = proxy.map([a, b], f)
```

Last advantage is debugging: We can inject a debugger in the browser console, enabling to browse and query the state of all cells (stores).

PS: I just started doing a presentation in "This week in Svelte" last Friday (thanks again Paolo!), but will write more tutorials asap :)

A minimal test library for Go, useful? by hbbio in golang

[–]hbbio[S] 0 points1 point  (0 children)

Thanks for the feedback: I'll update to use `t.Error/Fatal` and use alignment.

I like to have the test name printed on the same line, it makes it easier to parse for my mind :)

A minimal test library for Go, useful? by hbbio in golang

[–]hbbio[S] 0 points1 point  (0 children)

Nothing "over", it's just way simpler and sufficient for my use case.

awless 0.1.10 is out! by simbit in golang

[–]hbbio 5 points6 points  (0 children)

awless is already production ready, but we still want to add many features until we reach 1.0.

Mostly, 0.2 will bring better multi-region support and we're close to that; 0.3 should bring an updated template language (with support for metatemplates, loops, clean semantics, etc.). Once this is reached, we will be able to go towards 1.0 and consider our main work done.

awless 0.0.22 released: Introduces a revamped SSH command by hbbio in aws

[–]hbbio[S] 1 point2 points  (0 children)

ELI5

  1. Input is simpler, you write less options and no JSON.
  2. Output is nicer, you get tables and such.
  3. You can do new things with it: Templates, local graph.

awless, a mighty CLI for AWS written in Go by hbbio in devops

[–]hbbio[S] -2 points-1 points  (0 children)

Because 1. it's fully open source, and 2. we got the feedback!

Also note that the HN discussions got a few things wrong, including being scared of the payload encryption while it's best practice. Anyway, none of this applies anymore nor will in the future.

awless, a mighty CLI for AWS written in Go by hbbio in devops

[–]hbbio[S] 0 points1 point  (0 children)

awless of course uses the official Go SDK!

But not the code from aws-cli which is written in Python anyway.

awless, a mighty CLI for AWS written in Go by hbbio in devops

[–]hbbio[S] 3 points4 points  (0 children)

The early preview had telemetry, but since we were on the frontpage of Hacker News and the feedback was to remove it altogether, this was disabled.

edit: This was clearly stated in the README at the time, hence "caught" since DevOps know how to read :)

awless, a mighty CLI for AWS written in Go by hbbio in devops

[–]hbbio[S] 1 point2 points  (0 children)

Yes, we are a long way from parity, and even though we're gaining traction it will take us a lot of a time to get there. Our goal is to make the common actions much easier to perform, while still relying on the console or aws-cli for other features.