menu for ruby dir

This commit is contained in:
Torsten Ruger 2018-04-11 13:51:31 +03:00
parent b1614dc353
commit ce155f2e30
4 changed files with 19 additions and 17 deletions

View File

@ -32,7 +32,7 @@
= yield
%footer.container
.row.center
%p © Copyright Torsten Ruger 2013-7
%p © Copyright Torsten Ruger 2013-8
:javascript
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),

View File

@ -1,8 +1,9 @@
%hr/
%p
layout: rubyx
title: Types, memory layout and management
- title = "Types, memory layout and management"
= render "pages/rubyx/menu"
%h1#main-layers Memory management
%p Memory management must be one of the main horrors of computing. Thats why garbage collected languages like ruby are so great. Even simple malloc implementations tend to be quite complicated. Unnecessary so, if one used object oriented principles of data hiding.
%h3#object-and-values Object and values
%p As has been mentioned, in a true OO system, object tagging is not really an option. Tagging being the technique of adding the lowest bit as marker to pointers and thus having to shift ints and loosing a bit. Mri does this for Integers but not other value types. We accept this and work with it and just say “off course” , but its not modeled well.

View File

@ -1,8 +1,9 @@
%hr/
%p
layout: rubyx
title: Optimisation ideas
- title = "Optimisation ideas"
= render "pages/rubyx/menu"
%h1 Optimisation ideas
%p I wont manage to implement all of these idea in the beginning, so i just jot them down.
%h3#avoid-dynamic-lookup Avoid dynamic lookup
%p This off course is a broad topic, which may be seen under the topic of caching. Slightly wrongly though in my view, as avoiding them is really the aim. Especially for variables.

View File

@ -1,9 +1,9 @@
%hr/
%p
layout: rubyx
title: Threads are broken
author: Torsten
- title = "Threads are broken"
= render "pages/rubyx/menu"
%h1 "Threads are broken"
%p
Having just read about rubys threads, i was moved to collect my thoughts on the topic. How this will influence implementation
i am not sure yet. But good to get it out on paper as a basis for communication.