Difference between revisions of "Talk:Mono"
Jump to navigation
Jump to search
(new question) |
|||
| Line 1: | Line 1: | ||
Here's a question about mono that the article doesn't address: Will scripters be limited to LSL or will they be able to code in C# or something else more Mono-like? --[[User:Steamy Latte|Steamy Latte]] 12:20, 22 January 2008 (PST) | ==Other languages== | ||
Here's a question about mono that the article doesn't address: Will scripters be limited to | |||
LSL or will they be able to code in C# or something else more Mono-like? --[[User:Steamy Latte|Steamy Latte]] 12:20, 22 January 2008 (PST) | |||
:Until LL can ensure that Mono is properly sandboxed and secure, the compiler will remain server side and the only language available will be LSL. -- [[User:Strife Onizuka|Strife Onizuka]] 12:40, 23 January 2008 (PST) | :Until LL can ensure that Mono is properly sandboxed and secure, the compiler will remain server side and the only language available will be LSL. -- [[User:Strife Onizuka|Strife Onizuka]] 12:40, 23 January 2008 (PST) | ||
| Line 6: | Line 8: | ||
:::In 16k you don't want OOP. Trust me. The overhead would be killer. I just want pass by reference. Pass by value is the worst feature of LSO. If I had to guess I would say that most of speed improvements come from pass by reference alone. -- [[User:Strife Onizuka|Strife Onizuka]] 17:19, 24 January 2008 (PST) | :::In 16k you don't want OOP. Trust me. The overhead would be killer. I just want pass by reference. Pass by value is the worst feature of LSO. If I had to guess I would say that most of speed improvements come from pass by reference alone. -- [[User:Strife Onizuka|Strife Onizuka]] 17:19, 24 January 2008 (PST) | ||
==Compile Data Flow== | |||
Can someone describe the way the current flow works, and how the new flow will contrast. That is, I think at present: | |||
#You edit on the viewer. | |||
#When you [save], the source is uploaded. | |||
#A compiler in the viewer creates bytecode. | |||
#The bytecode is uploaded. | |||
Is this correct? How will this change, if at all? | |||
[[User:Lee Ponzu|Lee Ponzu]] 09:20, 26 January 2008 (PST) | |||
Revision as of 09:20, 26 January 2008
Other languages
Here's a question about mono that the article doesn't address: Will scripters be limited to LSL or will they be able to code in C# or something else more Mono-like? --Steamy Latte 12:20, 22 January 2008 (PST)
- Until LL can ensure that Mono is properly sandboxed and secure, the compiler will remain server side and the only language available will be LSL. -- Strife Onizuka 12:40, 23 January 2008 (PST)
- That makes total sense. Your comment does make it sound like there's a future plan to add other languages, after adequate testing has taken place. If so it's good news, as LSL lacks OOP and is cumbersome by comparison. --Steamy Latte 09:53, 24 January 2008 (PST)
- In 16k you don't want OOP. Trust me. The overhead would be killer. I just want pass by reference. Pass by value is the worst feature of LSO. If I had to guess I would say that most of speed improvements come from pass by reference alone. -- Strife Onizuka 17:19, 24 January 2008 (PST)
Compile Data Flow
Can someone describe the way the current flow works, and how the new flow will contrast. That is, I think at present:
- You edit on the viewer.
- When you [save], the source is uploaded.
- A compiler in the viewer creates bytecode.
- The bytecode is uploaded.
Is this correct? How will this change, if at all? Lee Ponzu 09:20, 26 January 2008 (PST)