Last time I checked, pure NDK apps are best for games that use OpenGL as their primary interface. If you want native controls, you can't really do that entirely from the NDK side.
It is certainly doable. I haven't done it myself, but I know of people who have done it successfully on Android.
Unfortunately, I don't think Phonegap is a very good solution. Depending on your application, it may be good enough, but it's overall not as good as true native development.
So, I've been involved on Clojure/Android for a long time. I really like what Alexander has done with Skummet, and I think there is still room for improvement. However, I have to wonder to what extent is it good enough?
I use a lot of applications which have terrible load times. Some of these may be native, others are probably using some sort of cross-platform development framework. While I would prefer better performance, I am coming to the conclusion that startup time really isn't an absolute deal-breaker for a lot of people.
1. Clojure is a general purpose programming language. Just because it isn't used much for desktop GUIs doesn't mean it's not usable for that. What percentage of Java/Scala development is used for GUIs?
2. Clojure in iOS isn't just available via ClojureScript. There is also RoboVM, though it doesn't support REPL-driven development, if I understand it correctly.
3. I am very interested in what React Native can do. For me, the key questions about using it are: Can you create applications that fit will into the UX idioms of the host platform? What happens when something goes wrong? Do the various levels of indirection make debugging much more difficult? Do you still have access to the full platform? If not, then only certain classes of applications can be implemented using React Native.
Additionally, at least with Vanguard, if you have a lot of money invested you get access to funds with lower costs. For example, for $3,000-$10,000 you can VFINX which costs 0.17%, but if you have more than $10,00 invested you can buy VFIAX, which costs 0.05%. For $5M and up, you can buy VINIXm which costs 0.04%.
It's not so much that you are paying only for algorithmic/mechanical money management, but there are transaction costs as well. For example, an fund that tracks a particular index will need to buy/sell as the composition of the index changes. Even without that, you still have contributions and redemptions to deal with. Ideally, you try to match redemptions with contributions dollar for dollar, but they won't always match up, resulting purchasing or selling stock (which incurs transaction fees). Of course, there's the administrative overhead of managing a fund (keeping records, filing reports, etc.). As such, you aren't just paying for the algorithm.
Those lists aren't even close to being correct. For example, Clojure was accepted last year and this year. syslog-ng, Python, and X.org were all accepted this year.
What is most interesting to me is the number of accepted organisations is down significantly: from 190 last year to 137 this year, the lowest since 2007. Naturally, the question that arises is 'Has Google cut funding for GSoC, or is it adopting a significantly different strategy from what they have done the past ten years?'
No idea, but it does seem the programme has been scaled back. Last year there were 190 organisations accepted, and this year only 137, the fewest since 2007.
I don't think it's so much that it's hard to get a productive working environment. In my experience, getting vim-fireplace working with a new Leiningen project takes nearly zero effort. Moreover, I get all sorts of nice functionality (easy evaluation of expressions, sourc/doc lookup, etc.). Getting all of these features with ClojureScript takes quite a bit more effort, especially connecting it all to a browser REPL. At least, this has been my experience.
I generally agree. Even as an experienced Clojure developer (but not much of a web developer), it took a bit of time for me to get a ClojureScript working environment integrated with Vim fully worked out.
However, you can still get to a very usable state with a minimal setup. Once you get lein-cljsbuild set up, just running 'lein cljsbuild auto' and reloading the page after changes works fairly well. No, it doesn't have the polish or Vim integration of this full configuration, but it's usable.
Pretty neat. Figwheel is pretty new to me, so it's something I'll have to look into.
I just recently got my head around using ClojureScript with vim-fireplace and Austin. It took a bit of work, but I finally got to a point where I easily have a browser REPL running using an environment stored in a var. This helps avoid security error, but it's not as simple a setup.
I suppose one big difference is the HTML I am using is being served via a Ring-based server rather than using a separate serving process. This allows me to add middleware in development mode that will inject the necessary JavaScript to connect to the browser REPL.
A different approach, which I used for Clojure/Android, is to generate JVM bytecode and then use a bundled dx tool to generate Dalvik bytecode from that.
I used to think that fingerprint sensors were pretty cool, and even purchased the option on a laptop some years ago. That was until I found out the relative ease of duplicating fingerprints [1]. Now, I am wary of leaving my password on everything I touch.
I'd like to thank Alexander for all of his hard work. It's entirely my fault that his Neko work hasn't been merged in, but it's something I am going to get done soon.
This is the same state where car dealerships are only allowed to be open one day of either Saturday or Sunday. There was recently a proposal to get rid of this law, but it failed. Who was one of the biggest proponents of the status quo? The Texas Automobile Dealers Association.
It's yet another example of where government is used to protect special interests.
This article didn't seem all that great. It just claims "the prices are higher" without any substantive recommendations on how that problem can be solved.
Nonetheless, it does make one interesting point:
This is a good deal for residents of other countries, as our high spending makes medical innovations more profitable. “We end up with the benefits of your investment,” Sackville says. “You’re subsidizing the rest of the world by doing the front-end research.”
In other words, the low prices for health care found in other countries is, in part, subsidised by the American consumer. As a result, it would stand to reason that if price controls were implemented in the U.S., it could result in less medical innovation or rising prices elsewhere in the world.
I think this is sometimes indeed the purpose. I haven't verified this, but I remember reading that there was one part of the Affordable Care Act that was intended to be some pork for Nevada. However, the act didn't read that way. It was written as a sort of benefit to states which met something on the order of two pages' worth of qualifications. In the end, it ruled out every state but Nevada.