What exactly does "neat and transactional" imply? It would be really great if you could provide some technical details to support that statement. I think it would help the announcement, if there existed at least a few words of what's going on and one wouldn't have to go and mine the comments on HN. Sorry, I'm not going to go find and read the source code right now and later I will probably forget about this being a cool thing in the first place, as I wasn't told what exactly is cool about it. Some seem to suggest above that there is a relation/inspiration to Nix, but that's not backed in any way either. Also, once it's a clear response to CoreOS, a detailed comparison would help a lot.
So, how come we are talking about it being Nix-like here? I don't seem to find any reference to that... And what exactly does "All neat and transactional." imply?
It's pretty cool indeed what you guys are doing with it, although currently there are not as many MCUs where Duktape fits... The STM32F4 Discovery board that AllJoyn+Duktape targets, is the same one Java Embedded also runs on, IIRC. From my knowledge the STM32F4's are some of the fatter micros currently on the market.
It's funny how in issue #1 users are asking for DTLS. I'm pretty sure this is what's finally going to get implemented and probably will appear in mbed OS soon too.
> Each compile job gets its own short-lived container
Just curious, how do handle input and output? Do you prepare a volume with the input and then grab output from there as well, or the program inside the container is fetching input from somewhere first, runs exec latex and then uploads the output elsewhere?
Today it's becoming harder and harder if users have to make sure that feature X is enabled in kernel version N or even compile and load a module. I do not disagree that your suggestion would benefit the performance.
Maxime, amazing work! I haven't looked at the code yet... But very curious how it works for demo/testing on Linux, does it use tun/tap device or something like that?
Yeah, exactly. NetBSD's implementation makes sense to use, as it's a rather solid one and very portable. Plus it's probably very general-purpose, while lwIP had never been. Not to say that general-purposeness is the best thing, so that's why I pointed at mTCP, which is actually optimised for multicore systems... Anyhow, I don't think these guys even get their point across. Why have they chosen lwIP in this particular instance actually?
Lol, supposedly mine wasn't of the same origin. To be fair, you just broke my whole idea of the two groups of people, which indeed was a very poor attempt that by itself will fall into another group. I am going to asume codehero is a nice guy and walk away from this incredibly amusing discussion. Thank you, dbaupp, for pointing this out.
That's good for you! I don't personally find the tool in question exactly the most appealing to me personally, but what I am excited about is that the industry is moving on, as C is far too dated as a language and even C14 doesn't give much hope. So, as you suggested that you don't appreciate the abstarction this tool adds, would you consider Rust, as it compiles right down to machine code? Essentially Rust is much C-like in terms of basic syntax, but has expressivenes of a functional language, safety-aware compiler and a ton of other features, including the fact that it's aimed at system-level applications and one should be able to write a kernel in Rust.
I'm sure one can use any libraries/SDKs from Mbeddr, right? And my other impression is that the aim is not to support boards or chips at all, it's just a tool, in my understanding. Are there plans to support C++?
There are two problematic types of engineers out there, some have no clue what they do and some have too much clue and wave their flags all over the place. You are in the second group and have probably been doing too much C for too long.
Razor is for private cloud, the biggest problems it solves are bare-metal provisioning as well as OS-specific mass-install tools. One of use-case for Razor: pop-in a new server into the rack, get provision ESXi with Razor and then provision a number of CentOS and Debian VMs without having to care how different is Kickstart from Preseed. It's a great too, but it's mostly for private cloud and Teraform is for public cloud and is therefore at a higher level.