"We discuss our tools and techniques to monitor and inject packets in Bluetooth Low Energy. Also known as BTLE or Bluetooth Smart, it is found in recent high-end smartphones, sports devices, sensors, and will soon appear in many medical devices. We show that we can effectively render useless the encryption of any Bluetooth Low Energy link."
Heroku is great for clients though. When I was a freelancer, I built these apps for other companies that assumed that I would do the admin & hosting. Heroku is great way to just "tack on a fee" for doing the hosting. If they want a cheaper option, they can always do it themselves. Most clients don't care about the savings on hosting..
Paypal is ancient. It's likely they developed their web framework before any open source java web frameworks became popular. Paypal existed around 1998, Java Struts 1.0 came out in 1999. Struts 1.0 is probably one of the big reasons many people flocked to PHP.
They probably made their own web framework because nothing good existed at the time.
I did it the same way -- parse & rewrite js code, and have a server that stores the same cookies that your browser would. The browser js code also contains the same js rewriter so that it can handle stuff like eval(). It also had to do lots of header manipulation since there are lots of headers that have domain-name based security, like CORS for example. The one I wrote works great with js-heavy sites like gmail or facebook.
The copenhagen wheel looks pretty cool. Too bad nobody can buy it. I guess those copenhagen people can put whatever they want on their press release since they will probably never turn it into an actual product.
Seems like it's a good pre-filter. The designers who do know Jekyll are likely to be pretty good and well rounded. If they only required HTML, you might end up with a bunch of guys that think they know design because they're great in Dreamweaver.
Designers these days have to do more than picking the right font and background color. They have to consider different devices, proper i18n, and accessibility. Back in 2002, only knowing html was good enough.
having written a fair amount of lua code, there aren't many libraries out there. Their npm equivalent is called 'luarocks'. To give you an idea of how old the libraries are: many of them mention the perl package it was translated from.
The reason for that of course is that it's so trivial to embed it in a C program, that if you want a library you can just expose a C library in lua. luajit even makes this absurdly easy with its FFI api.
Right, but libraries consist of many other things, including ORM or testing suites. There aren't many great ORM libraries written in C, and you need the test suite to work in lua because you're testing lua code. In general, the world of lua is pretty small, probably smaller than languages like Clojure or OCaml.
The fact that many libraries are "translated from" Perl packages does not mean they are old, it means a significant part of the Lua community has used Perl before. Actually, because Lua 5.2 has been released recently and broke compatibility, libraries that support it are by definition not "old" (or at least they are maintained).
That being said, the community is small and there are indeed way too few libraries available in LuaRocks (slightly over 300). We have been discussing that on the language's mailing list and I will probably talk about it at the upcoming Lua Workshop (http://www.lua.org/wshop13.html).