From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:50c:: with SMTP id 12mr7840613itl.18.1543864337558; Mon, 03 Dec 2018 11:12:17 -0800 (PST) X-Received: by 2002:a9d:2c22:: with SMTP id f31mr268950otb.4.1543864337323; Mon, 03 Dec 2018 11:12:17 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!feeder4.usenet.farm!feed.usenet.farm!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!q69no638879itb.0!news-out.google.com!v141ni765ita.0!nntp.google.com!k10no637513itk.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 3 Dec 2018 11:12:16 -0800 (PST) In-Reply-To: <960eb922-6ea5-47d6-af48-289fff1f6fb5@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=208.114.128.47; posting-account=MRPdDAoAAADUJmZVjnYaoafXFMadSeY1 NNTP-Posting-Host: 208.114.128.47 References: <9524b3ee-476f-4af6-ab83-b15a6c2a417c@googlegroups.com> <6508fa19-5b93-471a-8b06-216907736b1b@googlegroups.com> <960eb922-6ea5-47d6-af48-289fff1f6fb5@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: GNATCOLL JSON Parsing From: Olivier Henley Injection-Date: Mon, 03 Dec 2018 19:12:17 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:54931 Date: 2018-12-03T11:12:16-08:00 List-Id: >> Interesting rant. Could you point us to some of the libraries you had ma= de >> available to others and that have great documentation ? You have a gi= thub >> account with no repository... Critics are easy. 1) Responsibilities comes with providing; it is a statement. If I did not '= published' much is exactly because I prefer to not share, than share half-b= aked stuff (missing meaningful useage contexts). There is also the fact tha= t I am doing Ada during the week-ends, when I can, and I do not find myself= fluent enough to tackle the kind of projects I wan to undertake. 2) Man, I would practice due diligence before biting. My https://github.com= /ohenley has 12 repos. i. The most complete Awesome Ada page ... by far is my last baby, WIP. ii. A simple native Mouse Capture in Ada. Toy project grabbing the coords o= f a PC mouse and outputting it to the terminal. Code in is very straightfor= ward, clean and naive... on purpose. Not using any 'mad' dependencies. iii. Aglw, a replacement for GLFW3 in Ada, with a demo, the git project Agl= w-demos. The demo is the doc/tutorial... sir. iv. Los33, a cookbook to build a crypto mining rig on Linux v. A readme template, to help people who wants to have a 'streamlined' read= me with most sections appropriate for a newcomer to understand the project *All my code repos are in Ada, to show a commitment. >> Writing documentation is really a difficult things. Some things are obvi= ous >> to anyone who has used Ada before. Should we keep repeating them in= =20 >> documentation ? For instance, one of the difficult things for new Ada us= ers >> are functions returning string. No but you could definitely point out a clear resource that does it (a url = staring by http://...), what about that? >> So you are not a contributor in the sense "please provide a patch", but = you >> are definitely a client in the sense of "please kindly provide addit= ional >> information on how to use such and such API". That's the price to = pay to=20 >> use open-source software. Look, if you want to put your head in the sand fine. Many language communit= ies are more structured than Ada and THIS is exactly why they flourish. The= new efforts by Adacore are perfect (the blog, LearnAda, Make with Ada, a m= odern look of their pages etc) But if you want to bring back Ada strong we will have to push harder. GoF P= atterns in Ada, games, more blogs, super robust JSON, bindings to Graph dat= abse (eg DGraph, Noe4j) etc >> That said, there certainly are libraries that could use some higher-leve= l >> documentation. Just ask their authors to do it, explaining your=20 >> difficulties. Now, I am fine, I surf without help most of the time. But when I got in Ada= I was pissed!=20 >> (hint: if you start by telling them they have a God complex, you might a= s >> well not bother sending a message). Seriously!? I really though I could approach people this way...=20 > Emmanuel I said SOME of the old guard, so if you feel concerned it is on you, sorry. But, all that said, I know I was a bit too harsh. I would really like to ha= ve Ada praised everywhere. That is why I am shaking the tree.