"Why Static Website Generators Are The Next Big Thing" smashingmagazine.com/2015/11… s/The Next Big Thing/The New Ajax Libraries/
1
16
18
@codepo8 why the /s/ there? They can be totally complimentary actually.
1
@briankardell 100s of them.
1
1
@codepo8 I've been doing this for years - I think it's a great idea actually, nice to see someone express some of the reasons - there's more
2
@briankardell if it is less work to write one than to sift through dozens to test out for you, then something is broken in our methodology.
1
1
@codepo8 This is almost literally how it always works though, things will settle down to a happy number. In '94 there were 16 browsers!
2
@briankardell and now we have about 16 on Android alone…
1
2
@codepo8 in 94 though that was 1 per ~175 websites. in '92 there were 7 browsers for only 22 websites :)
2
@briankardell @codepo8 Devs can sort this. I can't in good conscience develop a class based on public trends. Yet that's what's asked for.
2
@briankardell @codepo8 The over frameworking, portalizing, generating all override core skills (HTML/JS/CSS) because apps are easy to teach.

Nov 2, 2015 · 2:44 PM UTC

1
Replying to @mholzschlag
@mollydotcom @codepo8 static site generation isn't that though, at least not any more than PHP/Java//NET/CGI/ETC were
1
@briankardell @codepo8 That's from a dev, not instructional designer. So different. We have limited time to impress core values in students.
1