net 4 we can share libraries) - this produces a lot of programming and testing efficiencies.Īlso - someone commented above to "just write native apps" - I have updated my apps in place literally hundreds of times - all transparent to the end users. (right now we "link" the code files into SL and regular. We compute results on the client side using EXACTLY the same chunks of code that we use on the server side.
#Microsoft silverlight mac os x full
Mutli-Threaded execution - you can process data in parallel and take full advantage of multiple-core cpus (combined with #1 you can a lot of things not possible before).
Isolated storage - you can store large datasets locally, encrypted if you please.There are a lot of things that you will find very valuable for a data-intensive application when using SL (many of which I believe are impossible in more traditional web languages): (you can look at my other questions to see the silverlight cpu usage question) I have had some rendering/performance issues on the mac though - nothing that made me regret using SL. From a data-intensive app standpoint, there is really no difference between the mac and the PC.
One began as a SL2-B2 app and shipped in SL2 and the other is a S元 app. I have developed two data intensive applications in Silverlight.
0 kommentar(er)
