F#, which is usually pronounced as F sharp is one of the newly launched and rapidly developing programming languages.  It has recently become focus of attention due to its quick advancement to the 12^th position in the recent TIOBE index and the overall rise in popularity.

What is F#?

F# is an open source, functional and object oriented programming language which is available in cross platform. It was developed by a company called F# software foundation with help of Microsoft and other open contributors. F# runs on Linux, windows, iOS, Android and the GPUs and HTML as well. It is a mature programming language which helps the users as well as the organizations to solve the complex problems in a much simpler way with easy code. With its wide range of usage in the specialist and application areas, it is proving itself to be a worthy contender for the top 10 list.

Why choose F#?

Creating an enum in Python prior to Python 3.4 was accomplished as follows:

def enum(**enums)::
      return type('Enum',(),enums)

then use as:

Animals=enum(Dog=1,Cat=2)

and accessed as:

Animals.Dog

The new version can be created as follows:

from enum import Enum

class Animal(Enum):
    Dog=1
    Cat=2

Unless you have a great product, service or idea for which people are willing to wait, chances are highly likely that these potential clients will leave your website should your response time take too long to their incoming requests.  Ignore your application’s performance and you are more likely to be dumped by your users sooner than expected.

To improve the performance of an ASP.Net application you need to optimize your front-end UI (user interface) code as well as the back-end database. You can also think of the following tips as a brief best practices guide for the ASP.net performance optimization. So, whether you are a developer, UI designer or member of the deployment team, the following tips may help you. No matter what’s your role in the project or what you do to boost performance of your application, always remember that your goal should be to:

·          Minimize the amount of data you sent across the network.

·          Reduce the number of server requests.

Here you go (in no particular order)

At Database level

When making a strategic cloud decision, organizations can follow either one of two ideologies: open or closed.

In the past, major software technologies have been widely accepted because an emerging market leader simplified the initial adoption.  After a technology comes of age, the industry spawns open alternatives that provide choice and flexibility, and the result is an open alternative that quickly gains traction and most often outstrips the capabilities of its proprietary predecessor.

After an organization invests significantly in a technology, the complexity and effort required steering a given workload onto a new system or platform is, in most cases, significant. Switching outlays, shifting to updated or new software/hardware platforms, and the accompanying risks may lead to the ubiquitousness of large, monolithic and complex ERP systems – reason not being that they offer the best value for an organization, but rather because shifting to anything else is simply – unthinkable.

There’s no denying that these are critical considerations today since a substantial number of organizations are making their first jump into the cloud and making preparations for the upsetting shift in how IT is delivered to both internal and external clientele. Early adopters are aware of the fact that the innovation brought about by open technologies can bring dramatic change, and hence are realizing how crucial it is to be able to chart their own destiny.