TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Comparing Dynamic and Static Language Approaches to Web Frameworks [pdf]

29 pointsby telemachosabout 13 years ago

3 comments

mahmudabout 13 years ago
Hate to be mean, but this is just waxing poetic over the basics. Author is comparing syntax, froth; no actual productive parts of web development is discussed.<p>I have written web apps in Common Lisp for 2-3 years, and in Java (with Play! Framework) for a year now: routes, templates and form submission are the most <i>standardized</i> parts of all framworks. My Lisp code to do those things is identical to the way it's done in Java.<p>If you want to compare web frameworks start by comparing their database &#38; Model substrates: ORM, migrations, validation .. those are where you will become unstuck. (if you don't consider those an integral part of the web-framework, then we haven nothing to discuss, pedal your big-wheel away)
评论 #3916408 未加载
denshabout 13 years ago
It should have been named "Comparing Rails with Yesod". Even though other dynamic languages are somewhat similar to ruby, it's hard to say that haskell is just another statically typed language. Inclusion of other languages and frameworks would have really improved this talk.
评论 #3914547 未加载
评论 #3914411 未加载
jseimsabout 13 years ago
I found this article pretty light on substance, but I agree with the &#60;tl;dr&#62;:<p>Dynamic languages: faster to write something, less code, no time wasted waiting for compilation, but harder to maintain and a bitch to refactor. Need more unit tests.<p>Static languages: more boilerplate, slower write time, but man it's nice to get compile-time vs. run-time errors...
评论 #3915555 未加载