Re: Guix beyond 1.0: let’s have a roadmap!

[John Soo]

Hi all,

I’m a newcomer of sorts but I would like a programming abstraction over 
profiles. It feels like some requests for better cache file state handling, 
declarative user services, and declarative user packages could be gained. Plus 
I think profiles are still maybe the most confusing thing to a newcomer and 
they are not explicit in the configuration.

- John

> On Jun 27, 2019, at 11:11 PM, Julien Lepiller <address@hidden> wrote:
> 
> Le 28 juin 2019 00:33:12 GMT+02:00, swedebugia <address@hidden> a écrit :
>> On 2019-06-27 21:02, Alex Griffin wrote:
>>> 
>>> ** TODO better Node.js packaging and tooling
>> 
>> This seem to have gotten stuck. But I heard something about a 
>> guile-semver and also we need to handle circular dependencies better in
>> 
>> guix to make it easier to discover and mitigate them.
>> 
>> Compared to the whole expat/JS community Guix is still a very small 
>> project. The bootstrap problems will probably take years to complete 
>> with the current pace/manpower/interest.
>> 
>> Maybe we should propose The GNU Project to create and seek funding for
>> a 
>> "fix JS (bootstrap)" campaign? Compilers will need to be written 
>> according to Julien (like rustc).
> 
> We're good with nust now :). A big issue is coffeescript and probably most of 
> the languages that compile to javascript.
> 
>> 
>>> *** TODO package important Icecat and Ungoogled-Chromium extensions.
>> This is a pain point because IceCat steers users away from Firefox
>> Add-ons and Ungoogled-Chromium completely disallows installing from
>> Chrome Web Store.
>> 
>> Actually currently our Chrome does not support add-ons at all. See bug 
>> #35709
> 
>