Earlier quoted context omitted.
We might not want the hassle of dealing with files and folders all the time, but I sometimes worry that a new generation of "programmers" will emerge who have no understanding of how the underlying filesystem works.
Why is that a bad thing (aside from the "I had to walk uphill both ways through the snow" aspect)? A significant portion of this generation doesn't understand CPUs and buses. They wouldn't have been able to write anything remotely complex 20 years ago). That doesn't seem to be hindering things much, though. There are still system programmers out there who dive into it, but our abstractions have gotten good enough tha…
Light Table - a new IDE concept
101–110 of 315 posts
Re: Light Table - a new IDE concept
#102Am I the only one who wants to see multiple, proportional fonts in editors? Sure, I want to keep the methods themselves in monospaced font, but can't I have the method declaration in a larger size, and comments in a proportional serif? There is a wealth of design experience out there in communicating things better and more quickly with typography, so why do we not take advantage of that in our IDEs?
Re: Light Table - a new IDE concept
#103I'm interested because when I played with Clojure I didn't feel like you can make quick prototypes with it.
Re: Light Table - a new IDE concept
#104One question though: Where do you store all your functions? Do you use a db or something like that? Or just one flat file or file/func?
Re: Light Table - a new IDE concept
#105How long did it take you to build this prototype? I'm interested because when I played with Clojure I didn't feel like you can make quick prototypes with it.
Re: Light Table - a new IDE concept
#106Isn't it ironic that this is posted on a site that does startup funding and the comments are "please put this on kickstarter" not "please apply for Y Combinator"? Is it possible that Kickstarter will disrupt Y combinator style startup funding? If we (the consumers) can bypass the investors and pay for what we want, why do we need the startup gatekeepers? Obviously this wouldn't work for all startups but a large porti…
Re: Light Table - a new IDE concept
#107Re: Light Table - a new IDE concept
#108I can't get my hands on this soon enough. It makes so much sense: we're moving away from the files and folders metaphor everywhere, so why not in the IDE too?
We might not want the hassle of dealing with files and folders all the time, but I sometimes worry that a new generation of "programmers" will emerge who have no understanding of how the underlying filesystem works.
First, an explosion in the power of the hardware being programmed on has made people think less of the efficiency that coding once required and more about getting something done. This feels sloppy, but can be a good starting point for iteration (+1 buzzword).
Similarly, the number of tools out there to get someone (like me) started on programming has EXPLODED in recent years. This results in a lot more people at least starting to code in whatever limited way.
I think it's naïve to think that people who start to code "the simple way" will always code that way. If they're actually pursuing as a career, they will always be digging more and trying to find out why something works a particular way.
Not seeing the filesystem/structure at first glance also isn't necessarily the same as NEVER looking at it or being interested in how the pieces all fit together. it simply means you don't have to worry about it RIGHT NOW.
Re: Light Table - a new IDE concept
#109Earlier quoted context omitted.
I can think of a few reasons, though they may not be the ones he has in mind. There's the fact that you're dealing with cell references rather than variable names, so all of your expressions look like ($K4 - $S$1) rather than (principal - payment). There's the fact that the IDE you're working in is trash -- rather than a text file with carefully indented parenthetical statements, it's a single line text field. Sort o…
Those reasons are spot on. Also errors are difficult to track down and spreadsheets have horrible code re-use.
You get compiler errors about as helpful as trying to debug C++ macros -- namely, something is wrong with this big glob of code, but it ain't gonna tell you what or where.
Re: Light Table - a new IDE concept
#110Am I the only one who wants to see multiple, proportional fonts in editors? Sure, I want to keep the methods themselves in monospaced font, but can't I have the method declaration in a larger size, and comments in a proportional serif? There is a wealth of design experience out there in communicating things better and more quickly with typography, so why do we not take advantage of that in our IDEs?