Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah, prebuilding frameworks like Jekyll in 2013 changed the game for some. However, as much as I love markdown, the issue in my post was with the OP's assessment of what web development was like in 2012 which was off base.

Most enterprises at the time weren't using markdown outside of engineering documentation. The rise of JIRA during this time period helped a bit as they had their own flavor of markdown-like syntactic sugar. We started to explore other ways of generating pages. Ruby on Rails started gaining serious traction ($1B+ VC backed startups using it). Things like haml existed to make writing html "fun again" (my words). Which gave rise to other processing languages to spit out HTML from lessons learned.

It was around this time that microservices started to be a thing to replace those old enterprise SOA architectures (hello jboss). The application server began to die in favor of self-hosted apps. Docker was new. Spring Framework was relatively new. Bootstrap was just released. There weren't any standard css frameworks that provided as much as Bootstrap did at the time.

<script type="template"> was a thing. Backbone.js was used often. Underscore.js as well (Jeremy, again, sorry about Coffeescript, they can't all be winners).

Now we have web components and I'm so happy we do. It's refreshing to be able to do the things we wanted to do back then but couldn't without some other framework.

I've been around a long time. I started doing web development in 1998 right out of high school. I've written all kinds of web apps, platforms, services, etc.

I still like writing my content in markdown.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: