Hi Azalee,
Django Girls (Python/Django) and Railsbridge (Ruby/Rails) which are both
1.5 day workshops to teach beginners to develop a full stack web
application use Atom as their preferred editor. Both are run often and
students have no difficulty using Atom.
As to your questions:
*
There are many well-formulated opinions either way in this thread, but I
have to agree with Mark, Bennet and others.
FYI, for a new undergraduate Python course on Windows lab computers we
chose between two candidate editors: atom and notepad++. I found atom a bit
heavy and slow in this context
Just my 2c: Notepad can safely be substituted for nano for Windows
users. No additional setup required, and it's something learners are
likely already familiar with. In my opinion Atom is a bit overkill for
what we are asking learners to do, i.e., create small files, edit
existing files and write
Hi Raniere,
Thanks for bringing this up. I think it is always good to re-examine our
options as the field is constantly changing. I agree that Nano isn’t ideal and
its always disappointing to tell students we’re going to use it for the
workshop and they will likely never use it again. My big
I think Bennet summed up my views on the issue best. It seems to me it is not
so much about whether Atom is hard to learn, but that it is a fundamentally
different
tool (GUI) in many respects. Nano is something that will allow them to work
remotely,
keep their mind centered on where they are
I agree with Erik.
I would not perhaps mind if it will be added to the list of alternative
editors in the workshop template, which currently says "Others editors
that you can use areNotepad++ or Sublime Text for Win; Text Wrangler
or Sublime Text for macOS; Gedit,Kate or Sublime Text for
On Thu, 30 Mar 2017 12:56:31 -0400
Jeremy Gray wrote:
> I think the cognitive load of Atom (or any new fancy text editor) is
> being underestimated.
I totally agree with this. I tried Atom once, and thought: "this
looks great, but I'll need some time to get into it".
Hi,
The original motivation for the choice of Atom was:
today at the workshop, one of the our Windows learners asked me why
after quit nano the previous command weren't available when scroll
the window up. The learner was very annoyed to not be able to see
the history.
This is indeed
I think the cognitive load of Atom (or any new fancy text editor) is being
underestimated. I really like Atom, but a workshop might not be the best
place to start people using it.
A lot of the time people are using whatever works, and if you ask them to
change, you need a good reason - nano has
I would also encourage the move to Atom as the default editor. I believe
that Atom offers benefits that nano, while simple, does not offer.
Installation of Atom is very stable. It works out of the box with no
additional configuration. It's "an editor that will be welcoming to an
elementary
Without being able to speak to most of the
issues being discussed in this thread, I
second what Mark says in his first paragraph.
I've been teaching a Programming for Non-majors
course at my (and Mark's) institution for
17 years, and we've always used nano (or pico,
nano's predecessor).
The
On Thu, Mar 30, 2017 at 3:17 PM, Bennet Fauber wrote:
> I really do not mean to be a troll, here, but it seems to me that the
> trend is to develop SWC/DC away from a coherently organized workshop
> centered around the idea of creating a pipeline that is run using
> scripts,
I really do not mean to be a troll, here, but it seems to me that the
trend is to develop SWC/DC away from a coherently organized workshop
centered around the idea of creating a pipeline that is run using
scripts, invoked from a command line, and that is under version
control. That is how I
Also +1 to Noam's suggestion
On Thu, Mar 30, 2017 at 4:59 AM, Ethan White wrote:
> I support this change in concept and agree with Noam that it should only
> be undertaken broadly following experimentation to make sure it works more
> effectively than the current approach
I support this change in concept and agree with Noam that it should only
be undertaken broadly following experimentation to make sure it works
more effectively than the current approach and to iron out any
unanticipated issues.
Ethan
On 03/30/2017 07:13 AM, Noam Ross wrote:
I support this,
I support this, but I think the appropriate approach is to gather
evidence. Many (most?) changes to lessons and methods start as experiments
by instructors, so I think a set of instructors should produce the
following for an upcoming workshop, which other instructors can try out:
- A fork of
Thanks Raniere. If there is not a commitment to maintain the Windows
installer, then it sounds like this might be the best route.
The main reason I don't like this as a solution is that when people are on
an HPC or remote computers like Amazon EC2, they likely won't have access
to Atom. So, I
Hi all,
today at the workshop,
one of the our Windows learners asked me why after quit nano the
previous command weren't available when scroll the window up.
The learner was very annoyed to not be able to see the history.
I would like to motion to change nano with Atom as the recommended/default
18 matches
Mail list logo