0. make a list like this? :)
static reflection? how does that work? I see runtime Reflection there
In your case, "static reflection" may be better. http://www.digitaltapestry.net/blog/reflecting-on-code
Keep in mind that reflection is slow, whether it's runtime reflection or static reflection. It's best to find ways to cache the results and not use reflection every time.
why limit yourself to a desktop or a laptop, the two are not mutually exclusive, you can do development on the laptop and on the desktop, at home I only use a laptop, at work I have multiple desktops, for the most things a laptop is sufficient, for smaller components and such, but when it comes to raw power, to build massive things, a laptop will never cut it, and that will never change anytime soon, no matter how much better the hardware gets
yes, cause we all know, once you start spitting native code, you're automagically the fastest kid in town :) and there's no such thing as uncontrolled abstractions
Here is an FAQ on it.
Sounds very promising. This is going to be a great improvement in keeping .Net and C# moving forward. I hope it can even replace microframework in the future. This leaves C/C++ for device drivers and really gives you no reason to use C/C++ for application development. Hopefully they even make it to target a Linux distribution. Charge a fee to compile it in the cloud and make your money per compile and link. That way you don't care if it goes on Linux, Microsoft still makes their money.
how are you running 64-bit code on a 32-bit system? and then, anycpu really means run as whatever
Mar 03, 2014 at 12:17PM
Last time I checked an 32-bit ARM was two to three times more expensive than a 8-bit AVR, and AVR is one of the more expensive 8-bit controllers. The sweet little 8-bit controllers run the world, and ARM CPUs doesn't even come close in terms of power consumption. So you're not going to use an overkill CPU for a simple smoke detector. Until energy is free, and can be wirelessly transmitted everywhere at any wattage, the need for tiny computing devices, and a "small footprint language" is going to be there.
And C#-N probably won't show up on your 8-bit AVR anytime soon. In fact, Samsung sold their 4-bit and 8-bit MPU divisions about a year ago. Why? Because 32-bit ARM devices these days costs less than 8-bit AVR's. In other words: there is no need for small footprint languages.
why do you mean by freeze and what do you mean by cache?
A case for moving desktop motherboards to non-user expandable RAM and adding a user swappable GPU socketFeb 23, 2014 at 12:34AM
@androidi: why not another memory hierarchy? registers: bits -> L1/L2 caches: kBs - MBs -> internal memory: GBs -> external memory: GBs - TBs
A case for moving desktop motherboards to non-user expandable RAM and adding a user swappable GPU socketFeb 23, 2014 at 12:31AM
@PopeDai: blasphemy never, you are aware that it's using non standard hardware parts, like the GPU, who do you think is going to supply firmware and drivers for these? ATI or nVidia? nope