Code Mechanical Keyboards
Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
This is a good question as I am in the process of looking for a mechanical keyboard. The Code keyboards seem pretty expensive by the time they get to Aus so I was thinking one of these http://www.pccasegear.com/index.php?main_page=product_infocPath=113_1276products_id=2 On Fri, Oct 24, 2014 at 1:34 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
I kind of don't understand what they do, their just a robust keyboard? You still have to press as hard? I've been loving apple keyboards as it's soft and easy to press, is it like this or going in the opposite direction? Thanks On Fri, Oct 24, 2014 at 1:49 PM, Craig van Nieuwkerk crai...@gmail.com wrote: This is a good question as I am in the process of looking for a mechanical keyboard. The Code keyboards seem pretty expensive by the time they get to Aus so I was thinking one of these http://www.pccasegear.com/index.php?main_page=product_infocPath=113_1276products_id=2 On Fri, Oct 24, 2014 at 1:34 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
I use the Filco Tenkeyless (without the numeric pad on the right) with the blue cherry switches. I spent probably $220 on it all up (I've got the plain keys without lettering so the keyboard is completely black... can't touchtype? not 1337 enough to use my computer!) If you spend 8+ hours per day on your keyboard at least five days per week, having a decent keyboard is mandatory, and not something to cheap out on in my opinion. Given all of that, mechanical keyboards are great, and this keyboard looks great. I want it :P -- Les Hughes l...@datarev.com.au On 24/10/14 13:34, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
I have 2x das keyboards which also have mechanical switches. After using for a long time anything else seems terrible by comparison. Joseph On Oct 24, 2014 12:35 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
Thanks Craig, that looks interesting - not sure about the big flat front bit but says it uses Cherry MX switches similar to the code keyboards and it’s reasonably priced… Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ === From: Craig van Nieuwkerk Sent: Friday, 24 October 2014 10:49 AM To: ozDotNet This is a good question as I am in the process of looking for a mechanical keyboard. The Code keyboards seem pretty expensive by the time they get to Aus so I was thinking one of these http://www.pccasegear.com/index.php?main_page=product_infocPath=113_1276products_id=2 On Fri, Oct 24, 2014 at 1:34 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
I've been using Corsair Vengence K90 gaming keyboard for the longest time... three years?. Mechanical keys wouldn't change back but i'm sure there are equally awesome keyboards out there. Had a Razor gaming keyboard which died. I also got a Code keyboard (without numberpad) and the micro usb port broke on it the first time I tried to unplug it. The support was good, they sent me a replacement part (and said they had improved the design for future keyboards). It's a nice keyboard, which I use when on client sites. None of the extra stuff you don't need and nice to type on. +61 (0) 428 028 599 step...@lythixdesigns.com @lythixdesigns | @lyynx www.lythixdesigns.com www.linkedin.com/in/lyynx On Fri, Oct 24, 2014 at 11:38 AM, Joseph Cooney joseph.coo...@gmail.com wrote: I have 2x das keyboards which also have mechanical switches. After using for a long time anything else seems terrible by comparison. Joseph On Oct 24, 2014 12:35 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
I am pretty sure you can remove the hand rest part at the front. On Fri, Oct 24, 2014 at 2:40 PM, osjasonrobe...@gmail.com wrote: Thanks Craig, that looks interesting - not sure about the big flat front bit but says it uses Cherry MX switches similar to the code keyboards and it’s reasonably priced… Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ === *From:* Craig van Nieuwkerk crai...@gmail.com *Sent:* Friday, 24 October 2014 10:49 AM *To:* ozDotNet ozdotnet@ozdotnet.com This is a good question as I am in the process of looking for a mechanical keyboard. The Code keyboards seem pretty expensive by the time they get to Aus so I was thinking one of these http://www.pccasegear.com/index.php?main_page=product_infocPath=113_1276products_id=2 On Fri, Oct 24, 2014 at 1:34 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Code Mechanical Keyboards
Looking at the companies web page you can remove the wrist rest http://www.tesorotec.com/gaming-keyboard/tesoro-durandal-ultimate-g1nl-led-backlit-mechanical-gaming-keyboard.html?sl=EN I also like that it has USB and headphone/speaker plugs which is convenient. Any keyboard with Cherry switches should be fairly similar as the switches are made by the same company, although I am no expert. Just need to make sure you get the right colour. On Fri, Oct 24, 2014 at 2:46 PM, Craig van Nieuwkerk crai...@gmail.com wrote: I am pretty sure you can remove the hand rest part at the front. On Fri, Oct 24, 2014 at 2:40 PM, osjasonrobe...@gmail.com wrote: Thanks Craig, that looks interesting - not sure about the big flat front bit but says it uses Cherry MX switches similar to the code keyboards and it’s reasonably priced… Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ === *From:* Craig van Nieuwkerk crai...@gmail.com *Sent:* Friday, 24 October 2014 10:49 AM *To:* ozDotNet ozdotnet@ozdotnet.com This is a good question as I am in the process of looking for a mechanical keyboard. The Code keyboards seem pretty expensive by the time they get to Aus so I was thinking one of these http://www.pccasegear.com/index.php?main_page=product_infocPath=113_1276products_id=2 On Fri, Oct 24, 2014 at 1:34 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Opinions sought on Xamarin
I've got a bit of free time so I'm starting to play around with mobile development and getting somewhat bewildered with the options offered. The dream is to knock up a business style app that will allow persistence of data to the local database eg. sqlite then a transfer to a base server. Looked at Android dev kit, and that is OK but of course that strikes out Ios Windows. Looked at PhoneGap/Cordova and got infuriated by the simple task of posting data (jsonp is a bit of a security risk in my books) Early last year I did play with Xamarin and found it unstable, crashing at a whim. Is it worth giving it another go, or should I just suck it up and work on platform specific development tools. -- - Stuart Kinnear Mobile: 040 704 5686. Office: 03 9589 6502 SK Pro-Active! Pty Ltd acn. 81 072 778 262 PO Box 6082 Cromer, Vic 3193. Australia Business software developers. SQL Server, Visual Basic, C# , Asp.Net, Microsoft Office. -
Re: Code Mechanical Keyboards
Cool, personally don’t need all the extras (speaker plugs etc), look like a CODE 87 Key Clear will be about $210 including delivery to Perth It’s weird, I’ve never really thought too much about keyboards before and yet I spend 40+ hours a week with it! Are mechanical keyboards supposed to be better/less strain/impact on hands/fingers/joints? CODE 87-Key Mechanical Keyboard - Cherry MX Clear Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ === From: Craig van Nieuwkerk Sent: Friday, 24 October 2014 11:50 AM To: ozDotNet Looking at the companies web page you can remove the wrist rest http://www.tesorotec.com/gaming-keyboard/tesoro-durandal-ultimate-g1nl-led-backlit-mechanical-gaming-keyboard.html?sl=EN I also like that it has USB and headphone/speaker plugs which is convenient. Any keyboard with Cherry switches should be fairly similar as the switches are made by the same company, although I am no expert. Just need to make sure you get the right colour. On Fri, Oct 24, 2014 at 2:46 PM, Craig van Nieuwkerk crai...@gmail.com wrote: I am pretty sure you can remove the hand rest part at the front. On Fri, Oct 24, 2014 at 2:40 PM, osjasonrobe...@gmail.com wrote: Thanks Craig, that looks interesting - not sure about the big flat front bit but says it uses Cherry MX switches similar to the code keyboards and it’s reasonably priced… Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ === From: Craig van Nieuwkerk Sent: Friday, 24 October 2014 10:49 AM To: ozDotNet This is a good question as I am in the process of looking for a mechanical keyboard. The Code keyboards seem pretty expensive by the time they get to Aus so I was thinking one of these http://www.pccasegear.com/index.php?main_page=product_infocPath=113_1276products_id=2 On Fri, Oct 24, 2014 at 1:34 PM, osjasonrobe...@gmail.com wrote: Anyone used/using one of these (or similar keyboard)? http://codekeyboards.com/ Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts === I welcome VSRE emails. Learn more at http://vsre.info/ ===
Re: Opinions sought on Xamarin
Go Xamarin it's the best! (Opinion may be bias www.michaelridland.com)
Traditional Xamarin (Native API) as the platform is awesome and solid and
fast, the IDE and some of the tools around it can be a bit buggy.
Xamarin.Forms is pretty early, and can be frustrating but I have build some
XPlat app pretty rapidly with it.
Actually I'm doing a 'Introduction to Xamarin' at SydMobile in a few weeks,
you should come along I'd love to answer any questions you have.
http://www.meetup.com/SydMobile/
Below is a unpublished blog post on why you should use Xamarin...
*Should I use Xamarin for Mobile Development? YES you should!*
In my opinion you'd be insane if you didn't use Xamarin for mobile
development. Many people don't know what they're missing out on by not
using Xamarin so I'm going to highlight some reasons I think people should be
using Xamarin.
1) It's Native but with 80%+ code share?
So for those that aren't aware of Xamarin or how it works, Xamarin allows
you to develop apps for iOS, Android and Mac from a single code base. When
I say this I don't mean in a webview or customised API, it actually usesthe
Native APIs. So when developing you use UITableView which is the same API
that a native developer would be using.
2) C# and F# are Modern languages
C# might not be the hipster language of the year it is a continually
evolving language with solid features like type interference, dynamic
types, language integrated query (LINQ), async/await and first class
functions. C# is designed for developing large robust applications.
And for the functional types there's F#, which from what I've been told
it's like scala but faster and better thought out.
I'd argue they're better languages than java, javascript and objective-c...
and seeing that they're currently the only languages with built in async
you could say their even better than swift...
3) async/await
.. 'wait but javascript is all async' i hear you say... C#/F# async/await
is different to what people normally think async is. C#/F# async/await
tackles the callback hell problems in rich clients, anyone who works with
rich clients will know of these problems. This is a problem that's
attempted to be solved with promises and generators but neither are at the
level of async/await.
Here's a little before/after sample:
*Before:*
doAsync1(function () {
doAsync2(function () {
doAsync3(function () {
doAsync4(function () {
})
})
})
})
*After:*
await doAsync1()
await doAsync2()
await doAsync3()
await doAsync4()
4) Watches, Google Glass wearables and the future of devices.
In case you haven't noticed the future isn't just mobiles it's wearables,
devices and IOT. Xamarin has same day support for all these platforms
including android wear, google glass, Amazon TV and more. As I've said
beforeXamarin uses the Native APIs and compiles down to native so using
Xamarin you're in the perfect position develop all modern platforms.
5) It's ready now!
All the time I hear people say 'html is a fast moving target' or 'it will
get there eventually'. Xamarin is here now, it's Native and it's cross
platform. Why wait to have a great app when you can have it now and as a
bonus know that your application is future proof for future devices.
6) It's fast and stable
From personal experience the Xamarin traditional (Xamarin.iOS and
Xamarin.Android)
platform is solid, fast and stable. You'd be hard pressed to find a problem
with the core parts of the platform, any app bugs will probably be your own
bugs.
7) Documentation
The documentation for Xamarin is solid, it's generally better than the
Apple and Android documentation.
8) Xamarin.Forms
So how about 100% codeshare and still be Native? Xamarin.Forms allows you
to program against a single API and have that single API mapped to native
controls on each platform. Hanselman describes it well, 'Write Once Run
Everywhere AND Be Native'.
It's still early days for the product but the top component developers like
Telerik and DevExpress are already developing components for Xamarin.Forms.
9) It's the best of all worlds (Hybrid and Native)
If you've taken a look at my Xamarin mashup blog
http://www.michaelridland.com/mobile/asp-net-mvc-xamarin-mashups/ you'd
already know that the possibilities with Xamarin are vast, you can
essential create your own Cordova and you can completely integrate it with
your C# Mvvm/c# Native Code. So you have the full power of the .net
framework to build your client application architecture which becomes very
useful when you have complex requirements like Offline.
10) Large Community
Xamarin uses the .net framework and because of this it's inherited the
pre-existing community, this means that even though it's a fairly new
platform we already have support for Awesome projects like Json.net, Fody
and ReactiveExtensions/ReactiveUI.
11) Profitable Innovative Company
Xamarin as a company has a passion for enabling mobile developers to
deliver leading experiences. Their
Re: Opinions sought on Xamarin
... but that said, Xamarin is pretty heavy weight, it's s big learning
curve.. if you want something lightweight and 'pretty' good you should try
out Ionic...
On Fri, Oct 24, 2014 at 3:19 PM, Michael Ridland rid...@gmail.com wrote:
Go Xamarin it's the best! (Opinion may be bias www.michaelridland.com)
Traditional Xamarin (Native API) as the platform is awesome and solid and
fast, the IDE and some of the tools around it can be a bit buggy.
Xamarin.Forms is pretty early, and can be frustrating but I have build some
XPlat app pretty rapidly with it.
Actually I'm doing a 'Introduction to Xamarin' at SydMobile in a few
weeks, you should come along I'd love to answer any questions you have.
http://www.meetup.com/SydMobile/
Below is a unpublished blog post on why you should use Xamarin...
*Should I use Xamarin for Mobile Development? YES you should!*
In my opinion you'd be insane if you didn't use Xamarin for mobile
development. Many people don't know what they're missing out on by not
using Xamarin so I'm going to highlight some reasons I think people should be
using Xamarin.
1) It's Native but with 80%+ code share?
So for those that aren't aware of Xamarin or how it works, Xamarin allows
you to develop apps for iOS, Android and Mac from a single code base. When
I say this I don't mean in a webview or customised API, it actually usesthe
Native APIs. So when developing you use UITableView which is the same API
that a native developer would be using.
2) C# and F# are Modern languages
C# might not be the hipster language of the year it is a continually
evolving language with solid features like type interference, dynamic
types, language integrated query (LINQ), async/await and first class
functions. C# is designed for developing large robust applications.
And for the functional types there's F#, which from what I've been told
it's like scala but faster and better thought out.
I'd argue they're better languages than java, javascript and
objective-c... and seeing that they're currently the only languages with
built in async you could say their even better than swift...
3) async/await
.. 'wait but javascript is all async' i hear you say... C#/F# async/await
is different to what people normally think async is. C#/F# async/await
tackles the callback hell problems in rich clients, anyone who works with
rich clients will know of these problems. This is a problem that's
attempted to be solved with promises and generators but neither are at the
level of async/await.
Here's a little before/after sample:
*Before:*
doAsync1(function () {
doAsync2(function () {
doAsync3(function () {
doAsync4(function () {
})
})
})
})
*After:*
await doAsync1()
await doAsync2()
await doAsync3()
await doAsync4()
4) Watches, Google Glass wearables and the future of devices.
In case you haven't noticed the future isn't just mobiles it's wearables,
devices and IOT. Xamarin has same day support for all these platforms
including android wear, google glass, Amazon TV and more. As I've said
beforeXamarin uses the Native APIs and compiles down to native so using
Xamarin you're in the perfect position develop all modern platforms.
5) It's ready now!
All the time I hear people say 'html is a fast moving target' or 'it will
get there eventually'. Xamarin is here now, it's Native and it's cross
platform. Why wait to have a great app when you can have it now and as a
bonus know that your application is future proof for future devices.
6) It's fast and stable
From personal experience the Xamarin traditional (Xamarin.iOS and
Xamarin.Android)
platform is solid, fast and stable. You'd be hard pressed to find a problem
with the core parts of the platform, any app bugs will probably be your own
bugs.
7) Documentation
The documentation for Xamarin is solid, it's generally better than the
Apple and Android documentation.
8) Xamarin.Forms
So how about 100% codeshare and still be Native? Xamarin.Forms allows you
to program against a single API and have that single API mapped to native
controls on each platform. Hanselman describes it well, 'Write Once Run
Everywhere AND Be Native'.
It's still early days for the product but the top component developers
like Telerik and DevExpress are already developing components for Xamarin
.Forms.
9) It's the best of all worlds (Hybrid and Native)
If you've taken a look at my Xamarin mashup blog
http://www.michaelridland.com/mobile/asp-net-mvc-xamarin-mashups/ you'd
already know that the possibilities with Xamarin are vast, you can
essential create your own Cordova and you can completely integrate it with
your C# Mvvm/c# Native Code. So you have the full power of the .net
framework to build your client application architecture which becomes very
useful when you have complex requirements like Offline.
10) Large Community
Xamarin uses the .net framework and because of this it's
Re: Opinions sought on Xamarin
http://ionicframework.com/
On Fri, Oct 24, 2014 at 3:22 PM, Michael Ridland rid...@gmail.com wrote:
... but that said, Xamarin is pretty heavy weight, it's s big learning
curve.. if you want something lightweight and 'pretty' good you should try
out Ionic...
On Fri, Oct 24, 2014 at 3:19 PM, Michael Ridland rid...@gmail.com wrote:
Go Xamarin it's the best! (Opinion may be bias www.michaelridland.com)
Traditional Xamarin (Native API) as the platform is awesome and solid and
fast, the IDE and some of the tools around it can be a bit buggy.
Xamarin.Forms is pretty early, and can be frustrating but I have build some
XPlat app pretty rapidly with it.
Actually I'm doing a 'Introduction to Xamarin' at SydMobile in a few
weeks, you should come along I'd love to answer any questions you have.
http://www.meetup.com/SydMobile/
Below is a unpublished blog post on why you should use Xamarin...
*Should I use Xamarin for Mobile Development? YES you should!*
In my opinion you'd be insane if you didn't use Xamarin for mobile
development. Many people don't know what they're missing out on by not
using Xamarin so I'm going to highlight some reasons I think people
should be using Xamarin.
1) It's Native but with 80%+ code share?
So for those that aren't aware of Xamarin or how it works, Xamarin allows
you to develop apps for iOS, Android and Mac from a single code base. When
I say this I don't mean in a webview or customised API, it actually usesthe
Native APIs. So when developing you use UITableView which is the same
API that a native developer would be using.
2) C# and F# are Modern languages
C# might not be the hipster language of the year it is a continually
evolving language with solid features like type interference, dynamic
types, language integrated query (LINQ), async/await and first class
functions. C# is designed for developing large robust applications.
And for the functional types there's F#, which from what I've been told
it's like scala but faster and better thought out.
I'd argue they're better languages than java, javascript and
objective-c... and seeing that they're currently the only languages with
built in async you could say their even better than swift...
3) async/await
.. 'wait but javascript is all async' i hear you say... C#/F#
async/await is different to what people normally think async is. C#/F#
async/await tackles the callback hell problems in rich clients, anyone who
works with rich clients will know of these problems. This is a problem
that's attempted to be solved with promises and generators but neither are
at the level of async/await.
Here's a little before/after sample:
*Before:*
doAsync1(function () {
doAsync2(function () {
doAsync3(function () {
doAsync4(function () {
})
})
})
})
*After:*
await doAsync1()
await doAsync2()
await doAsync3()
await doAsync4()
4) Watches, Google Glass wearables and the future of devices.
In case you haven't noticed the future isn't just mobiles it's wearables,
devices and IOT. Xamarin has same day support for all these platforms
including android wear, google glass, Amazon TV and more. As I've said
beforeXamarin uses the Native APIs and compiles down to native so using
Xamarin you're in the perfect position develop all modern platforms.
5) It's ready now!
All the time I hear people say 'html is a fast moving target' or 'it will
get there eventually'. Xamarin is here now, it's Native and it's cross
platform. Why wait to have a great app when you can have it now and as a
bonus know that your application is future proof for future devices.
6) It's fast and stable
From personal experience the Xamarin traditional (Xamarin.iOS and
Xamarin.Android)
platform is solid, fast and stable. You'd be hard pressed to find a problem
with the core parts of the platform, any app bugs will probably be your own
bugs.
7) Documentation
The documentation for Xamarin is solid, it's generally better than the
Apple and Android documentation.
8) Xamarin.Forms
So how about 100% codeshare and still be Native? Xamarin.Forms allows
you to program against a single API and have that single API mapped to
native controls on each platform. Hanselman describes it well, 'Write Once
Run Everywhere AND Be Native'.
It's still early days for the product but the top component developers
like Telerik and DevExpress are already developing components for Xamarin
.Forms.
9) It's the best of all worlds (Hybrid and Native)
If you've taken a look at my Xamarin mashup blog
http://www.michaelridland.com/mobile/asp-net-mvc-xamarin-mashups/ you'd
already know that the possibilities with Xamarin are vast, you can
essential create your own Cordova and you can completely integrate it with
your C# Mvvm/c# Native Code. So you have the full power of the .net
framework to build your client application architecture which becomes very
useful when you have complex
Re: Opinions sought on Xamarin
+1 for big leaning curve. Played around with it a bit few years ago then
didn't touch it til a few months ago and I was lost like never before. That
said, the Xamarin people have added so much to it now so stability is
probably much better now
On Fri, Oct 24, 2014 at 3:22 PM, Michael Ridland rid...@gmail.com wrote:
... but that said, Xamarin is pretty heavy weight, it's s big learning
curve.. if you want something lightweight and 'pretty' good you should try
out Ionic...
On Fri, Oct 24, 2014 at 3:19 PM, Michael Ridland rid...@gmail.com wrote:
Go Xamarin it's the best! (Opinion may be bias www.michaelridland.com)
Traditional Xamarin (Native API) as the platform is awesome and solid and
fast, the IDE and some of the tools around it can be a bit buggy.
Xamarin.Forms is pretty early, and can be frustrating but I have build some
XPlat app pretty rapidly with it.
Actually I'm doing a 'Introduction to Xamarin' at SydMobile in a few
weeks, you should come along I'd love to answer any questions you have.
http://www.meetup.com/SydMobile/
Below is a unpublished blog post on why you should use Xamarin...
*Should I use Xamarin for Mobile Development? YES you should!*
In my opinion you'd be insane if you didn't use Xamarin for mobile
development. Many people don't know what they're missing out on by not
using Xamarin so I'm going to highlight some reasons I think people
should be using Xamarin.
1) It's Native but with 80%+ code share?
So for those that aren't aware of Xamarin or how it works, Xamarin allows
you to develop apps for iOS, Android and Mac from a single code base. When
I say this I don't mean in a webview or customised API, it actually usesthe
Native APIs. So when developing you use UITableView which is the same
API that a native developer would be using.
2) C# and F# are Modern languages
C# might not be the hipster language of the year it is a continually
evolving language with solid features like type interference, dynamic
types, language integrated query (LINQ), async/await and first class
functions. C# is designed for developing large robust applications.
And for the functional types there's F#, which from what I've been told
it's like scala but faster and better thought out.
I'd argue they're better languages than java, javascript and
objective-c... and seeing that they're currently the only languages with
built in async you could say their even better than swift...
3) async/await
.. 'wait but javascript is all async' i hear you say... C#/F#
async/await is different to what people normally think async is. C#/F#
async/await tackles the callback hell problems in rich clients, anyone who
works with rich clients will know of these problems. This is a problem
that's attempted to be solved with promises and generators but neither are
at the level of async/await.
Here's a little before/after sample:
*Before:*
doAsync1(function () {
doAsync2(function () {
doAsync3(function () {
doAsync4(function () {
})
})
})
})
*After:*
await doAsync1()
await doAsync2()
await doAsync3()
await doAsync4()
4) Watches, Google Glass wearables and the future of devices.
In case you haven't noticed the future isn't just mobiles it's wearables,
devices and IOT. Xamarin has same day support for all these platforms
including android wear, google glass, Amazon TV and more. As I've said
beforeXamarin uses the Native APIs and compiles down to native so using
Xamarin you're in the perfect position develop all modern platforms.
5) It's ready now!
All the time I hear people say 'html is a fast moving target' or 'it will
get there eventually'. Xamarin is here now, it's Native and it's cross
platform. Why wait to have a great app when you can have it now and as a
bonus know that your application is future proof for future devices.
6) It's fast and stable
From personal experience the Xamarin traditional (Xamarin.iOS and
Xamarin.Android)
platform is solid, fast and stable. You'd be hard pressed to find a problem
with the core parts of the platform, any app bugs will probably be your own
bugs.
7) Documentation
The documentation for Xamarin is solid, it's generally better than the
Apple and Android documentation.
8) Xamarin.Forms
So how about 100% codeshare and still be Native? Xamarin.Forms allows
you to program against a single API and have that single API mapped to
native controls on each platform. Hanselman describes it well, 'Write Once
Run Everywhere AND Be Native'.
It's still early days for the product but the top component developers
like Telerik and DevExpress are already developing components for Xamarin
.Forms.
9) It's the best of all worlds (Hybrid and Native)
If you've taken a look at my Xamarin mashup blog
http://www.michaelridland.com/mobile/asp-net-mvc-xamarin-mashups/ you'd
already know that the possibilities with Xamarin are vast, you can
essential create your own Cordova and
Re: Opinions sought on Xamarin
On a related note, Dropbox used C++ for their Android/iOS apps -
http://oleb.net/blog/2014/05/how-dropbox-uses-cplusplus-cross-platform-development/
On 24 October 2014 15:22, Michael Ridland rid...@gmail.com wrote:
http://ionicframework.com/
On Fri, Oct 24, 2014 at 3:22 PM, Michael Ridland rid...@gmail.com wrote:
... but that said, Xamarin is pretty heavy weight, it's s big learning
curve.. if you want something lightweight and 'pretty' good you should try
out Ionic...
On Fri, Oct 24, 2014 at 3:19 PM, Michael Ridland rid...@gmail.com
wrote:
Go Xamarin it's the best! (Opinion may be bias www.michaelridland.com)
Traditional Xamarin (Native API) as the platform is awesome and solid
and fast, the IDE and some of the tools around it can be a bit buggy.
Xamarin.Forms is pretty early, and can be frustrating but I have build some
XPlat app pretty rapidly with it.
Actually I'm doing a 'Introduction to Xamarin' at SydMobile in a few
weeks, you should come along I'd love to answer any questions you have.
http://www.meetup.com/SydMobile/
Below is a unpublished blog post on why you should use Xamarin...
*Should I use Xamarin for Mobile Development? YES you should!*
In my opinion you'd be insane if you didn't use Xamarin for mobile
development. Many people don't know what they're missing out on by not
using Xamarin so I'm going to highlight some reasons I think people
should be using Xamarin.
1) It's Native but with 80%+ code share?
So for those that aren't aware of Xamarin or how it works, Xamarin allows
you to develop apps for iOS, Android and Mac from a single code base. When
I say this I don't mean in a webview or customised API, it actually usesthe
Native APIs. So when developing you use UITableView which is the same
API that a native developer would be using.
2) C# and F# are Modern languages
C# might not be the hipster language of the year it is a continually
evolving language with solid features like type interference, dynamic
types, language integrated query (LINQ), async/await and first class
functions. C# is designed for developing large robust applications.
And for the functional types there's F#, which from what I've been told
it's like scala but faster and better thought out.
I'd argue they're better languages than java, javascript and
objective-c... and seeing that they're currently the only languages with
built in async you could say their even better than swift...
3) async/await
.. 'wait but javascript is all async' i hear you say... C#/F#
async/await is different to what people normally think async is. C#/F#
async/await tackles the callback hell problems in rich clients, anyone who
works with rich clients will know of these problems. This is a problem
that's attempted to be solved with promises and generators but neither are
at the level of async/await.
Here's a little before/after sample:
*Before:*
doAsync1(function () {
doAsync2(function () {
doAsync3(function () {
doAsync4(function () {
})
})
})
})
*After:*
await doAsync1()
await doAsync2()
await doAsync3()
await doAsync4()
4) Watches, Google Glass wearables and the future of devices.
In case you haven't noticed the future isn't just mobiles it's
wearables, devices and IOT. Xamarin has same day support for all these
platforms including android wear, google glass, Amazon TV and more. As I've
said beforeXamarin uses the Native APIs and compiles down to native
so using Xamarin you're in the perfect position develop all modern
platforms.
5) It's ready now!
All the time I hear people say 'html is a fast moving target' or 'it
will get there eventually'. Xamarin is here now, it's Native and it's
cross platform. Why wait to have a great app when you can have it now and
as a bonus know that your application is future proof for future devices.
6) It's fast and stable
From personal experience the Xamarin traditional (Xamarin.iOS and
Xamarin.Android) platform is solid, fast and stable. You'd be hard
pressed to find a problem with the core parts of the platform, any app bugs
will probably be your own bugs.
7) Documentation
The documentation for Xamarin is solid, it's generally better than the
Apple and Android documentation.
8) Xamarin.Forms
So how about 100% codeshare and still be Native? Xamarin.Forms allows
you to program against a single API and have that single API mapped to
native controls on each platform. Hanselman describes it well, 'Write Once
Run Everywhere AND Be Native'.
It's still early days for the product but the top component developers
like Telerik and DevExpress are already developing components for
Xamarin.Forms.
9) It's the best of all worlds (Hybrid and Native)
If you've taken a look at my Xamarin mashup blog
http://www.michaelridland.com/mobile/asp-net-mvc-xamarin-mashups/ you'd
already know that the possibilities with Xamarin are vast, you can
essential create your own Cordova
Re: Opinions sought on Xamarin
Nice blog post... but if they had just used Xamarin their job would have
been alot easier.
They wouldn't of had to write their own persistance layer, with Xamarin you
can use the Native SQLite instances. Their serious backend code eg Offline,
Caching, would have been able to use C# and the full .net framework.
Actually the project I'm working on at the moment is more complicated than
the dropbox app, more feature with offline support etc and I've been
able to implement as a single developer...
For serious applications Xamarin is hands down the best!
On Fri, Oct 24, 2014 at 4:29 PM, William Luu will@gmail.com wrote:
On a related note, Dropbox used C++ for their Android/iOS apps -
http://oleb.net/blog/2014/05/how-dropbox-uses-cplusplus-cross-platform-development/
On 24 October 2014 15:22, Michael Ridland rid...@gmail.com wrote:
http://ionicframework.com/
On Fri, Oct 24, 2014 at 3:22 PM, Michael Ridland rid...@gmail.com
wrote:
... but that said, Xamarin is pretty heavy weight, it's s big learning
curve.. if you want something lightweight and 'pretty' good you should try
out Ionic...
On Fri, Oct 24, 2014 at 3:19 PM, Michael Ridland rid...@gmail.com
wrote:
Go Xamarin it's the best! (Opinion may be bias www.michaelridland.com)
Traditional Xamarin (Native API) as the platform is awesome and solid
and fast, the IDE and some of the tools around it can be a bit buggy.
Xamarin.Forms is pretty early, and can be frustrating but I have build some
XPlat app pretty rapidly with it.
Actually I'm doing a 'Introduction to Xamarin' at SydMobile in a few
weeks, you should come along I'd love to answer any questions you have.
http://www.meetup.com/SydMobile/
Below is a unpublished blog post on why you should use Xamarin...
*Should I use Xamarin for Mobile Development? YES you should!*
In my opinion you'd be insane if you didn't use Xamarin for mobile
development. Many people don't know what they're missing out on by not
using Xamarin so I'm going to highlight some reasons I think people
should be using Xamarin.
1) It's Native but with 80%+ code share?
So for those that aren't aware of Xamarin or how it works, Xamarin allows
you to develop apps for iOS, Android and Mac from a single code base. When
I say this I don't mean in a webview or customised API, it actually
usesthe Native APIs. So when developing you use UITableView which is
the same API that a native developer would be using.
2) C# and F# are Modern languages
C# might not be the hipster language of the year it is a continually
evolving language with solid features like type interference, dynamic
types, language integrated query (LINQ), async/await and first class
functions. C# is designed for developing large robust applications.
And for the functional types there's F#, which from what I've been told
it's like scala but faster and better thought out.
I'd argue they're better languages than java, javascript and
objective-c... and seeing that they're currently the only languages with
built in async you could say their even better than swift...
3) async/await
.. 'wait but javascript is all async' i hear you say... C#/F#
async/await is different to what people normally think async is. C#/F#
async/await tackles the callback hell problems in rich clients, anyone who
works with rich clients will know of these problems. This is a problem
that's attempted to be solved with promises and generators but neither are
at the level of async/await.
Here's a little before/after sample:
*Before:*
doAsync1(function () {
doAsync2(function () {
doAsync3(function () {
doAsync4(function () {
})
})
})
})
*After:*
await doAsync1()
await doAsync2()
await doAsync3()
await doAsync4()
4) Watches, Google Glass wearables and the future of devices.
In case you haven't noticed the future isn't just mobiles it's
wearables, devices and IOT. Xamarin has same day support for all these
platforms including android wear, google glass, Amazon TV and more. As I've
said beforeXamarin uses the Native APIs and compiles down to native
so using Xamarin you're in the perfect position develop all modern
platforms.
5) It's ready now!
All the time I hear people say 'html is a fast moving target' or 'it
will get there eventually'. Xamarin is here now, it's Native and it's
cross platform. Why wait to have a great app when you can have it now and
as a bonus know that your application is future proof for future devices.
6) It's fast and stable
From personal experience the Xamarin traditional (Xamarin.iOS and
Xamarin.Android) platform is solid, fast and stable. You'd be hard
pressed to find a problem with the core parts of the platform, any app bugs
will probably be your own bugs.
7) Documentation
The documentation for Xamarin is solid, it's generally better than the
Apple and Android documentation.
8) Xamarin.Forms
So how about 100% codeshare and
