C# PROGRAMMING –MAIN DESIGN GOALS

C# is a popular programming language these days, and it was designed from inception to provide a simple, clean, general purpose programming language for those intending to work within the confines of Microsoft’s .NET framework.  Since then, it has been approved as one of the standard languages by both ECMA and ISO, making C# programming an essential tool in every programmers’ kit.

Different languages have different uses and specialties, and C# was designed for programmers to be able to use it to create different components for use in software that would be deployed and distributed en masse, to live use environments.  This means that designers had to really put an emphasis on making the actual source code extremely compatible and portable.  Those already familiar with C or C++ should definitely notice this emphasis.

Another particular point of emphasis during design was focus on internationalization of the language; it was intended from inception to be available all over the world, and to see all sorts of different implementations based on variance in regional programming technique.  The resultant use should help the language develop sophistication as it is refined throughout different versions.

It is said that spoken languages shape thoughts by their inclusion and exclusion of concepts, and by structuring them in different ways. Similarly, programming languages shape solutions by making some tasks easier and others less aesthetic. Using F# instead of C# reshapes software projects in ways that prefer certain development styles and outcomes, changing what is possible and how it is achieved.

F# is a functional language from Microsoft's research division. While once relegated to the land of impractical academia, the principles espoused by functional programming are beginning to garner mainstream appeal.

As its name implies, functions are first-class citizens in functional programming. Blocks of code can be stored in variables, passed to other functions, and infinitely composed into higher-order functions, encouraging cleaner abstractions and easier testing. While it has long been possible to store and pass code, F#'s clean syntax for higher-order functions encourages them as a solution to any problem seeking an abstraction.

F# also encourages immutability. Instead of maintaining state in variables, functional programming with F# models programs as a series of functions converting inputs to outputs. While this introduces complications for those used to imperative styles, the benefits of immutability mesh well with many current developments best practices.

For instance, if functions are pure, handling only immutable data and exhibiting no side effects, then testing is vastly simplified. It is very easy to test that a specific block of code always returns the same value given the same inputs, and by modeling code as a series of immutable functions, it becomes possible to gain a deep and highly precise set of guarantees that software will behave exactly as written.

Further, if execution flow is exclusively a matter of routing function inputs to outputs, then concurrency is vastly simplified. By shifting away from mutable state to immutable functions, the need for locks and semaphores is vastly reduced if not entirely eliminated, and multi-processor development is almost effortless in many cases.

Type inference is another powerful feature of many functional languages. It is often unnecessary to specify argument and return types, since any modern compiler can infer them automatically. F# brings this feature to most areas of the language, making F# feel less like a statically-typed language and more like Ruby or Python. F# also eliminates noise like braces, explicit returns, and other bits of ceremony that make languages feel cumbersome.

Functional programming with F# makes it possible to write concise, easily testable code that is simpler to parallelize and reason about. However, strict functional styles often require imperative developers to learn new ways of thinking that are not as intuitive. Fortunately, F# makes it possible to incrementally change habits over time. Thanks to its hybrid object-oriented and functional nature, and its clean interoperability with the .net platform, F# developers can gradually shift to a more functional mindset while still using the algorithms and libraries with which they are most familiar.

Related F# Resources:

F# Programming Essentials Training

In May 2012 Google Chrome hit a milestone. It kicked Microsoft's Internet Explorer into excess phone oh that oh that second place as the most used browser on planet Earth.
With Microsoft being in second place, it makes a dark hole for Firefox coming in at number three. Google likes to trumpet three key reasons: security, simplicity and speed.
Available for free on Android, Linux, Mac, and Windows. It gets its speed from the open source JavaScript engine written in C++ known as V8.
In my daily use I use Microsoft's Internet Explorer version 10, Apple's Safari (on OS X) and chrome on both Windows 8 and OS X.

Admittedly people do not know anything about Internet Explorer version 10 since you can only get it on Windows 8/RT.

I do not need a crystal ball to know that the Mother of All Browser Battles is set to begin in the fall of 2012 and beyond.

I have said this before and I'm going to say it again.

It is hard not to wonder how current technology would have altered the events surrounding the tragic death of John F. Kennedy. On the afternoon of November 22, 1963, shots rang out in Dallas, TX, taking the life of JFK, one of the most beloved Americans. Given the same circumstances today, surely the advances in IT alone, would have drastically changed the outcome of that horrible day. Would the government have recognized that there was a viable threat looming over JFK? Would local and government agencies have been more prepared for a possible assassination attempt? Would the assortment of everyday communication devices assisted in the prevention of the assassination, not to mention, provided greater resources into the investigation? With all that the IT world has to offer today, how would it have altered the JFK tragedy?

As many conspiracy theories have rocked the foundation of the official story presented by government agencies, realization of the expansive nature of technology provides equal consideration as to how the event would have been changed had this technology been available during the time of the shooting. There were T.V. cameras, home 8mm recorders, even single shot-hand held cameras snapping away as the car caravan approached. Yet, there remains little documentation of the shooting and even less information pertaining to the precautions taken by officials prior to JFK's arrival. Theorists consider these possibilities along with how the world would have turned out had the great John F. Kennedynever been assassinated on that day.