From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catonano Subject: Re: interesting thread Date: Wed, 24 May 2017 21:26:28 +0200 Message-ID: References: <878tlmqlf4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c0de2ccc0c86705504a1419" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46438) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDbvY-0004sg-Ca for guix-devel@gnu.org; Wed, 24 May 2017 15:26:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDbvW-0002cI-Qt for guix-devel@gnu.org; Wed, 24 May 2017 15:26:36 -0400 In-Reply-To: <878tlmqlf4.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jan Nieuwenhuizen Cc: guix-devel --94eb2c0de2ccc0c86705504a1419 Content-Type: text/plain; charset="UTF-8" 2017-05-24 18:17 GMT+02:00 Jan Nieuwenhuizen : > Catonano writes: > > > no comments ? > > I saw this message, had a quick look and a frown... > > > I was so enthsiast of aving discovered this > > Can you summarize what's to get enthousiastic about? > > > https://lists.w3.org/Archives/Public/public-lod/2017May/0005.html > > > > they published the metadata about the WHOLE collection of packaged > in npm !! > > Having looked into npm and worked on the guix npm importer, I found that > even the some of the most trivial packages cannot be built from source. > Cyclic dependencies in the build systems. > > So after having tried to get npm into GuixSD, I'm at the point of giving > up on npm and am planning to migrate away from it. > > I can hardly imagine...but does this report in any way hint that some > packages can be built from source and how to do that? > I only skimmed through it but I think it doesn' t I think the authors are not well versed in software engineering, they might be not completely aware of the issues involved in software reproducibility. This is one of the reasons why this post is interesting. These people might be interested in learning about Guix and its reasons And frankly, I believe that the "data oriented" approach could help Guix; so yes, I think that Guix has something to learn from their effort too I know the issues that plague the npmjs world. In my grand plan, we would have a complete graph of the npmjs packages and the dependencies among them. This could help in doing a sane bootstrap of nodejs in Guix. Sort of what Ricardo is doing with Java He' s doing that manually, discovering binary blobs in "sources" as he proceeds Because the nodejs graph is so large and dense, a more systematic approach would be, in my opinion, necessary, in order to achieve the same result. I have been thinking about giving up on the web entirely because of javascript I never liked the idea of apps in the browser, anyway. I still miss my favourite native email client, Eudora But the community working with nodejs, around the world, is enormous. Huge Think about the Mediawiki foundation, or Wordpress. Think about Ruby on Rails. Recently I even found an IDE for Postgresql, it looked like a native application, instead it has a frame with javascript infested content in it Renouncing to nodejs would be a huge blow to Guix. As huge as the nodejs community is Then, add Gnunet to the equation: if there was a set of native Gnome apps integrated with Gnunet, the Free Software movement could offer something valuable to many people working with php/nodejs off the shelve solutions today. It would be an important opportunity for the Free Software at large, not Guix only. I believe this is important Now: as you might remember, I made an effort to collect the jquery dependencies graph and store it in a graph db The Graph db I used was not mature enough, so that when a version advancement came, I discovered that there was no upgrade path for my data I thought to re-do that from scratch using Postgresql But I slacked off and I had some difficulties in wrapping my mind around the possibility to make such a scraper concurrent But that's another story Anyway, this is the reason why I am enthusiastic about this release: they published a COMPLETE nodejs dependencies graph as linked data So my scraping effort is not needed anymore ! Now it' s just a matter of querying those data to identify culprit packages, unbuildable or otherwise problematic I think it' s an advancement ! As for my personal projects, I could prefer usig Gnome over the web based stuff too. But what I was thinking is not only my personal toys. So, these is my reasoning. I hope I made myself clearer now --94eb2c0de2ccc0c86705504a1419 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


2017-05-24 18:17 GMT+02:00 Jan Nieuwenhuizen <janneke@gnu.org>:
Catonano writes:

> no comments ?

I saw this message, had a quick look and a frown...

> I was so enthsiast of aving discovered this

Can you summarize what's to get enthousiastic about?

>=C2=A0 =C2=A0 =C2=A0https://lis= ts.w3.org/Archives/Public/public-lod/2017May/0005.html
>
>=C2=A0 =C2=A0 =C2=A0they published the metadata about the WHOLE collect= ion of packaged in npm !!

Having looked into npm and worked on the guix npm importer, I found = that
even the some of the most trivial packages cannot be built from source.
Cyclic dependencies in the build systems.

So after having tried to get npm into GuixSD, I'm at the point of givin= g
up on npm and am planning to migrate away from it.

I can hardly imagine...but does this report in any way hint that some
packages can be built from source and how to do that?
=
I only skimmed through it but I think it doesn' t
I think the authors are not well versed in software engineering= , they might be not completely aware of the issues involved in software rep= roducibility.

This is one of the reasons why this post is= interesting. These people might be interested in learning about Guix and i= ts reasons

And frankly, I believe that the "data ori= ented" approach could help Guix; so yes, I think that Guix has somethi= ng to learn from their effort too

I know the issues that plagu= e the npmjs world.

In my grand plan= , we would have a complete graph of the npmjs packages and the dependencies= among them.

This could help in doi= ng a sane bootstrap of nodejs in Guix. Sort of what Ricardo is doing with J= ava

He' s doing that manually, = discovering binary blobs in "sources" as he proceeds

Because the nodejs graph is so large and dense,= a more systematic approach would be, in my opinion, necessary, in order to= achieve the same result.

I have be= en thinking about giving up on the web entirely because of javascript
I never liked the idea of apps in the br= owser, anyway. I still miss my favourite native email client, Eudora
But the community working with nodejs, ar= ound the world, is enormous. Huge

T= hink about the Mediawiki foundation, or Wordpress.

Think about Ruby on Rails.

Recently I even found an IDE for Postgresql, it looked like a nati= ve application, instead it has a frame with javascript infested content in = it

Renouncing to nodejs would be a = huge blow to Guix. As huge as the nodejs community is

Then, add Gnunet to the equation: if there was a set of = native Gnome apps integrated with Gnunet, the Free Software movement could = offer something valuable to many people working with php/nodejs off the she= lve solutions today.

It would be an= important opportunity for the Free Software at large, not Guix only.
I believe this is important

Now: as you might remember, I made an effort to= collect the jquery dependencies graph and store it in a graph db

The Graph db I used was not mature enough, s= o that when a version advancement came, I discovered that there was no upgr= ade path for my data

I thought to r= e-do that from scratch using Postgresql

But I slacked off and I had some difficulties in wrapping my mind arou= nd the possibility to make such a scraper concurrent

But that's another story

Anyway, this is the reason why I am enthusiastic about this rel= ease: they published a COMPLETE nodejs dependencies graph as linked data
So my scraping effort is not needed a= nymore !

Now it' s just a matte= r of querying those data to identify culprit packages, unbuildable or other= wise problematic

I think it' s = an advancement !

As for my personal= projects, I could prefer usig Gnome over the web based stuff too. But what= I was thinking is not only my personal toys.

So, these is my reasoning.
<= br>
I hope I made myself clearer now
--94eb2c0de2ccc0c86705504a1419--