Group items matching

in title, tags, annotations or url

It occurred to me that the title of this blog is going to mean something different to anyone who reads it. So I will explain what it means to me.A lifecycle describes the progression of something from its very conception until it no longer has any value. A lifecycle breaks down this progression into generalized stages so we can be smart about dealing with whatever it is based on where we think it is in the lifecycle. The most obvious lifecycle is our own from child, to young adult, to middle age, to old age. We make these distinctions in order deal with the realities of say, voting, retirement planning, and advertising. It's one lifecycle, but it is treated differently by government, banking, and marketing stakeholders, respectively.

design and build your application as a .NET client application, then assign the portions of the application to run on the server and the client tiers late in the development process. The compiler creates cross-browser JavaScript for the client tier, web services for the server tier, and communication, serialization, synchronization, security, and other boilerplate code to tie the tiers together.

QuickGraph 2.0 provides generic directed graph datastructures and algorithms for .Net 2.0. QuickGraph comes with algorithms such as depth first seach, breath first search, shortest path, network flow etc... QuickGraph supports GLEE and Graphviz to render the graphs.

Almost every article I see that describes the difference between value types and reference types explains in (frequently incorrect) detail about what “the stack” is and how the major difference between value types and reference types is that value types go on the stack.

I find this characterization of a value type based on its implementation details rather than its observable characteristics to be both confusing and unfortunate. Surely the most relevant fact about value types is not the implementation detail of how they are allocated, but rather the by-design semantic meaning of “value type”, namely that they are always copied “by value”.

Of course, the simplistic statement I described is not even true. As the MSDN documentation correctly notes, value types are allocated on the stack sometimes. For example, the memory for an integer field in a class type is part of the class instance’s memory, which is allocated on the heap.

The web browser is a good example, on a pc it may make sense to ask a user to find, click, type, and browse the web or look for a service. In a mobile, converged product, you need to help the user be present with the service even or especially when they are driving or have the product in a pocket or handbag, and requiring them to constantly select 'yes' or to type in forms etc. are real headaches for a consumer.

We will not provide a store front, but will help the community create multiple online stores from which they can generate revenue for themselves and the developer.

At the other end of the spectrum, you see hoards of teenagers in the U.S., Europe and Asia happily texting one handed, using predictive text.

It is impossible to build a hash table in JavaScript that works on arbitrary objects. You would have to manually allocate unique ID’s for every object and include them in the toString. So no collections in JavaScript. Adobe provides a true built-in hashtable in ActionScript 3.

Objects can function as sets and maps. Arrays can function as lists and iterators (generate an array when you need an iterator). More that good enough in this context.

VB also often compiles down to better MSIL than C#. It is also the only .NET language with first-class edit-and-continue Lisp-like debugging capabilities.