Re: [julia-users] Re: home page content

[cdm]

not sure how new this feature is, but over on tmpnb.org each session is 
served
with access to terminal ... Julia is installed.

long live the REPL,

cdm



On Wednesday, December 10, 2014 12:59:02 AM UTC-8, Jan Niklas Hasse wrote: 
>
>
> 
> Unfortunately http://forio.com/julia/repl/ doesn't work anymore, in my 
> opinion it was excellent and a link to it on the front page would be enough.
>

Re: [julia-users] Re: home page content

[cdm]

the wise individuals @tmpnb have made a

   "Julia - Intro to Gadfly.ipynb" 

file available with every session ...


sweet sauce, yo.

cdm


On Tuesday, December 9, 2014 11:14:41 PM UTC-8, Valentin Churavy wrote:
>
> 
> For the runnable part. Maybe we could use tmpnb/juliabox to host an 
> example notebook. We should probably use a docker image with an userimages 
> otherwise the attention span will be over before Gadfly is loaded.
>
>>

Re: [julia-users] Re: home page content

[Jim Garrison]

Instead of settling on a single "Why Julia", perhaps there should be a page 
on the new julialang.org that includes testimonials like this from 
different people using Julia.

On Wednesday, December 10, 2014 11:55:14 AM UTC-8, Isaiah wrote:
>
> I've tried to start something like it at
>> http://homepages.warwick.ac.uk/staff/C.Ortner/index.php?page=julia
>> This was aimed mostly at my own research group and some friends and 
>> colleagues.
>>
>
> Your "Why Julia" section is really fantastic.
>
> On Wed, Dec 10, 2014 at 2:47 PM, Christoph Ortner  > wrote:
>
>> I would really like to see a page along the lines of 
>> http://www.mathworks.com/examples/
>>
>> I've tried to start something like it at
>> http://homepages.warwick.ac.uk/staff/C.Ortner/index.php?page=julia
>> This was aimed mostly at my own research group and some friends and 
>> colleagues.
>>
>> Some ideas:
>>   * If I want a specific standard problem solved, then I can go look how 
>> a competent Julia programmer did it.
>>   * They should to be "attractive"
>>   * Could be useful for teaching
>>   * Could have examples of 4 different coding paradigms that some people 
>> are keen on
>>   * Maybe some core Julia group could review submissions rather than 
>> letting anybody post notebooks
>>   * What I am unsure about is whether notebooks, once posted, should 
>> become open source or not.
>>   * Finally - I am unsure whether it would be really necessary to make 
>> them interactive. But possibly an [export to Julia-box] button?
>>
>> I think such a page will also quickly show where the bottlenecks are in 
>> getting Julia to a wider community.
>>
>>Christoph
>>
>>
>> On Tuesday, 9 December 2014 22:23:26 UTC, Stefan Karpinski wrote:
>>>
>>> We're looking to redesign the JuliaLang.org home page and try to give it 
>>> a little more focus than it currently has. Which raises the question of 
>>> what to focus on. We could certainly have better code examples and maybe 
>>> highlight features of the language and its ecosystem better. What do people 
>>> think we should include?
>>>
>>
>

Re: [julia-users] Re: home page content

[Matt Bauman]

On Wednesday, December 10, 2014 7:30:42 PM UTC-5, Tony Kelman wrote:
>
> "This week in Julia" was a great contribution to the community but 
> evidently took more effort than Matt had time to keep up with.
>

Yes, indeed it was.  Conferences, end-of-semester, and my own version of 
Jeff's issue #8839  all 
meant that this slid off my desk.  But, there's good news!  Some of the 
folks in the /r/Julia  subreddit are 
picking up my slack!  Check out their first (stickied) post: This Fortnight 
In Julia: 12 Dec - 26 Dec 


http://www.reddit.com/r/Julia/comments/2p36av/this_fortnight_in_julia_12_dec_26_dec/

Re: [julia-users] Re: home page content

[cdm]

in support of "Why Julia", it seems that fact that Julia is attracting some 
of the best
and brightest minds spanning a diverse collection of fields ought to be 
displayed
prominently ...

as an example, perusing the COIN-OR Cup winners list returns several 
familiar
names  ( see http://www.coin-or.org/coinCup/coinCup.html ) ... speaking of 
which,
it looks as though the cup needs to come home next year, as it is off for a 
stay in
Python land  ( http://www.coin-or.org/coinCup/coinCup2014Winner.html ) and
when it has been won again, the string "Julia" should be featured in the 
team/
application name.


in addition to INFORMS, there are other "conferences" to target ...
the hit-list:

http://en.wikipedia.org/wiki/List_of_computer_science_conferences


stay the course, Julians ...

cdm



On Thursday, December 11, 2014 3:40:52 AM UTC-8, Christoph Ortner wrote:
>
> I'm glad people agree with my "Why Julia" paragraph.
>

Re: [julia-users] Re: home page content

[Christoph Ortner]

I'm glad people agree with my "Why Julia" paragraph.

Concerning Juliabloggers, I regularly look at this page, but don't find it 
nearly as useful as the "Matlab Examples" webpage; not so much because of 
lack of content, but mostly because of how it is organised.

Personally, I'd be very happy to maintain (through new versions of Julia) a 
small set of such examples notebooks, and I expect other will do the same. 
I would even help review submissions in my area of research (if this if 
felt to be useful). But unfortunately I don't have the capacity to create 
and maintain an entire website of this kind.

   Christoph


On Wednesday, 10 December 2014 20:05:09 UTC, Randy Zwitch wrote:
>
> Note that the framework is in place via juliabloggers.com. If someone 
> wanted to pick up this task, but didn't want to dedicate creating a blog, 
> I'm willing to create an author account to post directly.
>
> On Wednesday, December 10, 2014 1:46:03 PM UTC-5, John Myles White wrote:
>>
>> As always in Julia (and OSS in general), I think the problem is that 
>> there's no labor supply to do most "nice" things for the community. 
>> Everybody would love to see weekly updates. Not many people have both the 
>> time and desire to do the work. 
>>
>>  -- John 
>>
>> On Dec 10, 2014, at 10:41 AM, Tamas Papp  wrote: 
>>
>> > 
>> > On Wed, Dec 10 2014, Christian Peel  wrote: 
>> > 
>> >> provide would be helpful. Also, I'd be happy for something like a 
>> weekly 
>> >> update; or a weekly blog post to help those who don't peruse this 
>> group in 
>> >> depth each day. 
>> > 
>> > there was 
>> > 
>> > http://thisweekinjulia.github.io/ 
>> > 
>> > but it has not been updated since late October. 
>> > 
>> > best, 
>> > 
>> > Tamas 
>>
>>

Re: [julia-users] Re: home page content

[Tony Kelman]

-1 on trying to put plans, schedule, roadmap on the website. "This week in 
Julia" was a great contribution to the community but evidently took more 
effort than Matt had time to keep up with.

New features get developed as the PR's for them get worked on and finished. 
You can subscribe to just the subset of issues/PR's for things you (along 
with everyone else) are eagerly awaiting. Better yet, help with testing and 
code review if you can.

We have been doing a good job of monthly backport bugfix releases, we 
should be able to continue doing that. But 0.4 is still unstable and has 
several big-ticket items still open and being worked on (check the 
milestones on github). It's too early to try to make time estimates, if 
people are impatient and want a release sooner it's not going to be 
possible without punting on a number of targeted features and pushing them 
back to 0.5 or later.


On Wednesday, December 10, 2014 1:58:52 PM UTC-8, Randy Zwitch wrote:
>
> I think it would please everyone if you moved daily televised scrums.
>
>
> On Wednesday, December 10, 2014 4:53:50 PM UTC-5, John Myles White wrote:
>>
>> Stefan, I shared your moment of terror about the idea of posting plans 
>> (essentially all of which will be invalidated) to the home page.
>>
>> Although it's huge volume of e-mail, I do feel like people who want to 
>> keep up with new developments in Julia should try to subscribe to the issue 
>> tracker and watch decisions get made in real time. It's a large increase in 
>> workload to ask people to both do work on Julia and write up regular 
>> reports about the work.
>>
>>  -- John
>>
>> On Dec 10, 2014, at 1:48 PM, Stefan Karpinski  
>> wrote:
>>
>> I have to say the concept of putting plans up on the home page fills me 
>> with dread. That means I have update the home page while I'm planning 
>> things and as that plan changes and then do the work and then document it. 
>> It's hard enough to actually do the work.
>>
>> On Wed, Dec 10, 2014 at 4:44 PM, David Anthoff  
>> wrote:
>>
>>> +1 on that! Even vague plans that are subject to change would be great 
>>> to have.
>>>
>>>  
>>>
>>> *From:* julia...@googlegroups.com [mailto:julia...@googlegroups.com] *On 
>>> Behalf Of *Christian Peel
>>> *Sent:* Wednesday, December 10, 2014 10:15 AM
>>> *To:* julia...@googlegroups.com
>>> *Subject:* Re: [julia-users] Re: home page content
>>>
>>>  
>>>
>>> One thing that I would very much appreciate is some kind of development 
>>> schedule.  For example
>>>   - Some kind of general roadmap
>>>   - a plan for when 0.4 and future releases will come
>>>   - Any plans to switch to a regular schedule?  (yearly, six
>>> months, ...) 
>>>   - What features remain before a 1.0 release?
>>>   - When will following arrive?
>>> > faster compilation
>>> > pre-compiled modules
>>> > Interactive debugging; line numbers for all errors
>>> > Automatic reload on file modification.
>>> > Solving P=NP
>>>
>>> I know that it's tough to make such a schedule, but anything that you 
>>> can provide would be helpful. Also, I'd be happy for something like a 
>>> weekly update; or a weekly blog post to help those who don't peruse this 
>>> group in depth each day.
>>>
>>> Thanks!
>>>
>>> Chris
>>>
>>> On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:
>>>
>>> From the discussion, it looks like that homepages for programming 
>>> languages (and realed projects) serve two purposes: 
>>>
>>> A. provide resources for the existing users (links to mailing lists, 
>>> package directories, documentation, etc) 
>>>
>>> B. provide information for potential new users (showcasing features of 
>>> the language, links to tutorials). 
>>>
>>> Given that space on the very front page is constrained (in the soft 
>>> sense: no one wants pages that go on and on any more), I think that 
>>> deciding on a balance between A and B would be a good way to focus the 
>>> discussion. 
>>>
>>> Once we have decided that, we can shamelessly copy good practices. 
>>>
>>> For example, 
>>>
>>> 1. the R website emphasizes content for existing users (in a non-flashy 
>>> way that I am OK with), with very little material for new users, 
>>>
>>> 2. about 1/3

Re: [julia-users] Re: home page content

[Randy Zwitch]

I think it would please everyone if you moved daily televised scrums.


On Wednesday, December 10, 2014 4:53:50 PM UTC-5, John Myles White wrote:
>
> Stefan, I shared your moment of terror about the idea of posting plans 
> (essentially all of which will be invalidated) to the home page.
>
> Although it's huge volume of e-mail, I do feel like people who want to 
> keep up with new developments in Julia should try to subscribe to the issue 
> tracker and watch decisions get made in real time. It's a large increase in 
> workload to ask people to both do work on Julia and write up regular 
> reports about the work.
>
>  -- John
>
> On Dec 10, 2014, at 1:48 PM, Stefan Karpinski  > wrote:
>
> I have to say the concept of putting plans up on the home page fills me 
> with dread. That means I have update the home page while I'm planning 
> things and as that plan changes and then do the work and then document it. 
> It's hard enough to actually do the work.
>
> On Wed, Dec 10, 2014 at 4:44 PM, David Anthoff  > wrote:
>
>> +1 on that! Even vague plans that are subject to change would be great to 
>> have.
>>
>>  
>>
>> *From:* julia...@googlegroups.com  [mailto:
>> julia...@googlegroups.com ] *On Behalf Of *Christian Peel
>> *Sent:* Wednesday, December 10, 2014 10:15 AM
>> *To:* julia...@googlegroups.com 
>> *Subject:* Re: [julia-users] Re: home page content
>>
>>  
>>
>> One thing that I would very much appreciate is some kind of development 
>> schedule.  For example
>>   - Some kind of general roadmap
>>   - a plan for when 0.4 and future releases will come
>>   - Any plans to switch to a regular schedule?  (yearly, six
>> months, ...) 
>>   - What features remain before a 1.0 release?
>>   - When will following arrive?
>> > faster compilation
>> > pre-compiled modules
>> > Interactive debugging; line numbers for all errors
>> > Automatic reload on file modification.
>> > Solving P=NP
>>
>> I know that it's tough to make such a schedule, but anything that you can 
>> provide would be helpful. Also, I'd be happy for something like a weekly 
>> update; or a weekly blog post to help those who don't peruse this group in 
>> depth each day.
>>
>> Thanks!
>>
>> Chris
>>
>> On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:
>>
>> From the discussion, it looks like that homepages for programming 
>> languages (and realed projects) serve two purposes: 
>>
>> A. provide resources for the existing users (links to mailing lists, 
>> package directories, documentation, etc) 
>>
>> B. provide information for potential new users (showcasing features of 
>> the language, links to tutorials). 
>>
>> Given that space on the very front page is constrained (in the soft 
>> sense: no one wants pages that go on and on any more), I think that 
>> deciding on a balance between A and B would be a good way to focus the 
>> discussion. 
>>
>> Once we have decided that, we can shamelessly copy good practices. 
>>
>> For example, 
>>
>> 1. the R website emphasizes content for existing users (in a non-flashy 
>> way that I am OK with), with very little material for new users, 
>>
>> 2. about 1/3 of the middle bar on 
>> https://www.haskell.org/haskellwiki/Haskell is for new users 
>> (explanations/tutorials/etc), the 1/3 is for existing users (specs, 
>> libraries), and the final 1/3 is for both (forums, wiki, etc), 
>>
>> 3. http://new-www.haskell.org/ is mostly caters to potential new users 
>> ("see how great this language is"), 
>>
>> 4. the content of clojure.org is similarly for potential new users, 
>> while the sidebar has links for existing users. 
>>
>> Best, 
>>
>> Tamas 
>>
>> On Wed, Dec 10 2014, Hans W Borchers  wrote: 
>>
>> > Look at the R home page. R is one of the most popular languages, and 
>> esp. so 
>> > for statistical and computational applications. A programming language 
>> does 
>> > not need bloated home pages. 
>> > 
>> > I like the old Haskell home page much more than the new one. The new 
>> one 
>> > has 
>> > large, uninformative background pictures and not much information in a 
>> > small 
>> > and readable view. The HaskellWiki front page was much better in that. 
>> It 
>> > may 
>> > not even be decided which version will win. 
>> > 
>> > [Clojure])http://clojure.org/) has a nice, simple and informative home 
>> > page, 
>> > while [Scala](http://www.scala-lang.org/) has overdone it like the new 
>> > Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) - 
>> > formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages. 
>> > 
>> > In the end I feel the condensed form of the Python home page will 
>> attract 
>> > more interest, for example with 'latest news' and 'upcoming events' on 
>> the 
>> > first page.This gives the impression of a lively and engaged community. 
>> > 
>> > 
>> > On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote: 
>> >> 
>> >> I like the Haskell one better than the Rust one. 
>> >> 
>> >> --Tim 
>> >> 
>> >> 
>>
>>
>
>

Re: [julia-users] Re: home page content

[John Myles White]

Stefan, I shared your moment of terror about the idea of posting plans 
(essentially all of which will be invalidated) to the home page.

Although it's huge volume of e-mail, I do feel like people who want to keep up 
with new developments in Julia should try to subscribe to the issue tracker and 
watch decisions get made in real time. It's a large increase in workload to ask 
people to both do work on Julia and write up regular reports about the work.

 -- John

On Dec 10, 2014, at 1:48 PM, Stefan Karpinski  wrote:

> I have to say the concept of putting plans up on the home page fills me with 
> dread. That means I have update the home page while I'm planning things and 
> as that plan changes and then do the work and then document it. It's hard 
> enough to actually do the work.
> 
> On Wed, Dec 10, 2014 at 4:44 PM, David Anthoff  wrote:
> +1 on that! Even vague plans that are subject to change would be great to 
> have.
> 
>  
> 
> From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
> Behalf Of Christian Peel
> Sent: Wednesday, December 10, 2014 10:15 AM
> To: julia-users@googlegroups.com
> Subject: Re: [julia-users] Re: home page content
> 
>  
> 
> One thing that I would very much appreciate is some kind of development 
> schedule.  For example
>   - Some kind of general roadmap
>   - a plan for when 0.4 and future releases will come
>   - Any plans to switch to a regular schedule?  (yearly, six
> months, ...) 
>   - What features remain before a 1.0 release?
>   - When will following arrive?
> > faster compilation
> > pre-compiled modules
> > Interactive debugging; line numbers for all errors
> > Automatic reload on file modification.
> > Solving P=NP
> 
> I know that it's tough to make such a schedule, but anything that you can 
> provide would be helpful. Also, I'd be happy for something like a weekly 
> update; or a weekly blog post to help those who don't peruse this group in 
> depth each day.
> 
> Thanks!
> 
> Chris
> 
> On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:
> 
> From the discussion, it looks like that homepages for programming 
> languages (and realed projects) serve two purposes: 
> 
> A. provide resources for the existing users (links to mailing lists, 
> package directories, documentation, etc) 
> 
> B. provide information for potential new users (showcasing features of 
> the language, links to tutorials). 
> 
> Given that space on the very front page is constrained (in the soft 
> sense: no one wants pages that go on and on any more), I think that 
> deciding on a balance between A and B would be a good way to focus the 
> discussion. 
> 
> Once we have decided that, we can shamelessly copy good practices. 
> 
> For example, 
> 
> 1. the R website emphasizes content for existing users (in a non-flashy 
> way that I am OK with), with very little material for new users, 
> 
> 2. about 1/3 of the middle bar on 
> https://www.haskell.org/haskellwiki/Haskell is for new users 
> (explanations/tutorials/etc), the 1/3 is for existing users (specs, 
> libraries), and the final 1/3 is for both (forums, wiki, etc), 
> 
> 3. http://new-www.haskell.org/ is mostly caters to potential new users 
> ("see how great this language is"), 
> 
> 4. the content of clojure.org is similarly for potential new users, 
> while the sidebar has links for existing users. 
> 
> Best, 
> 
> Tamas 
> 
> On Wed, Dec 10 2014, Hans W Borchers  wrote: 
> 
> > Look at the R home page. R is one of the most popular languages, and esp. 
> > so 
> > for statistical and computational applications. A programming language does 
> > not need bloated home pages. 
> > 
> > I like the old Haskell home page much more than the new one. The new one 
> > has 
> > large, uninformative background pictures and not much information in a 
> > small 
> > and readable view. The HaskellWiki front page was much better in that. It 
> > may 
> > not even be decided which version will win. 
> > 
> > [Clojure])http://clojure.org/) has a nice, simple and informative home 
> > page, 
> > while [Scala](http://www.scala-lang.org/) has overdone it like the new 
> > Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) - 
> > formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages. 
> > 
> > In the end I feel the condensed form of the Python home page will attract 
> > more interest, for example with 'latest news' and 'upcoming events' on the 
> > first page.This gives the impression of a lively and engaged community. 
> > 
> > 
> > On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote: 
> >> 
> >> I like the Haskell one better than the Rust one. 
> >> 
> >> --Tim 
> >> 
> >>
> 
> 

Re: [julia-users] Re: home page content

[Stefan Karpinski]

I have to say the concept of putting plans up on the home page fills me
with dread. That means I have update the home page while I'm planning
things and as that plan changes and then do the work and then document it.
It's hard enough to actually do the work.

On Wed, Dec 10, 2014 at 4:44 PM, David Anthoff  wrote:

> +1 on that! Even vague plans that are subject to change would be great to
> have.
>
>
>
> *From:* julia-users@googlegroups.com [mailto:julia-users@googlegroups.com]
> *On Behalf Of *Christian Peel
> *Sent:* Wednesday, December 10, 2014 10:15 AM
> *To:* julia-users@googlegroups.com
> *Subject:* Re: [julia-users] Re: home page content
>
>
>
> One thing that I would very much appreciate is some kind of development
> schedule.  For example
>   - Some kind of general roadmap
>   - a plan for when 0.4 and future releases will come
>   - Any plans to switch to a regular schedule?  (yearly, six
> months, ...)
>   - What features remain before a 1.0 release?
>   - When will following arrive?
> > faster compilation
> > pre-compiled modules
> > Interactive debugging; line numbers for all errors
> > Automatic reload on file modification.
> > Solving P=NP
>
> I know that it's tough to make such a schedule, but anything that you can
> provide would be helpful. Also, I'd be happy for something like a weekly
> update; or a weekly blog post to help those who don't peruse this group in
> depth each day.
>
> Thanks!
>
> Chris
>
> On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:
>
> From the discussion, it looks like that homepages for programming
> languages (and realed projects) serve two purposes:
>
> A. provide resources for the existing users (links to mailing lists,
> package directories, documentation, etc)
>
> B. provide information for potential new users (showcasing features of
> the language, links to tutorials).
>
> Given that space on the very front page is constrained (in the soft
> sense: no one wants pages that go on and on any more), I think that
> deciding on a balance between A and B would be a good way to focus the
> discussion.
>
> Once we have decided that, we can shamelessly copy good practices.
>
> For example,
>
> 1. the R website emphasizes content for existing users (in a non-flashy
> way that I am OK with), with very little material for new users,
>
> 2. about 1/3 of the middle bar on
> https://www.haskell.org/haskellwiki/Haskell is for new users
> (explanations/tutorials/etc), the 1/3 is for existing users (specs,
> libraries), and the final 1/3 is for both (forums, wiki, etc),
>
> 3. http://new-www.haskell.org/ is mostly caters to potential new users
> ("see how great this language is"),
>
> 4. the content of clojure.org is similarly for potential new users,
> while the sidebar has links for existing users.
>
> Best,
>
> Tamas
>
> On Wed, Dec 10 2014, Hans W Borchers  wrote:
>
> > Look at the R home page. R is one of the most popular languages, and
> esp. so
> > for statistical and computational applications. A programming language
> does
> > not need bloated home pages.
> >
> > I like the old Haskell home page much more than the new one. The new one
> > has
> > large, uninformative background pictures and not much information in a
> > small
> > and readable view. The HaskellWiki front page was much better in that.
> It
> > may
> > not even be decided which version will win.
> >
> > [Clojure])http://clojure.org/) has a nice, simple and informative home
> > page,
> > while [Scala](http://www.scala-lang.org/) has overdone it like the new
> > Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) -
> > formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages.
> >
> > In the end I feel the condensed form of the Python home page will
> attract
> > more interest, for example with 'latest news' and 'upcoming events' on
> the
> > first page.This gives the impression of a lively and engaged community.
> >
> >
> > On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote:
> >>
> >> I like the Haskell one better than the Rust one.
> >>
> >> --Tim
> >>
> >>
>
>

RE: [julia-users] Re: home page content

[David Anthoff]

+1 on that! Even vague plans that are subject to change would be great to have.

 

From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
Behalf Of Christian Peel
Sent: Wednesday, December 10, 2014 10:15 AM
To: julia-users@googlegroups.com
Subject: Re: [julia-users] Re: home page content

 

One thing that I would very much appreciate is some kind of development 
schedule.  For example
  - Some kind of general roadmap
  - a plan for when 0.4 and future releases will come
  - Any plans to switch to a regular schedule?  (yearly, six
months, ...) 
  - What features remain before a 1.0 release?
  - When will following arrive?
> faster compilation
> pre-compiled modules
> Interactive debugging; line numbers for all errors
> Automatic reload on file modification.
> Solving P=NP

I know that it's tough to make such a schedule, but anything that you can 
provide would be helpful. Also, I'd be happy for something like a weekly 
update; or a weekly blog post to help those who don't peruse this group in 
depth each day.

Thanks!

Chris

On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:

>From the discussion, it looks like that homepages for programming 
languages (and realed projects) serve two purposes: 

A. provide resources for the existing users (links to mailing lists, 
package directories, documentation, etc) 

B. provide information for potential new users (showcasing features of 
the language, links to tutorials). 

Given that space on the very front page is constrained (in the soft 
sense: no one wants pages that go on and on any more), I think that 
deciding on a balance between A and B would be a good way to focus the 
discussion. 

Once we have decided that, we can shamelessly copy good practices. 

For example, 

1. the R website emphasizes content for existing users (in a non-flashy 
way that I am OK with), with very little material for new users, 

2. about 1/3 of the middle bar on 
https://www.haskell.org/haskellwiki/Haskell is for new users 
(explanations/tutorials/etc), the 1/3 is for existing users (specs, 
libraries), and the final 1/3 is for both (forums, wiki, etc), 

3. http://new-www.haskell.org/ is mostly caters to potential new users 
("see how great this language is"), 

4. the content of clojure.org <http://clojure.org>  is similarly for potential 
new users, 
while the sidebar has links for existing users. 

Best, 

Tamas 

On Wed, Dec 10 2014, Hans W Borchers  > wrote: 

> Look at the R home page. R is one of the most popular languages, and esp. so 
> for statistical and computational applications. A programming language does 
> not need bloated home pages. 
> 
> I like the old Haskell home page much more than the new one. The new one 
> has 
> large, uninformative background pictures and not much information in a 
> small 
> and readable view. The HaskellWiki front page was much better in that. It 
> may 
> not even be decided which version will win. 
> 
> [Clojure])http://clojure.org/) has a nice, simple and informative home 
> page, 
> while [Scala](http://www.scala-lang.org/) has overdone it like the new 
> Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) - 
> formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages. 
> 
> In the end I feel the condensed form of the Python home page will attract 
> more interest, for example with 'latest news' and 'upcoming events' on the 
> first page.This gives the impression of a lively and engaged community. 
> 
> 
> On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote: 
>> 
>> I like the Haskell one better than the Rust one. 
>> 
>> --Tim 
>> 
>> 

Re: [julia-users] Re: home page content

[Stefan Karpinski]

Yeah, that's really a good "why Julia".

On Wed, Dec 10, 2014 at 2:55 PM, Isaiah Norton 
wrote:

> I've tried to start something like it at
>> http://homepages.warwick.ac.uk/staff/C.Ortner/index.php?page=julia
>> This was aimed mostly at my own research group and some friends and
>> colleagues.
>>
>
> Your "Why Julia" section is really fantastic.
>
> On Wed, Dec 10, 2014 at 2:47 PM, Christoph Ortner <
> christophortn...@gmail.com> wrote:
>
>> I would really like to see a page along the lines of
>> http://www.mathworks.com/examples/
>>
>> I've tried to start something like it at
>> http://homepages.warwick.ac.uk/staff/C.Ortner/index.php?page=julia
>> This was aimed mostly at my own research group and some friends and
>> colleagues.
>>
>> Some ideas:
>>   * If I want a specific standard problem solved, then I can go look how
>> a competent Julia programmer did it.
>>   * They should to be "attractive"
>>   * Could be useful for teaching
>>   * Could have examples of 4 different coding paradigms that some people
>> are keen on
>>   * Maybe some core Julia group could review submissions rather than
>> letting anybody post notebooks
>>   * What I am unsure about is whether notebooks, once posted, should
>> become open source or not.
>>   * Finally - I am unsure whether it would be really necessary to make
>> them interactive. But possibly an [export to Julia-box] button?
>>
>> I think such a page will also quickly show where the bottlenecks are in
>> getting Julia to a wider community.
>>
>>Christoph
>>
>>
>> On Tuesday, 9 December 2014 22:23:26 UTC, Stefan Karpinski wrote:
>>>
>>> We're looking to redesign the JuliaLang.org home page and try to give it
>>> a little more focus than it currently has. Which raises the question of
>>> what to focus on. We could certainly have better code examples and maybe
>>> highlight features of the language and its ecosystem better. What do people
>>> think we should include?
>>>
>>
>

Re: [julia-users] Re: home page content

[Randy Zwitch]

Note that the framework is in place via juliabloggers.com. If someone 
wanted to pick up this task, but didn't want to dedicate creating a blog, 
I'm willing to create an author account to post directly.

On Wednesday, December 10, 2014 1:46:03 PM UTC-5, John Myles White wrote:
>
> As always in Julia (and OSS in general), I think the problem is that 
> there's no labor supply to do most "nice" things for the community. 
> Everybody would love to see weekly updates. Not many people have both the 
> time and desire to do the work. 
>
>  -- John 
>
> On Dec 10, 2014, at 10:41 AM, Tamas Papp > 
> wrote: 
>
> > 
> > On Wed, Dec 10 2014, Christian Peel > 
> wrote: 
> > 
> >> provide would be helpful. Also, I'd be happy for something like a 
> weekly 
> >> update; or a weekly blog post to help those who don't peruse this group 
> in 
> >> depth each day. 
> > 
> > there was 
> > 
> > http://thisweekinjulia.github.io/ 
> > 
> > but it has not been updated since late October. 
> > 
> > best, 
> > 
> > Tamas 
>
>

Re: [julia-users] Re: home page content

[Isaiah Norton]

>
> I've tried to start something like it at
> http://homepages.warwick.ac.uk/staff/C.Ortner/index.php?page=julia
> This was aimed mostly at my own research group and some friends and
> colleagues.
>

Your "Why Julia" section is really fantastic.

On Wed, Dec 10, 2014 at 2:47 PM, Christoph Ortner <
christophortn...@gmail.com> wrote:

> I would really like to see a page along the lines of
> http://www.mathworks.com/examples/
>
> I've tried to start something like it at
> http://homepages.warwick.ac.uk/staff/C.Ortner/index.php?page=julia
> This was aimed mostly at my own research group and some friends and
> colleagues.
>
> Some ideas:
>   * If I want a specific standard problem solved, then I can go look how a
> competent Julia programmer did it.
>   * They should to be "attractive"
>   * Could be useful for teaching
>   * Could have examples of 4 different coding paradigms that some people
> are keen on
>   * Maybe some core Julia group could review submissions rather than
> letting anybody post notebooks
>   * What I am unsure about is whether notebooks, once posted, should
> become open source or not.
>   * Finally - I am unsure whether it would be really necessary to make
> them interactive. But possibly an [export to Julia-box] button?
>
> I think such a page will also quickly show where the bottlenecks are in
> getting Julia to a wider community.
>
>Christoph
>
>
> On Tuesday, 9 December 2014 22:23:26 UTC, Stefan Karpinski wrote:
>>
>> We're looking to redesign the JuliaLang.org home page and try to give it
>> a little more focus than it currently has. Which raises the question of
>> what to focus on. We could certainly have better code examples and maybe
>> highlight features of the language and its ecosystem better. What do people
>> think we should include?
>>
>

Re: [julia-users] Re: home page content

[Tracy Wadleigh]

It might be nice to have a few examples of workflows that people who use
Julia in real life have set up for themselves.

On Wed, Dec 10, 2014 at 2:03 PM, Christian Peel  wrote:

> OK, thanks for the replies; John's reply below makes the situation clear.
>
> Chris
>
> On Wednesday, December 10, 2014 10:46:03 AM UTC-8, John Myles White wrote:
>>
>> As always in Julia (and OSS in general), I think the problem is that
>> there's no labor supply to do most "nice" things for the community.
>> Everybody would love to see weekly updates. Not many people have both the
>> time and desire to do the work.
>>
>>  -- John
>>
>> On Dec 10, 2014, at 10:41 AM, Tamas Papp  wrote:
>>
>> >
>> > On Wed, Dec 10 2014, Christian Peel  wrote:
>> >
>> >> provide would be helpful. Also, I'd be happy for something like a
>> weekly
>> >> update; or a weekly blog post to help those who don't peruse this
>> group in
>> >> depth each day.
>> >
>> > there was
>> >
>> > http://thisweekinjulia.github.io/
>> >
>> > but it has not been updated since late October.
>> >
>> > best,
>> >
>> > Tamas
>>
>>

Re: [julia-users] Re: home page content

[Christian Peel]

OK, thanks for the replies; John's reply below makes the situation clear.

Chris

On Wednesday, December 10, 2014 10:46:03 AM UTC-8, John Myles White wrote:
>
> As always in Julia (and OSS in general), I think the problem is that 
> there's no labor supply to do most "nice" things for the community. 
> Everybody would love to see weekly updates. Not many people have both the 
> time and desire to do the work. 
>
>  -- John 
>
> On Dec 10, 2014, at 10:41 AM, Tamas Papp > 
> wrote: 
>
> > 
> > On Wed, Dec 10 2014, Christian Peel > 
> wrote: 
> > 
> >> provide would be helpful. Also, I'd be happy for something like a 
> weekly 
> >> update; or a weekly blog post to help those who don't peruse this group 
> in 
> >> depth each day. 
> > 
> > there was 
> > 
> > http://thisweekinjulia.github.io/ 
> > 
> > but it has not been updated since late October. 
> > 
> > best, 
> > 
> > Tamas 
>
>

Re: [julia-users] Re: home page content

[John Myles White]

As always in Julia (and OSS in general), I think the problem is that there's no 
labor supply to do most "nice" things for the community. Everybody would love 
to see weekly updates. Not many people have both the time and desire to do the 
work.

 -- John

On Dec 10, 2014, at 10:41 AM, Tamas Papp  wrote:

> 
> On Wed, Dec 10 2014, Christian Peel  wrote:
> 
>> provide would be helpful. Also, I'd be happy for something like a weekly
>> update; or a weekly blog post to help those who don't peruse this group in
>> depth each day.
> 
> there was
> 
> http://thisweekinjulia.github.io/
> 
> but it has not been updated since late October.
> 
> best,
> 
> Tamas

Re: [julia-users] Re: home page content

[Tamas Papp]

On Wed, Dec 10 2014, Christian Peel  wrote:

> provide would be helpful. Also, I'd be happy for something like a weekly
> update; or a weekly blog post to help those who don't peruse this group in
> depth each day.

there was

http://thisweekinjulia.github.io/

but it has not been updated since late October.

best,

Tamas

Re: [julia-users] Re: home page content

[Stefan Karpinski]

We can add a bullet point about Julia not eating your laundry. My point of
view is that Julia's pre-1.0 status does not mean that it can do whatever
it wants and we have no responsibility. Rather it sends the much milder
signal that between now and 1.0 we may change the language and standard
library in ways that will require you to change your code. Bugs that cause
destructive behavior are no less serious now than later.

On Wed, Dec 10, 2014 at 1:25 PM, Valentin Churavy 
wrote:

> I like the point: Solving P=NP reminds me of rust's
>
> * In theory. Rust is a work-in-progress and may do anything it likes up to
>> and including eating your laundry.
>
>
> On Wednesday, 10 December 2014 19:15:05 UTC+1, Christian Peel wrote:
>>
>> One thing that I would very much appreciate is some kind of development
>> schedule.  For example
>>   - Some kind of general roadmap
>>   - a plan for when 0.4 and future releases will come
>>   - Any plans to switch to a regular schedule?  (yearly, six
>> months, ...)
>>   - What features remain before a 1.0 release?
>>   - When will following arrive?
>> > faster compilation
>> > pre-compiled modules
>> > Interactive debugging; line numbers for all errors
>> > Automatic reload on file modification.
>> > Solving P=NP
>>
>> I know that it's tough to make such a schedule, but anything that you can
>> provide would be helpful. Also, I'd be happy for something like a weekly
>> update; or a weekly blog post to help those who don't peruse this group in
>> depth each day.
>>
>> Thanks!
>>
>> Chris
>>
>> On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:
>>>
>>> From the discussion, it looks like that homepages for programming
>>> languages (and realed projects) serve two purposes:
>>>
>>> A. provide resources for the existing users (links to mailing lists,
>>> package directories, documentation, etc)
>>>
>>> B. provide information for potential new users (showcasing features of
>>> the language, links to tutorials).
>>>
>>> Given that space on the very front page is constrained (in the soft
>>> sense: no one wants pages that go on and on any more), I think that
>>> deciding on a balance between A and B would be a good way to focus the
>>> discussion.
>>>
>>> Once we have decided that, we can shamelessly copy good practices.
>>>
>>> For example,
>>>
>>> 1. the R website emphasizes content for existing users (in a non-flashy
>>> way that I am OK with), with very little material for new users,
>>>
>>> 2. about 1/3 of the middle bar on
>>> https://www.haskell.org/haskellwiki/Haskell is for new users
>>> (explanations/tutorials/etc), the 1/3 is for existing users (specs,
>>> libraries), and the final 1/3 is for both (forums, wiki, etc),
>>>
>>> 3. http://new-www.haskell.org/ is mostly caters to potential new users
>>> ("see how great this language is"),
>>>
>>> 4. the content of clojure.org is similarly for potential new users,
>>> while the sidebar has links for existing users.
>>>
>>> Best,
>>>
>>> Tamas
>>>
>>> On Wed, Dec 10 2014, Hans W Borchers  wrote:
>>>
>>> > Look at the R home page. R is one of the most popular languages, and
>>> esp. so
>>> > for statistical and computational applications. A programming language
>>> does
>>> > not need bloated home pages.
>>> >
>>> > I like the old Haskell home page much more than the new one. The new
>>> one
>>> > has
>>> > large, uninformative background pictures and not much information in a
>>> > small
>>> > and readable view. The HaskellWiki front page was much better in that.
>>> It
>>> > may
>>> > not even be decided which version will win.
>>> >
>>> > [Clojure])http://clojure.org/) has a nice, simple and informative
>>> home
>>> > page,
>>> > while [Scala](http://www.scala-lang.org/) has overdone it like the
>>> new
>>> > Haskell. For other approaches see the [Nim](http://nimrod-lang.org/)
>>> -
>>> > formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages.
>>> >
>>> > In the end I feel the condensed form of the Python home page will
>>> attract
>>> > more interest, for example with 'latest news' and 'upcoming events' on
>>> the
>>> > first page.This gives the impression of a lively and engaged
>>> community.
>>> >
>>> >
>>> > On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote:
>>> >>
>>> >> I like the Haskell one better than the Rust one.
>>> >>
>>> >> --Tim
>>> >>
>>> >>
>>>
>>

Re: [julia-users] Re: home page content

[Valentin Churavy]

I like the point: Solving P=NP reminds me of rust's 

* In theory. Rust is a work-in-progress and may do anything it likes up to 
> and including eating your laundry.


On Wednesday, 10 December 2014 19:15:05 UTC+1, Christian Peel wrote:
>
> One thing that I would very much appreciate is some kind of development 
> schedule.  For example
>   - Some kind of general roadmap
>   - a plan for when 0.4 and future releases will come
>   - Any plans to switch to a regular schedule?  (yearly, six
> months, ...) 
>   - What features remain before a 1.0 release?
>   - When will following arrive?
> > faster compilation
> > pre-compiled modules
> > Interactive debugging; line numbers for all errors
> > Automatic reload on file modification.
> > Solving P=NP
>
> I know that it's tough to make such a schedule, but anything that you can 
> provide would be helpful. Also, I'd be happy for something like a weekly 
> update; or a weekly blog post to help those who don't peruse this group in 
> depth each day.
>
> Thanks!
>
> Chris
>
> On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:
>>
>> From the discussion, it looks like that homepages for programming 
>> languages (and realed projects) serve two purposes: 
>>
>> A. provide resources for the existing users (links to mailing lists, 
>> package directories, documentation, etc) 
>>
>> B. provide information for potential new users (showcasing features of 
>> the language, links to tutorials). 
>>
>> Given that space on the very front page is constrained (in the soft 
>> sense: no one wants pages that go on and on any more), I think that 
>> deciding on a balance between A and B would be a good way to focus the 
>> discussion. 
>>
>> Once we have decided that, we can shamelessly copy good practices. 
>>
>> For example, 
>>
>> 1. the R website emphasizes content for existing users (in a non-flashy 
>> way that I am OK with), with very little material for new users, 
>>
>> 2. about 1/3 of the middle bar on 
>> https://www.haskell.org/haskellwiki/Haskell is for new users 
>> (explanations/tutorials/etc), the 1/3 is for existing users (specs, 
>> libraries), and the final 1/3 is for both (forums, wiki, etc), 
>>
>> 3. http://new-www.haskell.org/ is mostly caters to potential new users 
>> ("see how great this language is"), 
>>
>> 4. the content of clojure.org is similarly for potential new users, 
>> while the sidebar has links for existing users. 
>>
>> Best, 
>>
>> Tamas 
>>
>> On Wed, Dec 10 2014, Hans W Borchers  wrote: 
>>
>> > Look at the R home page. R is one of the most popular languages, and 
>> esp. so 
>> > for statistical and computational applications. A programming language 
>> does 
>> > not need bloated home pages. 
>> > 
>> > I like the old Haskell home page much more than the new one. The new 
>> one 
>> > has 
>> > large, uninformative background pictures and not much information in a 
>> > small 
>> > and readable view. The HaskellWiki front page was much better in that. 
>> It 
>> > may 
>> > not even be decided which version will win. 
>> > 
>> > [Clojure])http://clojure.org/) has a nice, simple and informative home 
>> > page, 
>> > while [Scala](http://www.scala-lang.org/) has overdone it like the new 
>> > Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) - 
>> > formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages. 
>> > 
>> > In the end I feel the condensed form of the Python home page will 
>> attract 
>> > more interest, for example with 'latest news' and 'upcoming events' on 
>> the 
>> > first page.This gives the impression of a lively and engaged community. 
>> > 
>> > 
>> > On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote: 
>> >> 
>> >> I like the Haskell one better than the Rust one. 
>> >> 
>> >> --Tim 
>> >> 
>> >> 
>>
>

Re: [julia-users] Re: home page content

[Christian Peel]

One thing that I would very much appreciate is some kind of development 
schedule.  For example
  - Some kind of general roadmap
  - a plan for when 0.4 and future releases will come
  - Any plans to switch to a regular schedule?  (yearly, six
months, ...) 
  - What features remain before a 1.0 release?
  - When will following arrive?
> faster compilation
> pre-compiled modules
> Interactive debugging; line numbers for all errors
> Automatic reload on file modification.
> Solving P=NP

I know that it's tough to make such a schedule, but anything that you can 
provide would be helpful. Also, I'd be happy for something like a weekly 
update; or a weekly blog post to help those who don't peruse this group in 
depth each day.

Thanks!

Chris

On Wednesday, December 10, 2014 5:41:35 AM UTC-8, Tamas Papp wrote:
>
> From the discussion, it looks like that homepages for programming 
> languages (and realed projects) serve two purposes: 
>
> A. provide resources for the existing users (links to mailing lists, 
> package directories, documentation, etc) 
>
> B. provide information for potential new users (showcasing features of 
> the language, links to tutorials). 
>
> Given that space on the very front page is constrained (in the soft 
> sense: no one wants pages that go on and on any more), I think that 
> deciding on a balance between A and B would be a good way to focus the 
> discussion. 
>
> Once we have decided that, we can shamelessly copy good practices. 
>
> For example, 
>
> 1. the R website emphasizes content for existing users (in a non-flashy 
> way that I am OK with), with very little material for new users, 
>
> 2. about 1/3 of the middle bar on 
> https://www.haskell.org/haskellwiki/Haskell is for new users 
> (explanations/tutorials/etc), the 1/3 is for existing users (specs, 
> libraries), and the final 1/3 is for both (forums, wiki, etc), 
>
> 3. http://new-www.haskell.org/ is mostly caters to potential new users 
> ("see how great this language is"), 
>
> 4. the content of clojure.org is similarly for potential new users, 
> while the sidebar has links for existing users. 
>
> Best, 
>
> Tamas 
>
> On Wed, Dec 10 2014, Hans W Borchers > 
> wrote: 
>
> > Look at the R home page. R is one of the most popular languages, and 
> esp. so 
> > for statistical and computational applications. A programming language 
> does 
> > not need bloated home pages. 
> > 
> > I like the old Haskell home page much more than the new one. The new one 
> > has 
> > large, uninformative background pictures and not much information in a 
> > small 
> > and readable view. The HaskellWiki front page was much better in that. 
> It 
> > may 
> > not even be decided which version will win. 
> > 
> > [Clojure])http://clojure.org/) has a nice, simple and informative home 
> > page, 
> > while [Scala](http://www.scala-lang.org/) has overdone it like the new 
> > Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) - 
> > formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages. 
> > 
> > In the end I feel the condensed form of the Python home page will 
> attract 
> > more interest, for example with 'latest news' and 'upcoming events' on 
> the 
> > first page.This gives the impression of a lively and engaged community. 
> > 
> > 
> > On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote: 
> >> 
> >> I like the Haskell one better than the Rust one. 
> >> 
> >> --Tim 
> >> 
> >> 
>

Re: [julia-users] Re: home page content

[Jan Niklas Hasse]

>
> Am I the only one who thinks these runnable code widgets are totally 
> useless?  I'm curious as to how users interact with them in the real 
> world.  I bet 99% of them either ignore it or just press the button and see 
> the default output.  The ones who probably interact with it the most are 
> going to be the same users that are going to download and run the language 
> anyway.  They displace huge amounts of real estate for basically no 
> practical value.  
>
> To me the landing page to a programming language is really a nice backdrop 
> for four things, A giant button where I can go download what I want because 
> I'm lazy and just click on the top google hit.  Another prominent link to 
> the Julia package ecosystem because I'm lazy and typing "julia" AND 
> "packages" is way too much work (haskell did a survey a while back, if I 
> remember correctly a majority of users to the front page fell under this 
> category). In addition, enough background information to get people to 
> click on the manual and a nice community / development activity section so 
> I can see that things are happening.  Please, please don't make me scroll 
> past a huge useless web 2.0 header to get to what I actually want (again, 
> lazy).  I like the  Racket, Haskell, and OCaml websites as I think they are 
> utilitarian but actually useful. I agree that the Rust site is a bit too 
> minimalist. I absolutely hate the python website.  The R website is just 
> laughably bad.  Altogether, I don't think PL's set a high bar in this 
> regard. 
>
> -Jake
>

No you're not the only one ;)
Unfortunately http://forio.com/julia/repl/ doesn't work anymore, in my 
opinion it was excellent and a link to it on the front page would be enough.

For everyone who doesn't already know, I've uploaded a preview of my 
homepage revamp here: http://julialang.herokuapp.com/
If you like I can use that page for a sandbox for ideas that come up during 
this discussion.

Re: [julia-users] Re: home page content

[Tamas Papp]

>From the discussion, it looks like that homepages for programming
languages (and realed projects) serve two purposes:

A. provide resources for the existing users (links to mailing lists,
package directories, documentation, etc)

B. provide information for potential new users (showcasing features of
the language, links to tutorials).

Given that space on the very front page is constrained (in the soft
sense: no one wants pages that go on and on any more), I think that
deciding on a balance between A and B would be a good way to focus the
discussion.

Once we have decided that, we can shamelessly copy good practices.

For example,

1. the R website emphasizes content for existing users (in a non-flashy
way that I am OK with), with very little material for new users,

2. about 1/3 of the middle bar on
https://www.haskell.org/haskellwiki/Haskell is for new users
(explanations/tutorials/etc), the 1/3 is for existing users (specs,
libraries), and the final 1/3 is for both (forums, wiki, etc),

3. http://new-www.haskell.org/ is mostly caters to potential new users
("see how great this language is"),

4. the content of clojure.org is similarly for potential new users,
while the sidebar has links for existing users.

Best,

Tamas

On Wed, Dec 10 2014, Hans W Borchers  wrote:

> Look at the R home page. R is one of the most popular languages, and esp. so
> for statistical and computational applications. A programming language does
> not need bloated home pages.
>
> I like the old Haskell home page much more than the new one. The new one
> has
> large, uninformative background pictures and not much information in a
> small
> and readable view. The HaskellWiki front page was much better in that. It
> may
> not even be decided which version will win.
>
> [Clojure])http://clojure.org/) has a nice, simple and informative home
> page,
> while [Scala](http://www.scala-lang.org/) has overdone it like the new
> Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) -
> formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages.
>
> In the end I feel the condensed form of the Python home page will attract
> more interest, for example with 'latest news' and 'upcoming events' on the
> first page.This gives the impression of a lively and engaged community.
>
>
> On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote:
>>
>> I like the Haskell one better than the Rust one.
>>
>> --Tim
>>
>>

Re: [julia-users] Re: home page content

[Hans W Borchers]

Look at the R home page. R is one of the most popular languages, and esp. so
for statistical and computational applications. A programming language does
not need bloated home pages.

I like the old Haskell home page much more than the new one. The new one 
has 
large, uninformative background pictures and not much information in a 
small 
and readable view. The HaskellWiki front page was much better in that. It 
may 
not even be decided which version will win.

[Clojure])http://clojure.org/) has a nice, simple and informative home 
page, 
while [Scala](http://www.scala-lang.org/) has overdone it like the new 
Haskell. For other approaches see the [Nim](http://nimrod-lang.org/) - 
formerly 'Nimrod' - and [Nemerle](http://nemerle.org/) home pages.

In the end I feel the condensed form of the Python home page will attract
more interest, for example with 'latest news' and 'upcoming events' on the 
first page.This gives the impression of a lively and engaged community.


On Wednesday, December 10, 2014 11:23:37 AM UTC+1, Tim Holy wrote:
>
> I like the Haskell one better than the Rust one. 
>
> --Tim 
>
>

Re: [julia-users] Re: home page content

[elextr]

One thing, (probably not on the front page) would be online access to the 
latest Git version for those of us limited to packaged versions.

Re: [julia-users] Re: home page content

[Job van der Zwan]

My two cents:

   - Plots are great, but please make them readable for the colourblind - 
   use triangles/squares/etc in addition to circles, use lightness and 
   saturation on top of hue. I can't make sense of the linked examples so far.
   - Code widgets are probably not that interesting outside of tutorial 
   pages, but an online sandbox is fantastic for discussing short snippets of 
   code. For example, play.golang.org is basically a runnable gist, and it 
   is constantly used in online discussions like *how to do x* or *why 
   doesn't y compile*?
   

Re: [julia-users] Re: home page content

[Simon Byrne]

Yeah, I don't think we need runnable widgets on the main page. A better 
option would be to have a "Run in JuliaBox" link which could start a new 
session.

As far as code samples go, the ideal ones should:
* be around 10 lines or so
* demonstrate the key features of Julia (i.e. all the things under "A 
Summary of Features" on the current homepage). Haskell's site does this 
well.
* do something that is cool and/or useful (some of the Wolfram Alpha 
examples are quite neat, albeit gimmicky).

We should definitely have a prominent link to the packages: a common 
critique of new languages is that they lack the package ecosystem of 
Python/R/etc. 


On Wednesday, 10 December 2014 11:28:24 UTC, Valentin Churavy wrote:
>
> I agree that displaying runnable code widgets are useless, but showing the 
> good integration with Jupyter/IPython via juliabox/tmpnb/SAGE is not.
> It would enable to demonstrated people features of Julia without having 
> them actually installing yet another programming environment, thus reducing 
> the barrier of entry.
>
> On Wednesday, 10 December 2014 08:20:48 UTC+1, Jake Bolewski wrote:
>>
>> Am I the only one who thinks these runnable code widgets are totally 
>> useless?  I'm curious as to how users interact with them in the real 
>> world.  I bet 99% of them either ignore it or just press the button and see 
>> the default output.  The ones who probably interact with it the most are 
>> going to be the same users that are going to download and run the language 
>> anyway.  They displace huge amounts of real estate for basically no 
>> practical value.  
>>
>> To me the landing page to a programming language is really a nice 
>> backdrop for four things, A giant button where I can go download what I 
>> want because I'm lazy and just click on the top google hit.  Another 
>> prominent link to the Julia package ecosystem because I'm lazy and typing 
>> "julia" AND "packages" is way too much work (haskell did a survey a while 
>> back, if I remember correctly a majority of users to the front page fell 
>> under this category). In addition, enough background information to get 
>> people to click on the manual and a nice community / development activity 
>> section so I can see that things are happening.  Please, please don't make 
>> me scroll past a huge useless web 2.0 header to get to what I actually want 
>> (again, lazy).  I like the  Racket, Haskell, and OCaml websites as I think 
>> they are utilitarian but actually useful. I agree that the Rust site is a 
>> bit too minimalist. I absolutely hate the python website.  The R website is 
>> just laughably bad.  Altogether, I don't think PL's set a high bar in this 
>> regard. 
>>
>> -Jake
>>
>>
>>
>> On Wednesday, December 10, 2014 1:16:42 AM UTC-5, cdm wrote:
>>>
>>>
>>> re tight code ...
>>>
>>> S. Danisch's code length v. speed plot may well be deserving of some 
>>> real esate:
>>>
>>>
>>>
>>> https://lh3.googleusercontent.com/-7IPcrjXuxFY/VICwQ3TrgRI/JV0/_HmDWZiBrXQ/s1600/benchmarks.png
>>>
>>>
>>>
>>> awesome.
>>>
>>> cdm
>>>
>>>
>>> On Tuesday, December 9, 2014 9:09:03 PM UTC-8, Stefan Karpinski wrote:

 On Tue, Dec 9, 2014 at 6:43 PM, Leah Hanson  wrote:

> I don't know if you want to encourage different styles, but seeing 
> examples of Python like, c like, and functional-ish ways of writing Julia 
> would be a way to show off the variety of things you can do.


 I really this idea. Having a grid of four code examples with different 
 styles – Pythonic/Matlabish, C-like, functional and Julian (i.e. with 
 types 
 and multiple dispatch). Now we just need to come up with good examples. 
 Another thing I wonder if it would be good to highlight is how tight the 
 code generated for simple, high-level Julia code is. Maybe not on the main 
 page though but on the about page.

>>>

Re: [julia-users] Re: home page content

[Valentin Churavy]

I agree that displaying runnable code widgets are useless, but showing the 
good integration with Jupyter/IPython via juliabox/tmpnb/SAGE is not.
It would enable to demonstrated people features of Julia without having 
them actually installing yet another programming environment, thus reducing 
the barrier of entry.

On Wednesday, 10 December 2014 08:20:48 UTC+1, Jake Bolewski wrote:
>
> Am I the only one who thinks these runnable code widgets are totally 
> useless?  I'm curious as to how users interact with them in the real 
> world.  I bet 99% of them either ignore it or just press the button and see 
> the default output.  The ones who probably interact with it the most are 
> going to be the same users that are going to download and run the language 
> anyway.  They displace huge amounts of real estate for basically no 
> practical value.  
>
> To me the landing page to a programming language is really a nice backdrop 
> for four things, A giant button where I can go download what I want because 
> I'm lazy and just click on the top google hit.  Another prominent link to 
> the Julia package ecosystem because I'm lazy and typing "julia" AND 
> "packages" is way too much work (haskell did a survey a while back, if I 
> remember correctly a majority of users to the front page fell under this 
> category). In addition, enough background information to get people to 
> click on the manual and a nice community / development activity section so 
> I can see that things are happening.  Please, please don't make me scroll 
> past a huge useless web 2.0 header to get to what I actually want (again, 
> lazy).  I like the  Racket, Haskell, and OCaml websites as I think they are 
> utilitarian but actually useful. I agree that the Rust site is a bit too 
> minimalist. I absolutely hate the python website.  The R website is just 
> laughably bad.  Altogether, I don't think PL's set a high bar in this 
> regard. 
>
> -Jake
>
>
>
> On Wednesday, December 10, 2014 1:16:42 AM UTC-5, cdm wrote:
>>
>>
>> re tight code ...
>>
>> S. Danisch's code length v. speed plot may well be deserving of some real 
>> esate:
>>
>>
>>
>> https://lh3.googleusercontent.com/-7IPcrjXuxFY/VICwQ3TrgRI/JV0/_HmDWZiBrXQ/s1600/benchmarks.png
>>
>>
>>
>> awesome.
>>
>> cdm
>>
>>
>> On Tuesday, December 9, 2014 9:09:03 PM UTC-8, Stefan Karpinski wrote:
>>>
>>> On Tue, Dec 9, 2014 at 6:43 PM, Leah Hanson  wrote:
>>>
 I don't know if you want to encourage different styles, but seeing 
 examples of Python like, c like, and functional-ish ways of writing Julia 
 would be a way to show off the variety of things you can do.
>>>
>>>
>>> I really this idea. Having a grid of four code examples with different 
>>> styles – Pythonic/Matlabish, C-like, functional and Julian (i.e. with types 
>>> and multiple dispatch). Now we just need to come up with good examples. 
>>> Another thing I wonder if it would be good to highlight is how tight the 
>>> code generated for simple, high-level Julia code is. Maybe not on the main 
>>> page though but on the about page.
>>>
>>

Re: [julia-users] Re: home page content

[Tim Holy]

I like the Haskell one better than the Rust one.

--Tim

On Tuesday, December 09, 2014 11:14:41 PM Valentin Churavy wrote:
> An other nice example might be the new haskell
> homepage http://new-www.haskell.org/
> 
> For the runnable part. Maybe we could use tmpnb/juliabox to host an example
> notebook. We should probably use a docker image with an userimages
> otherwise the attention span will be over before Gadfly is loaded.
> 
> Does this work for more than 10
> minutes?
> https://cfa4733.tmpnb.org/user-C6qXAatonjbQ/notebooks/Julia%20Test.ipynb#?
> On Wednesday, 10 December 2014 07:16:42 UTC+1, cdm wrote:
> > re tight code ...
> > 
> > S. Danisch's code length v. speed plot may well be deserving of some real
> > esate:
> > 
> > 
> > 
> > https://lh3.googleusercontent.com/-7IPcrjXuxFY/VICwQ3TrgRI/JV0/_Hm
> > DWZiBrXQ/s1600/benchmarks.png
> > 
> > 
> > 
> > awesome.
> > 
> > cdm
> > 
> > On Tuesday, December 9, 2014 9:09:03 PM UTC-8, Stefan Karpinski wrote:
> >> On Tue, Dec 9, 2014 at 6:43 PM, Leah Hanson  wrote:
> >>> I don't know if you want to encourage different styles, but seeing
> >>> examples of Python like, c like, and functional-ish ways of writing
> >>> Julia
> >>> would be a way to show off the variety of things you can do.
> >> 
> >> I really this idea. Having a grid of four code examples with different
> >> styles – Pythonic/Matlabish, C-like, functional and Julian (i.e. with
> >> types
> >> and multiple dispatch). Now we just need to come up with good examples.
> >> Another thing I wonder if it would be good to highlight is how tight the
> >> code generated for simple, high-level Julia code is. Maybe not on the
> >> main
> >> page though but on the about page.

Re: [julia-users] Re: home page content

[Jake Bolewski]

Am I the only one who thinks these runnable code widgets are totally 
useless?  I'm curious as to how users interact with them in the real 
world.  I bet 99% of them either ignore it or just press the button and see 
the default output.  The ones who probably interact with it the most are 
going to be the same users that are going to download and run the language 
anyway.  They displace huge amounts of real estate for basically no 
practical value.  

To me the landing page to a programming language is really a nice backdrop 
for four things, A giant button where I can go download what I want because 
I'm lazy and just click on the top google hit.  Another prominent link to 
the Julia package ecosystem because I'm lazy and typing "julia" AND 
"packages" is way too much work (haskell did a survey a while back, if I 
remember correctly a majority of users to the front page fell under this 
category). In addition, enough background information to get people to 
click on the manual and a nice community / development activity section so 
I can see that things are happening.  Please, please don't make me scroll 
past a huge useless web 2.0 header to get to what I actually want (again, 
lazy).  I like the  Racket, Haskell, and OCaml websites as I think they are 
utilitarian but actually useful. I agree that the Rust site is a bit too 
minimalist. I absolutely hate the python website.  The R website is just 
laughably bad.  Altogether, I don't think PL's set a high bar in this 
regard. 

-Jake



On Wednesday, December 10, 2014 1:16:42 AM UTC-5, cdm wrote:
>
>
> re tight code ...
>
> S. Danisch's code length v. speed plot may well be deserving of some real 
> esate:
>
>
>
> https://lh3.googleusercontent.com/-7IPcrjXuxFY/VICwQ3TrgRI/JV0/_HmDWZiBrXQ/s1600/benchmarks.png
>
>
>
> awesome.
>
> cdm
>
>
> On Tuesday, December 9, 2014 9:09:03 PM UTC-8, Stefan Karpinski wrote:
>>
>> On Tue, Dec 9, 2014 at 6:43 PM, Leah Hanson  wrote:
>>
>>> I don't know if you want to encourage different styles, but seeing 
>>> examples of Python like, c like, and functional-ish ways of writing Julia 
>>> would be a way to show off the variety of things you can do.
>>
>>
>> I really this idea. Having a grid of four code examples with different 
>> styles – Pythonic/Matlabish, C-like, functional and Julian (i.e. with types 
>> and multiple dispatch). Now we just need to come up with good examples. 
>> Another thing I wonder if it would be good to highlight is how tight the 
>> code generated for simple, high-level Julia code is. Maybe not on the main 
>> page though but on the about page.
>>
>

Re: [julia-users] Re: home page content

[Valentin Churavy]

An other nice example might be the new haskell 
homepage http://new-www.haskell.org/

For the runnable part. Maybe we could use tmpnb/juliabox to host an example 
notebook. We should probably use a docker image with an userimages 
otherwise the attention span will be over before Gadfly is loaded.

Does this work for more than 10 
minutes? 
https://cfa4733.tmpnb.org/user-C6qXAatonjbQ/notebooks/Julia%20Test.ipynb#?

On Wednesday, 10 December 2014 07:16:42 UTC+1, cdm wrote:
>
>
> re tight code ...
>
> S. Danisch's code length v. speed plot may well be deserving of some real 
> esate:
>
>
>
> https://lh3.googleusercontent.com/-7IPcrjXuxFY/VICwQ3TrgRI/JV0/_HmDWZiBrXQ/s1600/benchmarks.png
>
>
>
> awesome.
>
> cdm
>
>
> On Tuesday, December 9, 2014 9:09:03 PM UTC-8, Stefan Karpinski wrote:
>>
>> On Tue, Dec 9, 2014 at 6:43 PM, Leah Hanson  wrote:
>>
>>> I don't know if you want to encourage different styles, but seeing 
>>> examples of Python like, c like, and functional-ish ways of writing Julia 
>>> would be a way to show off the variety of things you can do.
>>
>>
>> I really this idea. Having a grid of four code examples with different 
>> styles – Pythonic/Matlabish, C-like, functional and Julian (i.e. with types 
>> and multiple dispatch). Now we just need to come up with good examples. 
>> Another thing I wonder if it would be good to highlight is how tight the 
>> code generated for simple, high-level Julia code is. Maybe not on the main 
>> page though but on the about page.
>>
>

Re: [julia-users] Re: home page content

[Pontus Stenetorp]

On 10 December 2014 at 08:43, Leah Hanson  wrote:
>
> Seeing code examples of a type and a couple of functions that use it would
> probably give a good idea of what the code looks like.

This would be excellent, maybe with some JavaScript magic we could
have a set of examples to switch between and the default one changing
upon each visit.  We already have a nice tutorial, but perhaps we
could link it more prominently.  I would also be really excited to
have blurbs [1], a personal favourite of mine would be this one [2],
but there ought to be a lot more.

Pontus

[1]: https://en.wikipedia.org/wiki/Blurb
[2]: https://news.ycombinator.com/item?id=7679386

Re: [julia-users] Re: home page content

[cdm]

re tight code ...

S. Danisch's code length v. speed plot may well be deserving of some real 
esate:


https://lh3.googleusercontent.com/-7IPcrjXuxFY/VICwQ3TrgRI/JV0/_HmDWZiBrXQ/s1600/benchmarks.png



awesome.

cdm


On Tuesday, December 9, 2014 9:09:03 PM UTC-8, Stefan Karpinski wrote:
>
> On Tue, Dec 9, 2014 at 6:43 PM, Leah Hanson  > wrote:
>
>> I don't know if you want to encourage different styles, but seeing 
>> examples of Python like, c like, and functional-ish ways of writing Julia 
>> would be a way to show off the variety of things you can do.
>
>
> I really this idea. Having a grid of four code examples with different 
> styles – Pythonic/Matlabish, C-like, functional and Julian (i.e. with types 
> and multiple dispatch). Now we just need to come up with good examples. 
> Another thing I wonder if it would be good to highlight is how tight the 
> code generated for simple, high-level Julia code is. Maybe not on the main 
> page though but on the about page.
>

Re: [julia-users] Re: home page content

[David Smith]

+1 for a runnable code widget.  

I think the typical scientific user will want to see immediately how to

1. create some variables.
2. do some math, probably with a matrix or vector.
3. plot something.
4. make a function.

That is a basic fooling-around paradigm.  Having a plot in the browser will 
be tricky, but I think it is crucial.





On Tuesday, December 9, 2014 5:54:33 PM UTC-6, Elliot Saba wrote:
>
> Perhaps not now, but as a long-term goal, having a live, editable widget 
> of code on the homepage is such an awesome draw-in, IMO.
> -E
>
> On Tue, Dec 9, 2014 at 3:43 PM, Leah Hanson  > wrote:
>
>> Seeing code examples of a type and a couple of functions that use it 
>> would probably give a good idea of what the code looks like. The JuMP seems 
>> exciting enough to highlight both as a package and a use of macros.
>>
>> I don't know if you want to encourage different styles, but seeing 
>> examples of Python like, c like, and functional-ish ways of writing Julia 
>> would be a way to show off the variety of things you can do.
>>
>> --Leah
>>
>> On Wed, Dec 10, 2014 at 8:50 AM Elliot Saba > > wrote:
>>
>>> We're having intermittent DNS issues.  http://julialang.org is now up 
>>> for me however, and I can dig it: (I couldn't, previously)
>>>
>>> $ dig julialang.org
>>>
>>> ; <<>> DiG 9.8.3-P1 <<>> julialang.org
>>> ;; global options: +cmd
>>> ;; Got answer:
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56740
>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4
>>>
>>> ;; QUESTION SECTION:
>>> ;julialang.org. IN  A
>>>
>>> ;; ANSWER SECTION:
>>> julialang.org.  2202IN  CNAME   julialang.github.io.
>>> julialang.github.io.2202IN  CNAME   github.map.fastly.net.
>>> github.map.fastly.net.  15  IN  A   199.27.79.133
>>> ...
>>> -E
>>>
>>>
>>>
>>> On Tue, Dec 9, 2014 at 2:46 PM, > wrote:
>>>


 On Wednesday, December 10, 2014 8:23:26 AM UTC+10, Stefan Karpinski 
 wrote:
>
> We're looking to redesign the JuliaLang.org home page and try to give 
> it a little more focus than it currently has. Which raises the question 
> of 
> what to focus on. We could certainly have better code examples and maybe 
> highlight features of the language and its ecosystem better. What do 
> people 
> think we should include?
>

 The whole site seems to be offline?  Is that because of this? 

>>>
>>>  
>

Re: [julia-users] Re: home page content

[Stefan Karpinski]

The Rust site is very nice – although I do feel that it has too little
content on it and feels like a landing page that you just have to click
through to somewhere else from. I can see having something like the Rust
page but with more content "below the fold".

On Tue, Dec 9, 2014 at 9:36 PM, John Myles White 
wrote:

> +1 for emulating the Rust site
>
>  -- John
>
> On Dec 9, 2014, at 4:46 PM, Joey Huchette  wrote:
>
> I think the [Rust website](http://www.rust-lang.org/) is pretty
> fantastic, in terms of both design and content. Having the code examples
> runnable and editable (via JuliaBox) would be a killer feature, though I
> have no idea how feasible that is.
>
> On Tuesday, December 9, 2014 6:54:33 PM UTC-5, Elliot Saba wrote:
>>
>> Perhaps not now, but as a long-term goal, having a live, editable widget
>> of code on the homepage is such an awesome draw-in, IMO.
>> -E
>>
>> On Tue, Dec 9, 2014 at 3:43 PM, Leah Hanson  wrote:
>>
>>> Seeing code examples of a type and a couple of functions that use it
>>> would probably give a good idea of what the code looks like. The JuMP seems
>>> exciting enough to highlight both as a package and a use of macros.
>>>
>>> I don't know if you want to encourage different styles, but seeing
>>> examples of Python like, c like, and functional-ish ways of writing Julia
>>> would be a way to show off the variety of things you can do.
>>>
>>> --Leah
>>>
>>> On Wed, Dec 10, 2014 at 8:50 AM Elliot Saba  wrote:
>>>
 We're having intermittent DNS issues.  http://julialang.org is now up
 for me however, and I can dig it: (I couldn't, previously)

 $ dig julialang.org

 ; <<>> DiG 9.8.3-P1 <<>> julialang.org
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56740
 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4

 ;; QUESTION SECTION:
 ;julialang.org. IN  A

 ;; ANSWER SECTION:
 julialang.org.  2202IN  CNAME   julialang.github.io.
 julialang.github.io.2202IN  CNAME   github.map.fastly.net.
 github.map.fastly.net.  15  IN  A   199.27.79.133
 ...
 -E



 On Tue, Dec 9, 2014 at 2:46 PM,  wrote:

>
>
> On Wednesday, December 10, 2014 8:23:26 AM UTC+10, Stefan Karpinski
> wrote:
>>
>> We're looking to redesign the JuliaLang.org home page and try to
>> give it a little more focus than it currently has. Which raises the
>> question of what to focus on. We could certainly have better code 
>> examples
>> and maybe highlight features of the language and its ecosystem better. 
>> What
>> do people think we should include?
>>
>
> The whole site seems to be offline?  Is that because of this?
>


>>
>

Re: [julia-users] Re: home page content

[Stefan Karpinski]

On Tue, Dec 9, 2014 at 6:43 PM, Leah Hanson  wrote:

> I don't know if you want to encourage different styles, but seeing
> examples of Python like, c like, and functional-ish ways of writing Julia
> would be a way to show off the variety of things you can do.


I really this idea. Having a grid of four code examples with different
styles – Pythonic/Matlabish, C-like, functional and Julian (i.e. with types
and multiple dispatch). Now we just need to come up with good examples.
Another thing I wonder if it would be good to highlight is how tight the
code generated for simple, high-level Julia code is. Maybe not on the main
page though but on the about page.

Re: [julia-users] Re: home page content

[John Myles White]

+1 for emulating the Rust site

 -- John

On Dec 9, 2014, at 4:46 PM, Joey Huchette  wrote:

> I think the [Rust website](http://www.rust-lang.org/) is pretty fantastic, in 
> terms of both design and content. Having the code examples runnable and 
> editable (via JuliaBox) would be a killer feature, though I have no idea how 
> feasible that is.
> 
> On Tuesday, December 9, 2014 6:54:33 PM UTC-5, Elliot Saba wrote:
> Perhaps not now, but as a long-term goal, having a live, editable widget of 
> code on the homepage is such an awesome draw-in, IMO.
> -E
> 
> On Tue, Dec 9, 2014 at 3:43 PM, Leah Hanson  wrote:
> Seeing code examples of a type and a couple of functions that use it would 
> probably give a good idea of what the code looks like. The JuMP seems 
> exciting enough to highlight both as a package and a use of macros.
> 
> I don't know if you want to encourage different styles, but seeing examples 
> of Python like, c like, and functional-ish ways of writing Julia would be a 
> way to show off the variety of things you can do.
> 
> --Leah
> 
> On Wed, Dec 10, 2014 at 8:50 AM Elliot Saba  wrote:
> We're having intermittent DNS issues.  http://julialang.org is now up for me 
> however, and I can dig it: (I couldn't, previously)
> 
> $ dig julialang.org
> 
> ; <<>> DiG 9.8.3-P1 <<>> julialang.org
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56740
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4
> 
> ;; QUESTION SECTION:
> ;julialang.org. IN  A
> 
> ;; ANSWER SECTION:
> julialang.org.  2202IN  CNAME   julialang.github.io.
> julialang.github.io.2202IN  CNAME   github.map.fastly.net.
> github.map.fastly.net.  15  IN  A   199.27.79.133
> ...
> -E
> 
> 
> 
> On Tue, Dec 9, 2014 at 2:46 PM,  wrote:
> 
> 
> On Wednesday, December 10, 2014 8:23:26 AM UTC+10, Stefan Karpinski wrote:
> We're looking to redesign the JuliaLang.org home page and try to give it a 
> little more focus than it currently has. Which raises the question of what to 
> focus on. We could certainly have better code examples and maybe highlight 
> features of the language and its ecosystem better. What do people think we 
> should include?
> 
> The whole site seems to be offline?  Is that because of this? 
> 
> 

Re: [julia-users] Re: home page content

[Joey Huchette]

I think the [Rust website](http://www.rust-lang.org/) is pretty fantastic, 
in terms of both design and content. Having the code examples runnable and 
editable (via JuliaBox) would be a killer feature, though I have no idea 
how feasible that is.

On Tuesday, December 9, 2014 6:54:33 PM UTC-5, Elliot Saba wrote:
>
> Perhaps not now, but as a long-term goal, having a live, editable widget 
> of code on the homepage is such an awesome draw-in, IMO.
> -E
>
> On Tue, Dec 9, 2014 at 3:43 PM, Leah Hanson  > wrote:
>
>> Seeing code examples of a type and a couple of functions that use it 
>> would probably give a good idea of what the code looks like. The JuMP seems 
>> exciting enough to highlight both as a package and a use of macros.
>>
>> I don't know if you want to encourage different styles, but seeing 
>> examples of Python like, c like, and functional-ish ways of writing Julia 
>> would be a way to show off the variety of things you can do.
>>
>> --Leah
>>
>> On Wed, Dec 10, 2014 at 8:50 AM Elliot Saba > > wrote:
>>
>>> We're having intermittent DNS issues.  http://julialang.org is now up 
>>> for me however, and I can dig it: (I couldn't, previously)
>>>
>>> $ dig julialang.org
>>>
>>> ; <<>> DiG 9.8.3-P1 <<>> julialang.org
>>> ;; global options: +cmd
>>> ;; Got answer:
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56740
>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4
>>>
>>> ;; QUESTION SECTION:
>>> ;julialang.org. IN  A
>>>
>>> ;; ANSWER SECTION:
>>> julialang.org.  2202IN  CNAME   julialang.github.io.
>>> julialang.github.io.2202IN  CNAME   github.map.fastly.net.
>>> github.map.fastly.net.  15  IN  A   199.27.79.133
>>> ...
>>> -E
>>>
>>>
>>>
>>> On Tue, Dec 9, 2014 at 2:46 PM, > wrote:
>>>


 On Wednesday, December 10, 2014 8:23:26 AM UTC+10, Stefan Karpinski 
 wrote:
>
> We're looking to redesign the JuliaLang.org home page and try to give 
> it a little more focus than it currently has. Which raises the question 
> of 
> what to focus on. We could certainly have better code examples and maybe 
> highlight features of the language and its ecosystem better. What do 
> people 
> think we should include?
>

 The whole site seems to be offline?  Is that because of this? 

>>>
>>>  
>

Re: [julia-users] Re: home page content

[Elliot Saba]

Perhaps not now, but as a long-term goal, having a live, editable widget of
code on the homepage is such an awesome draw-in, IMO.
-E

On Tue, Dec 9, 2014 at 3:43 PM, Leah Hanson  wrote:

> Seeing code examples of a type and a couple of functions that use it would
> probably give a good idea of what the code looks like. The JuMP seems
> exciting enough to highlight both as a package and a use of macros.
>
> I don't know if you want to encourage different styles, but seeing
> examples of Python like, c like, and functional-ish ways of writing Julia
> would be a way to show off the variety of things you can do.
>
> --Leah
>
> On Wed, Dec 10, 2014 at 8:50 AM Elliot Saba  wrote:
>
>> We're having intermittent DNS issues.  http://julialang.org is now up
>> for me however, and I can dig it: (I couldn't, previously)
>>
>> $ dig julialang.org
>>
>> ; <<>> DiG 9.8.3-P1 <<>> julialang.org
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56740
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4
>>
>> ;; QUESTION SECTION:
>> ;julialang.org. IN  A
>>
>> ;; ANSWER SECTION:
>> julialang.org.  2202IN  CNAME   julialang.github.io.
>> julialang.github.io.2202IN  CNAME   github.map.fastly.net.
>> github.map.fastly.net.  15  IN  A   199.27.79.133
>> ...
>> -E
>>
>>
>>
>> On Tue, Dec 9, 2014 at 2:46 PM,  wrote:
>>
>>>
>>>
>>> On Wednesday, December 10, 2014 8:23:26 AM UTC+10, Stefan Karpinski
>>> wrote:

 We're looking to redesign the JuliaLang.org home page and try to give
 it a little more focus than it currently has. Which raises the question of
 what to focus on. We could certainly have better code examples and maybe
 highlight features of the language and its ecosystem better. What do people
 think we should include?

>>>
>>> The whole site seems to be offline?  Is that because of this?
>>>
>>
>>

Re: [julia-users] Re: home page content

[Leah Hanson]

Seeing code examples of a type and a couple of functions that use it would
probably give a good idea of what the code looks like. The JuMP seems
exciting enough to highlight both as a package and a use of macros.

I don't know if you want to encourage different styles, but seeing examples
of Python like, c like, and functional-ish ways of writing Julia would be a
way to show off the variety of things you can do.

--Leah
On Wed, Dec 10, 2014 at 8:50 AM Elliot Saba  wrote:

> We're having intermittent DNS issues.  http://julialang.org is now up for
> me however, and I can dig it: (I couldn't, previously)
>
> $ dig julialang.org
>
> ; <<>> DiG 9.8.3-P1 <<>> julialang.org
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56740
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4
>
> ;; QUESTION SECTION:
> ;julialang.org. IN  A
>
> ;; ANSWER SECTION:
> julialang.org.  2202IN  CNAME   julialang.github.io.
> julialang.github.io.2202IN  CNAME   github.map.fastly.net.
> github.map.fastly.net.  15  IN  A   199.27.79.133
> ...
> -E
>
>
>
> On Tue, Dec 9, 2014 at 2:46 PM,  wrote:
>
>>
>>
>> On Wednesday, December 10, 2014 8:23:26 AM UTC+10, Stefan Karpinski wrote:
>>>
>>> We're looking to redesign the JuliaLang.org home page and try to give it
>>> a little more focus than it currently has. Which raises the question of
>>> what to focus on. We could certainly have better code examples and maybe
>>> highlight features of the language and its ecosystem better. What do people
>>> think we should include?
>>>
>>
>> The whole site seems to be offline?  Is that because of this?
>>
>
>

Re: [julia-users] Re: home page content

[Elliot Saba]

We're having intermittent DNS issues.  http://julialang.org is now up for
me however, and I can dig it: (I couldn't, previously)

$ dig julialang.org

; <<>> DiG 9.8.3-P1 <<>> julialang.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56740
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;julialang.org. IN  A

;; ANSWER SECTION:
julialang.org.  2202IN  CNAME   julialang.github.io.
julialang.github.io.2202IN  CNAME   github.map.fastly.net.
github.map.fastly.net.  15  IN  A   199.27.79.133
...
-E



On Tue, Dec 9, 2014 at 2:46 PM,  wrote:

>
>
> On Wednesday, December 10, 2014 8:23:26 AM UTC+10, Stefan Karpinski wrote:
>>
>> We're looking to redesign the JuliaLang.org home page and try to give it
>> a little more focus than it currently has. Which raises the question of
>> what to focus on. We could certainly have better code examples and maybe
>> highlight features of the language and its ecosystem better. What do people
>> think we should include?
>>
>
> The whole site seems to be offline?  Is that because of this?
>