blocks|key|4039806|text|托管代码==“拥有完整员工或管家、女佣、厨师和园丁的豪宅，以保持地方的整洁。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4039807|非托管代码==“我曾经住在大学里的地方”|4039808|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Managed Code == "Mansion House with an entire staff or Butlers, Maids, Cooks &amp; Gardeners to keep the place nice"

Unmanaged Code == "Where I used to live in University"

blocks|key|4039721|text|想想你的办公桌，如果你经常清理它，就会有空间坐在你面前实际正在做的事情。如果你不把它清理干净，你的空间就用完了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4039722|该空间相当于RAM、硬盘等计算机资源。|4039723|托管代码允许系统自动选择清理的时间和内容。非托管代码使该过程变得“手动”-因为程序员需要告诉系统何时清理以及清理什么。|4039724|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

think of your desk, if you clean it up regularly, there's space to sit what you're actually working on in front of you. if you don't clean it up, you run out of space.

That space is equivalent to computer resources like RAM, Hard Disk, etc.

Managed code allows the system automatically choose when and what to clean up. Unmanaged Code makes the process "manual" - in that the programmer needs to tell the system when and what to clean up.

blocks|key|3193425|text|我很确定基本的解释是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3193426|3193427|Managed+=运行时管理的资源清理(例如，垃圾Collection)|unordered-list-item|offset|length|style|BOLD|3193428|Unmanaged+=您自己清理(例如，free)|CODE|3193429|和malloc|3193430|entityMap^0|0|0|0|7|0|0|9|K|4|0|1|6|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@$F|W|G|X|H|I]|$F|Y|G|Z|H|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|10|8|@$F|11|G|12|H|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|P|$]]

I'm pretty sure the basic interpretation is:

<ul>
<li>Managed = resource cleanup managed by runtime (i.e. Garbage Collection)</li>
<li>Unmanaged = clean up after yourself (i.e. <code>malloc</code> &amp; <code>free</code>)</li>
</ul>

blocks|key|5451570|text|我对这次讨论中出现的东西感到惊讶(嗯，不是真的，而是在修辞上)。让我补充一些东西，即使我迟到了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5451571|虚拟机(VM)和垃圾收集(GC)+是几十年前的和这两个独立的概念。垃圾收集的本机代码编译语言已经存在了，甚至是几十年前的语言(典型的例子：ANSI+Common+Lisp；好吧，至少有一种+garbage-collected声明性语言--+Mercury+-但显然大众对类似Prolog的语言叫苦不迭)。|offset|length|style|BOLD|5451572|突然之间，基于GCed字节码的虚拟机成为治疗所有IT疾病的灵丹妙药。Sandboxing+of+existing+binaries+(其他示例here、here和here)？Principle+of+least+authority+(POLA)/capabilities-based+security？Slim+binaries+(或其现代变体SafeTSA)？Region+inference？不，先生:微软和Sun甚至没有授权我们只考虑这样的变态。不，最好为这个精彩的(？)重写我们的整个软件堆栈新(？)语言§/API。正如我们的一位主持人所说，这又是一次。|5451573|§别傻了:我知道C#不是唯一一种针对.Net/Mono的语言，它是一种hyperbole。|5451574|编辑：根据我所指出的内存管理/安全/代码移动性的替代技术来看待S.Lott的comments+to+this+answer特别有指导意义。|5451575|我的观点是，非技术人员不需要为这种详细程度的技术细节而烦恼。|5451576|另一方面，如果他们对微软/Sun的营销印象深刻，有必要向他们解释他们被愚弄了-基于GCed字节码的VM并不像他们声称的那样新颖，它们不能神奇地解决每一个it问题，并且存在这些实现技术的替代方案(有些更好)。|5451577|编辑2:垃圾收集是一种内存管理技术，作为每种实现技术，都需要理解才能正确使用。看看ITA+Software的they+bypass+GC+to+obtain+good+perfomance是如何做到的|5451578|5451579|+4-因为我们需要快速访问大约2+of的静态数据，所以我们使用C%2B%2B代码对包含无指针C结构(航班、票价等)的大型文件进行内存映射，然后使用外部数据访问从Common+Lisp访问这些文件。一个struct字段访问会编译成两条或三条指令，所以实际上没有任何性能。访问C而不是Lisp对象的代价。通过这样做，我们阻止了Lisp垃圾收集器看到数据(对于Lisp，每个指向C对象的指针都只是一个补丁，尽管我们经常将这些指针临时包装在Lisp对象中以提高可调试性)。因此，我们的Lisp图像只有大约250兆的“工作”数据结构和代码。|blockquote|5451580|5451581|..。|5451582|9-我们可以在一个800+and的盒子上做10秒的Lisp计算，而不超过5k的数据。这是因为我们预先分配了我们需要的所有数据结构，并在超过它们的查询中死亡。这可能会让许多Lisp程序员畏缩不前，但由于250兆的图像和实时限制，我们不能产生垃圾。例如，我们不使用cons，而是使用"cons!"，它从我们预先分配的10,000,000个单元格的数组中获取单元格，并在每次查询时重置。|5451583|5451584|编辑3:+(为了避免误解)+GC比直接摆弄指针更好吗？当然，大多数时候都是这样，但是和都有替代方案。有必要用这些细节来烦扰用户吗？除了在必要时驱散一些营销炒作之外，我没有看到任何证据表明这是真的。|5451585|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Common_Lisp|1|http://www.cs.mu.oz.au/research/mercury/information/papers.html#mazur-thesis|2|http://www.sandboxie.com/|3|http://pdos.csail.mit.edu/papers/vx32:usenix08/|4|http://www.ecsl.cs.sunysb.edu/bird/|5|http://code.google.com/p/nativeclient/|6|http://en.wikipedia.org/wiki/Principle_of_least_authority|7|http://www.erights.org/|8|http://docs.google.com/gview?a=v&q=cache:WgXzRpdXtusJ:www.oberon2005.ru/paper/mf1997-01e.pdf|9|http://en.wikipedia.org/wiki/SafeTSA|10|http://en.wikipedia.org/wiki/Region_inference|11|http://en.wikipedia.org/wiki/Hyperbole|12|https://stackoverflow.com/questions/252014/how-would-you-describe-the-difference-between-managed-byte-code-and-unmanaged-nat/252026#252026|13|http://www.paulgraham.com/carl.html^0|0|H|6|O|8|1X|G|0|2M|I|1|0|Y|V|2|1Z|4|3|24|4|4|29|4|5|2F|Z|6|3F|R|7|47|D|8|4S|7|9|51|G|A|0|Z|9|B|0|0|3|12|N|C|0|0|U|0|0|0|4|1I|14|D|0|0|13|3|48|I|0|0|0|35|8|0|0|0|4|16|1|1P|2|0^^$0|@$1|2|3|4|5|6|7|23|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|24|8|@$D|25|E|26|F|G]|$D|27|E|28|F|G]]|9|@$D|29|E|2A|1|2B]|$D|2C|E|2D|1|2E]]|A|$]]|$1|H|3|I|5|6|7|2F|8|@]|9|@$D|2G|E|2H|1|2I]|$D|2J|E|2K|1|2L]|$D|2M|E|2N|1|2O]|$D|2P|E|2Q|1|2R]|$D|2S|E|2T|1|2U]|$D|2V|E|2W|1|2X]|$D|2Y|E|2Z|1|30]|$D|31|E|32|1|33]|$D|34|E|35|1|36]]|A|$]]|$1|J|3|K|5|6|7|37|8|@]|9|@$D|38|E|39|1|3A]]|A|$]]|$1|L|3|M|5|6|7|3B|8|@$D|3C|E|3D|F|G]]|9|@$D|3E|E|3F|1|3G]]|A|$]]|$1|N|3|O|5|6|7|3H|8|@$D|3I|E|3J|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|3K|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|3L|8|@$D|3M|E|3N|F|G]]|9|@$D|3O|E|3P|1|3Q]]|A|$]]|$1|T|3|-4|5|6|7|3R|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|3S|8|@$D|3T|E|3U|F|G]|$D|3V|E|3W|F|G]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|3X|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|3Z|8|@$D|40|E|41|F|G]]|9|@]|A|$]]|$1|12|3|-4|5|6|7|42|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|43|8|@$D|44|E|45|F|G]|$D|46|E|47|F|G]|$D|48|E|49|F|G]]|9|@]|A|$]]|$1|15|3|-4|5|6|7|4A|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]|1D|$5|18|19|1A|A|$1B|1E]]|1F|$5|18|19|1A|A|$1B|1G]]|1H|$5|18|19|1A|A|$1B|1I]]|1J|$5|18|19|1A|A|$1B|1K]]|1L|$5|18|19|1A|A|$1B|1M]]|1N|$5|18|19|1A|A|$1B|1O]]|1P|$5|18|19|1A|A|$1B|1Q]]|1R|$5|18|19|1A|A|$1B|1S]]|1T|$5|18|19|1A|A|$1B|1U]]|1V|$5|18|19|1A|A|$1B|1W]]|1X|$5|18|19|1A|A|$1B|1Y]]|1Z|$5|18|19|1A|A|$1B|20]]|21|$5|18|19|1A|A|$1B|22]]]]

I'm astonished by what emerges from this discussion (well, not really but rhetorically). Let me add something, even if I'm late.

Virtual Machines (VMs) and Garbage Collection (GC) are decades old and two separate concepts. Garbage-collected native-code compiled languages exist, even these from decades (canonical example: <a href="http://en.wikipedia.org/wiki/Common_Lisp" rel="nofollow noreferrer">ANSI Common Lisp</a>; well, there is at least a <a href="http://www.cs.mu.oz.au/research/mercury/information/papers.html#mazur-thesis" rel="nofollow noreferrer">compile-time garbage-collected</a> declarative language, Mercury - but apparently the masses scream at Prolog-like languages).

Suddenly GCed byte-code based VMs are a panacea for all IT diseases. <a href="http://www.sandboxie.com/" rel="nofollow noreferrer">Sandboxing of existing binaries</a> (other examples <a href="http://pdos.csail.mit.edu/papers/vx32:usenix08/" rel="nofollow noreferrer">here</a>, <a href="http://www.ecsl.cs.sunysb.edu/bird/" rel="nofollow noreferrer">here</a> and <a href="http://code.google.com/p/nativeclient/" rel="nofollow noreferrer">here</a>)? <a href="http://en.wikipedia.org/wiki/Principle_of_least_authority" rel="nofollow noreferrer">Principle of least authority (POLA)</a>/<a href="http://www.erights.org/" rel="nofollow noreferrer">capabilities-based security</a>? <a href="http://docs.google.com/gview?a=v&amp;q=cache:WgXzRpdXtusJ:www.oberon2005.ru/paper/mf1997-01e.pdf" rel="nofollow noreferrer">Slim binaries</a> (or its modern variant <a href="http://en.wikipedia.org/wiki/SafeTSA" rel="nofollow noreferrer">SafeTSA</a>)? <a href="http://en.wikipedia.org/wiki/Region_inference" rel="nofollow noreferrer">Region inference</a>? No, sir: Microsoft &amp; Sun does not authorize us to even only think about such perversions. No, better rewrite our entire software stack for this wonderful(???) new(???) language§/API. As one of our hosts says, it's <a href="http://www.joelonsoftware.com/articles/fog0000000339.html" rel="nofollow noreferrer">Fire and Motion</a> all over again.

§ Don't be silly: I know that C# is not the only language that target .Net/Mono, it's an <a href="http://en.wikipedia.org/wiki/Hyperbole" rel="nofollow noreferrer">hyperbole</a>.

Edit: it is particularly instructive to look at <a href="https://stackoverflow.com/questions/252014/how-would-you-describe-the-difference-between-managed-byte-code-and-unmanaged-nat/252026#252026">comments to this answer</a> by S.Lott in the light of alternative techniques for memory management/safety/code mobility that I pointed out.

My point is that non technical people don't need to be bothered with technicalities at this level of detail.

On the other end, if they are impressed by Microsoft/Sun marketing it is necessary to explain them that they are being fooled - GCed byte-code based VMs are not this novelty as they claim, they don't solve magically every IT problem and alternatives to these implementation techniques exist (some are better).

Edit 2: Garbage Collection is a memory management technique and, as every implementation technique, need to be understood to be used correctly. Look how, at ITA Software, <a href="http://www.paulgraham.com/carl.html" rel="nofollow noreferrer">they bypass GC to obtain good perfomance</a>:

<blockquote>
 4 - Because we have about 2 gigs of static data we need rapid access to,
 we use C++ code to memory-map huge
 files containing pointerless C structs
 (of flights, fares, etc), and then
 access these from Common Lisp using
 foreign data accesses. A struct field
 access compiles into two or three
 instructions, so there's not really
 any performance. penalty for accessing
 C rather than Lisp objects. By doing
 this, we keep the Lisp garbage
 collector from seeing the data (to
 Lisp, each pointer to a C object is
 just a fixnum, though we do often
 temporarily wrap these pointers in
 Lisp objects to improve
 debuggability). Our Lisp images are
 therefore only about 250 megs of
 "working" data structures and code.
 
 ...
 
 9 - We can do 10 seconds of Lisp computation on a 800mhz box and cons
 less than 5k of data. This is because
 we pre-allocate all data structures we
 need and die on queries that exceed
 them. This may make many Lisp
 programmers cringe, but with a 250 meg
 image and real-time constraints, we
 can't afford to generate garbage. For
 example, rather than using cons, we
 use "cons!", which grabs cells from an
 array of 10,000,000 cells we've
 preallocated and which gets reset
 every query.
</blockquote>

Edit 3: (to avoid misunderstanding) is GC better than fiddling directly with pointers? Most of the time, certainly, but there are alternatives to both. Is there a need to bother users with these details? I don't see any evidence that this is the case, besides dispelling some marketing hype when necessary.

blocks|key|4039851|text|也许可以将其与投资股票市场进行比较。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4039852|你可以自己买卖股票，试图成为一名能带来最佳风险/回报的专家--或者你可以投资一只由一位“专家”管理的基金，他会为你做这件事--代价是你失去了一些控制权，可能还会失去一些佣金。(诚然，我更喜欢跟踪器基金，股市“专家”最近表现不是很好，但....)|4039853|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Perhaps compare it with investing in the stock market.

You can buy and sell shares yourself, trying to become an expert in what will give the best risk/reward - or you can invest in a fund which is managed by an "expert" who will do it for you - at the cost of you losing some control, and possibly some commission. (Admittedly I'm more of a fan of tracker funds, and the stock market "experts" haven't exactly done brilliant recently, but....)

blocks|key|849819|text|这是我的答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|849820|托管(.NET)或字节码(Java)将为您节省时间和金钱。|849821|现在让我们将两者进行比较：|849822|非托管代码或本机代码|offset|length|style|BOLD|849823|您需要进行自己的资源(RAM+/内存)分配和清理。如果你忘记了什么，你最终会导致所谓的“内存泄漏”，这可能会使计算机崩溃。内存泄漏是一个术语，表示应用程序开始耗尽(消耗完)Ram/内存，但不会释放它，以便计算机可以将其用于其他应用程序；最终，这会导致计算机崩溃。|849824|为了在不同的操作系统(Mac+OSX、Windows等)上运行应用程序您需要专门为每个操作系统编译您的代码，并且可能会更改许多特定于操作系统的代码，以便在每个操作系统上运行。|849825|.NET托管代码或Java字节码|849826|所有资源(RAM+/内存)的分配和清理都会为您完成，并将创建“内存泄漏”的风险降至最低。这允许更多的时间来编码功能，而不是将其花费在资源管理上。|849827|为了在不同的操作系统(Mac+OSX、Windows等)上运行应用程序你只需编译一次，只要它们支持你的应用程序运行在其上的给定框架(Java/+Mono或.NET)，它就可以在每个框架上运行。|849828|短中的|849829|使用Java+(托管代码)或.NET+(字节码)进行开发使构建能够轻松面向多个操作系统的应用程序的总体成本更低，并允许将更多的时间用于构建丰富的功能，而不是普通的内存/资源管理任务。|849830|此外，在有人指出.NET框架不支持多种操作系统之前，我需要指出的是，从技术上讲，Windows98、WinXP+32位、WinXP+64位、WinVista+32位、WinVista+64位和Windows+Server都是不同的操作系统，但每种操作系统都可以运行相同的.NET应用程序。此外，还有为Linux和Mac带来.NET的Mono+Project。|849831|entityMap|0|LINK|mutability|MUTABLE|url|http://mono-project.com/|1^0|0|0|0|0|A|0|0|0|0|G|0|0|20|4|0|0|0|0|2J|0|0|4Z|4M|C|1|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1D|8|@$H|1E|I|1F|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1H|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1I|8|@$H|1J|I|1K|J|K]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1L|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1M|8|@]|9|@$H|1N|I|1O|1|1P]]|A|$]]|$1|V|3|W|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1R|8|@$H|1S|I|1T|J|K]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1U|8|@$H|1V|I|1W|J|K]]|9|@$H|1X|I|1Y|1|1Z]]|A|$]]|$1|11|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18]]|19|$5|14|15|16|A|$17|18]]]]

Here's my Answer:

Managed (.NET) or Byte Code (Java) will save you time and money.

Now let's compare the two:

Unmanaged or Native Code

You need to do your own resource (RAM / Memory) allocation and cleanup. If you forget something, you end up with what's called a "Memory Leak" that can crash the computer. A Memory Leak is a term for when an application starts using up (eating up) Ram/Memory but not letting it go so the computer can use if for other applications; eventually this causes the computer to crash.

In order to run your application on different Operating Systems (Mac OSX, Windows, etc.) you need to compile your code specifically for each Operating System, and possibly change alot of code that is Operating System specific so it works on each Operating System.

.NET Managed Code or Java Byte Code

All the resource (RAM / Memory) allocation and cleanup are done for you and the risk of creating "Memory Leaks" is reduced to a minimum. This allows more time to code features instead of spending it on resource management.

In order to run you application on different Operating Systems (Mac OSX, Windows, etc.) you just compile once, and it'll run on each as long as they support the given Framework you are app runs on top of (.NET Framework / <a href="http://mono-project.com" rel="nofollow noreferrer">Mono</a> or Java).

In Short

Developing using the .NET Framework (Managed Code) or Java (Byte Code) make it overall cheaper to build an application that can target multiple operating systems with ease, and allow more time to be spend building rich features instead of the mundane tasks of memory/resource management.

Also, before anyone points out that the .NET Framework doesn't support multiple operating systems, I need to point out that technically Windows 98, WinXP 32-bit, WinXP 64-bit, WinVista 32-bit, WinVista 64-bit and Windows Server are all different Operating Systems, but the same .NET app will run on each. And, there is also the <a href="http://mono-project.com" rel="nofollow noreferrer">Mono Project</a> that brings .NET to Linux and Mac OSX.

blocks|key|855231|text|非托管代码是计算机要遵循的指令列表。托管代码是计算机的任务列表，计算机可以自由地解释如何完成这些任务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|855232|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Unmanaged code is a list of instructions for the computer to follow.
Managed code is a list of tasks for the computer follow that the computer is free to interpret on its own on how to accomplish them.

blocks|key|5451418|text|最大的区别是内存管理。对于本机代码，您必须自己管理内存。这可能是困难的，并且是许多bug的原因，并且花费了大量的开发时间来跟踪这些bug。使用托管代码，您仍然会遇到问题，但这些问题要少得多，而且更容易跟踪。这通常意味着更少的buggy软件，更少的开发时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5451419|还有其他区别，但内存管理可能是最大的区别。|5451420|如果他们仍然感兴趣，我可能会提到许多缓冲区溢出的漏洞，而您不会在托管代码中获得这些漏洞，或者代码重用现在很容易，或者我们不再需要处理COM+(如果您幸运的话)。我可能会远离COM，否则我会对它有多糟糕发表长篇大论。|5451421|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The big difference is memory management. With native code, you have to manage memory yourself. This can be difficult and is the cause of a lot of bugs and lot of development time spent tracking down those bugs. With managed code, you still have problems, but a lot less of them and they're easier to track down. This normally means less buggy software, and less development time.

There are other differences, but memory management is probably the biggest.

If they were still interested I might mention how a lot of exploits are from buffer overruns and that you don't get that with managed code, or that code reuse is now easy, or that we no longer have to deal with COM (if you're lucky anyway). I'd probably stay way from COM otherwise I'd launch into a tirade over how awful it is.

blocks|key|4040094|text|这就像玩台球的边缘有没有保险杠的区别。除非你和所有其他球员总是投得很好，否则你需要一些东西来保持球在桌上。(忽略故意的弹跳...)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4040095|或者使用有墙的足球而不是边线和终点线，或者没有后盾的棒球，没有球门后面的网的曲棍球，没有障碍的纳斯卡，或者没有头盔的足球…)|4040096|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It's like the difference between playing pool with and without bumpers along the edges. Unless you and all the other players always make perfect shots, you need something to keep the balls on the table. (Ignore intentional ricochets...)

Or use soccer with walls instead of sidelines and endlines, or baseball without a backstop, or hockey without a net behind the goal, or NASCAR without barriers, or football without helmets ...)

blocks|key|3193315|text|“托管代码这一特定术语在微软世界中特别普遍。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3193316|因为我在MacOS和Linux界工作，所以我不会使用或遇到这个术语。|3193317|布拉德·艾布拉姆斯的博客文章"What+is+Managed+Code“的定义类似于".NET框架公共语言运行时”。|offset|length|3193318|我的观点是:可能根本不适合用术语来解释它。如果它是一个bug，hack或者变通方法，它并不是很重要。当然还不够重要，无法做出复杂的门外汉描述。它可能会随着下一批MS产品的发布而消失。|3193319|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/brada/archive/2004/01/09/48925.aspx^0|0|0|F|K|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

"The specific term managed code is particularly pervasive in the Microsoft world."

Since I work in MacOS and Linux world, it's not a term I use or encounter.

The Brad Abrams "<a href="http://blogs.msdn.com/brada/archive/2004/01/09/48925.aspx" rel="nofollow noreferrer">What is Managed Code</a>" blog post has a definition that say things like ".NET Framework Common Language Runtime".

My point is this: it may not be appropriate to explain it the terms at all. If it's a bug, hack or work-around, it's not very important. Certainly not important enough to work up a sophisticated lay-persons description. It may vanish with the next release of some batch of MS products.

Sometimes it's difficult to describe some of the things that "us programmers" may think are simple to non-programmers and management types.

So...

How would you describe the difference between Managed Code (or Java Byte Code) and Unmanaged/Native Code to a Non-Programmer?

What's the difference between Managed/Byte Code and Unmanaged/Native Code?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有时很难描述一些“我们程序员”可能认为对非程序员和管理类型来说很简单的事情。所以..。对于非程序员，您如何描述托管代码(或Java字节代码)和非托管/本机代码之间的区别？

问托管/字节码和非托管/本机代码有什么区别？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问托管/字节码和非托管/本机代码有什么区别？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问托管/字节码和非托管/本机代码有什么区别？
EN