From: Yuri Khan <yurivkhan@gmail.com>
To: edgar@openmail.cc
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Org-mode <emacs-orgmode@gnu.org>
Subject: Re: General advice beyond Org
Date: Fri, 18 May 2018 17:54:45 +0700 [thread overview]
Message-ID: <CAP_d_8VPt_Meyq_c3yGY8KFZAq2uy=zqOJNtEqzD=HtnKAGZXw@mail.gmail.com> (raw)
In-Reply-To: <7dc580d0ea76c21328dc586ffadb5499@openmail.cc>
On Fri, May 18, 2018 at 7:29 AM <edgar@openmail.cc> wrote:
> _I_ need help. I am in graduate school, and I keep having issues with my
> advisor for my strong inclination to use free software. I am obviously
> not in position to refuse, but she dislikes to have discussions about
> it. She pays a stipend to me every month, and my tuition is wa[i]ved.
> Is anyone here aware of a place where they do computational human
> biomechanics, mechanics, materials or finite elements where I could
> interact with free software? (having github, LaTeX, Python, etc.; avoid
> Micro$oft products, Matlab, Mathematica, etc.). Is there no place where
> one can simply use free software on a daily basis?
Are you required to pay for licenses for proprietary software you are asked
to use? Chances are, your school is getting academic discounts, and you get
to use it for no charge.
Your instructors and professors probably have a lot of experience with
those tools. They are understandably reluctant to switch, because the tools
work well enough for them.
Also, as a student, you do not have sufficient influence to convert
everybody at your school to free software.
> As a student or junior faculty, how do you go about this? Do you just
> nod and wave your freedom good bye?
The point of education is to get exposed to many tools, techniques and
workflows. By limiting yourself to free software only, you will miss out.
Be a scout in the proprietary camp. Learn the tools your instructors are
willing to teach. Learn what it takes to achieve the same results with free
software. Learn the difference in workflows and user experience.
You will find something you can do with free software that you don’t know
how to do with proprietary tools. Ask your teachers. They will either point
you at something you missed (and then you can study it); or they will admit
that feature is nice but their tool doesn’t have it (and then you have
demonstrated the merits of free software); or they will say it’s not
important.
You will also likely find more than a few points where non-free software
delivers better UX. Use that knowledge to improve free software so that it
can compete with proprietary software on UX terms, not only on the issue of
freedom.
next prev parent reply other threads:[~2018-05-18 10:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 0:28 General advice beyond Org edgar
2018-05-18 1:52 ` Peter Neilson
2018-05-18 7:12 ` S. Champailler
2018-05-18 8:10 ` edgar
2018-05-18 11:44 ` Diego Zamboni
2018-05-18 14:21 ` Aaron Ecay
2018-05-18 22:31 ` Stefan Monnier
2018-05-18 10:54 ` Yuri Khan [this message]
2018-05-18 11:10 ` S. Champailler
2018-05-18 13:50 ` Kevin Buchs
2018-05-18 13:50 ` hymie!
2018-05-19 7:18 ` Marcin Borkowski
2018-05-18 19:57 ` Adonay Felipe Nogueira
2018-05-19 7:17 ` Marcin Borkowski
2018-05-20 1:24 ` Samuel Wales
2018-05-20 4:56 ` Exporting ODT to Org [was Re: General advice beyond Org] edgar
2018-06-05 19:52 ` General advice beyond Org Adonay Felipe Nogueira
2018-06-06 8:58 ` Marco
2018-06-15 16:24 ` Grant Rettke
[not found] <mailman.79.1527004820.3124.emacs-orgmode@gnu.org>
2018-05-23 4:15 ` edgar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP_d_8VPt_Meyq_c3yGY8KFZAq2uy=zqOJNtEqzD=HtnKAGZXw@mail.gmail.com' \
--to=yurivkhan@gmail.com \
--cc=edgar@openmail.cc \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).