From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: call function in other window ?
Date: Tue, 23 May 2017 14:58:04 +0200 [thread overview]
Message-ID: <87k25791cz.fsf@debian.uxu> (raw)
In-Reply-To: 20170523085421.GA6637@tuxteam.de
<tomas@tuxteam.de> writes:
> the web's sucess means there's no backtracking; once
> some idea is "out there", it will stay there, to
> embarras the designer in eternity, because people
> are using it.
That's interesting.
To some extent even web technology can change because
one can use it in a new way.
For example, when I first did HTML no one had ever
heard of CSS and those homepages today would be cut in
half to remove all the design and layup stuff.
(Not that that would much improve the quality of the
actual webpages which must have been
extremely immature...)
> then the Holy Grail of Apps and some form of
> perverted Java (never thought *that* could be done)
> in everyone's pocket, car and sex toy. That's why
> Free software (the real Free, written with a big
> "F") is more important than ever. And not just the
> Free software, but awareness out there.
I've heard this from RMS as well but I didn't
understand it that time either. What I can see, the
smartphones are so totally unergonomic so they can't
be used to do creative stuff. Only consumption of
material. That doesn't have to be bad. It depends what
you consume. But the problem is if people use
smartphones instead of computers they can never leave
the "consumer prison". I honestly don't see how FOSS
can improve that. So what exactly is it FOSS is
expected to do for smartphones?
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-05-23 12:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 15:35 call function in other window ? Jean-Christophe Helary
2017-05-20 20:25 ` Drew Adams
2017-05-20 22:43 ` Jean-Christophe Helary
2017-05-20 23:50 ` Emanuel Berg
2017-05-21 1:27 ` Drew Adams
2017-05-21 1:58 ` Emanuel Berg
2017-05-21 2:39 ` Jean-Christophe Helary
2017-05-21 10:07 ` Emanuel Berg
2017-05-21 10:16 ` Jean-Christophe Helary
2017-05-21 10:50 ` Joost Kremers
2017-05-21 11:08 ` Jean-Christophe Helary
2017-05-21 13:52 ` Emanuel Berg
2017-05-21 15:05 ` Eli Zaretskii
2017-05-21 15:14 ` Jean-Christophe Helary
2017-05-21 15:56 ` Emanuel Berg
2017-05-22 6:39 ` Jean-Christophe Helary
2017-05-22 21:18 ` Emanuel Berg
2017-05-22 22:26 ` Jean-Christophe Helary
2017-05-22 22:42 ` Kaushal Modi
2017-05-23 0:20 ` Emanuel Berg
2017-05-23 0:19 ` Emanuel Berg
2017-05-23 7:10 ` tomas
2017-05-23 7:44 ` Emanuel Berg
2017-05-23 7:57 ` tomas
2017-05-23 8:14 ` Emanuel Berg
2017-05-23 8:54 ` tomas
2017-05-23 12:58 ` Emanuel Berg [this message]
2017-05-23 13:03 ` Jean-Christophe Helary
2017-05-23 13:14 ` Emanuel Berg
2017-05-23 19:18 ` tomas
2017-05-23 20:25 ` Tomas Nordin
2017-05-23 21:02 ` John Ankarström
2017-05-24 19:40 ` Emanuel Berg
2017-05-24 7:26 ` tomas
2017-05-21 15:59 ` Eli Zaretskii
2017-05-21 22:58 ` Drew Adams
[not found] ` <<83tw4enqtl.fsf@gnu.org>
2017-05-21 23:00 ` Drew Adams
2017-05-21 13:48 ` Emanuel Berg
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k25791cz.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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.
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).