Live data from Hacker News

Xamarin Open-Sourced

open.xamarin.com

161–170 of 206 posts

Re: Xamarin Open-Sourced

#161
post #51

Earlier quoted context omitted.

Google hasn't anyone to blame but themselves.

Yep, not buying Sun was their biggest mistake.

It wasn't a mistake at all. Sun was a lot of things besides Java, it just wasn't worth it for them and they were right to take a pass. Even if they end up paying big dollars to Oracle, the amount won't be high enough to retroactively justify buying Sun. Android is big now and it can weather whatever comes from this patent battle.

Re: Xamarin Open-Sourced

#162

Earlier quoted context omitted.

Why do you link to gitter when you should actually like to the repos instead ?

Depends on how you learn. Some learn by being around others, social interaction, asking questions and absorbing knowledge. It's clear you fall into the latter category which likes to learn by diving right into the code, so here it is: .NET CLR Managed Runtime - https://github.com/dotnet/coreclr .NET Framework - https://github.com/dotnet/corefx .NET Compiler as a Service ("Roslyn") - https://github.com/dotnet/roslyn .…

> Some learn by being around others, social interaction, asking questions and absorbing knowledge. It's clear you fall into the latter category which likes to learn by diving right into the code, so here it is

Props for how you dealt with negative feedback in this thread, and this positive re-frame.

Re: Xamarin Open-Sourced

#163

Earlier quoted context omitted.

Let's be clear, this isn't left-pad we are talking about - these are MASSIVE projects which are in some cases 16+ years old. Personally, I find the fastest way to get up to speed is on projects of this size is to usually jump into IRC, find a mentor and start sending in documentation patches. Here the engineers for the runtime, framework, compiler teams are hanging out in Gitter and engaging with the community out in…

How do you start documenting software that you don't know well? That seems like a very good way for bad documentation to get out, damaging the project. Perhaps this is my impostor syndrome talking, but I for one would be hesitant to tempt the wrath of the Great Unseen Masters that make open source software with potentially inane questions.

> That seems like a very good way for bad documentation to get out, damaging the project.

Read the code, try your best to understand it, and then get the documentation reviewed by someone who does know the software well. This works for code, too. Bonus points: Explicitly enlist feedback ("Anything I'm missing here? Any edge cases I forgot to note? Is my understanding of this correct?")

> I for one would be hesitant to tempt the wrath of the Great Unseen Masters that make open source software with potentially inane questions.

http://www.catb.org/esr/faqs/smart-questions.html

But if you're making an effort to contribute, that already counts for a lot. There might be some gruff redirection towards more effective means of contributing, if you're being a significant time sink and not helping that much, but hopefully that's a win/win in the end.

Re: Xamarin Open-Sourced

#164
post #31

Honestly, I am a little tired of all the articles (edit: I meant posts) claiming MS is suddenly in the Open Source camp. To truly support Open Source, they should show a willingness to work against Software Patents. The essence of Open Source is the freedom for anyone with a computer to turn their imagination into code. MS remains one of the biggest obstacles in that path. Instead here is what they do: 1) Directly at…

> Honestly, I am a little tired of all the articles (edit: I meant posts) claiming MS is suddenly in the Open Source camp.

Okay...but this isn't one nor is it really an "article". It's simply the page about Xamarin being opened source. That's it. It's MIT licensed and opened sourced.

Did you not read the page or did you just want to rant about the same things people complain about with Microsoft in almost every HN thread about their open source efforts? I'm not saying some of these are not issues but when they're unrelated and don't add anything to the context of the content I don't get the point.

Re: Xamarin Open-Sourced

#165

Earlier quoted context omitted.

Whilst I would never be rude to a newbie, isn't it reasonable that they at least read the FAQ, README or an I tried before asking such basic questions?

Sure. But ask in gitter first. You'll receive an answer suggesting you go read the README.md as it covers this info.

I've never heard of people needing to ask where the project readme is, especially when your in a chatroom linked to the repo, which has it on the homepage.

On top of that, it's inefficient. I want a couple of paragraphs telling me what the project is about, not a conversation.

Re: Xamarin Open-Sourced

#166

Earlier quoted context omitted.

Whilst I would never be rude to a newbie, isn't it reasonable that they at least read the FAQ, README or an I tried before asking such basic questions?

Sure. But ask in gitter first. You'll receive an answer suggesting you go read the README.md as it covers this info.

Which you probably already could assume before, so you just wasted your AND somebody elses time. rude.

Re: Xamarin Open-Sourced

#167

Earlier quoted context omitted.

Whilst I would never be rude to a newbie, isn't it reasonable that they at least read the FAQ, README or an I tried before asking such basic questions?

Sure. But ask in gitter first. You'll receive an answer suggesting you go read the README.md as it covers this info.

That seems... inefficient. Basically, instead of reading the readme, you suggest going to gitter to be told to read the readme?

I think I could streamline that process a bit.

Re: Xamarin Open-Sourced

#168
post #121
post #98

Earlier quoted context omitted.

Couple billion dollars in revenue generated with it via Unity alone. https://en.wikipedia.org/wiki/Unity_(game_engine) -- and that was a HORRIBLE version of it. Way better now.

tl;dr. The success of Unity can't be used as an indicator that cross-platform frameworks are good for productivity/utility apps. Xamarin and Unity don't have anything in common, other than the fact that Unity uses C# for scripting (on an ancient runtime). Cross-platform app development frameworks are generally awful because they don't tightly integrate with the native look and feel of every platform. Video games don'…

I don't think Unity does it any more, but it wasn't that long ago when Unity used Xamarin to be able to run on iOS, Android and PS4. Now they do it with il2cpp I think.

Also, it seems you have no idea what you're talking about. Xamarin gives you access to the same native APIs that you use when developing a native app. You still need to know the native API if you want to build an iOS app. Xamarin.Forms helps, but doesn't support everything.

Re: Xamarin Open-Sourced

#169
post #51

Earlier quoted context omitted.

Google hasn't anyone to blame but themselves.

Yep, not buying Sun was their biggest mistake.

That was their second mistake.

The first mistake was screwing Sun during their license agreement discussions for Android.

Re: Xamarin Open-Sourced

#170
post #31

Honestly, I am a little tired of all the articles (edit: I meant posts) claiming MS is suddenly in the Open Source camp. To truly support Open Source, they should show a willingness to work against Software Patents. The essence of Open Source is the freedom for anyone with a computer to turn their imagination into code. MS remains one of the biggest obstacles in that path. Instead here is what they do: 1) Directly at…

It's a fallacy that you cannot support both open source and software patents. Religious opinions aside, they are both simply different forms of IP, each effective for different things.

IBM and Intel are two good examples of it.
Post reply on HN