Entries tagged frameworks in 2013
I think this is a pretty interesting idea—simulating these kind of conditions isn’t easy so I imagine many teams don’t bother. If it was good (really easy to get started with, great control and reporting tools, maybe helped set up the actual tests to replay) and I trusted the service I would definitely consider paying for it.[... 125 words]
My preference is to start by designing the URLs, then roughing out the first version of the database models. Everything else tends to evolve from there.[... 44 words]
Maybe. One of the things I like about Node.js is that the raw abstraction it provides over HTTP is much closer to how the actual protocol works than the abstractions provided many of the more widely used frameworks such as PHP, Django or Rails. That might actually make it an effective learning tool—I’d be interested in hearing from some web developers who learnt Node.js as their first server-side technology.[... 87 words]
Why aren’t there any popular web frameworks in C/C++ even though they are more performance intensive languages?
Because it’s very hard writing secure code in them due to the way they handle memory management, and web applications have an enormous number of potential paths for malicious input. It’s much easier to write secure web application code in a higher level language (which isn’t to say it’s easy at all even then).[... 77 words]
How do I choose between asynchronous web frameworks? My tech group is fairly language agnostic and we’re trying to standardize on some technologies.
Since they are all pretty close to each other and it sounds like your tech group’s skills would support any of them, I would suggest having your tram build a simple prototype in all three so you can compare them for your own particular team and situation.[... 76 words]
Those codebases are all terrifyingly ancient. I suggest taking a look at http://www.discourse.org/ instead which is a much more modern take on forum software.[... 46 words]