We sell diagramming libraries, most notably (by sales volume) a JavaScript diagramming library: https://gojs.net https://gojs.net Our stack is: we don't care.

We sell diagramming libraries, most notably (by sales volume) a JavaScript diagramming library: https://gojs.net https://gojs.net Our stack is: we don't care. One of us spun up a couple AWS resources and a windows machine with IIS because that's what he knew how to configure the quickest. It seems like it would be a waste of time to spend any more time thinking about it until we have a real need. We have some orders database stuff we wrote ourselves ages ago with SQL Server that hasn't needed significant changes in 10+ years. In other words, to us, the stack is whatever makes itself disappear the soonest so we can work on the actual product. Nothing fancy, nothing new, nothing changed for the sake of it. If our product touched the stack more, we'd spend more time on it, but only insomuch as it was the product (if the product is a speedy website, etc). Our workflow/cycle is all JavaScript based for the JS product. We push release with a gulp script I wrote.