440 karma · joined March 6, 2011
Might not be that important in your case, I am guessing.
Print the CLA, sign it and scan it (or use a camera to photograph it) and e-mail it to hello(at)robovm.com. Include your GitHub user name in the e-mail.
print & scan in 21st century...really? they built a wooden model to demonstrate their answer — although Bozóki notes
that the model doesn’t verify the result because manufacturing errors
are much greater than any errors the computer could have made.
What's the point, when its not practically possible? Work on the Ruby interpreter is weirdly silo'ed off and mostly done by Japanese developers, so there's a significant barrier to entry for any enterprising C developer to roll her sleeves up and get hacking.
This is wrong. Ruby Developers welcome contribution in any form. Also, they have various resource to get started: Official Contributing Guide: http://ruby-doc.org/core-2.1.1/doc/contributing_rdoc.html
Ruby Hacking Guide: http://ruby-hacking-guide.github.io/
Book on ruby internals: http://www.amazon.com/Ruby-Under-Microscope-Illustrated-Internals/dp/1593275277
RubySpecs: http://rubyspec.org/
Further, incase you are stuck. you can post on the mailing-lists. someone will surely help you get started. http://tmm1.net/ruby21-rgengc/
http://tmm1.net/ruby21-oobgc/
And 2.1.1 is point release, so only contains bug fixes. It doesn't contain new features.Other that, anything that improves performance is a welcome change.
Incompatibility
There are five notable incompatibilities we know of:
The default encoding for ruby scripts is now UTF-8 [#6679]. Some people report that it affects existing programs, such as some benchmark programs becoming very slow [ruby-dev:46547].
Iconv was removed, which had already been deprecated when M17N was introduced in ruby 1.9. Use String#encode, etc. instead.
There is ABI breakage [ruby-core:48984]. We think that normal users can/should just reinstall extension libraries. You should be aware: DO NOT COPY .so OR .bundle FILES FROM 1.9.
#lines, #chars, #codepoints, #bytes now returns an Array instead of an Enumerator [#6670]. This change allows you to avoid the common idiom "lines.to_a". Use #each_line, etc. to get an Enumerator.
Object#inspect does always return a string like #<ClassName:0x…> instead of delegating to #to_s. [#2152]
NEWS: https://www.ruby-lang.org/en/news/2013/02/24/ruby-2-0-0-p0-is-released/
I would encourage you to try out ruby2 today, you will be surprised how easy the upgrading process is. Plus, your app will run 20% faster due to performance improvements yum install rubygem-rails
and Bam, it will install latest ruby, rails & other dependencies. That's not all, they have more than 2thousand ruby related packages(all recent versions).Fedora seems to have one of best ruby support. Way to go!
Another book worth looking at is: Recipes with Angular.js which is covered under Leanpub Unconditional Return Guarantee. so if you don't like the book. 45 days of purchase you can get a 100% refund.
https://leanpub.com/recipes-with-angular-js
so you can try the above, if you don't like the other two https://devcenter.heroku.com/categories/ruby - AngularJS http://shop.oreilly.com/product/0636920028055.do
- Web Application Development With AngularJS http://www.packtpub.com/angularjs-web-application-development/bookThank you!
so I am wondering, it makes sense to stop designing a VM & just focus on language. Perhaps, something like Truffle can be used to do the optimizations for you. Ruby on truffle is already 4-5x faster than MRI. And the ruby implementation was done by an intern in just 6months. All because power of JVM.
https://twitter.com/headius/status/362616159897534465
http://www.oracle.com/technetwork/java/jvmls2013wimmer-2014084.pdf
Something to keep in mind.Maybe this makes sense on Chrome OS. But for other main stream OSes like Windows, User accounts should be best left on OS. maybe a quick way to change profiles but that should be limit. Any further than this would be just reinventing the wheel & duplicating the features(parental control for example) that are already present in Modern Operating System.
on a related note, has anyone noticed memory usage of Google Chrome? Its crazy bonkers?
I suggest you to start building something. If you have no idea what you want to build, ask your family, friends or co-workers for a neat idea that solves a problem & try to build it. if you are unsure about your skills, then pick a dead simple idea. complexity of idea is not important. More importantly, the satisfaction taking an idea & turning into reality is amazing.
This is how you will go from a novice learner to experienced developer that ships code that people actually use.
Ember team, release it already. Its going to be fine. if there any bugs left, you can follow it up with minor bug fix release. More Importantly, not having a stable release does hurt the adoption of framework. Just Saying