Is there any comparison between .net micro framework and micropython? both seems to work in the same environment, target high-level language and use permissive open-source licenses.
Is the uPy community interested in inter-operability between 2 frameworks, i.e. using approach similar to Python for .NET?
The point of Python is easy dynamic language, while .NET Micro Framework already has stuff built around it.
.net micro framework
Re: .net micro framework
Well, Python is very high-level interpreted language thenrbli wrote:Is there any comparison between .net micro framework and micropython? both seems to work in the same environment, target high-level language and use permissive open-source licenses.
. There's no detailed comparison, and basically it would be the same as comparing Python and C#."similar to Python for .NET" - as we're working on Python, I'm not sure if we could care much if .NET uses approach similar to Python, or its own. If you mean the opposite, learning from .NET micro framework API for accessing hardware stuff, that would be interesting, yes, I would eagerly read such comparison and would listen to arguments why uPy should have API (more) similar to .NETuF.Is the uPy community interested in inter-operability between 2 frameworks, i.e. using approach similar to Python for .NET?
The point of Python is easy dynamic language, while .NET Micro Framework already has stuff built around it.
Awesome MicroPython list
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Pycopy - A better MicroPython https://github.com/pfalcon/micropython
MicroPython standard library for all ports and forks - https://github.com/pfalcon/micropython-lib
More up to date docs - http://pycopy.readthedocs.io/
Re: .net micro framework
As far as I know, .NET micro framework doesn't have the capability to compile code on the board. Instead you need a complete development environment and compiler on your desktop, similar to Arduino, mbed etc.
Micro Python tries to keep things as simple and self contained as possible, while still offering complete control over the hardware.
Micro Python tries to keep things as simple and self contained as possible, while still offering complete control over the hardware.
Re: .net micro framework
What I meant is related to this issue open in .NET Micro framework issue tracking system:
https://netmf.codeplex.com/workitem/1839
Instead of using IronPython, .NET developers could use uPy as a scripting environment without the need to recompile the code.
https://netmf.codeplex.com/workitem/1839
Instead of using IronPython, .NET developers could use uPy as a scripting environment without the need to recompile the code.
Re: .net micro framework
The huge difference being that in IronPython you have access to all CLR assemblies and types and integration with the host app is *ridiculously* easy as you can just add any .Net variable to the Python scope and it all just works.rbli wrote:Instead of using IronPython, .NET developers could use uPy as a scripting environment without the need to recompile the code.
The codebase needed to establish all this is probably significant, and all targetted towards IronPython.
Redoing that for uPy means starting from scratch, all over again. I doubt the devs are going to want to repeat that effort, with reason.