In most computer nowadays you cannot code (tables and smartphones), are computers doomed to be an expensive tool for few "nerd" ? What will be the impact on computer literacy ?
In most computer nowadays you cannot code (tables and smartphones), are computers doomed to be an expensive tool for few "nerd" ? What will be the impact on computer literacy ?
http://boingboing.net/2012/08/23/civilwar.html
http://boingboing.net/2012/01/10/lockdown.html
...and RMS predicted this almost 20 years ago:
http://www.gnu.org/philosophy/right-to-read.en.html
I think the rise of P2P, file sharing, and the openness of the Internet in the last decade significantly narrowed the developer-user gap; and it's been growing since then, motivated by corporations' desire to maintain control over their users.
I think that's only one factor, and not a majority one.
Most users don't want to have to deal with "how it works". They want a simple, easy to use tool that works reliably... And they want to call someone to "fix it" when it "breaks". That's how it works with plumbing, cars, landline phones, stereo components, televisions, and all the electronics they've ever used.
The exceptions are computers and some smartphones, which can present cryptic error messages, have weird things in their settings, and generally make a "dumb user" feel out of their element. Think about the confusion users feel when confronted with a funny noise in their car. "I'm not a mechanic, what does that noise mean?" is no different from "I'm not a computer person, what does that error mean?" What's more, the meaning of the question is not "what, mechanically/electrically, is at fault?" It is "how much time/money will it cost to get it fixed?"
It's not just a small preference, either - the height of luxury are "push button" services that "just work". Go to a high end hotel, and your room phone has just one button. Top end consumer products of all sorts struggle to be an easy-to-use "appliance". A dumbed down user interface without developer tools is user preference, it's status, it's customer comfort and pride, all tied into one.
So 99% of companies end up designing their interfaces like that hotel phone: http://salestores.com/stores/images/images_747/IPN330091.jpg
IMO the most impressive thing about OSX is how well it supports both audiences: it feels like a push-button, high luxury, comfortable, easy device to my mother. But under the hood there are great logs and a solid BSD-based operating system model. It comes prepackaged with a lot of developer tools, hidden in a place where I would look right away, but my mother would never notice.
Sure, some companies use software to limit and control their customers (cough cough Sony), usually with sharp legal/lobbyist teeth to enforce that control. But 99% of companies out there just want to make their users feel comfortable, high status, and competent to use their device.
While I agree with RMS that this split is inevitable, I don't believe it's about control. It's about two distinct market segments: auto enthusiasts who want control over the torque settings in their high end car, and people who just want a car that fucking works. Chefs who want sector-by-sector control over their oven's heating profile, and people who just want to be able to cook a fucking roast without burning it.
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.
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 will bet you £100 that we won't be programming by speech and gestures in even 25 years time as the disadvantages are enormous.
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.
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.
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.
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.
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.
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.
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.
A more specialized scenario: I was copy/pasting stuff to a colleague in the same room yesterday.
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.
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.
No. Because of the Glorious PC Master Race - mods, trainers, hacks, overlays etc - these all need dev and root access.
Btw- game modding, cracking, save game editing etc - are the best gateway drugs towards full blown IT career.
http://www.ubuntu.com/tablet/developers https://plus.google.com/u/0/105864202742705090915/posts/jNvZ...
Hell, even lack of window management in iOS/Android systems is making UX much more easier to understand for majority of users I know. My granddad, who was an excellent mechanical engineer, have been using computers for the last 20 years, and he still struggles with click/double-click distinction.
Only if you want to keep them illiterate, which companies are more than happy to do since it means they can be more easily persuaded and dependent consumers.
Somehow nobody complains that cars, or microwave ovens are too complicated. Everybody knows they have to learn how to use them - either through a training course or just by reading a manual.
Are my parents or family interested in password managers ? Heck no... why should they, because the browser will remember stuff for them.
Permissions ? You have to be joking... they want to read their email or draw a picture.
Computers are there to make life easy - they're convenience tools (for the mass market). If people have to understand them more than switch them on a press a few buttons, they've failed.
It's not the IT world... for years, we were outcast as geeks and nerds (they were insults in the past). It's that the average person doesn't want (or need) to know about this.
How many people service their own car ?
True, but there is still some learning to do. The only way you can reduce it (barring solving general AI and making a system that actually knows what you mean) is by reducing the things a device/piece of software can do. That's what the industry is doing - cutting out features, turning software into shiny toys. Because from the market perspective, is enough that the people sign up / buy the product - it doesn't have to be actually useful.
That's why software for professionals look complicated - because there the company actually has to make a useful tool. This state of thing is sadly a big loss for humanity - if the only way to make stuff "sexy" is to make it barely useful, then the general population is in fact missing out on all the amazing things technology could allow.
(And the tech people are missing out too, because they're too small a niche. It's more profitable to target the masses instead. That's why all mobile devices are getting dumber.)
> It's not the IT world... for years, we were outcast as geeks and nerds (they were insults in the past). It's that the average person doesn't want (or need) to know about this.
Oh but it is the IT world. We've been invaded by the "normal people" and we've lost the battle. Most programmers employed nowadays are not much different from your average non-tech person, and have nowhere near the technical expertise you'd associate with the "geek and nerds" of the past.
> How many people service their own car ?
I'm not talking about servicing, but about driving. You have to spent 30+ hours in training to be allowed to drive on a public road. Nobody complains because people understand that to use the car well, you have to learn how to do it.
If I had to read a manual to operate my microwave, toaster, coffee machine, sandwich maker, oven, games console, etc etc, I'd just get rid of them.
I say class, because most tosters work the same, most microwaves work the same, most smartphones work the same and most 3D modelling programs work the same too. But you have to get that first little bit of knowledge about the class of tools from somewhere, even if from your own experimentation. Humans aren't born with knowledge how to use technology.
You sound like a guy who teaches his kid to swim by throwing him in the stormy sea.
I don't think anyone ever has.
Have you tried teaching him that? I highly doubt an old person, especially one with engineering background, will have trouble with understanding the distinction if someone bothers explaining it to them.
Or in general - it's surprising how much non-tech people can understand about technology if someone bothers to sit down with them and explain the concepts to them. Usually the reason they don't learn this stuff themselves is the typical human impulse of "if I haven't figured it out in 3 seconds flat, it's too difficult and I won't understand it".
So here's just a few ways you can code on Android:
QPython: https://play.google.com/store/apps/details?id=com.hipipal.qp...
AIDE (Java): https://play.google.com/store/apps/details?id=com.aide.ui&hl...
Terminal IDE: https://play.google.com/store/apps/details?id=com.spartacusr...
If all else fails, just deploy debian with Linux Deploy: https://play.google.com/store/apps/details?id=ru.meefik.linu...
If desktops become more expensive, it'll just mean people are more motivated to make tools like this. Android phones and tablets are basically treated as cheap commodities and there's an extremely competitive market for them, if anything, the entry price has gone down.
Now, admittedly I'm not sure how this situation is on iOS, but maybe someone could link similar tools on there?
For one thing, a Raspberry Pi is more powerful than the Sinclair ZX-81, Apple IIe, or Atari 400/800 I had access to back then, and much cheaper.
The tablet I currently own cost me $80 and came with a C# compiler preinstalled! (Maybe that's an extreme example: It is a Windows tablet, and Android or iOS only come with JavaScript JIT compilers preinstalled.)
During one weekend in which my only options were android devices, I was pleasantly surprised by the packages available in termux. With tmux, git, and ssh installed, I mounted the tablet at the right height and connected a quality keyboard via usb. I actually forgot that I was coding on a tablet!
The phone experience was far more sensitive to maintaining good posture throughout, but being strongly incentivized to keep good posture actually made the experience more pleasant in a way. However, this particular phone was around 1280x720 I believe - seeing individual pixels again, and being pixel-limited (not physical size limited) in the use of panes in tmux were the only facets I found truly unpleasant.
I'm eager to try coding with a high res VR headset.
While being able to play around with Project Euler can be fun, it amounts to "I can run a Turing-machine simulator" and doesn't represent anything more than a tiny fraction of what people want to do with computers when they say they want to "code". You may as well be playing one of the numerous puzzle games that involve much of the same concepts.
To use your iPod Touch as an example, if it were more like a traditional desktop computer, you would also be able to do things like write an app to manage your music playlists.
The tablet I currently own cost me $80 and came with a C# compiler preinstalled! (Maybe that's an extreme example: It is a Windows tablet, and Android or iOS only come with JavaScript JIT compilers preinstalled.)
Not surprising if it's a Windows tablet based on the PC architecture - those are far closer to the traditional desktop than iDevices and Androids. If by C# compiler you're referring to the one that comes with the .NET framework, that's been there since the first versions; pity it's not so well known with MS trying to push VS as hard as possible...
Yes, you can. See https://play.google.com/store/apps/details?id=com.aide.ui
It seems like a vast majority of software developers, consciously or not, do not wish for software development to improve beyond a certain point as they fear it would become too accessible and therefore lower the value of their skills. The truth is that we actively make programming as difficult as possible, and everybody loses. I can understand that writing code as text would make sense 50 years ago, but there is no excuse for this today.
Consumer UI is now reaching the 3rd dimension with AR and VR, while software development is stuck in the 1st dimension. A long linear piece of string. It is difficult to believe that those who have the power to create great consumer UX are completely blind to improving their own. Software development has some of the worst UX ever.
The solution to all of those issues has been known for a while, and is dead simple to understand. We need to create a new communication platform, powered by ideas from logic programming and the semantic web. Think of it as 2 huge semantic knowledge graphs, the first describing the real state of the world, the second describing the ideal state of the world. Build a UI on top of it (which should feel more like a graph-oriented Excel than RDF/Prolog) to let people, agents and IoT devices communicate "what is" and "what should be". Then, all it takes is an inference algorithm that can match providers with seekers, get them to commit to some set of world changes (through some sort of contract), and let people manage and track the commitments/tasks they're expected to get done. That's it, that replaces 80% of software needs. Thank you very much.
Knowledge Graph -> Semantic Marketplace -> Smart Contracts -> Task Management
Perhaps I should take this opportunity to make that happen.