4 ms·

Around 2012 there were all kinds of static prebuilding frameworks rising again, and by 2014ish pandoc was very popular already. Personally I switched around 20

Around 2012 there were all kinds of static prebuilding frameworks rising again, and by 2014ish pandoc was very popular already. Personally I switched around 2015 to writing most of my web pages in markdown (well, or commonmark) because I got fed up of repeating myself too often in HTML. VIM isn't a great IDE for HTML and all its syntax highlighting quirks either, which contributed to the markdown migration. The beauty of markdown is that it's so lightweight, you can use it for dynamic lazy loading as well. There's almost zero overhead for layouting information for the text if you do it right.

gabereiser 4y ago
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.
- deleted 4y ago
  [deleted]
jrumbut 4y ago
Vim with Emmet and the right tweaks is very good if your job is churning out HTML. I've had a few projects that would have been endless slogs with nearly any other setup get completed at lightspeed. This setup's strength is its own downfall though. If you don't have the arcane keystrokes and useful patterns burned into your muscle memory you would be better off with almost anything else. Hopefully if this project gets off the ground they will remember that many of us write HTML as a small component of our jobs rather than it's sole focus.

gabereiser 4y ago

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.

deleted 4y ago
[deleted]

jrumbut 4y ago

Vim with Emmet and the right tweaks is very good if your job is churning out HTML. I've had a few projects that would have been endless slogs with nearly any other setup get completed at lightspeed. This setup's strength is its own downfall though. If you don't have the arcane keystrokes and useful patterns burned into your muscle memory you would be better off with almost anything else. Hopefully if this project gets off the ground they will remember that many of us write HTML as a small component of our jobs rather than it's sole focus.