News for hackers. Stuff that matters.
Re:Building an Open Source Service by codemac on Wednesday October 26, 2016 @05:08PM (#12800571)
.NET and Swift were open sourced after long periods of being closed source (swift obviously shorter).

What were the positives and negatives of going open source earlier?

Re:Building an Open Source Service by zeeg on Wednesday October 26, 2016 @05:11PM (#12800595)
It's much easier to start open source, rather than tack it on after the fact. Depending on your business, it could also be a huge advantage. For us, being open source means companies like Uber and Airbnb, whom have ample engineering expertise, can still use Sentry. In another world they might have rolled their own. This opens up a big opportunity that you can take a number of business directions:

- a hosted offering (effectively what sentry.io is going for)

- paid on-premise support (we offer this as well to select customers)

- on-premise enterprise offering (open core)

I'm not a big fan of the distraction of doing both on-premise and SaaS (thus our stance), and I really would love if we never have to build crippleware (open core).

Re:Building an Open Source Service by intrasight on Wednesday October 26, 2016 @09:03PM (#12802135)
.Net and Swift are languages/runtimes. I fail to see the analogy with application software.