Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Official support for .NET

stripe.com

Post reply on HN
Print view View original

11–20 of 64 posts

Re: Official support for .NET

#11

Post by mattchamb »

maxxxxx wrote: post #9
tracker1 wrote: post #4

Aside: there seems to be a lot of renewed interest in .Net with the advances of Core and other cross platform support in the open.

My company uses .NET mainly so it's nice to see these libraries. But from recent experience with several of them I am starting to be a little wary of .NET SDKs. It seems most .NET SDKs are either buggy, incomplete or have some other issues. It feels like you are a second class citizen with .NET. I would prefer if I could call Java SDKs from .NET. These SDKs seem to be higher quality than most .NET SDKs. C# is a great…

not sure i would go this route, but you can actually call java libraries from .net using a project called IKVM. I used it for a toy project and it seemed to work

Re: Official support for .NET

#12

Post by littlecranky67 »

c0nfused wrote: post #7
tracker1 wrote: post #4

Aside: there seems to be a lot of renewed interest in .Net with the advances of Core and other cross platform support in the open.

It always seems odd to me that people are excited about .net coming to Linux or osx. Mono has been around for so long I can't remember when it showed up, 2001? As far as I know mono's been feature complete for a decade or more. .net core is neat, but for me it's a tooling thing and not a "we can write .net of Linux" thing

Well, before .net core, Mono never had support for the most important frameworks that were commonly used in .NET world. Namely no support for WPF, EntityFramework, WebAPI, WCF (partial support came later on). This was a dealbreaker for most windows devs. If you accepted this and went for open source alternatives and/or mono's own frameworks (NHibernate, Gtk#, ServiceStack etc.), mono was pretty solid.

Re: Official support for .NET

#13

Post by westcoastdev »

c0nfused wrote: post #7
tracker1 wrote: post #4

Aside: there seems to be a lot of renewed interest in .Net with the advances of Core and other cross platform support in the open.

It always seems odd to me that people are excited about .net coming to Linux or osx. Mono has been around for so long I can't remember when it showed up, 2001? As far as I know mono's been feature complete for a decade or more. .net core is neat, but for me it's a tooling thing and not a "we can write .net of Linux" thing

mono has been around but was very buggy outside of Xamarin based apps. .net core is a first class .net implementation using lots of the same code code from .net framework and works much better in high stress server workloads.

Re: Official support for .NET

#14

Post by dpim »

tomnipotent wrote: post #3
jmkni wrote: post #2

Works with .net core also (they don't specify this).

>> targets the .NET Standard It was mentioned.

Yes, and in case there's confusion around Core vs. Standard. Standard can be thought of a spec, and supporting a version of .NET Standard implies support in a specific set of versions of .NET Core.

https://docs.microsoft.com/en-us/dotnet/standard/net-standar...

Re: Official support for .NET

#15

Post by ComputerGuru »

Ugh, thank God.

I get that until 2016 and Nadella/.NETCore only Ruby, JavaScript, and Python were the hipster languages of choice for web development... but .NET has been an awesome, rapid-development, tried-and-tested, business-friendly option for creating business applications, including, believe it or not, eCommerce platforms.

Outside the "hacker bubble" no one in their right mind would have neglected .NET as a first-class API target for this long. It's insane that Stripe got away with it for as long as they did, actually.

Re: Official support for .NET

#16

Post by ComputerGuru »

c0nfused wrote: post #7
tracker1 wrote: post #4

Aside: there seems to be a lot of renewed interest in .Net with the advances of Core and other cross platform support in the open.

It always seems odd to me that people are excited about .net coming to Linux or osx. Mono has been around for so long I can't remember when it showed up, 2001? As far as I know mono's been feature complete for a decade or more. .net core is neat, but for me it's a tooling thing and not a "we can write .net of Linux" thing

Mono has never put a focus on reliability or production-ready code. It's been awesome for desktop software and client applications, but we actually deployed ASP.NET on Mono to unify our deployment environment across our web infrastructure and ran into random bugs and show stoppers on a daily basis. And I'm not just talking about the horrible process of getting Visual Studio projects to deploy to a Mono server, the unavailability of certain APIs, functions that don't quite work the same way, or issues with the Mono frontend server, but also runtime infrastructure issues, random crashes, and more that made it a horrible nightmare worth maintaining two different operating systems for (our reliance on PHP for WordPress and vBulletin (back then, now XenForo instead of vB) meant we faced basically the same .NET-on-Linux issues with PHP-on-Windows, prevented us from going all-Windows at the time).

.NET Core is actually cross-platform from the ground up and the .NET Core team considers it blocking issue and won't release if the codebase doesn't run properly and identically on all supported platforms. It's a night-and-day difference.

Re: Official support for .NET

#17

Post by Kipters »

mattchamb wrote: post #11
maxxxxx wrote: post #9

Earlier quoted context omitted.

My company uses .NET mainly so it's nice to see these libraries. But from recent experience with several of them I am starting to be a little wary of .NET SDKs. It seems most .NET SDKs are either buggy, incomplete or have some other issues. It feels like you are a second class citizen with .NET. I would prefer if I could call Java SDKs from .NET. These SDKs seem to be higher quality than most .NET SDKs. C# is a great…

not sure i would go this route, but you can actually call java libraries from .net using a project called IKVM. I used it for a toy project and it seemed to work

IKVM development has been halted: http://weblog.ikvm.net/

Re: Official support for .NET

#18

Post by martinald »

ComputerGuru wrote: post #16
c0nfused wrote: post #7

Earlier quoted context omitted.

It always seems odd to me that people are excited about .net coming to Linux or osx. Mono has been around for so long I can't remember when it showed up, 2001? As far as I know mono's been feature complete for a decade or more. .net core is neat, but for me it's a tooling thing and not a "we can write .net of Linux" thing

Mono has never put a focus on reliability or production-ready code. It's been awesome for desktop software and client applications, but we actually deployed ASP.NET on Mono to unify our deployment environment across our web infrastructure and ran into random bugs and show stoppers on a daily basis. And I'm not just talking about the horrible process of getting Visual Studio projects to deploy to a Mono server, the un…

I agree, I've been using mono in semi-production for the best part of a decade for ASP.NET and it's been a complete nightmare every time.

It's also a shame that VS for Mac is so half baked for web projects despite MSFTs backing. This issue I have been search for an answer for a while is so obvious I don't understand how they didn't catch it: https://stackoverflow.com/questions/43967326/visual-studio-m...

Re: Official support for .NET

#19

Post by DaiPlusPlus »

I'm using the Stripe.NET library - but begrudgingly - there's a whole slew of FxCop-compliance issues with the code and some code-smells that I don't like (e.g. they read the JSON objects into strings, then deserialize the strings - it's more efficient to use the JSON.NET stream-deserializer). My biggest issue is the lack of `using()` statements: objects are not being disposed-of correctly!

(I'd submit a PR with fixes, but I'm short for time).

Re: Official support for .NET

#20

Post by jackfoxy »

Kipters wrote: post #17
mattchamb wrote: post #11

Earlier quoted context omitted.

not sure i would go this route, but you can actually call java libraries from .net using a project called IKVM. I used it for a toy project and it seemed to work

IKVM development has been halted: http://weblog.ikvm.net/

Development halted, yes, but AFAIK rock solid up to current Java release.
Post reply on HN