fix the project pages

This commit is contained in:
Torsten Ruger 2018-04-11 15:33:32 +03:00
parent 9de06bfb68
commit 22a3d42cb6
6 changed files with 83 additions and 95 deletions

View File

@ -1,10 +1,10 @@
.row .row
%ul.nav %ul.nav
%li %li
%a{:href => "/project/motivation.html"} Motivation %a{:href => "motivation.html"} Motivation
%li %li
%a{:href => "/project/ideas.html"} Ideas %a{:href => "ideas.html"} Ideas
%li %li
%a{:href => "/project/history.html"} History %a{:href => "history.html"} History
%li %li
%a{:href => "/project/contribute.html"} Contribute %a{:href => "contribute.html"} Contribute

View File

@ -1,8 +1,7 @@
%hr/ = render "pages/project/menu"
%p
layout: project %h1= title "Join the fun"
title: Join the fun
%p %p
I am very open for people to join. Say hello at the I am very open for people to join. Say hello at the
= succeed "." do = succeed "." do
@ -22,27 +21,19 @@
(on mac) (on mac)
%p I wrote some ideas in the about page, but here some more code related guidelines %p I wrote some ideas in the about page, but here some more code related guidelines
%ul %ul
%li %li Walk the straight line
%p Or “No futureproof” means not to design before you code. Not to anticipate, only to do the job that
Walk the straight line needs doing. Better design should be extracted from working code.
Or “No futureproof” means not to design before you code. Not to anticipate, only to do the job that %li tdd extreme
needs doing. Better design should be extracted from working code. Having suffered from broken software (small feature add breaks whole software) so many times, the new tdd
%li wind is not just nice, it is essential. Software size is measured in tests passed, not lines written. Any
%p new feature is only accepted with enough tests, bugs fixed after a failed test is written.
tdd extreme %li Use names rightly
Having suffered from broken software (small feature add breaks whole software) so many times, the new tdd Or the principle of least surprise. Programming is so much naming, so if done right will lead to a
wind is not just nice, it is essential. Software size is measured in tests passed, not lines written. Any natural understanding, even of code not read.
new feature is only accepted with enough tests, bugs fixed after a failed test is written. Good names are Formatter or compile, but unfortunately not everything we have learnt is named well, like
%li Array (should be ordered list), Hash (names implementation not function) or string (should be word, or bytebuffer).
%p %li No sahara
Use names rightly There has been much misunderstood talk about drying things up. Dry is good, but was never meant for code, but
or the principle of least surprise. Programming is so much naming, so if done right will lead to a for information (configuration). Trying to dry code completely leads to overly interdependent functions,
natural understanding, even of code not read. calling chains that are difficult to understand and serve only a misunderstood slogan.
Good names are Formatter or compile, but unfortunately not everything we have learnt is named well, like
Array (should be ordered list), Hash (names implementation not function) or string (should be word, or bytebuffer).
%li
%p
No sahara
There has been much misunderstood talk about drying things up. Dry is good, but was never meant for code, but
for information (configuration). Trying to dry code leads to overly small functions, calling chains that
are difficult to understand and serve only a misundertood slogan.

View File

@ -1,41 +1,37 @@
\--- = render "pages/project/menu"
layout: project
title: RubyX, where it started %h1= title "RubyX, where it started"
\---
.row.vspace10
.span12.center
%h1
%span
%p
.row .row
.span1   %p
.span10 Torsten Ruger started this on 10.04.2014 after having read the Blue Book 20 years earlier.
%p The main ideas were:
Torsten Ruger started this on 10.04.2014 after having read the Blue Book 20 years earlier. %p
The main ideas were: %ul
%p %li Mikrokernel
%b> Mikrokernel The microkernel idea: anything that can be left out, should, puts a nice upper limit
\: The microkernel idea: anything that can be left out, should, puts a nice upper limit
on things and at the same time provides a great cooking pot for everyone else to try out their ideas. on things and at the same time provides a great cooking pot for everyone else to try out their ideas.
%br/ %br
Given gems and bundler this also seems an obvious choice. I really hope to see things i hadn't even thought of. Given gems and bundler this also seems an obvious choice. I really hope to see things i hadn't even thought of.
%br/ %li Layers represent an interface, not an implementation
= succeed ":" do It is said that every problem in computing can be solved by adding another layer
%b Layers represent an interface, not an implementation of indirection. And so we have many layers, which, when done right, help us to
%br/ understand the system. (Read, layers are for us, not the computer)
= succeed ":" do But implementing each layer comes with added cost, often unnecessary.
%b Empowerment %li Empowerment
%br/ I like the openness of ruby. Everyone can do what and how they want.
And change other peoples code in an easy and sensible way.
The best ideas survive and even better ones are coming.
Friendly competition as it were, cooperation, independent improvement all make
ruby gems better all the time.
%br
But ruby itself has not benefited from this in the same way (ie by ruby developers), because it is not in ruby. But ruby itself has not benefited from this in the same way (ie by ruby developers), because it is not in ruby.
%br/ %br
= succeed ":" do %li To get it done
%b To get it done Beats me why this hasn't been done before.
%br/
.row .row
.span12.center %h1.center Thanks
%h1 %p.center This would not have happened without:
%span Thanks
%p This would not have happened without:
/ About Us / About Us
.row .row
.tripple .tripple
@ -94,10 +90,11 @@ title: RubyX, where it started
%b %b
%a{:href => "https://github.com/cyndis/as"} As %a{:href => "https://github.com/cyndis/as"} As
ended up being the starting point for the assembly layer. ended up being the starting point for the assembly layer.
It was nice and small and produced working ARM code, which is what i wanted, as raspberry is arm. It was nice and small and produced working ARM code, which is what i wanted,
= succeed "got" do as raspberry is arm.
%b %b
%a{:href => "https://github.com/seattlerb/wilson"} Wilson %a{:href => "https://github.com/seattlerb/wilson"} Wilson
got assimilated for similar reasons, ie small and no dependencies.
%p %p
%b %b
%a{:href => "http://kschiess.github.io/parslet/"} Parslet %a{:href => "http://kschiess.github.io/parslet/"} Parslet
@ -107,11 +104,11 @@ title: RubyX, where it started
%b %b
%a{:href => "http://bundler.io/"} Bundler %a{:href => "http://bundler.io/"} Bundler
just makes you wonder how we managed before. just makes you wonder how we managed before.
Thanks to Yahuda, for starting it and Andre for making it fantastic. Thanks to Yahuda for starting it, and Andre for making it fantastic.
.row .row
.span12.center %p
%p Lastly, but most importantly there is a spiritual side to this too.
Lastly, but most importantly there is a siritual side to this too. Actually to anything i have done for at Actually to anything i have done for at
least 15 years, and i just mention it least 15 years, and i just mention it
= succeed "," do = succeed "," do
%a{:href => "spiritual.html"} here %a{:href => "spiritual.html"} here

View File

@ -1,8 +1,7 @@
\--- = render "pages/project/menu"
layout: project
title: Effectiveness, not efficiency %h1.center= title "Effectiveness, not efficiency"
sub-title: By way of a new look at programming. //# By way of a new look at programming.
\---
.row .row
.tripple .tripple
%h2.center Where to go %h2.center Where to go

View File

@ -1,9 +1,10 @@
\--- = render "pages/project/menu"
layout: project
title: Ruby in Ruby %h1= title "Ruby in Ruby"
sub-title: RubyX hopes make the the mysterious more accessible, shed light in the farthest (ruby) corners, and above all, %p
%b empower you %span
\--- RubyX hopes make the the mysterious more accessible, shed light in the farthest (ruby) corners, and above all,
%em empower you
.row .row
.tripple .tripple
%h2.center A better tool, a better job %h2.center A better tool, a better job
@ -59,7 +60,7 @@ sub-title: RubyX hopes make the the mysterious more accessible, shed light in th
%em %em
at all. at all.
Only the c std library makes them look like c functions, but they are not. Only the c std library makes them look like c functions, but they are not.
.span12 .row
%p.center %p.center
%span %span
%b So what does empowerment mean. %b So what does empowerment mean.

View File

@ -1,9 +1,9 @@
%hr/ = render "pages/project/menu"
%p
layout: project %h1.center= title "Yes, there is a spiritual side"
title: Yes, there is a spiritual side %p.center
sub-title: It is the question that drives us %span
It is the question that drives us
%p %p
Its taken me a while to come out with it, but here it goes. The nice quote (got it?) has truth in it. Though we often dont Its taken me a while to come out with it, but here it goes. The nice quote (got it?) has truth in it. Though we often dont
know what the question is and that is fine. It is the search that drives us and almost defines us as humans. know what the question is and that is fine. It is the search that drives us and almost defines us as humans.