Hello!
Edouard Klein skribis:
> Thank you Liliana and Attila for the swift and actionable feedback :)
>
> Below is a revised proposition.
>
> Here is a minimal working example of an os declaration:
> --mwe.scm---
> (use-modules
> (beaver system)
> (beaver functional
Hello,
just FTR, i don't think that the guix codebase is too bad in this regard.
It's not bad for the slightly initiated, which does still take time, and I
think that front would perhaps benefit from some attention.
My main take away from this was that what I liked mostly about the BeaverLab
> > the downside of generating countless macros is that they won't show up
> > in backtraces, and they cannot be found when grep'ping the codebase,
> > and as such make the codebase much less approachable.
>
>
> Reading your words really helped me feel that I'm not alone. You more or
> less summa
Hi Attila,
On Wed, Nov 29 2023, Attila Lendvai wrote:
> i agree. in my experience, it's good practice in general to try to
> make a functional API as convenient as possible, and if that is still
> too verbose or cumbersome, only then add a thin layer of syntactic
> abstractions that expand to cod
> lines of code. I think hyper-focusing on syntax to make services
> "nicer" might be the wrong approach here: You could greatly reduce the
> complexity by making them procedures instead of syntax and still keep
> most of the configuration readable to a great extent.
i agree. in my experience, it
Am Sonntag, dem 26.11.2023 um 21:46 +0100 schrieb Edouard Klein:
>
> Liliana Marie Prikler writes:
> > > (instantiate nginx)
> > I do wish you spelled out service. Also, instantiate takes as much
> > characters to type as add-service.
> >
>
> Done, see below. I was worried about the parony
Liliana Marie Prikler writes:
>> (instantiate nginx)
> I do wish you spelled out service. Also, instantiate takes as much
> characters to type as add-service.
>
Done, see below. I was worried about the paronymy between add-service
and add-services which already exists. I defer to you and y
Hello guix,
I'll chime in because I've been playing around with this kind of thing
in my channel [1]
for a bit now and perhaps some of the ideas will be deemed useful.
(service+ OS SERVICE [CONF])
(service- OS SERVICE)
(modify-service OS SERVICE UPDATE)
I found that defining a functional A
Am Sonntag, dem 26.11.2023 um 17:49 +0100 schrieb Edouard Klein:
> Thank you Liliana and Attila for the swift and actionable feedback :)
>
> Below is a revised proposition.
>
> Here is a minimal working example of an os declaration:
> --mwe.scm---
> (use-modules
> (be
Thank you Liliana and Attila for the swift and actionable feedback :)
Below is a revised proposition.
Here is a minimal working example of an os declaration:
--mwe.scm---
(use-modules
(beaver system)
(beaver functional-services)
(gnu packages version-control)
(gnu
> (service+ OS SERVICE [CONF])
> (service- OS SERVICE)
> (modify-service OS SERVICE UPDATE)
what would the benefit of generating multiple macros for each service compared
to the above functional API (with 3-4 elements altogether)?
i could be missing something here, but it seems to be precious l
Am Freitag, dem 24.11.2023 um 22:43 +0100 schrieb Edouard Klein:
> Dear Guixers,
>
> Here is a quick status update on my proposition to expose composable
> functions to change operating-system declarations.
>
> Thank you all for the feedback you gave me :) It's very nice to not
> be talking in th
Dear Guixers,
Here is a quick status update on my proposition to expose composable
functions to change operating-system declarations.
Thank you all for the feedback you gave me :) It's very nice to not be
talking in the void.
After Liliana opined that these functions should not put too much burd
13 matches
Mail list logo
