Linux Kernel Map.


... there are plenty of 'Linux Kernel Maps' to be found in the Internet.

... this one is for a Linux Kernel version 2.6.36, judging by image.

... should be checked & confirmed before use i think ...


... thanks to Karolina Boboli & others, i had this insight ...

... or so i think at least, due to thoughts appearing in mind.

... i've 'told' her via email that since a certain day i'll be able to protect Lama Ole Nydahl's Transmission passed via the Internet, as a Hacker ...

... hopefully in this life.


... is it compatible with Mathematics & Cryptography ? ...

... plans for old age for me, perhaps ? ...

... i think it is, people can ask themselves that question as well ...


see also, if You wish or need, ... : NM108-Crypto.


'Stitie Space', '3D Object Matrix' comes to mind with that ...

perhaps cooperation will ensue ...

perhaps it's worth to see what they expect ...

perhaps it's worth to consider their needs in Dragonfly Algorithm work ...

FEI is nanotech Corp, if i am not wrong ...


Part of Hardware Shot Away, Rest Works Somehow Still ...

... perhaps it's possible to do,

... with 3D (Cubic) Processors, that are added like 'building blocks', scaling well with amount & mass ...

... perhaps performance loss is quite proportional to % of 'computing mass' being shot away ...

... each of these '3D Processors' would contain a little of memory, a little of CPU, would handle a single 'Stitie Machine' ...

... there should be also some space in between 'cubes', for 'hardware & software infrastructure', for coordinating these 'cubes',

... as arranging them into 'Space' requires extra code at least.

see also, if You wish or need: Stitie Space as Hardware.

Global Lock.

i think this would simplify use & understanding of MATEN invocations, if there was an option for using 'Global Lock' for processes running on Stitie Machines.

it should NOT be mandatory, just an option to use or not.

single part of Stitie Space's state would determine if processes running on Stitie Machines in given Stitie Space should enter 'waiting' state until this 'Global Lock' is removed.

it should be available to be used outside MATEN as well.

perhaps it should be implemented in Stitie Space 1.2 'Satellite' or in Stitie Space 1.3 'November Rain', before writing 'Ola AH' Programming Language's Interpreter.

... or perhaps lack of 'Global Lock' can be considered as a bug in version 1.1 of Stitie Space 'Sunsail' & fixed in this version, probably that's the best option anyway ...

update, 07 VIII 2015.

as it is for now,

in Stitie Machine 1.1.35 RC 0-0-2 'Sunsail',

'Global Lock' determines who can call a given Sunsail(s) methods.

it is not about putting all threads on 'waiting' state, it's about preventing method calls on a Sunsails' group(s).

once we are sure that no one will intervene as we modify Stitie Space, we can take care of each of the Threads 'at peace', the way we prefer.

MATEN invocations can consist of two or more phases, for example:

1st phase:
 establishing 'Global Lock'.

2nd phase: managing threads:
 copying, modifying, putting on wait, whatever we need.

3rd phase:
 whatever else we need.

4rd phase:
 managing threads again, perhaps modifying & 'notifying' threads
 so they can commence with their work again.

5th phase:
 removing 'Global Lock'.

Imaging Space in another Space, an Idiom.

... another of possible Idioms.


there can be multiple Stitie Space objects used simultaneously.

'mindful imaging' can be used to 'copy' an image from one space to another space.

for example we can use multiple small spaces to model living beings in various forms (states), enriched with clothing & other equipment ...

... then we can 'image' them, copying to one common space at different positions, for example ...


see also, if You wish: Agile Transformation of Information State.

MATEN, then Prism(s), an Idiom.

... this seems useful a tool for many of situations,

... one of 'Ola AH' Programming Language's Idioms perhaps ?


to use MATEN to set-up a 'Generic, Bare, Minimalistic, Simplified ... a Form' in a Space, without paying too much of attention to finer of the details.

then use zero, one or many of Prism method call(s) to set-up these details,

... to 'enrich' a Form.


MATEN needs NOT to be used only once at program's beginning (initialization).

perhaps when a certain 'state' is reached, one of many possible MATEN calls can be executed as well.

Prism call(s) then may follow or not.


there can be 'MATEN Forms' that by design & definition have list of
'Prism Transformations', that can be modified dynamically during program's a run.

there's need to mention that these 'MATEN Forms' have to also contain lists of
'coords arguments' for these 'Prism Transformations'. these should also be able to be modified dynamically, during program's a run.

with a Global Lock this can be easy & useful.

there can be optional security mechanism(s) associated with changing state of a 'MATEN Form', so we can ensure that no one without proper permissions changes a 'MATEN Form' in a time between adding it to space & invocation order execution.

'MATEN Maneuvers', parts of 'MATEN Form' can 'look' at a 'Certificate' passed to them, to know who (which 'Certificate Authority') is responsible for that a 'Certificate'. Depending on that knowledge they can execute or not, or execute different way when that 'MATEN Form' is invoked.


see also, if You wish: Agile Transformation of Information State.


Idioms, Idiomatic Programming, Hacking.

... there's more to tell than this article covers, ..
... but from my perspective this is also a truth ...

idioms are 'good practices', 'as author intended', 'going well with design'.

idiomatic programming is 'a fine programming practice', 'practice according with design', has a chance to work well in many of a situation.

hacking is either 'a certain mindset', 'something not according with design', 'outsmarting other programmer', 'taking over computer or other device', 'disabling device or computer', 'attack'.

programming might be more or less 'idiomatic', or more or less 'hacky'.

'Ola AH' Programming Language includes 'a hacking mindset' in it's design - especially by enabling 'AH' mode, allowing to change inner workings of a Programming Language, customizing them by 'an expert programmer', more or less.

'AH' stands for 'AH Mantra for Speech',

'AH' also stands for 'Anti-Hack'.


State Prism is efficient means of transforming part(s) of Stitie Space ...

finer solution for small changes than MATEN, especially when parts of Stitie Space are not connected internally.

(there are exceptions & exceptional situations, it's not just as simple as that - often MATEN can be used for something else than big changes, Prism has also ability to transform whole Space).

why it's named Prism?

because of its ability to affect light & colors,

in a context of this blog, state can be called color,

in a context of this blog (State, Strategy) pair can be called 'Light Point', an 'Object Equivalent'.

it's related with 'Mindful Imaging' software component, that lets state of information in computer memory be visualized on a monitor screen to see how software works, to see how data structures look.

(perhaps will elaborate details later, perhaps it's not neccessary).

see also, if You wish: Agile Transformation of Information State.

MATEN, a Certain Form Invocation in Space.

- what is MATEN functionality?
- it's 'a Certain Form Invocation' in Space.

- is it related with Buddhism?
- yes, with 'Three Lights Meditation'. forms may emerge from Space & return to Space, partially or not. there are other transitions (Transformations of Forms in Space) possible, in theory, at least. not sure if it's safe, however ...

- are there other names for MATEN?
- 'Matrix Enhanced'.

see also, if You wish: MATEN Mathematics, MATEN Types, Stitie Machine 1.1 'Sunsail', Agile Transformation of Information State.


there's 'Global Lock' functionality planned for MATEN & other uses, to simplify 'matters of thinking', mostly.

'Events' in Programming, Conditionality.

'event' occurs when something happens in space,

for example when part(s) of state change a value to a value belonging to certain set.

in response to 'event occurance' parts of code might be executed, do something, possibly causing certain conditions to cease it's hold & new conditions to arise, to hold.

before this is possible, parts of code must 'register' for being informed about event's occurance.

event notification(s) might be a cause for something to happen, or for condition(s) to arise, or for something to cease happening.

that's why conditionality is often joined with event-based programming.

Conditionality & Events are part of Stitie Space 1.1 'Sunsail', are methods for Agile Transformation of Information State.

See also, if You wish: Conditional Software Tiering, Causes & Conditions.


'Ola AH', Niche Language.


'Ola AH' Programming Language is targeted to Quantum Computer Architectures with the multi-core support of Advanced RISC Machines - it's designed for ARM / Quantum Architectures.

Quantum Computers are being created to simulate physical processes on Quantum level better than traditional computers.

ARM is a short word for Advanced RISC Machine.

RISC is a short word for Reduced Instruction Set Computing.

ARM computers consist of many small & cheap processors with minimal instructions set, working in parallel.

Considering that Space is discrete (there are smallest units of energy/matter as Physical Sciences postulate), Stitie Space should model these well enough.

'All the experimental evidence points to continuous space, down to the shortest distances at which we have been able to measure. We don't know what happens at shorter distances.'

By the time of language creation, such ARM/Quantum computers will be faster, more capable memory-wise, more secure thanks to Quantum Cryptography than traditional computers, will open more possibilities as well.

Nanoscale technology is strongly affected by the Quantum phenomena as well, due to it's size.

'Ola AH' Programming Language interpreter will still run on classical computers, perhaps compiler as well - but performance will be far worse than on ARM / Quantum architectures.

It's still a long time before Quantum Computers will be affordable by me, but i should not waste time & develop a compiler for classical or classical/ARM architectures meanwhile, as well. This should not only open language for more architectures, but also will be a step toward making ARM/Quantum compiler - because parts of this work should be portable to the target ARM/Quantum architecture.

The new way of programming machines.

'Ola AH' Programming Language aims to cut short time & costs of programming machines, using a 'Token Game', a 4GL Programming methodology for that.

Programmers will model the objects graph using visual/design tools, then fill objects with code where needed. This results in a better program's overview & less code to type - thus faster application development, debugging & modification.

Such an objects' graph can be visualized & managed at application's runtime as well.

Stitie Space.

'Ola AH' Programming Language should use 'Stitie Space' & 'Stitie Machine' as part of it's semantics (meaning), part of language, concepts, thinking patterns associated with language's use.

Stitie Space is three-dimensional data structure with certain qualities.

It's rather unique language, filling certain 'niche' quite well.

It'll be probably easy to model & manage three-dimensional 'systems', etc ... but many 'common problems & their solutions' will have costs of solving decreased.

i think it's bold move to include 3D thinking as part of language semantics & syntax as opposed to including it in library, but it's how situation evolved, i do not wish or mean to change this.

Perhaps it's just 'a very specialized drill for 3D-worlds solutions', there are many other programming languages that perform better with 'other ideas, other worlds'.

i think it's stupid to create copy of existing language anyway - it would not add anything exceptional, of value.

Niche solutions perform better in certain cases at least, and worse at rest.

See also, if You wish or need, ... : Stitie Machine 1.1 'Sunsail', Stitie Machine 1.2 'Satellite'.

Addressing possible concerns:

i do not want to write that 'every programming language is niche language', because then 'Ola AH' probably would be attacked with words 'but this is too narrow niche' or something similar.

i think that niche is not 'too narrow', it's an advantage, a reason for existence, not 'a fault at design'.

i think it's natural to think in 3D terms when thinking about real world, thus it's a natural step in programming language evolution - 'that's how mind works' trend continuation.

n-dimensional solutions are still possible with 'Ola AH', just not so cost-efficient.

i imagine that Space(s) will be object(s) to be created or not as part of programming - using one big single instance of 'Stitie Space' should NOT be enforced. users should have control over amount & sizes of 'Stitie Spaces' used, or if they are used at all.

Use Cases for 'Ola AH' Programming Language:

- Modelling 3D-phenomena' evolution with time (not only Physical),
- 3D Rendering, Graphics & Animations,
- 3D Computer Games,
- Nanotechnology & Robotics at other scales (NEMS Swarm coordination, MEMS Swarm coordination, ...),
- Arts' Expression Forms modelling,
- Hacking & Security,
- Probably Mathematics in Future Versions,
- While a Web Pages & the Internet Applications - distributed or not - 3D or not - will be possible to do with 'Ola AH', i prefer to not focus too much on this (GRID type of Distributed applications should be easy to do & maintain with 'Ola AH' as well),
- Virtual Reality,
- Artificial Intelligence (with focus on Neural Networks & Brain Modelling),
- ...

Even if not all of my ambitious goals will be achievable in this life, i hope at least part of these will succeed making it a very good, practical & useful programming language, nevertheless. Most of my concern is with nano- & micro-technology, but in this case, perhaps larger scales still will be supported at least. Main reason is not only memory size concern, but also still-very-uncertain & probabilistic nature of phenomena occuring on the small scales. Today's Quantum Physics can barely see & define what happens on nano scale - for example the very act of observation alone affects the quantum objects, anything smaller (pico & smaller) is still an unknown mystery today. Larger-scale-technology, however, is much easier, much more alike the Classical Physics of Today.

4GL-Object Graph Modelling & Linguistics, as well as 'Token Game' features are certainly achievable in this life, unless something bad happens. There's much more of certainly doable features planned as well, for example: the fractional data type with appropriate arithmetic operators.

i am not lowering my ambitions, just reassuring readers that language can still be a success, even if not everything planned succeeds fully.

i will keep trying for the best still.

i think this is quite a strategic decision to consider use cases for this language, which markets we enter, which markets we do not enter so much ... & why ?


See also, if You wish or need: Stitie Space & Robot Swarm Concurrency.


'Ada', 'Linda' & 'Ola AH', Programming Languages.

there are many of female names in Computer Sciences, most notably: Ada, Linda, Ola.

is there competition?

of course, i think it's friendly competition however.

different languages are different tools ... each of tools has different qualities, is better at certain tasks, worse at others.

just like different drills are for different purposes.

professionals will use many similar tools, programming languages can 'interoperate', which can be understood as 'working together to solve different issues with different tools'.


a while ago i've browsed the Internet resources (web pages etc.) for information about 'Ada Programming Language'. i've found more or less useful web page with some data. there was mention about eating hot-dogs there among other more technological things.

then on LinkedIn i've involved myself in professional Ada Programming Language Group & got link to: http://university.adacore.com/ .

As i know from anecdote i heard in Warsaw University (MIM UW) during a Lecture, Ada is the Military Programming Language for U.S. & NATO, perhaps more, since many years, at least officially, since it won proper contest.

i think Armies use other languages as well, more or less skillfully.

many of them more or less closely interoperate with Ada.

Ada Lovelace, related with Lord Byron is considered first programmer in the world (not the way people think - computers as we know today happened later), mathematical assistance for a famous scientist, i do not remember whom.

Portrait of Ada Lovelace by Scotty-Hoag on DeviantArt

(will remove this art from blog, if author prefers).


Linda is a 'Tuple Space', has uses in Concurrency, important part of Computer Sciences.

i've learned how to use Linda at MIM UW, it's nice experience, a lot can be done with Linda.

Ola AH:

'Ola AH' is a Programming Language i am trying to create.

it's properties are to be determined, basicly i am trying to support as many people as i can with this Language.

there are slated dates however, later it'll be harder to add any of features.

When 'Ola AH' will be Practical ?

When 'Ola AH' will be a Programming Language capable to be used Professionally ?

i think in this life, if something bad won't happen.

(i am 37 years old at moment of writing this).

speculation & more details: as soon as it's fast enough & complete, probably when compiler is done, i estimate it to be in about 15 - 20 years. by that time computers should be more powerful & code more optimal as well.

before that time interpreter will perhaps be used occasionally, but not in wide use.

Moore's Law.

'"Moore's law" is the observation that the number of transistors in a dense integrated circuit has doubled approximately every two years. The observation is named after Gordon E. Moore, co-founder of Intel and Fairchild Semiconductor, whose 1965 paper described a doubling every year in the number of components per integrated circuit, and projected this rate of growth would continue for at least another decade. In 1975, looking forward to the next decade, he revised the forecast to doubling every two years. His prediction proved accurate, in part because the law now is used in the semiconductor industry to guide long-term planning and to set targets for research and development. The capabilities of many digital electronic devices are strongly linked to Moore's law: quality-adjusted microprocessor prices, memory capacity, sensors and even the number and size of pixels in digital cameras. All of these are improving at roughly exponential rates.'


'Intel executive David House, who predicted that chip performance would double every 18 months (being a combination of the effect of more transistors and their being faster).'

Source: Moore's Law on Wikipedia.

There's also option of optimizing cpu usage at cost of memory (for example: with 'Cache') or optimizing memory usage at cost of CPU (less precomputed values, other algorithmic tricks), etc ...

There's also matter of optimizing 'Ola AH', but this should not happen prematurely as there are extra risks & costs.

Optimization Costs.

Optimization costs time & effort measured in programmers' work-hours.

Programmers are often paid for their time.

Optimized code is larger, harder to understand, harder to modify. So after optimization code is faster, better but also harder to modify. Modifications cost more of programmer's time, more stress, more errors, more delays, ...

Optimization should happen at end of Programming Effort. (after design, prototype, implementation at high level of abstraction, etc ...).

Premature Optimization is source of many problems.

see also, if You wish or need, ... : Optimization Triad.


is Research a 'Risk-Free' occupation?

no, there's no guarantee that someone buys ... but perhaps that way it'll succeed.

woman i love is beautiful, i have to take risks to earn for love i think.

safe work place would not suffice, i'd die anyway.

yes, i play for big amount of money, even if it's paid later.

for a Buddhist Woman i Love & for Lama Ole Nydahl.

i think that others can benefit as well, if owners agree.

in my opinion work of others should be considered by owners.

i am not owner, just creator ... perhaps my opinion still counts.

for more, see: http://fav.me/d91s7a1 & follow a link ... if You wish.



most of the 'lessons' on this blog are compatible with each other.

there are more or less powerful synergies (greater than sum of the parts) & combinations, however.

they are usually hyperlinked as is usual in the Internet.

this combination however, deserves separate post, most likely, i think.

- 'Talking Objects' Solutions,
- Finite State Automatons and Regular Expression Basics.

programmer's work is not only a knowledge of a subset of one of Programming Languages, perhaps other tools as well.

there are also 'theories' & 'fine practices', practical as 'Potatoes of the Earth'.

is this noble enough?