# shouldn't Published articles for shouldn't. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Sandboxing landscape DevFeed: [Sandboxing landscape]() Original publisher: [Read original article]() Author: Marek Published: 2017-03-27T22:00:00Z Content type: article Language: en Sources: [Marek Majkowski]() Topics: [Security](), [virtualization](), [Programming language](), [Process]() Tags: [isolation](), [javascript](), [lua](), [multi-tenancy](), [sandboxing](), [shouldn-t](), [virtualization]() ### AI overview This article surveys four approaches to isolating untrusted third-party code: programming-language runtimes, operating-system processes, software fault isolation, and virtual machines. It discusses requirements such as multi-tenancy, scheduling, memory limits, and restricting privileged operations, then examines Lua and JavaScript as examples. ### Source excerpt Sandboxing landscape Some time ago I started wondering - would it be possible for a CDN to run customer code on the edge servers? I read and asked around, over time I got acquainted to what is and what is not technically possible. But that didn't bring me closer to an useful answer. Fortunately exploring this subject has been enormous fun. In this blog post I'll describe my findings so far. ## How Agencies & Freelancers Should Do Web Hosting DevFeed: [How Agencies & Freelancers Should Do Web Hosting]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-03-09T07:10:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [hosting](), [Web](), [Server](), [Website]() Tags: [afterthought](), [article](), [hosting](), [insights](), [shouldn-t](), [useless](), [web-hosting](), [webserver](), [websites]() ### AI overview This article explains why agencies and freelancers should treat web hosting as an important project decision. It compares shared, managed, and VPS hosting and argues that VPS hosting is often the best choice, while criticizing shared hosting for its cost and reliability tradeoffs. ### Source excerpt Websites are useless without a webserver hosting it. Yet web hosting is often an afterthought. It shouldn't be. ## Value Types and Memory Usage DevFeed: [Value Types and Memory Usage]() Original publisher: [Read original article]() Published: 2012-11-28T00:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [C#](), [Algorithms, Complexity](), [Code](), [Sorting]() Tags: [algorithms](), [c-sharp](), [memory](), [shouldn-t](), [statement]() ### AI overview This article explains why sorting C# value types can use more memory than sorting reference types. Copies, boxing, and unboxing contribute to the overhead, although passing values by reference or using a custom sorting algorithm can avoid some additional memory use. ### Source excerpt Last week a respected colleague mentioned off hand that sorting on a value type takes a lot of memory in C#. Interested, I looked into this to see why/when this is true. Value types (using the struct keyword) are always passed by value, unlike reference types (class keyword) which are always passed by reference. This means that every time you pass them into a method, the whole value is copied; whereas with reference types, only the reference (pointer) is copied. Pointers are 4 to 8 bytes, so his original statement is only of concern if your value types are larger than that. Some such types are DateTime, Guid, and BsonObjectId. Some people like to think of value types as being allocated on the stack (versus the heap). In C#, this is irrelevant. The CLR allocates value and reference types wherever it feels like. Usually, local variables and parameters are stored on the stack (or registers) and values that are members of a class are usually allocated on the heap. It was done this way because the folks who wrote the CLR believe they can do a good enough job of optimizing stack and heap usage, so you shouldn't worry about it. If you're in C#, you shouldn't care where they're allocated. If you're doing something that requires you to care, you need to either break into an unsafe C# code block or C++. As for his actual statement - yes, using Base Class Library algorithms for sorting on value types will take more memory for value types than reference types because it has to copy values. However, there are exceptions to this. You can always write method parameters with the ref keyword so they're passed by reference. This would fix the problem of copying, but the all of the BCL classes* are written generically by using IComparable or some other interface. When you cast a value type like an Int32 to an interface like IComparable, it has to be boxed into a reference type. When boxing, the CLR allocates a managed reference type object and then copies the Int32 value into the mana