One of the main reasons we abandoned Pinta (https://github.com/PintaProject/Pinta) is we had to rewrite a significant portion of the app if we wanted to move to GTK3, as we had many custom UI needs.
See also:
GIMP, still on GTK2.
Inkscape released on GTK3 just within the past year or 2
Many comments (probably correctly) point out that SQL can't be displaced because it is ubiquitous and "good enough".
I wonder if there is room for a "TypeScript" of SQL that would allow developers to opt-in to whatever new language features or paradigms we feel SQL is missing.
It would then transpile down to regular SQL to be executed.
Ultimately there is very little consumer grade software anymore because modern consumers won't pay for software.
The only people who pay for software are enterprises and they aren't going to skimp a few hundred dollars on software that makes their $X0,000 creative workers X% less productive.
In this space there is basically Pixelmator and Affinity trying to eke out enough sales to keep their developers paid.
Thanks! Yeah, GitHub is definitely the way to go for OSS or projects with technical users. This is designed more for things like closed source apps or SaaS.
I built https://communiroo.com because I couldn't find a quick and simple single website to expose bug/feature tracking + SO type questions + forums + support requests for my other things I was building. It seemed (and still seems) like it fills a need for mine and everyone else's side projects.
I think the biggest issue is marketing. I tried a few Twitter/Facebook ad campaigns that didn't really pan out, and an HN submission that didn't make the front page. But really I haven't done much to market it, and it just sits there chugging along with few users other than myself while I work on other stuff.
I have a friend who is a medical researcher and it definitely seems they are stuck in the past.
In order to study something, he has to:
* Come up with a hypothesis that X may cause Y
* Request access to data about that hypothesis
* He is only given the data regarding his hypothesis
* He can then study whether his hypothesis has merit or not
We should be dumping these whole datasets into machine learning and having computers give us potential links to explore. Obviously there will be plenty of things that turn out to be unrelated, but it's also very likely the computer can find links that a human would not have considered.
I don't see it changing any time soon in the US, but I suspect other countries with this data will use it, and we'll find the next generation of medical breakthroughs no longer come from the US.
Communiroo grew out of a need after I had created my first hobby mobile app. I wanted a single place where users could file bugs, make suggestions, have discussion forums, and get support. The only option I could find was to use a myriad of different services like Bugzilla, UserVoice, Discourse, and ZenDesk. That seemed like a lot of extra work for both me and my users.
Communiroo provides a single site and a single login for:
I work for a very mature startup, and recently led our first site on ASP.NET Core. The framework itself is very nice and very solid, basically a "do-over" of all the previous ASP.NET frameworks with the benefit of hindsight. Although there's been some new things to learn, I've been very pleased with how consistent and thought out the new ASP.NET Core is. We run the site in production.
Having said that, the tooling around ASP.NET Core has been an absolute disaster. They went 90% of the way with one mechanism (project.json), then decided to start over with a new mechanism (msbuild). While I believe it is ultimately for the best, the interim has been incredibly difficult to work with, as ASP.NET has been officially released now for ~8 months with neither method fully working. For example, in the current project.json stuff you cannot reference another project without first putting it into a Nuget pacakge.
Hopefully this will all be cleared up with the upcoming release of VS2017, but if you need something sooner and aren't interested in dealing with a lot of pain, I'd stick to ASP.NET classic for now.
https://communiroo.com - I created a mobile app and wanted a single, easy-to-set-up site to direct users to for bug reports, feature requests, forums, and support, but I couldn't find one.
I built Communiroo to provide a community site for apps and services that can be set up in just a few clicks.
However, for some reason, many consumers will happily subscribe to SaaS apps. So developers go where the customers are.