# Zu

A program and space for researching how to use [NuShell plugins][op-nu].

This could be done using [phoenix],
though I'm beginning to feel like that framework
is thoroughly overkill for the nimble nuance of Elixir.
Seems as though phoenix authors are trying to pull us back
to the days of Ruby-on-Rails,
when everyone was trying to clone Twitter's architecture.

With vibe-coding becoming far more popular in Elixir,
app architectures need to become simpler.
Fewer moving pieces means your agent can produce more functional code;
the architecture needs to change around the agent producing the code,
especially when product teams are going from dozens of coders to one.

To accomplish this aim, Phoenix is a hard no.
[nucleus] is aiming to [replace the complexity of phoenix][op-nucleus],
and this is an experiment in that process.

Specifically, this is the first green-field program
that I'm coding using [data-star].

[op-nu]: https://operand.online/brief/code/nu
[nucleus]: https://hex.pm/packages/nucleus
[op-nucleus]: https://operand.online/brief/code/nucleus
[data-star]: https://data-star.dev/

- - -

## Using data-star in Elixir

The two popular data-star packages in Elixir are
[dstar] and [star_view].

Both of them use Phoenix helpers,
specifically the [`~H` sigil]

[dstar]: https://hex.pm/packages/dstar
[star_view]: https://hex.pm/packages/star_view
[`~H` sigil]: https://phoenix-live-view.hexdocs.pm/Phoenix.Component.html#sigil_H/2