tag:blogger.com,1999:blog-6894866515532737257.comments2024-03-10T00:10:08.312-08:00Probably Overthinking ItAllen Downeyhttp://www.blogger.com/profile/01633071333405221858noreply@blogger.comBlogger783125tag:blogger.com,1999:blog-6894866515532737257.post-14374882967623386762021-11-09T11:05:38.803-08:002021-11-09T11:05:38.803-08:00Hi Allen - thank you for this article! I'm tr...Hi Allen - thank you for this article! I'm trying to convert to bayesian b/c it looks so much more useful and practical, but I think this frequent objection mentioned in the Nature article sums up one of my biggest discomforts. Curious how you think about this. Is there any possible negative effect of using a uniform prior if in reality the distribution is quite different (although even that kind of blows my mind since in reality it's a point value, which i guess is covered in this first objection Nature covers above the one i paste below).<br /><br />"Second, Bayesian methods require specifying prior probability distributions, which are often themselves unknown. Bayesian analyses generally assume so-called 'uninformative' (often uniform) priors in such cases. Introducing subjective assumptions into an inference is unpalatable to some statisticians. The usual counterargument is that non-Bayesian methods make comparable assumptions implicitly, and it's probably better to have one's assumptions out in the open."Scott Edwardshttps://www.blogger.com/profile/09648322596981621100noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-84594326998038811402018-05-11T05:58:55.299-07:002018-05-11T05:58:55.299-07:00Hi Allen,
I have read and purchased Think DSP, Th...Hi Allen,<br /><br />I have read and purchased Think DSP, Think Stats and Think Bayes (in that order). You have done an excellent job in all three volumes.<br />Your Python classes make working in these subjects so much eaiser. In Think Bayes the PMF class was an eye opener.<br />As someone who always wanted to learn about Probability models - when I read the Python PMF class "all the light bulbs went on".<br />I remember studying Probability from text books - A Probability Mass function had no concerte concept - now (thanks to you) they do.<br />So does PDF, KDE and so on. Your one statement "Think of a PMF as a fundemental unit of computation" speaks volumes.<br />Thanks You for writing these books and Software.<br /><br />Please do not stop - Can't wait for Volume 2 :-)<br /><br />My Thoughts...<br /><br />DennisDennishttps://www.blogger.com/profile/09949443295298166463noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-14547124094209790722018-04-24T14:12:28.831-07:002018-04-24T14:12:28.831-07:00Thank you for the clarification - I misinterpreted...Thank you for the clarification - I misinterpreted twenties as the age, instead of the decade of birth.Anonymoushttps://www.blogger.com/profile/00027883649876487686noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-66855028646770841272018-04-24T13:57:13.538-07:002018-04-24T13:57:13.538-07:00The cells you are looking at are a single run, so ...The cells you are looking at are a single run, so they'll be different every time the notebook runs. The coefficient in Out[98] is a log odds ratio. The offset in Out[103] is a difference in percentage points. The median of that difference is -9.8 percentage points, as shown in Out[108].<br />Allen Downeyhttps://www.blogger.com/profile/01633071333405221858noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-13957453592875009202018-04-24T13:46:58.957-07:002018-04-24T13:46:58.957-07:00I'm having a little trouble connecting the dot...I'm having a little trouble connecting the dots between your comment "people born in the 1990s are 10 points less likely" and the ipynb that shows the coefficient for "twenties" as -0.0236 at Out[98] which eventually resulted in an offset of -0.473421 at Out[103]. I know you re-sampled to get to the confidence intervals, but it also seems odd that the twenties interval was about as wide as the other ages despite having a z score of -0.531 in the original regression and the thinnest base at about 500 respondents.<br /><br />Regardless of my slow understanding of this, I also worry that the GSS is not a good way to measure the political trends of all ages. Yougov or Google search trends may have less bias because they are not administered or done in-person, in private with less social norm pressure. Anonymoushttps://www.blogger.com/profile/00027883649876487686noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-83235214439099870682018-03-18T06:36:22.567-07:002018-03-18T06:36:22.567-07:00Troubleshooting can be frustrating. "How do I...Troubleshooting can be frustrating. "How do I solve a problem I don't know how to solve? How do I find the answer to a question I didn't know to ask?" But today it basically comes down to learning how to use google and stack exchange effectively and a healthy dose of curiousity. Teach those skills first, or very early. But yeah that first step in programming can be either motivating or demotivating depending on how it goes. Javascript in the browser is a pretty safe place to start if you want to achieve a quick feeling of success and the ability to go where curiousity takes the student in a tight feedback loop.Chrishttps://www.blogger.com/profile/04202161545158735491noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-47616587189556072902018-03-15T08:52:47.872-07:002018-03-15T08:52:47.872-07:00Great question -- that's exactly what I am wor...Great question -- that's exactly what I am working on now. I should have an answer soon!Allen Downeyhttps://www.blogger.com/profile/01633071333405221858noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-59508050202817173882018-03-15T08:39:33.263-07:002018-03-15T08:39:33.263-07:00Having lived in small town/rural environments in t...Having lived in small town/rural environments in the 70's to 90's, and in urban environments from the 90's until now, it is hard for me to disentangle decade from population density based on my own experience. But, I wonder if increasing urbanization impacts the attitudes towards gun control over time. I'm not sure if your dataset has any info on how urban/rural the respondents place of residence is, but if it is available it could show a significant effect.rosshttps://www.blogger.com/profile/02587634589065610863noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-25014222280533961432018-03-13T09:05:06.395-07:002018-03-13T09:05:06.395-07:00Wow - memories. I had the VIC-20 as well, althoug...Wow - memories. I had the VIC-20 as well, although I actually had an old Texas Instruments before that. Remember the cassette deck? I still have some old cassettes spitting out squawks of bytes :-) I also had a $300 dot matrix printer that took 2 days to print out a page.steve2k2https://www.blogger.com/profile/13651154374408208175noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-963453910318744602018-03-01T16:33:07.592-08:002018-03-01T16:33:07.592-08:00I think there will be always certain friction betw...I think there will be always certain friction between programmer and common user interfaces. Even programmers these days do not see everything. I am from 90s and barely wrote a few lines on a 8086 microprocessor, so did not get to learn from the excruciating debugging phases, while my previous generation made a living on these. Surya Kasturihttps://www.blogger.com/profile/07682217935243196654noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-19743579103816433852018-02-27T19:16:28.160-08:002018-02-27T19:16:28.160-08:00LOL.
I started on a VIC20.
I would totally swap wi...LOL.<br />I started on a VIC20.<br />I would totally swap with anyone learning today.<br />Try convincing your parents to spend hundreds of dollars, in 1980's cash, on a C compiler or a machine language cartridge. And hundreds more on books. $40 month for another phone line so you could log into BBS to message a few other programmers without tying up the family's only phone line. Then randomly lose your programs ("magic" peeks and pokes and tedious endless data statements) which were stored on budget audio cassettes you spent your meager allowance on at Kmart. <br /><br />The good old days were not a golden age. Your glasses are stained rosy by age.<br /><br />To your points:<br />1. Every computer sold today has several development environments orders of magnitude easier and more powerful than a C64 prompt preinstalled.<br />2. Yeah, "SYNTAX ERROR" was surely more helpful :) You must have had some OTHER Commodore OS. I had lock ups and mysterious errors. It is always better now.<br />3. Cloud? If it is confusing, skip it. I love Bluemix, but there is a world of things you can program without ever knowing about the cloud.Anonymoushttps://www.blogger.com/profile/03730177947678680397noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-29379546176084512812018-02-26T14:12:17.970-08:002018-02-26T14:12:17.970-08:00When I was learning to code, I had to find hard to...When I was learning to code, I had to find hard to find books on the topic, that were often quite expensive in of themselves. My Parents barely knew what a computer was or what good one was. <br /><br />_"What would anybody ever need a computer in their house for?"_<br /><br />That was the viewpoint of _most adults_ back in the day. <br /><br />The Internet didn't exist. But BBS and 300 baud modems did. I was one of the lucky first to own a 1200 baud modem! My hunger for knowledge led me to acquiring the code that runs those BBS's and run one myself. I wanted to play games and especially games that engaged other real people (computer AI was quite dumb back then...).<br /><br />Those learning to program then didn't grow up with innate computer skills. So new programmers of the day learned about computers as much as they learned about programming them. Not only that, they _built_ the tools they then used to program with. New editors. New languages. New frameworks.<br /><br />But the world of programming was still opaque. You had to go to college to really crack it. Why? Because the Internet didn't yet exist. Open Source didn't yet exist. I spent hours upon hours on Gopher and FTP chasing source code to learn from. My focus was on the very core things that are not taken for granted today. How to do doubly-linked-lists, queues, stacks, sorting algos, memory management. I wrote my own testing suites, my own low-level debugger and hacked on vi, the editor, just to have better tools to build and test with. I even learned Assembler and often traced the assembler generated by my program's compiler to find "my bug" vs. a compiler bug. <br /><br />Who hears about compiler bugs these days?<br /><br />Yup, I'm sorry, but programming today is not harder than when I was learning. Now, the programs you write today....different story. It may be getting harder and harder to come up with great, outstanding ideas that is, what they used to call, "the next killer app" that defines a whole industry and movement like 1-2-3 and Excel. Like Word. Like Amazon. Like Google or Facebook. It's harder to stand out. It's harder to hit a home run.<br /><br />Then again, it's not. Today, you can build something. Build it relatively quickly. Publish it to the App store. List it on websites all around like Product Hunt, TechCrunch, and so on. You can crowd source funding and quickly get mindshare of millions of people with virtually NO budget.<br /><br />If you don't know where to start, you know where to start getting answers. And those answers are, by and large, free to all who care to seek it out. Programming is more accessible to people of all walks of life than ever before. Even my young daughter of six has "programming environments" that lets her put together programs without knowing what a semi-colon is. There are even frameworks now that let you build entire applications that can be deployed to cloud and mobile alike without writing one single line of code.<br /><br />I'm sorry, but learning to program today is easier than ever before on every single front I can think of except one: The spark of an idea that will solve something not yet solved.<br />Michaelhttps://www.blogger.com/profile/08852936844154010496noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-52043942055007100842018-02-23T08:16:42.609-08:002018-02-23T08:16:42.609-08:00I actually believe there is an agenda to keep prog...I actually believe there is an agenda to keep programming elitist, not necessarily by programmers themselves but by those at the top of the pyramid.<br />Computers should be about making life easier, and doing all the hard tedious work for you.<br />Eg, it used to be that I could create a Textbox and give the command Str1$ = Textbox1 + "pie"<br /><br />And the environment would assume, ohh, what's in the textbox must be a string.<br /><br />Alternatively, I could give the command Num1 = Textbox1 * 2.4 <br /><br />And the environment would assume oh, now he's putting numbers in there.<br /><br />Now, very often, these things must be declared beforehand.<br /><br />Another example is machine language or assembler.<br />By default, a very fiddly thing to do, because you're down to the level of putting ones and zeros into registers and accumulators, shifting and adding binary etc.<br />That's a necessarily complicated thing to do.<br /><br />Then you work on a high level language like C++ and it's just as complicated, and I'm left thinking, this is just as <br />complicated and unforgiving as working with a low level language like assembler.<br /><br />I don't think it need be like this for the vast majority of high level programming situations.<br />Old versions of Visual basic used to be easy in this way, up until Version 5 came along.<br />Languages and environments that make it easy, tend to be ignored, two in particular I can think of are REBOL and MIT Appinventor.<br /><br />High level languages should be about making life easier for the programmer and I think in general they don't.<br />OK in the example above. a compiler needs to know whether what it is adding is a string, or a number, this is determined by the use of '$' as per early versions of basic.<br /><br />It ought to be possible for your average shop keeper to write his own code to carry out stock control, or whatever to run his business.<br />Of course, it would be better if software to do this were freely available, so he does not have to re invent the wheel.<br />And there is of course, but it would be nice if programming were not so intimidating for your average shop keeper.<br />There are of course occaisions where complex, deep coding is necessay, scientific projects etc, but for the vast majority of applications, much looser programming environments should be used, eg scratch like applications like MIT's app inventor, Visual Basic, REBOL.<br />Anonymoushttps://www.blogger.com/profile/00187973362353087213noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-62573045513377085472018-02-22T05:36:14.130-08:002018-02-22T05:36:14.130-08:00I don't think anyone is suggesting that people...I don't think anyone is suggesting that people who want to watch cat videos should boot to the command line, or even that anyone should *boot* to the command line. The suggestion is that, in order to learn programming, it either a) helps or b) is essential to be able to *use* the command line.<br /><br />Of my fairly wide range of acquaintance, I don't know anyone who a) can write simple code with some fluency and b) can't use the command line.<br /><br />Just for example, the Software Carpentry training organization starts every course with a morning on how to use the command line.<br /><br />Speaking as a programmier, researcher and teacher, I would say to my students who want to do meaningful analysis on their computer, that zero knowledge of {JS, JQuery, CSS, XML, Angular, bootstrap} would be fine, and a passing familiarity with {HTML, JSON} would likely come their way at some point.Matthew Bretthttps://www.blogger.com/profile/05189707947204391453noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-2319889009829665252018-02-22T02:48:04.007-08:002018-02-22T02:48:04.007-08:00Most people are not interested in programming. Fo...Most people are not interested in programming. Forcing EVERYONE to boot to a command line when only 1% of users actually want or need one is not going to make your operating system popular. Look at Linux, the reason we still haven't seen the "year of linux" is because it's still too complicated for the average user who only wants to get on facebook and watch cat videos. I do agree somewhat with the sentiment of the article, but for different reasons. Back in the day learning to code meant learning one language. Today to do anything meaningful on a computer you need to know several languages (JS, JQuery, CSS, Html, SQL, XML, JSon, Angular, boostrap etc.) Ok, some of those are not programming languages, but you still have to have a solid grasp of them to get things done. The learning curve to get to a "programmer" level was steep before and required a lot of dedication, but today I would say that it's literally a cliff.Unknownhttps://www.blogger.com/profile/11636325109511123041noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-14769835064874965692018-02-20T12:02:20.939-08:002018-02-20T12:02:20.939-08:00> Also, according to this logic, I should take ...> Also, according to this logic, I should take my parents and stick them on a Unix system with no gui so they "learn how to code". Silly.<br /><br />Yes - that is the key and interesting point in this article. It seems so obvious that it's a bad idea, it's just - silly. It's obvious that setting things up in the cloud will make it easier to learn. It is obvious that docker will solve our learners' problems with installation. It's obvious that they should not have think about the architecture computer on which they run their programs.<br /><br />And yet, it may well be wrong. Obvious things are often wrong. <br /><br />Eben Upton made the Raspberry Pi because he noticed that students applying to study computer science at Cambridge had learned much less than their counterparts 10 years before. The new generation lived in a world of ubiquitous computing, and they had learned very little about computing; the previous generation had battled with the BBC Micro, delving deep into its hardware. <br /><br />Look at the official Raspberry Pi guide "our first recommendation for adults and older kids interested in getting started with the Raspberry Pi". Depending on the edition, chapter 1 is "Meet the Raspberry Pi". Chapter 2 is "Linux System Administration".Matthew Bretthttps://www.blogger.com/profile/05189707947204391453noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-21220229692634682512018-02-20T11:04:15.825-08:002018-02-20T11:04:15.825-08:00Thanks for writing this article. Like you my first...Thanks for writing this article. Like you my first computer (a Commodore VIC20) had the built in programming enviroment. Like you, I just used tools as they became available, or was instructed to use them. In other words, I'm just used to the current way of doing things. In many respects, I thought of this as a golden age of programming because of all of the tools and information available. The large number of non-college educated programmers entering the professional programming ranks seems to support my original idea.<br /><br />You're article has made me realize, that for someone coming into this cold, there really is a lot to learn and be familiar with in order to do some simple things. Thank you for making me consider this. <br /><br />Concerning Nick coghlan's point, I agree and disagree. Business (esp small business) will embrace cloud computing given the challenges and costs of setting up and running server hardware. Using the cloud makes so much sense in comparison. However, for someone learning to program, locally available tools are good first step. If you can't do a basic programming locally, how are you going to do it in the cloud?<br /><br />Regards,<br />Mikehalciberhttps://www.blogger.com/profile/10789850839239543045noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-87307425347122566652018-02-20T10:49:03.256-08:002018-02-20T10:49:03.256-08:00Interesting points, wrong conclusions. When I was...Interesting points, wrong conclusions. When I was in high school there wasn't any computer programming classes. Now my high school has a whole department. My nephew is taking mobile programming classes. Cmon, if I had that in high school I could've done so much more.<br /><br />No, there's more available, but there's also much more complexity. There are so many languages and stacks it seems worse, but only if you want to want to know all the different areas. The number of tutorials and sites that help you have let me jump into a new job with new technologies and be productive within months, not years of schooling.<br /><br />Also, according to this logic, I should take my parents and stick them on a Unix system with no gui so they "learn how to code". Silly.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-18402449308141089242018-02-20T07:27:12.775-08:002018-02-20T07:27:12.775-08:00I started programming 40 years ago, in my early tw...I started programming 40 years ago, in my early twenties, writing machine code (i.e. no assembler!) for the Z80 on my NASCOM. There was no one to ask for help, but I had lots of time and I got stuff to work. I still feel the old excitement if I take a peek in the Z80 instruction set manual...<br /><br />Today, everyone wants stuff yesterday, I've learned 6 new languages/frameworks in the last year and Stack Exchange is a godsend to find examples to speed up my programming. Not as exciting, because one no longer feels as though one is doing something relatively unusual, for the first time.<br /><br />So, I guess it's swings and roundabouts. You have to get into using all the tools & help to be productive but it does add to the complexity. However, if it were too easy, everybody would be a programmer, right?Anonymoushttps://www.blogger.com/profile/01047139431565942586noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-49603232453980342052018-02-20T07:08:44.804-08:002018-02-20T07:08:44.804-08:00I learn programming using Atari 800XL by reading p...I learn programming using Atari 800XL by reading programming books and magazines. Today reading is sooo hard that most beginer programers can't do that? Magdahttps://www.blogger.com/profile/09132248280973229336noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-32250811457044751182018-02-20T05:19:39.444-08:002018-02-20T05:19:39.444-08:00More years ago than I care to admit to I learnt to...More years ago than I care to admit to I learnt to write computer programs using a BBC Micro, BBC Basic and the built-in 6502 assembler. The programming environment was almost the same as the command-line and the programs were mostly interpreted so feedback was pretty instant. So far, so straightforward. To make anything interesting happen I had to learn to operate the computer using the user manual provided. This took some time as I built a model in my head of what was going on and built some context for what worked and what didn't. Then I had to learn the syntax and grammar <br />of BBC Basic from the user manual provided. Another learning curve with a great deal of trial and error. For even more interesting things to happen I had to learn (i) what the "operating system" really was (ii) how to manipulate the complex interface between BBC Basic and the operating system. Building expertise does not happen in an intellectual vacuum so during this process I was building all manner of little projects from games to low-level graphics functions to mathematical approximations. Since then I have built my career in software engineering on the foundations of what started out as a hobby by dint of hard work, challenging work projects and continuous self-learning. At no time in this process has it ever been easy to quickly assemble the tools, expertise and domain knowledge to do anything other than the most trivial work. To suggest an easy solution does/should exist to investigate every complex problem without tears seems IMHO to call for the end of progress, innovation and effort. Programming as a tool to investigate difficult and novel problems is not only hard (and the skill hard-won) but always has been and until someone writes the code for Douglas Adams' DeepThought probably always will be.<br />These days I have a pile of domain knowledge across wireless comms, instrumentation, lasers, digital signal processing et. seq. and I usually write embedded software in C and assembler on microprocessors, microcontrollers and DSP processors.<br />Just lately I have gotten interested in massively parallel computing using GPUs and APIs like OpenGL and CUDA and I would like to ask why is it so hard to get all the tools, documentation and expertise into one place before I can get even the simplest shader program to work...?<br />If you are reading this and starting out in software engineering then I hope you have the very best of luck going <br />forward.Anonymoushttps://www.blogger.com/profile/08018383367697259291noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-25456976586989887102018-02-19T23:50:45.956-08:002018-02-19T23:50:45.956-08:00I think the main issues with IDEs for learners, lo...I think the main issues with IDEs for learners, local or cloud, is feature creep. <br /><br />Learners need a one-click install IDE that has very few menu options and does very little. It is easy to work out how to use it because there are very few options to choose from.<br /><br />This is great! But then someone adds another feature; wouldn't it be great of it could also do this too. And that. And another thing. All the developers agree the ID is getting "better", but it is no use as a leaner IDE any more. Before long it has joined the big heap of IDEs out there that put learners off before thy get started.<br />Anonymoushttps://www.blogger.com/profile/05831836227963317919noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-17009429132233933722018-02-19T13:09:05.720-08:002018-02-19T13:09:05.720-08:00Thank you for writing this, it's a very helpfu...Thank you for writing this, it's a very helpful reflection on a very difficult problem.<br /><br />As I was saying to a friend today, I find it very hard to convey my own sense of disconnection when I was being taught (at the time) to run canned programs on a mainframe, and the great difference it made when I realized I could install and run software on my own machine, for the same tasks. It is something to do with ownership, and with the feeling that you have agency, in using your tools. I believe that this effect is more important in the long term, than the pain of persuading people to get the tools. Programming does take a certain amount of courage, to explore and to fail and to feel foolish, at least some of the time.<br /><br />I was convinced by Rich Hickey's exposition of the difference between "easy" and "simple", and the importance of choosing simple instead of easy:<br /><br />https://www.infoq.com/presentations/Simple-Made-EasyMatthew Bretthttps://www.blogger.com/profile/05189707947204391453noreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-90818979029549324422018-02-19T11:09:02.513-08:002018-02-19T11:09:02.513-08:00Interesting viewpoint, but I'm not sure I agre...Interesting viewpoint, but I'm not sure I agree. In response to your three initial points;<br /><br />1. No computer manufacturer I can remember ever installed an SDE. The C64 only worked that way because it lacked a proper operating system (like CP/M). An SDE might have been included with some later operating systems, but most assumed the user was not a programmer. The other problem these days is the extreme fragmentation of programming tools. Back then, you had far fewer language options and generally a language didn't fall out of favor in a couple of years. If you included BASIC, that'd be good enough for most people -- not so with web development, there are a trillion languages/frameworks and most of them only work well for very specific applications. And honestly, if someone can't figure out how to install a development tool of some kind -- I honestly doubt they're going to have much luck developing anything. You have to learn to walk...<br /><br />2. This transition was deliberate -- it was part of making computers easier to use, and while they may obscure the internals, I do believe that GUIs do introduce great efficiencies when implemented properly. Just because you don't start in the "dark place" (as early Windows users called a command prompt) doesn't mean you can't get there. You can develop a ton of things on pretty much every OS from a command line (shell scripts, Powershell, batch files, VB script, etc). <br /><br />3. As you pointed out later on, in many ways cloud computing is a boon for budding programmers. You don't have to install anything. On a great many web pages, you can just right-click and view the source for most of what is going on -- which is something I still do today on misbehaving pages. There are many sites that allow you to write code right on a web page and when your code doesn't work, they'll even explain to you what you did wrong. Never mind the developer console in Chrome. And mobile devices are strictly for consumption. You can't develop on a phone (at least, not in any way that approaches normal programming and/or isn't painful).Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6894866515532737257.post-42688239828361302652018-02-19T07:38:04.876-08:002018-02-19T07:38:04.876-08:00Another problem is that languages added lots of co...Another problem is that languages added lots of convoluted bureaucracy and bookkeeping. Hello world in old basic<br /><br />10 print "hello world"<br /><br />Hello world in Java<br /><br /><br />public class HelloWorld {<br /> public static void main(String[] args) {<br /> System.out.println("Hello, World");<br /> }<br />}<br /><br />Way to complicated for no real reason. Especially since enforcing strict OOP is not even all that useful. There is no reason why main can't just be a top level function or why System.out.println can't just be println.Anonymousnoreply@blogger.com