31–40 of 228 posts
Starting at the framework end doesn't help me much. Instead I go with the people I have for the project and the things I want to do/validate - and start looking for what gets me progress as quickly as possible.
I (naturally) think that the article's summarily dismissing Haskell is unfortunate. It's probably just the result of poor PR on Haskell's part. Haskell is not only for surpassingly intelligent people, or even optimized for them. If anything, it's the opposite: one of its core tenants is that we're not smart enough to reason about our programs in most languages. Much of the design work focuses on unloading complexity…
I used to be a bench chemist in a pharmaceutical company and the tools we used to develop new drug candidates and the tools we used to put them into mass production were radically different. I don't see why software should be any different. Let Haskell be the proving ground for new ideas and we can cherry pick the best ones for simpler languages later.
If you are still considering PHP frameworks, then your choices are really Symfony or Laravel (maybe Zend at a stretch). Yes, Laravel does have a high "bus factor", but for me personally its the number one choice in terms of ecosystem, features, support and community,
There's a huge and active Laravel community, it's just that Taylor is the benevolent dictator.
If Taylor was hit by a bus, there would be plenty of others who would be willing and capable to take up the baton.
Seems to me pretty remarkable to rule out Laravel on this basis, yet keep CakePHP, ignoring all its other flaws.
I don't know what "MVC" means to this guy, but Wicket's approach is much, much better than any other framework I've used; you build your web pages out of objects, your component hierarchies out of object hierarchies, with actual encapsulation, reusability and composability. If that's not MVC then I don't want to be MVC.
http://en.wikipedia.org/wiki/Comparison_of_web_application_f... has a big fat 'no, modular event driven' in the 'supports MVC' column.
I (naturally) think that the article's summarily dismissing Haskell is unfortunate. It's probably just the result of poor PR on Haskell's part. Haskell is not only for surpassingly intelligent people, or even optimized for them. If anything, it's the opposite: one of its core tenants is that we're not smart enough to reason about our programs in most languages. Much of the design work focuses on unloading complexity…
Given I have been working with web development in Ruby and PHP for years, I would love to find a nice "getting started" guide for a good/well established Haskell framework.
"JavaScript web frameworks seem to have a half-life of about 6 months..." Express [1] has been the dominant framework for Node.js since 2009-2010. What frameworks are you talking about? [1] https://github.com/visionmedia/express
But I get what you are saying, Express was among the most stable+popular pieces of js done in the last years.
If you are still considering PHP frameworks, then your choices are really Symfony or Laravel (maybe Zend at a stretch). Yes, Laravel does have a high "bus factor", but for me personally its the number one choice in terms of ecosystem, features, support and community,
Laravel isn't going away, even if Taylor gets hit by a bus. There's a huge and active Laravel community, it's just that Taylor is the benevolent dictator. If Taylor was hit by a bus, there would be plenty of others who would be willing and capable to take up the baton. Seems to me pretty remarkable to rule out Laravel on this basis, yet keep CakePHP, ignoring all its other flaws.
Dropwizard is where it's at right now for Java frameworks. It's a superproject that glues together the best pieces out there. Surprised it wasn't on the wikipedia list. Which brings up another point: if we're talking about web frameworks for the next decade we should really be looking at service-oriented architectures / single-page apps or whatever you want to call that model. It's quite different from the web framew…
>Dropwizard can do web views but it really positions itself as a REST service framework. That would eliminate it for me. Not everyone is coding APIs and fat client web apps. I'd prefer a framework geared up to do standard web apps as well.
https://dropwizard.github.io/dropwizard/manual/views.html
Don't forget that old style web apps are basically REST frameworks that render content with a content type of text/html...