Open-source release of IoT app environment Calvin
1–10 of 14 posts
Re: Open-source release of IoT app environment Calvin
#2Why did ericsson ditch erlang?
Re: Open-source release of IoT app environment Calvin
#3Why did ericsson ditch erlang?
Companies can have projects use various languages. For calvin, it looks a lot like they want a framework that's relatively easy for people to fall in and start using, whereas erlang has a bit more of a learning curve involved. Horses for courses and all.
Re: Open-source release of IoT app environment Calvin
#4Why did ericsson ditch erlang?
You do know that Ericsson is a corporation with over 100,000 employees and hundreds/thousands of products and projects, right?
Considering how large they are, it's not that strange that they use various language for various projects.
Re: Open-source release of IoT app environment Calvin
#5Intriguing, but no doc, not even a research paper. A bit hard for the lay person to figure out the use cases.
Re: Open-source release of IoT app environment Calvin
#6> the basic functionality is simple enough to run on tiny IoT-devices
But it seems to be written in Python... Why do all of these IoT platforms forget that most things will be running on a Cortex M3 with 32 kB of RAM?
Or am I missing what this is? Their explanation is kind of buzzwordy.
Re: Open-source release of IoT app environment Calvin
#7> the basic functionality is simple enough to run on tiny IoT-devices But it seems to be written in Python... Why do all of these IoT platforms forget that most things will be running on a Cortex M3 with 32 kB of RAM? Or am I missing what this is? Their explanation is kind of buzzwordy.
From the article:
The reference Calvin implementation is written in Python and is available on Github. With time there will be leaner runtimes requiring less resources. The intention of the design is to even allow for micro controller based implementations.
It seems the idea is not to write a platform for the devices only, but a full-stack one that can run on the various parts (devices, intermediary hubs, and servers).
Re: Open-source release of IoT app environment Calvin
#8Intriguing, but no doc, not even a research paper. A bit hard for the lay person to figure out the use cases.
There is a readme and a tutorial in the repo. The installation was simple and the first couple of tutorials run well. There is plenty to be desired, but it is much better than what I usually find in a V0.1 release. This looks very promising, but I don't understand how CalvinScript will allow me to read/write data to hardware interfaces.
Re: Open-source release of IoT app environment Calvin
#9> the basic functionality is simple enough to run on tiny IoT-devices But it seems to be written in Python... Why do all of these IoT platforms forget that most things will be running on a Cortex M3 with 32 kB of RAM? Or am I missing what this is? Their explanation is kind of buzzwordy.
A little odd that they seem to be unaware of micropython.org as well...
Re: Open-source release of IoT app environment Calvin
#10Intriguing, but no doc, not even a research paper. A bit hard for the lay person to figure out the use cases.
There is a readme and a tutorial in the repo. The installation was simple and the first couple of tutorials run well. There is plenty to be desired, but it is much better than what I usually find in a V0.1 release. This looks very promising, but I don't understand how CalvinScript will allow me to read/write data to hardware interfaces.
With this initial release, they seem to be targetting boards like the raspberry pi that have spi ports or gpio ports that people have made python modules for that are resonably abstracted. From how everything's laid out, it looks like you're supposed to have a source actor which does the low level work, like polling the gpio ports, and from there, passing the message to other actors which may be on other servers. I'd like to see the spec hashed out a bit better, because right now, it seems that there are too many bits of it that only have code as documentation.