a minor rant but it would've been nice to see blog.nodejs.org powered by nodejs
It's a solved problem. No need to reinvent the wheel in node.js. My company has also recently dropped our custom blog (C#) and are going with WordPress (PHP).
Node.js has a new website
21–28 of 28 posts
Re: Node.js has a new website
#22Earlier quoted context omitted.
A blog engine is the type of CRUD app that node is not well suited for. Just because they could write it in node, doesn't mean that they should.
Why wouldn't node be suited for a "CRUD app"? I think it's not using node simply because what they have already works perfectly fine, there's no need to change it to a node powered system. Most of the main developers are also concentrating on actually developing node and probably have no time to do the switch.
"""Why wouldn't node be suited for a "CRUD app"? """
Because all the design decisions for node.js weren't about making CRUD apps.
Re: Node.js has a new website
#23Font is too small.
Re: Node.js has a new website
#24the code blocks on the front are kinda painful to read, they need some padding/margin and/or border to differentiate them between the paragraphs, the rest is nice though!
Re: Node.js has a new website
#25Earlier quoted context omitted.
Yeah... the fact that the only navigation links, aside from download, are below the fold completely destroys the usability of the site.
It's not a website. It's a landing page for people who are looking into node.js.
I think that is a bit of a misnomer. A landing page is like this - http://files.www.newmediacampaigns.com/posts/randoms/netflix...
IE a (typically) single page, completly above the fold, alternative to the official page of the site used as the page people see when they come via an ad or offer.
This is just a typical homepage for a computer language (listing accolades, testimonials, downloads, hello world, etc). It is much more featured filled than a landing page.
It just has poorer navigation than before.
Re: Node.js has a new website
#26Earlier quoted context omitted.
Why wouldn't node be suited for a "CRUD app"? I think it's not using node simply because what they have already works perfectly fine, there's no need to change it to a node powered system. Most of the main developers are also concentrating on actually developing node and probably have no time to do the switch.
"""Why wouldn't node be suited for a "CRUD app"? """ Because all the design decisions for node.js weren't about making CRUD apps.
I'm just wondering what design decisions exactly? How is Express or the other node.js frameworks any different from building an MVC app in Flask or some other conventionless framework?
Re: Node.js has a new website
#27I like the colors :D
Re: Node.js has a new website
#28I liked it when the 6-line web server code was the first thing you saw. This is what originally sucked me in to node.js. You think, "Woah! A web server in JavaScript, and it's that simple." I guess I can scroll down to the docs, but it would be nice if nodejs.org/docs redirected to the most recent version and linked to older ones. A memorable URL for docs is nice. e.g. docs.jquery.com When I go to a new project's sit…
I think the "In the industry" sections shows the user that Node is something awesome and stable, which is reassuring to new developers. Chances are if you're hitting the homepage you're a new-comer to Node, existing developers may be likely first hitting the site in the API docs from a Google search.