Re: [racket-users] opinions on YAML as communication tool

2016-10-22 Thread Stefan Schmiedl
'John Clements' via Racket Users (21.10. 16:32): > > > On Oct 21, 2016, at 12:42 PM, Tony Garnock-Jones wrote: > > > > You know how Excel guesses whether things are dates or not and messes > > things up as a consequence? YAML does that too. YAML does not guess, the processor does. Just like "u

Re: [racket-users] opinions on YAML as communication tool

2016-10-21 Thread 'John Clements' via Racket Users
> On Oct 21, 2016, at 12:42 PM, Tony Garnock-Jones wrote: > > On 10/21/2016 01:21 AM, 'John Clements' via Racket Users wrote: >> I thought hard about scribble and JSON (and xml, yecch), but I think >> that YAML and sexps are the two viable candidates, and I’m guessing >> that if non-programmer

Re: [racket-users] opinions on YAML as communication tool

2016-10-21 Thread Tony Garnock-Jones
On 10/21/2016 01:21 AM, 'John Clements' via Racket Users wrote: > I thought hard about scribble and JSON (and xml, yecch), but I think > that YAML and sexps are the two viable candidates, and I’m guessing > that if non-programmers have to edit it, they’ll be less likely to > botch the YAML one.

Re: [racket-users] opinions on YAML as communication tool

2016-10-21 Thread Jay McCarthy
Since we're all just making up stuff, I mostly agree with Ben that if a spreadsheet is the right tool, then use that tool. There are a few spreadsheets that support version control internally, like Google Docs and Microsoft Office Version Tracking. In addition, there are the elite tools of graybea

Re: [racket-users] opinions on YAML as communication tool

2016-10-21 Thread Ben Greenman
I vote that you stick with Excel & change the version control protocol. Maybe: http://stackoverflow.com/a/17106035/5237018 On Fri, Oct 21, 2016 at 9:22 AM, Matthias Felleisen wrote: > > See Claire’s paper on cKanren. Scheduling is one of her examples (though > small scale). > > > > > On Oct 21,

Re: [racket-users] opinions on YAML as communication tool

2016-10-21 Thread Matthias Felleisen
See Claire’s paper on cKanren. Scheduling is one of her examples (though small scale). > On Oct 21, 2016, at 7:18 AM, Robby Findler > wrote: > > Wh? You're not going to design your own language and implement a > syntax colorer in DrRacket for it so they can tell immediately when > some

Re: [racket-users] opinions on YAML as communication tool

2016-10-21 Thread Robby Findler
Wh? You're not going to design your own language and implement a syntax colorer in DrRacket for it so they can tell immediately when something goes wrong? ;) Robby On Fri, Oct 21, 2016 at 12:21 AM, 'John Clements' via Racket Users wrote: > Yet another totally off-topic question for you ext

Re: [racket-users] opinions on YAML as communication tool

2016-10-21 Thread Stefan Schmiedl
'John Clements' via Racket Users (21.10. 01:21): > I thought hard about scribble and JSON (and xml, yecch), but I think > that YAML and sexps are the two viable candidates, and I’m guessing > that if non-programmers have to edit it, they’ll be less likely to > botch the YAML one. My timesheet and

[racket-users] opinions on YAML as communication tool

2016-10-20 Thread 'John Clements' via Racket Users
Yet another totally off-topic question for you extremely smart people. Well, it’s a language design question, so it’s not *too* off-topic. I’m temporarily serving as my department’s scheduler (don’t ask). Currently, the planning for the future schedule is done using an Excel spreadsheet. I try