Unapologetically build your startup technology in C#

151–152 of 152 posts

Re: Unapologetically build your startup technology in C#

#151

Post by pbz » Mon, Jul 07, 2014, 10:23 PM UTC

jtseng wrote: post #133

sirchristian wrote: post #33

Earlier quoted context omitted.

I agree "get all the free Microsoft goodies when you start, and once you really need the paid versions you're probably successful enough that the cost doesn't matter much" is one fair conclusion to the article. However I don't believe that's the only conclusion. Mostly I want .NET to be a consideration as an option when building out the technology in a startup. I'm concerned about vender lock-in as well, just less co…

We've recently started down this C#/Postgres route. One of the main decisions to use C# was static typing, so I wanted to keep this with the data access layer as well. I've decided to use dotConnect for PostgreSQL so I can use EF. I figure I can use dapper or another micro ORM after I get into performance issues. Our biggest problem with Postgres is actually the lack of a good GUI. I'm using 0xDBE for the amazing aut…

LINQ to DB (not LINQ2SQL; it's an OSS library) is also a good option to talk to Postgres while keeping type safety and performance.

Re: Unapologetically build your startup technology in C#

#152

Post by JimmyM » Tue, Jul 08, 2014, 12:32 PM UTC

darylteo wrote: post #36

JimmyM wrote: post #32

Earlier quoted context omitted.

C# I can handle (despite coming to it late, as part of Unity3D), but I find Java more and more frustrating to work with. To be honest, I think I'm just using it for the wrong thing - I don't tend to work on big, collaborative projects which is where Java really shines. Meanwhile, C# has a few conveniences (such as LINQ and rectangular arrays, off the top of my head) which seem to me to make scripting and small projec…

> I don't tend to work on big, collaborative projects which is where Java really shines What aspects of C# makes working on large collaborative projects difficult? Not sure where you are going with this. Unless you meant Team Foundation Server / Visual Source Safe pukes .

> What aspects of C# makes working on large collaborative projects difficult?

None. I was just talking about my issues with using Java for small projects, not using C# for large projects. My argument is that C# covers scripting and small utility programs adequately, while Java seems to require more boilerplate.

C# would be my natural choice for projects large or small.

Post reply on HN