292 karma · joined November 1, 2016
https://www.google.de/publicdata/explore?ds=d5bncppjof8f9_&m...
Also, I searched for the Kurdish support: https://i.imgur.com/bWnm5Sb.png
I can say that I wasn't surprised.
It was very easy to develop, test and deploy. Npgsql has support for most of the postgres features (except complex types but that's planned).
I deployed everything on Ubuntu servers and runs like a champ. (I'm saying prototype and it is indeed, but it has 100-something users across the globe testing their workflows continuously and it has a lot of CPU-intensive stuff which is child's play with .NET to manage asynchronously. A production app would have two orders of magnitude more users but I think I'll be able to get away with a single server if it comes to that).
But you don't even use HTTPS. Why?
My point is, you can write any kind of app with almost any kind of server-side tech. If you don't like the culture, you may be right, but please be explicit about it.
C#'s type system is usually better except from the times that I feel creative. Works perfectly for large codebases with many changes. Not fun for side-projects.
I don't like node.js, but I occasionally use Typescript like a more powerful C#.
Best solution would have been a pipe operator if you ask me.
Sorry for being sarcastic but don't you also find this too obvious?
Duly noted! Although I'll try talking to her first, I'm sure there's more behind the decision :)
One of the methods that was inside takes a request, extracts the body and returns the parsed graph from the body. It's used by many controllers from many projects. I don't know where to put such a thing, hence the request extension.
In our work we use C# and it is very hard, even next to impossible to make a static class pass a code review - given it's not for extension methods (which I hate... why not be explicit about the first parameter and stop acting as a part of the class </rant>). They just tell us to use IoC and move to the next point. I honestly don't know why. Our IoC library can treat a dependency as static or singleton, but those are also discouraged. Once I had a static class named GraphRequestHelpers* and the reviewer got really negative, FSM knows why. She told me that we need IoC to make everything testable and "Helper" in the name is a code-smell. Sounds cargo-culting to me but I have only 6 years of experience so who I am to know.
* Now we have RequestExtensions and everything is apparently perfect.
Why doesn't recycling fully work?
Is the garbage generated from packaging higher in the countries where more recycling is made?
Sources with data and numbers would be very welcome.
There is no information about how it works, let alone some technical aspects - interesting, especially considering the name. About link doesn't work as well.