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.

Static variables in Python are created as part of the class declaration.  By contrast, instance variables are created as part of a regular method and not a classmethod or staticmethod.

class A:
  i=3  # static variable
	
  def dosomethingregularmethod(self):
       self.k=4   # instance variable
	
# to access static variables


A.i

Net Neutrality

You may have heard about net neutrality over the years. Recently, the concept has gone through some changes, and many would consider its underlying principles to be in danger of corruption or dissolution. However, the technical nature of net neutrality ethics makes it difficult to understand for the layperson. Read on, and the central themes and controversies surrounding the principle will be outlined and explained for your convenience.

The Theme

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!