I don't agree with this call to see the code, or remain silent. Like the OP said, there's nothing revolutionary about it. What is everyone expecting to find - whether it's MVC or MVVM? How de-coupled the objects are? A video is way more informative at this point than abstract code. I personally probably wouldn't have bothered deploying the code without more info. Don't get me wrong I'm not against seeing the code, but it's not fundamental to what the OP is trying to achieve or communicate. If this was 2004 and the video was of an iPhone prototype, I doubt everyone would discredit it because the hardware schematics weren't released. The whole "controversy" is simply a reaction to the OP trying to build a coalition by being divisive and condescending. Some perceive that as strength, others as naivety, I think that's all there is to it.
On Thu, Oct 11, 2012 at 1:29 PM, Ted Young <t...@radicaldesigns.org> wrote: > > I am mainly using this thing as blackmail to get people to be interested > in being my friend. I want to do some real world community building, and > something like this will go a long way to get a cooperative business up and > running. > > Furthermore... you do realize that asking another programmer to "just show > me your code" is exactly the same as asking a girl to "just show me your > breasts", right? I mean, I have nothing against it in principle, but, my > god... I hardly know ye!!! > > > Well, sharing code is sort of the main form of currency around web > communities these days. If you look at the people in the node community > that other people gravitate towards ( and would jump at a chance to work > with ), they all produce quite a bit of useful code that they share with > the community. And if I'm looking at someone as a technical cofounder, > reading their code and seeing how they create working, production-ready > libraries are at the top of my list. > > So anyways… that's how you do it! Regarding this particular project, I > would say many of the people involved in node are people who are interested > in rich-client browser apps. The "browser as OS" is an idea that's been > around for years now, and many people are already working on it in some > form[1]. However, one of the designs that's been tried and rejected along > the way is the idea that a browser OS would just be a re-implementation of > a desktop GUI, like macOS, only running on a javascript VM with a "cloud" > back-end. And some design principals, like a desktop with drag-and-drop, > are already going away in general as we move towards mouseless computing. > But if out of this project you came up with, say, an improvement on > drag-and-drop, or a library that was helpful to people who are building js > app's other than a desktop-like interface, people would be interested in > those pieces and would give you useful feedback. So breaking up your code > into open source libraries and sharing them is super helpful! > > BTW, a good short treatise, that was written before the current web boom > but predicts many of it's features, is "In the Beginning… Was the Command > Line" by Neal Stephenson[2]. Very short, definitely worth the read. > > Ted > > [1] http://www.chromium.org/chromium-os for the full-court-press version > of this > [2] http://en.wikipedia.org/wiki/In_the_Beginning..._Was_the_Command_Line > > > On Friday, October 5, 2012 5:56:26 PM UTC-4, sotonin wrote: >> >> Code.... post it.... else Zzzz >> >> On Fri, Oct 5, 2012 at 4:37 PM, Dennis Kane <dka...@gmail.com> wrote: >> >>> See the newest features here--> http://www.youtube.** >>> com/watch?v=pF_2DwueGLM <http://www.youtube.com/watch?v=pF_2DwueGLM> >>> >>> The current version of the program now includes drag and drop >>> functionality of text files from the native desktop straight into the >>> browser desktop or (any of the subfolders). The difference between my drag >>> and drop and all the HTML5 demos that you see on the web is that the >>> dropped files immediately become icons that are integrated into the program. >>> >>> I will soon start working on getting multimedia icons/files working, so >>> you'll be able to drop those directly in too. Then I will probably do a >>> very basic kind of image editing demo that will allow you to change >>> individual pixels or some such nonsense. But I don't want to get bogged >>> down in the details of any particular application, because I always want to >>> stay focused on the big picture of creating a totally powerful and >>> intuitive way to organize our online lives. >>> >>> Anyway, I know I am quite a controversial figure here, but there should >>> be no controversy that this thing is just about ready for prime time. I >>> really do need to start getting interested people on board who would like >>> to help me push the web forward. The basic mission statement for the >>> venture will basically be that the "old web" (HTML4/version 1.0) is dead >>> and gone. If anyone calls in search of help on their Flintstone era <html> >>> documents with all of their <a href> and <div> tags laying about, we'll >>> just point them in an entirely new direction. If they still insist on >>> doing things the old way, we'll just hang up on them… This thing is all >>> about the future! >>> >>> We can easily develop libraries of high-level interface widgets that >>> people just need to attach event listeners to. There will be no angle >>> brackets in sight! <hand><coded><html><markup></** >>> is></so></last></millenium>! >>> >>> Come one, come all, for the thrill of your lives :) >>> >>> >>> On Tuesday, September 25, 2012 7:36:37 PM UTC-4, Dennis Kane wrote: >>> >>>> I was thinking of just responding to this old >>>> thread<https://groups.google.com/forum/?fromgroups=#!topic/nodejs/bEhSbsm24Y4>, >>>> in which I talk about the browser based Desktop that I've been working on, >>>> but the new thing I've been doing for the past week is so superior that I >>>> thought it deserved a completely new thead. By the way, I know this forum >>>> is all about server side Javascript, but there is not really any serious >>>> place one can go on the web that talks about the client side. Besides, >>>> with socket.io & websockets... I don't really make much of a >>>> distinction between client and server anymore. I just know that there's no >>>> reason to do a document.getElementById() call in node :) >>>> >>>> This new thing is a totally shocking clone of OS X. I knew I was going >>>> to have to start over from the ground up, because my previous code base was >>>> so sh*tty, haha! I have really been concentrating on getting a nice, tight >>>> little API that developers will positively drool over. I don't want to >>>> make this thing publicly available for many reasons... but you can check >>>> out a youtube vid >>>> (http://www.youtube.com/watch?****v=Tq_W19QokXk<http://www.youtube.com/watch?v=Tq_W19QokXk>) >>>> that >>>> shows it in action, and I still have my same old crappy prototype online at >>>> http://luvluvluv.info. Well, hopefully this is proof that I am able >>>> to do some cool stuff, and hopefully summa yous will want to start being my >>>> friend now, LOL!!! >>>> >>>> And get this... the current, uncompressed js file size is only 54kb! >>>> >>> >>> -- >>> Job Board: http://jobs.nodejs.org/ >>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List-* >>> *Posting-Guidelines<https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines> >>> You received this message because you are subscribed to the Google >>> Groups "nodejs" group. >>> To post to this group, send email to nod...@googlegroups.com >>> To unsubscribe from this group, send email to >>> nodejs+un...@**googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/**group/nodejs?hl=en?hl=en<http://groups.google.com/group/nodejs?hl=en?hl=en> >>> >> >> > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
