11,979 karma · joined June 18, 2008
Personal blog at alexandros.balena.io
I am also @alexandrosm on twitter.
Contact me at alexandros@balena.io, I'm friendly!
I'm in the real world now for good, and I might be lucky that things in the class that would invoke the reaction this problem did, are few and far between. I'd like to find something that I can enjoy this much while being profitable, but, oh well, a man can dream, right?
Also, it's quite easy to make fun of a language by stating one non-central feature that's counter-intuitive. End of the day, anyone working in a language seriously learns the corner cases and moves on. After a while, it's no longer relevant to them.
I did like the discussion of dynamic vs. static though. It really feels dynamic is good for early codebases and static for late. So why aren't there languages that allow you to move to static as your codebase matures? TypeScript adds optional typing but doesn't quite go the whole way unfortunately.
But there are many times you need to create something new. At least I've had to, maybe I'm atypical. And when that time comes, I prefer manipulating familiar HTML and AngularJS that I also already know, than needing to understand yet another toolkit's approach to bindings.
But I have released code (see the bottom of the post or just https://github.com/resin-io/triangular.js ) that allows Angular/SVG graphs to add axes. Just didn't want to go deeper into documenting that too as I've gone past 2000 words already.
Hopefully in the future this will be done in pure angular, as these directives use more or less the old approach of encapsulating d3 in a directive. But at least they are re-usable.
The graphs aren't interactive in their current state (but there's nothing stopping them from being made interactive).
We are Resin.io, you can be anywhere.
We will offer £500 each to two projects that use Node.js on a Raspberry Pi. The resulting code should be open-sourced on GitHub but we do not require transferring ownership to us. The amount may not be much but may be a good extra incentive if you were looking to do a cool side-project with JS and hardware over the holidays.
Proposals should be sent to project at resin dot io. We will respond within a week and you'll have until the end of the year to complete the project. Projects will be judged based on how original the idea is. Bonus points for using more than one Raspberry Pi for the end result. If you offer to document your process and/or blog about it, we'll be even happier.
As mentioned, the resulting code will remain yours and you can keep evolving it (or not) as you please after the end of the project. We simply want to encourage cool JS projects on embedded devices. Some examples: http://ni-c.github.io/heimcontrol.js/ , http://googlecreativelab.github.io/coder/ .
It's quite sad that this comment is currently the top comment, in an article that raises quite an important topic for the JS and iOS developer communities. As much as I loathe the "hn is turning into reddit" crowd, this is much worse. HN is turning into a criticism machine that when it can't find anything worthwhile to criticise, will literally criticise anything at all rather than elevate a positive comment to the top.
I can connect you if you like, email in profile.
What we've done gets Docker over the 32-bit and "ARM architecture" barriers, so Android should be very feasible. Even the 3.8 kernel shouldn't be absolutely necessary since we got the devicemapper version of Docker to work (though there may be other gotchas).
In other news, chromium can now run on Wayland, which can run on Android, and also Docker can run chromium inside it, so Docker-on-Android is the last missing link for some pretty mindblowing use cases.
If anyone's interested in working on that, my email is in my profile, we'll help however we can.
[1]: http://www.geekbuying.com/item/MK808-Dual-Core-Android-4-1-J...
As a side note, getting this working on Raspbian should be feasible (consider it an exercise for the reader), we just used Arch as we've focused on that for a bunch of other things.
On the other hand, collectively, startups losing everyone's credentials/data are burning the commons wrt people's willingness to use new products.
But then on hand #3, it's not as if BigCo's have a much better record, so I guess this gets chalked up to the general 'why in the world do we release software this bad?' and the general answer is 'because people have been trained to accept it'. In the same way that if the car was invented today it'd never surpass our current health&safety considerations.
So I guess my point is, software is terrible in general, and security is just one aspect of many. As long as we don't have a better way to write it, it'll keep being bad. It's not fair to expect startups to set a higher standard, when they're optimising along several other dimensions at the same time.