And a lot of music creation apps exist for tablets/phones.
This production/consumption divide is too rigid.
Now don't get me wrong - while I only use the two a little, I think they're fine. It's communication, an important part of human experience. But, at least in my mind, Instagram and Snapchat fall firmly into the same group as browsing Facebook or 9gag, as opposed to e.g. making a let's play video or a comic strip.
Yes, there are ways to take photos and create music on tablets and phones. You can do some basic editing on them, even. But the "professional" tools for photography and music, with all the bells and whistles you can think of, are still dominated by laptop / desktop computer programs. (The dominant programs being Photoshop for images, and DAWs like Logic, Ableton Live, and Pro Tools for music.)
The distinction between "production" and "consumption" devices is indeed kind of too rigid in a sense that, of course, professionals will utilize the creative tools that come on tablets and phones, even if the desktop / laptop programs are the primary tool. Tablets also can shine as an extended interface for desktop programs. (EG: Logic Pro (and others) have apps that turns an iPad into a remote controller for the main DAW. There are programs like Astropad that turn your iPad into a Wacom-like tablet for Photoshop, etc.)
The obstacle is interface. The fine-tuned control of a tablet or (especially) a phone is much poorer than using a mouse and keyboard with a large screen. Until that gets resolved, I doubt desktops / laptops will go anywhere.
Development isn't done on tablets because the input devices we have to make code are limited to a keyboard, and most people think text files are code, rather than a serialisation/deserialisation format for an AST.
You could easily build an AST with gestures and speech rather than tapping buttons, and I think in 10-20 years time that's how we'll make software.
I doubt it. Perhaps we'll be making ASTs by writing (i.e. drawing symbols with styli or pens), but I don't think we'll be doing it via gestures and speech. There's a reason that we don't teach math via interpretive dance.
But text is a pretty fine form of communication and I find myself using it very often at work (and at home I often talk this way to people not in the same room, but in the same flat). It's fast, it's convenient, it's less disrupting, and the only reason to avoid it are some silly preconceptions that digital communiction is somehow "worse" than spoken words.
Also, you never passed papers to your friends while in school? That's pre-smartphone equivalent of IM.
Edit: And easier to search, remember, read again and the less nice variant of that; 'you never said that to me' 'I did: ' copy/paste.
Regarding being easier to search and read it again, it seems like there are potential technical solutions to that problem, but I would agree that we're not there yet.
Recorded speech is also searchable so not sure that's relevant.
It is ; recorded speech is not very searchable, especially if you are talking in a group in a conference where people can be from different countries with different dialects (which is the normal situation for our group talks). Also it is not convenient and sometimes not possible to record every (conference) meeting (too much noise etc). With text it's automatically recorded and perfectly searchable...
Also some of my colleagues are not good at English listening but are very good technically; if I type what I mean they understand while if I/we tell them, everything has to be translated and/or repeated many times.
I think the tech is not there yet to say it's not relevant.
A more specialized scenario: I was copy/pasting stuff to a colleague in the same room yesterday.
I will bet you £100 that we won't be programming by speech and gestures in even 25 years time as the disadvantages are enormous.
One other advantage of directly manipulating AST - it's very easily converted into any language runtime you want. It won't matter if you are targeting the JVM, V8 or native bytecode; you can do it all from the same AST. This same thing is possible with plain text code, but not quite as common.
I think there are ports of paredit-like features to those languages in Emacs too, and all the other semantic features of Emacs itself work with those. As long as the language's major mode properly defines what is e.g. a function, a symbol, etc. you can use semantic navigation and editing.
> One other advantage of directly manipulating AST - it's very easily converted into any language runtime you want. It won't matter if you are targeting the JVM, V8 or native bytecode; you can do it all from the same AST. This same thing is possible with plain text code, but not quite as common.
I don't think this is something that AST gives you. AST is just a more machine-friendly representation of what you typed in the source code. Portability between different platforms depend on what bytecode/machine code gets generated from that AST. And since AST is generated from the compiled source anyway as one of the first steps in compilation, getting it to emit a right set of platform-specific instructions means you can compile the original source there too.
And AST doesn't solve the problem of calling platform-specific functions and libraries anyway.
Data structures are shapes. A shape is better drawn than described in text.
> Data structures are shapes. A shape is better drawn than described in text.
Draw me a linked list. Tell me how much faster it is than typing:
(list 1 2 (foobar) (make-hash-table) (list "a" "b" "c") 6)
Even on a visual keyboard on a tablet, it's faster to type than to draw data structures. A flat sheet of glass maybe gives us the ability to get the (x, y) coordinates of a touched point easier and with more precision, but it sacrifices many other important aspects - like tactile feedback and the ability to feel shapes. With physical keyboard, you're employing more of the features your body and mind has, and that's why it's faster than a touchscreen.Unless you can find a completely different way of designing UX, then a tablet won't be a suitable device for creation. None of the currently existing solutions come close to beating a physical keyboard and a mouse.
I don't normally use linked lists, but here's an array:
"list joe (subtle gesture) mary (subtle gesture) dave end
If I wanted to delete dave from the list I could grab it and slide it away or say "list delete last".
> Tell me how much faster it is than typing
Everyone in the room I'm in now can talk at 200 words per minute and use their hands. Very few of them could type that fast.
How will you go about drawing "joe" and "mary"? Is it faster than typing? Note that you can't always select stuff from dropdowns - you often have to create new symbols and values.
> Everyone in the room I'm in now can naturally talk at 200 words per minute.
How fast they can track back and correct a mistake made three words before? Or take the last sentence and make it a subnode of the one before that? Speech is not flexible enough for the task unless you go full AI and have software that understands what you mean.
> How will you go about drawing "joe" and "mary"?
I'll just say it, it's easier. As I said at the top of the thread, gestures and speech.
> How fast they can track back and correct a mistake made three words before?
I gave an example of opening an existing structure and modifying it in the comment you're replying to.
> Or take the last sentence and make it a subnode of the one before that?
Like in a DOM? Easily: grab it and move it, just like you do it in DevTools today, except with your hands rather than a mouse.
Sorry, I misunderstood what you meant by "subtle gesture" there.
Anyway, in the original comment you said:
> Data structures are shapes. A shape is better drawn than described in text.
I'll grant you that speaking + gestures may not be a bad way of entering and manipulating small data structures and preforming simple operations. But until we have a technology that can recognize speech and gestures reliably and accurately (and tablets with OSes that don't lag and hang up for half a second at random), physical keyboards will still be much faster and much less annoying.
But I still doubt you could extend that to more complex editing and navigating tasks. Take a brief look at the things you can do in Paredit:
http://pub.gajendra.net/src/paredit-refcard.pdf
Consider the last three or four subsections and ask yourself, how to solve them with touch, gestures and speech. Are you going to drag some kind of symbolic representation of "tree node" to move a bunch elements into a sublevel? How about splitting a node into two at a particular point? Joining them together? Repeating this (or a more complex transformation) action 20 times in a row (that's what a decent editor has keyboard macros for)? Searching in code for a particular substring?
Sure, it can be done with the modes of input you're advocating, but I doubt it can be done in an efficient way that would still resemble normal speech and interaction. There are stories on the Internet of blind programmers using Emacs who can achieve comparable speed to sighted ones. This usually involves using voice pitch and style as a modifier, and also using short sounds for more complex operations. Like "ugh" for "function" and "barph" for "public class", etc. So yeah, with enough trickery it can be done. But the question is - unless you can't use the screen and the keyboard, why do it?
> Like in a DOM? Easily: grab it and move it, just like you do it in DevTools today, except with your hands rather than a mouse.
DevTools are a bad example for this task. Using keyboard is much faster and more convenient than mouse. C.f. Paredit.
Totally agreed. Theoretically, you should just be able to gesture a list with your hands and say "joe mary dave" and the software knows from your tone that's three items and not one.
I don't know that much about lisp and s-expressions asides from that it can edit it's own AST. That's not a way of avoiding the question, it's just my own lack of experience.
> Are you going to drag some kind of symbolic representation of "tree node" to move a bunch elements into a sublevel?
Yes, I already think of a tree of blocks/scopes when editing code with a keyboard, visualising that seems reasonable.
> Repeating this (or a more complex transformation) action 20 times in a row (that's what a decent editor has keyboard macros for).
Here's the kind of stuff I use an AST for: finding function declarations and making them function expressions. I imagine that would be (something to switch modes) "find function declarations and make them function expressions". Likewise "rename all instances of 'res' to 'result'" with either tone or placement to indicate the variable names. More complex operations on the doc would be very similar to complex operations in the doc.
> Searching in code for a particular substring?
Easy. Have a gesture or tone that makes 'search' a word for operating on the document, not in it.
> Sure, it can be done with the modes of input you're advocating, but I doubt it can be done in an efficient way that would still resemble normal speech and interaction.
Yep, I don't think it would still resemble normal speech and interaction either, the same way reading code aloud doesn't. It would however be easier to learn, removing the need to type efficiently as well as the (somewhat orthogonal) current unnecessary ability to create syntax errors.
> DevTools are a bad example for this task. Using keyboard is much faster and more convenient than mouse. C.f. Paredit.
Not sure if I'm reading you correctly here: typing DOM methods in a keyboard in devtools is obviously slower than a single drag and drop operation. Using hands to do it directly is obviously even faster with the mouse.
Stepping back a little: I guess some people assume speech and gestures won't get significantly better, I assume they will.
favouritePeople is Person list, name Joe age 32, Mary 23, Steve 64, end
Using tone to separate entries, but you could use a secondary gesture for that instead. Also some pattern matching.
Unless AI advances considerably. For years I've imagined myself talking to the small specialized AI living in my computer, giving it instructions that it would translate to code...
Writing software is about telling a blazingly fast, literal, moron what to do. The ambiguity inherent in natural language is not a good way of telling such a thing what to do.
I think I have discovered the source of your disagreement.
Tablets and phones are consumption. You can't do any serious work on them - development included.
This is why laptops and computers have stuck around in spite of the proliferation of cheap, tiny, elegant consumption devices.
So no, I don't think laptops and computers will go away for non-nerds, just for people who don't produce anything.