Fighting against Bloated Software

Today, hard disk space, memory and internet speeds are cheap, but that shouldn’t be an excuse to write bloated software. Not surprisingly, software development tools tend to be the biggest offenders in this space – massive applications that eat up your disk space and hog system resources.

What can you do if you need to run resource-hungry developer tools all day? You could go buy faster, bulkier computers that can hopefully take the load. You’ll have to guard against constant computer cooling fan noise, but one advantage may be reduced heating bills in winter. You’ll need a bigger backpack too!

What developers really want is productivity everywhere. When you have super-thin lightweight computers like the MacBook or Surface Pro 4 that let you work from anywhere, isn’t it time to call out bloated software? Portability can be performant if software development tools cooperate. This article discusses some of our most-used development tools, comparing them against lightweight efficient counterparts.

I hereby declare an an all-out war against bloated developer tools – make them light or I’m switching!

Read the whole article on TDN over HERE.

Adios!

Building NativeScript UI for .NET Developers

NativeScript is a framework for building cross-platform native mobile apps, with JavaScript. The ability to build cross-platform truly native apps from a single code base of JavaScript/TypeScript, XML and CSS can be exciting. As we saw in Part 1 of this series, NativeScript has a lot for .NET developers: robust Visual Studio support throughout app life cycle; easy JavaScript abstractions over native APIs; and full TypeScript support for building business logic.

Perhaps you’re not convinced yet though, with your biggest concern being user interface (UI). Surely building an abstracted, cross-platform UI cannot be easy? Maybe your background is in XAML or other UI composition markups in .NET, and you are just used to a rich developer ecosystem of tooling. These are valid concerns, but relax.

NativeScript has your back when it comes to UI composition. It combines simple markup with an abstracted platform-specific rendering. If you’re used to the richness of XAML, I think you’ll feel right at home building native UIs with NativeScript. In this article, I’ll walk you through building a NativeScript UI from a .NET developer’s perspective – I think you’ll be excited by what we find.

Read the whole article on TDN over HERE.

Adios!

NativeScript for .NET Developers

Contrary to what it may sound like, NativeScript is not a programming language – in fact, it simply uses languages you may already know: JavaScript, CSS and XML. NativeScript is a framework for building cross-platform truly native mobile apps with JavaScript!

There is no DOM, no cross-compilation and no hybrid mobile WebViewrendering. You have a single codebase of JavaScript, XML and CSS towards making a native app that runs cross-platform. NativeScript as a platform is open source, and offers free developer tooling via the Command Line Interface (CLI).

Now, it may sound like NativeScript is mostly catering to JavaScript developers – you know, those skinny jeans hipsters, so to speak. While you may respect non-Microsoft developers, perhaps you are not one of them. Maybe you are a .NET developer on the Microsoft stack and rather proud of it. If so, you’d have good reason – it is one of the richest possible developer ecosystems and with some of the best tooling available.

It turns out, NativeScript has lots and lots of appeal for .NET developers. You’re going to enjoy the possibilities. Let’s dive in.

Read the whole article on TDN over HERE.

Adios!