3 ms·

> non-web developers Sorry, not sure what that means </sarcasm> OK maybe not everything will be a web app, but pretty much everything that isn't some deep dri

> non-web developers Sorry, not sure what that means </sarcasm> OK maybe not everything will be a web app, but pretty much everything that isn't some deep driver-level boot code or embedded firmware is already almost always part of some sort of web app, and the stuff that isn't is pretty much all written in C/C++. When is the last time you wrote a Python program that didn't interact over TCP or equivalent with some other process? And how often was that other process not something at least nominally webby?

alextgordon 15y ago
> When is the last time you wrote a Python program that > didn't interact over TCP or equivalent with some other > process? My last python program was a set of scripts to help me analyze music harmony. Entirely CLI based. Before that? objcfix - a refactoring tool. Again, CLI based. That's not counting the multitude of small scripts I write on a day to day basis. I've written a large amount of Python code, and very little of it interacts with a network. Put it this way: Python was invented in 1991, the same time as the web. It didn't become a good tool for making websites until after 2005 when Django arrived. So, what did people do with it before then, if not make websites? > but pretty much everything that isn't some deep driver- > level boot code or embedded firmware is already almost > always part of some sort of web app, and the stuff that > isn't is pretty much all written in C/C++. This is not the reality we live in. There's: * Games (either written in C++, Objective-C or Java nowadays, plus a bit of Lua) * Big Software: MS Office, Photoshop, Avid, Logic, InDesign, etc. Written in C++ * Scientific Computing: Written in C++, Matlab, Mathematica, Python * Financial Computing: C, C++, Java, and a tiny spot of OCaml. * iPhone/Android Apps: again, Objective-C or Java. * "Enterprise Software", whatever that is. Java. And as you point out, embedded software. Everything around us runs Embedded C. The future is the same as the present: full of a rich and diverse selection of languages.

alextgordon 15y ago

> When is the last time you wrote a Python program that > didn't interact over TCP or equivalent with some other > process? My last python program was a set of scripts to help me analyze music harmony. Entirely CLI based. Before that? objcfix - a refactoring tool. Again, CLI based. That's not counting the multitude of small scripts I write on a day to day basis. I've written a large amount of Python code, and very little of it interacts with a network. Put it this way: Python was invented in 1991, the same time as the web. It didn't become a good tool for making websites until after 2005 when Django arrived. So, what did people do with it before then, if not make websites? > but pretty much everything that isn't some deep driver- > level boot code or embedded firmware is already almost > always part of some sort of web app, and the stuff that > isn't is pretty much all written in C/C++. This is not the reality we live in. There's: * Games (either written in C++, Objective-C or Java nowadays, plus a bit of Lua) * Big Software: MS Office, Photoshop, Avid, Logic, InDesign, etc. Written in C++ * Scientific Computing: Written in C++, Matlab, Mathematica, Python * Financial Computing: C, C++, Java, and a tiny spot of OCaml. * iPhone/Android Apps: again, Objective-C or Java. * "Enterprise Software", whatever that is. Java. And as you point out, embedded software. Everything around us runs Embedded C. The future is the same as the present: full of a rich and diverse selection of languages.