News for hackers. Stuff that matters.
Re:Developer inequality and the technical debt crisis by djur on Monday July 07, 2014 @08:17PM (#8002367)
I think there's not nearly as much agreement on how a "web app" might look or work today as there was for a desktop app even as early as the early '90s.

For "classic" (content-based) web apps (forums, CMSes, blogs), there's already fairly sophisticated, end user-targeted tools that fill that role. For a lot of people, WordPress is the Visual Basic of the web. Some wiki engines could be said to resemble Hypercard.

But the community is so split on what the "modern web app" should look like (thin client? thick client? standards-based or not? use the DOM or draw directly?) that I think it'd be much harder to gain much support for a "Hypercard for the Web" -- many web developers, possibly even a majority, would consider it to be "doing it wrong" and "teaching bad habits" _no matter what it looked like_.

Re:Developer inequality and the technical debt crisis by webmaven on Tuesday July 08, 2014 @10:25AM (#8004645)
I think I'd be fine with an opinionated partial solution, even if it wasn't too popular. But I don't really see anything like that.
Re:Developer inequality and the technical debt crisis by abrahamepton on Tuesday July 08, 2014 @02:30PM (#8005942)
What about Macaw? http://macaw.co/
Re:Developer inequality and the technical debt crisis by webmaven on Wednesday July 09, 2014 @10:34AM (#8009799)
General purpose design tools are again the equivalent of DTP (and very welcome), but not an app solution (unless I have completely misunderstood the audience Macaw is for).