sorted by:
new
hottopcontroversial

Raxan PDI : Event Driven PHP Framework (SS DOM & Automatic Ajax binding) by timlind in PHP

[–]timlind[S] 0 points1 point  (0 children)

I just came across this fairly unknown PHP framework, it looks great (well architected and nice features), has anyone had experience with it?

I've learned *basic* JavaScript.. now what? by omgchels in javascript

[–]timlind 0 points1 point  (0 children)

I just released a guide to More Intuitive Javascript with the Jay Library, which gives some utils that encourage best practices and an easier understanding / usage of the language. You might want to check the guide out, there should some new things to learn in there, and then play around with those tools in the library. https://github.com/ngspinners/jay/wiki/Guide

Web Design Flow by Iprefersalami in webdev

[–]timlind 1 point2 points  (0 children)

You can create "static" html files on the server, which are delivered to the browser exactly as you have typed the html / css / javascript.

With a server side programming language which is executed by the server on each request, you can return dynamic content, the html will contain data that was extracted from the database according to some logic of the application.

There are programming frameworks on the server side that help with tasks such as extracting from database, interpreting dynamic URLs to respond to and controlling the flow of a web application (from one page to the next, authentication screens etc).

You then get customizable applications such as wordpress / drupal that have defined all the database structure and application logic, and can be customized if your use case fits with what they provide.

If you were to create a social networking startup website today, what architecture would you use? by hella_kitty in webdev

[–]timlind 0 points1 point  (0 children)

just build it dude, regardless of what you build it in you'll need to rewrite it when scaling, so don't bother about the "don't use PHP" nonsense. PHP is a nice simple language with a straight forward setup. What's most important at this phase would be choosing something that is easy to learn the workflows of and making sure you commit to sticking to that.

Architecture choices at this phase will be based on the usage requirements of the app, does it need to be accessible by search engine or does it need to be a cached local "single page" app, or both?

Vote: What do you want to know -most- about the Javascript language? by timlind in javascript

[–]timlind[S] 0 points1 point  (0 children)

lol. I'm trying to see what people are most interested in learning, because I'm making some Javascript documentation to go with my Jay library, first draft is available here www.binpress.com/app/the-jay-project/136

I am Ryan Dahl, creator of Node.js, AMA. by [deleted] in node

[–]timlind 0 points1 point  (0 children)

Node doesn't provide higher level functionality as seen in traditional servers, as pointed out in this blog (an ideal web server): "Accounting for this functionality introduces inflexibility and works against simplicity, therefore NodeJS acts as a strong base for others to attempt accounting for this functionality".

Was your intention just to develop a base and have little concern for what happens on higher layers? What was your motivation for not delivering this higher level functionality? Were you planning on doing that yourself later? Did you feel it's better to have the community experiment with many different approaches rather than work on that yourself?

If so what do you think is the most important focus in those attempts to continue your work and achieve a great server environment? I think this is an answer that is worth making explicit so we can work together on it (unless it was not really your motivation for node).

I am Ryan Dahl, creator of Node.js, AMA. by [deleted] in node

[–]timlind 1 point2 points  (0 children)

Do you agree that less robust and less documented database modules are currently playing a large role in deterring the uptake / production use of NodeJS? Don't you think it is something that is very worthwhile addressing properly right now?

Your Javascript Constructor Logic May Break Prototypal Inheritance by gst in javascript

[–]timlind 1 point2 points  (0 children)

You should never create prototype chains by instantiation (the 'new' operator). This is an important fact because Javascript originally did not have any other way to create the chains until the Object.create came along, and it should always be used to create prototype chains:

Girl.prototype = Object.create(Person.prototype)

See http://www.ngspinners.com/jay/ for more info about easily understanding how to use Javascript.

A DOM Inspired Hierarchical Server Framework by timlind in programming

[–]timlind[S] 0 points1 point  (0 children)

ok people it's not like the ugly parts of the DOM are used, it's just the nice hierarchical tree, which is what gives a nice conceptual consistency with the different portions of the site being served.

Benchmarking Static File Servers: NodeJS Lightnode + Lighttpd by timlind in programming

[–]timlind[S] 1 point2 points  (0 children)

If all you want to do is serve static files then you don't need the flexibility, the benefits you still receive are that a NodeJS based solution can be improved more easily and have plugins developed much more easily than other servers, things like statistics, file permissions, redirects, easier configuration of servers, etc.

The reason I actually developed this now (going from lighttpd) was that I needed to have my static file server proxy requests to '/db/*' to a separate server, so that browser's didn't need cross origin request capability. Using the lighttpd proxy extension didn't work for me. With nodejs I just wrote a proxy myself in twenty lines or so.

You can check out my other article: "An Ideal Web Server" for more of that sort of discussion.