Xamarin is impressive, but..
-
+1 for the absurd pricing, we are the people they should be courting for business and they don't even have a proper free dev or academic license for evaluation.
We can’t stop here, this is bat country - Hunter S Thompson RIP
pkfox wrote:
they don't even have a proper free dev or academic license for evaluation.
Actually they do. And if you're an MSDN subscriber your eval license (with support) is automatically extended to 90 days. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
What about ... dare I say it ... VB (gasp). Or Fortran.NET .... COBOL.NET. I've mentioned COBOL 3 times this week. I fear my account may get deleted.:~
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
Exactly, lots of developers know and use VB (although getting constantly slammed for language choice gets tiring). With VB.net and C# being functionally equivalent, and compiling to the same IL; why not add it? I've actually had a COBOL book sitting in my wish list on amazon for the last 6 months now, temped to buy it and learn something new (old? :wtf: )
-
Matt McGuire wrote:
Everyone has their own personal preferences.
Well since you insist - Java stinks!
:laugh:
-
I don't like C# either, I'm more into VB or languages without all the {{{}}} and ;;;;; But since there are a lot of translaters out there to convert VB into C#, we don't have to worry. In my case, I guess I just have to code in VB and once done, let an engine translate it to me into C#. Never tried Xamarin though, so no proof that will work well but it seems doable. It also seems that Xamarin uses the MSIL code, that same code VB is turned into just like C#. If this is true, VB can easily be implemented as well in Xamarin. To be continued...
Lead, follow or get out of the way!
Agreed about the {{{}}} if the indenting is off (or forgotten), it is a pain to find the subtle problems. I really do prefer:
sub ...
if ...
for...
...
next
end if
end subBut I sometimes admit the C# can look a little cleaner in it's language like the for loop C#'s switch seems messy, but VB's select feels more flexible. Trade off's I suppose. Dabbling in D (not .NET). really liking this lang, even if it still uses {{{}}};;
-
Now That was Funny. But i love sprouts. :)
David
-
Exactly, lots of developers know and use VB (although getting constantly slammed for language choice gets tiring). With VB.net and C# being functionally equivalent, and compiling to the same IL; why not add it? I've actually had a COBOL book sitting in my wish list on amazon for the last 6 months now, temped to buy it and learn something new (old? :wtf: )
I try to ignore it. Much of the banter is meant in good humour. I've lived through many variations of technology prejudice. At Uni, much of my study was using C and Unix. My first job was in a VMS shop (bah! Unix, bunch of hackers!) They were horrified when I added some shell script batch commands to unixify my environment (removing a directory was painful under VMS, to say nothing of DIR *.*;* and deleting all versions of a file!). Dos => Windows - "All I need is a C prompt!" My involvement with VB was VB3. As a dyed in the wool C guy, it was a bit of a joke. Except it wasn't. It was great for prototyping and building user interfaces. With VB4 and OO (sort of) we were off to the races and I became a convert. I later did a project with a C++ programmer who had coded VB6 like C++ and the performance was awful and the code lengthy. After I sorted it out, he became a convert too. Tools have their strengths and weaknesses. Plain C is truly dangerous, although what you can sometimes achieve with 3 lines of code ... C# clearly doesn't have the issues that C has, it's a great tool but I personally don't like the style. The truth is that, generally, we prefer the tool we are most familiar with (shortcomings and all!)
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
What do you use instead?
Curvature of the Mind now with 3D
I used Qt [the project was cancelled, hence the past tense.] It can be quite goofy, but is much more complete and has pretty good documentation.
-
I used Qt [the project was cancelled, hence the past tense.] It can be quite goofy, but is much more complete and has pretty good documentation.
Can you use that with c#? I think it would be fun dusting off my C++ skills, but I'm not sure how much support it would get from everyone else here.
Curvature of the Mind now with 3D
-
Can you use that with c#? I think it would be fun dusting off my C++ skills, but I'm not sure how much support it would get from everyone else here.
Curvature of the Mind now with 3D
No, it's C++. Internal forums and Stack Overflow seem to be go to places for Qt support. (I've received very good assistance from both.)
-
Agreed about the {{{}}} if the indenting is off (or forgotten), it is a pain to find the subtle problems. I really do prefer:
sub ...
if ...
for...
...
next
end if
end subBut I sometimes admit the C# can look a little cleaner in it's language like the for loop C#'s switch seems messy, but VB's select feels more flexible. Trade off's I suppose. Dabbling in D (not .NET). really liking this lang, even if it still uses {{{}}};;
