PeformIQ Wiki - User contributions [en]

Category:Bonsai

2026-08-26T23:20:07Z

PeterHarding: Created page with "Bonsai ML links, notes and references..."

Bonsai ML links, notes and references...

Using Bonsai QWEN Models

2026-08-26T23:19:50Z

PeterHarding:

See - https://www.youtube.com/watch?v=V6LmF7TuBmY (Bonsai 27B Runs Qwen 3.6 27B at 10x less memory)

Not a corrupt download — a format mismatch. Q2_0 in that filename isn't stock llama.cpp's quant; it's Q2_0_g128, PrismML's custom ternary packing (2-bit slots, one FP16 scale per 128 weights) that only their fork's kernels understand. Your stock build computes a different byte size for the ternary tensors, so its running offset drifts from what's written in the header, and gguf_init_from_reader bails at the first tensor where the two disagree — here output_norm.weight.

Corroboration: their g64 file is 7.59 GB vs 7.17 GB for the g128 one. That 0.42 GB delta is exactly one extra FP16 scale per 64 weights across ~27B weights — the scale density is the thing your build is guessing wrong.

Two fixes, easiest first:

1. Use the g64 file with your existing build. The model card says Ternary-Bonsai-27B-Q2_g64.gguf matches the 64-value-group Q2_0 packing already in llama.cpp:

<pre>
hf download prism-ml/Ternary-Bonsai-27B-gguf Ternary-Bonsai-27B-Q2_g64.gguf --local-dir ./models
./llama-server -m ./models/Ternary-Bonsai-27B-Q2_g64.gguf --ctx-size 16384
</pre>

2. Build their fork if you want the g128 file and the tuned Metal kernels:

<pre>
git clone https://github.com/PrismML-Eng/llama.cpp && cd llama.cpp
cmake -B build && cmake --build build -j # Metal is on by default
</pre>

Two other things:

--ctx-size 65536 will hurt on an M1. Weights are ~7.2 GB and the README's 100K-context figure is 14.7 GB peak without KV compression. On a 16 GB machine you'll swap; start at 8–16K and climb. Their throughput numbers are M4/M5 Pro — expect meaningfully less on M1.
Ignore the "Use this model" snippets on the HF page (llama serve -hf ...:F16) — those are auto-generated by Hugging Face, not the author's instructions, and F16 is the 53.8 GB file.

If the g64 file throws the same offset error, run python gguf-py/gguf/scripts/gguf_dump.py --no-tensors <file> and check general.file_type — that'll confirm whether it's a type-ID collision rather than the group size, and it's worth a post in their discussions.

Sources: Model card · File listing · PrismML llama.cpp fork

[[Category:AI]]
[[Category:Bonsai]]
[[Category:Prism-ml]]
[[Category:Llama.cpp]]

Category:Llama.cpp

2026-08-26T23:19:20Z

PeterHarding: Created page with "llama.cpp links, notes and references..."

llama.cpp links, notes and references...

AI Notes

2026-08-26T23:19:05Z

PeterHarding: Replaced content with "= A Collection of AI Related Notes = * Using Bonsai QWEN Models Category:AI Category:QWEN Category:Llama.cpp"

= A Collection of AI Related Notes =

* [[Using Bonsai QWEN Models]]

[[Category:AI]]
[[Category:QWEN]]
[[Category:Llama.cpp]]

Using Bonsai QWEN Models

2026-08-26T23:18:19Z

PeterHarding: Created page with " See - https://www.youtube.com/watch?v=V6LmF7TuBmY (Bonsai 27B Runs Qwen 3.6 27B at 10x less memory) Not a corrupt download — a format mismatch. Q2_0 in that filename isn't stock llama.cpp's quant; it's Q2_0_g128, PrismML's custom ternary packing (2-bit slots, one FP16 scale per 128 weights) that only their fork's kernels understand. Your stock build computes a different byte size for the ternary tensors, so its running offset drifts from what's written in the header,..."

AI Notes

2026-08-26T23:17:22Z

PeterHarding:

= A Collection of AI Related Notes =

* [[Using Bonsai QWEN Models]]

See - https://www.youtube.com/watch?v=V6LmF7TuBmY (Bonsai 27B Runs Qwen 3.6 27B at 10x less memory)

Not a corrupt download — a format mismatch. Q2_0 in that filename isn't stock llama.cpp's quant; it's Q2_0_g128, PrismML's custom ternary packing (2-bit slots, one FP16 scale per 128 weights) that only their fork's kernels understand. Your stock build computes a different byte size for the ternary tensors, so its running offset drifts from what's written in the header, and gguf_init_from_reader bails at the first tensor where the two disagree — here output_norm.weight.

Corroboration: their g64 file is 7.59 GB vs 7.17 GB for the g128 one. That 0.42 GB delta is exactly one extra FP16 scale per 64 weights across ~27B weights — the scale density is the thing your build is guessing wrong.

Two fixes, easiest first:

1. Use the g64 file with your existing build. The model card says Ternary-Bonsai-27B-Q2_g64.gguf matches the 64-value-group Q2_0 packing already in llama.cpp:

<pre>
hf download prism-ml/Ternary-Bonsai-27B-gguf Ternary-Bonsai-27B-Q2_g64.gguf --local-dir ./models
./llama-server -m ./models/Ternary-Bonsai-27B-Q2_g64.gguf --ctx-size 16384
</pre>

2. Build their fork if you want the g128 file and the tuned Metal kernels:

<pre>
git clone https://github.com/PrismML-Eng/llama.cpp && cd llama.cpp
cmake -B build && cmake --build build -j # Metal is on by default
</pre>

Two other things:

--ctx-size 65536 will hurt on an M1. Weights are ~7.2 GB and the README's 100K-context figure is 14.7 GB peak without KV compression. On a 16 GB machine you'll swap; start at 8–16K and climb. Their throughput numbers are M4/M5 Pro — expect meaningfully less on M1.
Ignore the "Use this model" snippets on the HF page (llama serve -hf ...:F16) — those are auto-generated by Hugging Face, not the author's instructions, and F16 is the 53.8 GB file.

If the g64 file throws the same offset error, run python gguf-py/gguf/scripts/gguf_dump.py --no-tensors <file> and check general.file_type — that'll confirm whether it's a type-ID collision rather than the group size, and it's worth a post in their discussions.

Sources: Model card · File listing · PrismML llama.cpp fork

[[Category:AI]]
[[Category:QWEN]]

AI Notes

2026-08-26T23:16:44Z

PeterHarding: Created page with "= A Collection of AI Related Notes = See - https://www.youtube.com/watch?v=V6LmF7TuBmY (Bonsai 27B Runs Qwen 3.6 27B at 10x less memory) Not a corrupt download — a format mismatch. Q2_0 in that filename isn't stock llama.cpp's quant; it's Q2_0_g128, PrismML's custom ternary packing (2-bit slots, one FP16 scale per 128 weights) that only their fork's kernels understand. Your stock build computes a different byte size for the ternary tensors, so its running offset drif..."

= A Collection of AI Related Notes =

See - https://www.youtube.com/watch?v=V6LmF7TuBmY (Bonsai 27B Runs Qwen 3.6 27B at 10x less memory)

Not a corrupt download — a format mismatch. Q2_0 in that filename isn't stock llama.cpp's quant; it's Q2_0_g128, PrismML's custom ternary packing (2-bit slots, one FP16 scale per 128 weights) that only their fork's kernels understand. Your stock build computes a different byte size for the ternary tensors, so its running offset drifts from what's written in the header, and gguf_init_from_reader bails at the first tensor where the two disagree — here output_norm.weight.

Corroboration: their g64 file is 7.59 GB vs 7.17 GB for the g128 one. That 0.42 GB delta is exactly one extra FP16 scale per 64 weights across ~27B weights — the scale density is the thing your build is guessing wrong.

Two fixes, easiest first:

1. Use the g64 file with your existing build. The model card says Ternary-Bonsai-27B-Q2_g64.gguf matches the 64-value-group Q2_0 packing already in llama.cpp:

<pre>
hf download prism-ml/Ternary-Bonsai-27B-gguf Ternary-Bonsai-27B-Q2_g64.gguf --local-dir ./models
./llama-server -m ./models/Ternary-Bonsai-27B-Q2_g64.gguf --ctx-size 16384
</pre>

2. Build their fork if you want the g128 file and the tuned Metal kernels:

<pre>
git clone https://github.com/PrismML-Eng/llama.cpp && cd llama.cpp
cmake -B build && cmake --build build -j # Metal is on by default
</pre>

Two other things:

--ctx-size 65536 will hurt on an M1. Weights are ~7.2 GB and the README's 100K-context figure is 14.7 GB peak without KV compression. On a 16 GB machine you'll swap; start at 8–16K and climb. Their throughput numbers are M4/M5 Pro — expect meaningfully less on M1.
Ignore the "Use this model" snippets on the HF page (llama serve -hf ...:F16) — those are auto-generated by Hugging Face, not the author's instructions, and F16 is the 53.8 GB file.

If the g64 file throws the same offset error, run python gguf-py/gguf/scripts/gguf_dump.py --no-tensors <file> and check general.file_type — that'll confirm whether it's a type-ID collision rather than the group size, and it's worth a post in their discussions.

Sources: Model card · File listing · PrismML llama.cpp fork

[[Category:AI]]
[[Category:QWEN]]

RAG

2026-08-09T23:43:47Z

PeterHarding: Created page with "= RAG = Category:AI"

= RAG =

[[Category:AI]]

Category:Graph Databases

2026-08-09T23:43:24Z

PeterHarding: Created page with "Graph database links, notes and references..."

Graph database links, notes and references...

Graph Databases

2026-08-09T23:43:04Z

PeterHarding: Created page with "= Graph Databases = ... Category:Graph Databases Category:AI"

= Graph Databases =

...

[[Category:Graph Databases]]
[[Category:AI]]

Anthropic Gotchas

2026-07-28T10:30:46Z

PeterHarding:

Why am I getting this error in claude code - API Error: 400 You have reached your specified API usage limits. You will regain access on 2026-08-01 at 00:00 UTC.

= Identified API spend limit issue and recommended unsetting key =

That error isn't a Claude Code bug or a subscription rate limit — it's the Console API spend limit on your organization/workspace. Spend limits set a maximum monthly cost an organization can incur for API usage, and each usage tier has a limit on how much you can spend per calendar month. The 2026-08-01 00:00 UTC reset date is just the start of the next calendar month (10am Aug 1 your time).
anthropic

The important implication: Claude Code is billing through an API key, not your Claude subscription. That's almost certainly the same auth mix-up you hit before. If you have an active Claude subscription but also have ANTHROPIC_API_KEY set in your environment, the API key takes precedence once approved.

== Claude Code Docs ==

To check which route is active, run /status inside Claude Code — the Login method row shows your subscription account, and an API key row appears when an API key is in use.
Claude Code Docs

If you meant to use your subscription:

<pre>
echo "$ANTHROPIC_API_KEY" # if this prints anything, that's your culprit
unset ANTHROPIC_API_KEY
</pre>

Then grep your shell startup files, since it'll come straight back otherwise:

<pre>
grep -rn "ANTHROPIC_API_KEY" ~/.zshrc ~/.zprofile ~/.bash_profile ~/.bashrc ~/.config 2>/dev/null
</pre>

Also check project-level .env files and any devcontainer config. Then /logout and /login, picking the subscription option.

One gotcha specific to your VS Code workflow: VS Code often inherits a different environment than your interactive shell (especially if launched from Dock/Spotlight rather than code . from a terminal), so a key can be set in one and not the other — verify with /status from inside the VS Code integrated terminal specifically.

If you did intend to use the API key, then go to the Anthropic Console → Limits (or the workspace's spend limit setting) and raise the monthly cap, and check Usage to see what burned through it. Worth also confirming you haven't been paying twice all along.

[[Category:Anthropic]]
[[Category:Claude]]
[[Category:AI]]

AI

2026-07-28T10:29:48Z

PeterHarding: Created page with " Category:AI Category:Machine Learning"

[[Category:AI]]
[[Category:Machine Learning]]

Main Page

2026-07-28T10:29:17Z

PeterHarding: /* Some Areas of Interest */

<big>'''PerformIQ MediaWiki'''</big>

= Introduction =

This repository has been created for clients and other interested parties to explore information and software contributions developed by us which we though might be of interest to the community at large.

= Some Areas of Interest =

The following list some of the areas where we have been active in the last 20 years and maintain an interest:

* [[AI]]
* [[Machine Learning]]
* [[RAG]]
* [[Graph Databases]]
* [[Docker]]
* [[Kubernetes]]
* [[FastApi]]
* [[Gatling]]
* [[Kafka]]
* [[MQ]]
* [[React]]
* [[Angular]]
* [[MongoDB]]
* [[Scala]]
* [[Python]]
* [[Ruby]]
* [[Web Based Applications]]
* [[Web Services]], [[SOAP]]
* [[MS Visual Studio]]
* [[Performance Analysis]] and [[Capacity Planning]]
* [[Load Testing]], [[SVT]]
* [[LoadRunner]]
* [[PERL]]
* [[Java]]
* [[Enterprise Software]] and [[Middleware]], [[TIBCO]], [[MQ Series]]
* [[Eclipse IDE]]
*

== Papers ==

See [[Papers]] for some historically significant papers.

== MediaWiki ==

Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

My [[MediaWiki]] notes...

== Getting Started ==

* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

Category:Claude

2026-07-28T10:28:07Z

PeterHarding: Created page with "Claude links, notes and references..."

Claude links, notes and references...

Anthropic Giotchas

2026-07-28T10:27:43Z

PeterHarding: PeterHarding moved page Anthropic Giotchas to Anthropic Gotchas

#REDIRECT [[Anthropic Gotchas]]

Anthropic Gotchas

2026-07-28T10:27:43Z

PeterHarding: PeterHarding moved page Anthropic Giotchas to Anthropic Gotchas

Category:Anthropic

2026-07-28T10:27:31Z

PeterHarding: Created page with "Anthropic.ai links, notes and references..."

Anthropic.ai links, notes and references...

Anthropic Gotchas

2026-07-28T10:27:07Z

PeterHarding:

Anthropic Gotchas

2026-07-28T10:26:20Z

PeterHarding: Created page with "Why am I getting this error in claude code - API Error: 400 You have reached your specified API usage limits. You will regain access on 2026-08-01 at 00:00 UTC. # Identified API spend limit issue and recommended unsetting key That error isn't a Claude Code bug or a subscription rate limit — it's the Console API spend limit on your organization/workspace. Spend limits set a maximum monthly cost an organization can incur for API usage, and each usage tier has a limit..."

Why am I getting this error in claude code - API Error: 400 You have reached your specified API usage limits. You will regain access on 2026-08-01 at 00:00 UTC.

# Identified API spend limit issue and recommended unsetting key

That error isn't a Claude Code bug or a subscription rate limit — it's the Console API spend limit on your organization/workspace. Spend limits set a maximum monthly cost an organization can incur for API usage, and each usage tier has a limit on how much you can spend per calendar month. The 2026-08-01 00:00 UTC reset date is just the start of the next calendar month (10am Aug 1 your time).
anthropic

The important implication: Claude Code is billing through an API key, not your Claude subscription. That's almost certainly the same auth mix-up you hit before. If you have an active Claude subscription but also have ANTHROPIC_API_KEY set in your environment, the API key takes precedence once approved.

## Claude Code Docs

To check which route is active, run /status inside Claude Code — the Login method row shows your subscription account, and an API key row appears when an API key is in use.
Claude Code Docs

If you meant to use your subscription:

<pre>
echo "$ANTHROPIC_API_KEY" # if this prints anything, that's your culprit
unset ANTHROPIC_API_KEY
</pre>

Then grep your shell startup files, since it'll come straight back otherwise:

<pre>
grep -rn "ANTHROPIC_API_KEY" ~/.zshrc ~/.zprofile ~/.bash_profile ~/.bashrc ~/.config 2>/dev/null
</pre>

Also check project-level .env files and any devcontainer config. Then /logout and /login, picking the subscription option.

One gotcha specific to your VS Code workflow: VS Code often inherits a different environment than your interactive shell (especially if launched from Dock/Spotlight rather than code . from a terminal), so a key can be set in one and not the other — verify with /status from inside the VS Code integrated terminal specifically.

If you did intend to use the API key, then go to the Anthropic Console → Limits (or the workspace's spend limit setting) and raise the monthly cap, and check Usage to see what burned through it. Worth also confirming you haven't been paying twice all along.

Category:Firewalls

2026-03-17T22:21:10Z

PeterHarding: Created page with "Firewall links, route and references..."

Firewall links, route and references...

3D Imaging Notes

2026-03-02T10:40:59Z

PeterHarding:

= Links =

* https://www.codeproject.com/Articles/1182854/D-Face-Viewer-and-Matcher

[[Category:Imaging]]
[[Category:3D]]
[[Category:Development]]

Papers

2026-03-02T10:37:12Z

PeterHarding:

Back to [[Main Page]]

= Significant Papers =

[[Category:Papers]]

Papers

2026-03-02T10:36:51Z

PeterHarding:

Back to [[Index]]

= Significant Papers =

[[Category:Papers]]

Middleware

2026-03-02T10:31:51Z

PeterHarding:

= Links =

* [http://en.wikipedia.org/wiki/Middleware Wikipedia entry on Middleware]

[[Category:Middleware]]

Java

2026-03-02T10:19:08Z

PeterHarding:

== Full Name ==

Java

== Information ==

An [[object-oriented]] programming language for portable interpretive codes that supports interaction among remote objects. [[Javascript]] ([[JScript]] or [[JavaScript]]) . When [[Javascript]] is included in an [[HTML]] file it relies upon the browser to interpret the [[Javascript]]. If [[Javascript]] is combined with [[Cascading Style Sheets]] ([[CSS]]) and later versions of [[HTML]] (4.0 and later) the result is often called [[DHTML]].

== Related Links ==

* https://en.wikipedia.org/wiki/Java_%28programming_language%29
* [https://docs.oracle.com/en/java/ Java Documentation]
* [https://www.oracle.com/java/technologies/ Oracle Java web-site]
* [[Java Enterprise Edition]]
* [http://www.netbeans.org/ NetBeans IDE]
* [[Java Beans]]
* [http://en.wikipedia.org/wiki/Java_Class_Library Java Class Library]
* [http://en.wikipedia.org/wiki/Java_%28programming_language%29 Wikipedia entry on Java]
* [http://en.wikipedia.org/wiki/Java_Virtual_Machine JVM]
* [http://en.wikipedia.org/wiki/Java_Platform%2C_Enterprise_Edition JEE]
* [http://en.wikipedia.org/wiki/Special:Search?search=Java&fulltext=Search Java References on Wikipedia]
* [[Eclipse]]

[[Category:TERMINOLOGY]]
[[Category:Internet]]
[[Category:SOFTWARE]]

Performance Analysis

2026-03-02T10:01:58Z

PeterHarding:

= Overview =

Check out [http://en.wikipedia.org/wiki/Neil_Gunther Dr Neil Gunther]'s site - [http://www.perfdynamics.com/ Peformance Dynamics]...

Some interesting links:

* https://www.perfdynamics.com/Manifesto/gcaprules.html
* https://www.perfdynamics.com/Manifesto/USLScalability.html
* https://queue.acm.org/detail.cfm?id=2789974 - Hadoop Superlinear Scalability

= PDQ =

[http://www.perfdynamics.com/Tools/PDQ.html Pretty Damn Quick - PDQ]

[[Category:Performance]]

Scala

2026-03-02T09:51:47Z

PeterHarding:

= Scala Notes =

* https://en.wikipedia.org/wiki/Scala_(programming_language)

= Use of '_' =

From - https://stackoverflow.com/questions/8000903/what-are-all-the-uses-of-an-underscore-in-scala

<pre>
import scala._ // Wild card -- all of Scala is imported
import scala.{ Predef => _, _ } // Exception, everything except Predef
def f[M[_]] // Higher kinded type parameter
def f(m: M[_]) // Existential type
_ + _ // Anonymous function placeholder parameter
m _ // Eta expansion of method into method value
m(_) // Partial function application
_ => 5 // Discarded parameter
case _ => // Wild card pattern -- matches anything
val (a, _) = (1, 2) // same thing
for (_ <- 1 to 10) // same thing
f(xs: _*) // Sequence xs is passed as multiple parameters to f(ys: T*)
case Seq(xs @ _*) // Identifier xs is bound to the whole matched sequence
var i: Int = _ // Initialization to the default value
def abc_<>! // An underscore must separate alphanumerics from symbols on identifiers
t._2 // Part of a method name, such as tuple getters
1_000_000 // Numeric literal separator (Scala 2.13+)
</pre>

So...

==Existential types==
def foo(l: List[Option[_]]) = ...
==Higher kinded type parameters==
case class A[K[_],T](a: K[T])
==Ignored variables==
val _ = 5
==Ignored parameters==
List(1, 2, 3) foreach { _ => println("Hi") }
==Ignored names of self types==
trait MySeq { _: Seq[_] => }
==Wildcard patterns==
Some(5) match { case Some(_) => println("Yes") }
==Wildcard patterns in interpolations==
"abc" match { case s"a$_c" => }
==Sequence wildcard in patterns==
C(1, 2, 3) match { case C(vs @ _*) => vs.foreach(f(_)) }
==Wildcard imports==
import java.util._
==Hiding imports==
import java.util.{ArrayList => _, _}
==Joining letters to operators==
def bang_!(x: Int) = 5
==Assignment operators==
def foo_=(x: Int) { ... }
==Placeholder syntax==
List(1, 2, 3) map (_ + 2)
==Method values==
List(1, 2, 3) foreach println _
==Converting call-by-name parameters to functions==
def toFunction(callByName: => Int): () => Int = callByName _
==Default initializer==
var x: String = _ // unloved syntax may be eliminated

=Other=

* https://alvinalexander.com/scala/how-to-use-scala-match-expression-like-switch-case-statement/

=Match Expressions=

* https://docs.scala-lang.org/overviews/scala-book/match-expressions.html

<pre>
def getClassAsString(x: Any): String = x match {
case s: String => s + " is a String"
case i: Int => "Int"
case f: Float => "Float"
case l: List[_] => "List"
case p: Person => "Person"
case _ => "Unknown"
}
</pre>

<pre>
def isTrue(a: Any) = a match {
case 0 | "" => false
case _ => true
}
</pre>

<pre>
// Version 1 - compiles to a tableswitch
import scala.annotation.switch

class SwitchDemo {
val i = 1
val x = (i: @switch) match {
case 1 => "One"
case 2 => "Two"
case _ => "Other"
}
}
</pre>

<pre>
expr match {
case List(1,_,_) => "A List with three elements"
case List(_ *) => "A List with zero or more elements"
case Map(_,_) => "A Map with any Key and Value type"
case _ => "Anythiong else"
}
</pre>

=Getters and Setters=

According to the Scala docs:

Scala does not follow the Java convention of prepending set/get to mutator and accessor methods (respectively). Instead, the following conventions are used:

* For accessors of properties, the name of the method should be the name of the property.
* In some instances, it is acceptable to prepend “is” on a boolean accessor (e.g. isEmpty). This should only be the case when no corresponding mutator is provided.
* For mutators, the name of the method should be the name of the property with “_=” appended.

So:

<pre>
class Foo {
def bar = ...
def bar_=(bar: Bar) {
...
}
def isBaz = ...
}
</pre>

<pre>
val nums = List(1,2,3,4,5,6,7,8,9)

nums filter (_ % 2 == 0)
nums reduce (_ + _)
nums.exists (_ > 5)
nums.takeWhile(_ < 8)
</pre>

As used in Swift for un-named or unused values:

<pre>
def getProps = {
Config.getHost, Config.getPort, Config.getIp, Config.getMask
}

val (host, port, ignore1, ignore2) = getProps

val (host, port, _, _) = getProps
</pre>

=Types=

<pre>
type StringMatcher = String => (String => Boolean)

def starts: StringMatcher = (prefix:String) => _ startsWith prefix

...or...

def starts: StringMatcher = (prefix:String) => (s) => s startsWith prefix
</pre>

=Generating Random Strings=

One liner:

<pre>
Random.alphanumeric.take(10).mkString
</pre>

From - https://alvinalexander.com/scala/creating-random-strings-in-scala/

<pre>
import scala.annotation.tailrec

/**
* Examples of different ways to write "random string" methods in Scala.
* See the main method for examples of how each method is called.
* Created by Alvin Alexander, https://alvinalexander.com
*/
object RandomStringExamples {

def main(args: Array[String]) {
println("1: " + randomString(10))
println("2: " + randomStringArray(10))
println("3: " + randomStringRecursive(10).mkString)
println("3: " + randomStringRecursive2(10).mkString)
println("4: " + randomStringTailRecursive(10, Nil).mkString)
println("5: " + randomStringRecursive2Wrapper(10))
println("6: " + randomAlphaNumericString(10))
println("6: " + randomAlphaNumericString(10))
println("6: " + randomAlphaNumericString(10))
println("x2: " + x2(10, ('a' to 'z') ++ ('A' to 'Z')))
}

// 1 - a java-esque approach
def randomString(length: Int) = {
val r = new scala.util.Random
val sb = new StringBuilder
for (i <- 1 to length) {
sb.append(r.nextPrintableChar)
}
sb.toString
}

// 2 - similar to #1, but using an array
def randomStringUsingArray(length: Int): String = {
val r = new scala.util.Random
val a = new Array[Char](length)
val sb = new StringBuilder
for (i <- 0 to length-1) {
a(i) = r.nextPrintableChar
}
a.mkString
}

// 3 - recursive, but not tail-recursive
def randomStringRecursive(n: Int): List[Char] = {
n match {
case 1 => List(util.Random.nextPrintableChar)
case _ => List(util.Random.nextPrintableChar) ++ randomStringRecursive(n-1)
}
}

// 3b - recursive, but not tail-recursive
def randomStringRecursive2(n: Int): String = {
n match {
case 1 => util.Random.nextPrintableChar.toString
case _ => util.Random.nextPrintableChar.toString ++ randomStringRecursive2(n-1).toString
}
}

// 4 - tail recursive, no wrapper
@tailrec
def randomStringTailRecursive(n: Int, list: List[Char]):List[Char] = {
if (n == 1) util.Random.nextPrintableChar :: list
else randomStringTailRecursive(n-1, util.Random.nextPrintableChar :: list)
}

// 5 - a wrapper around the tail-recursive approach
def randomStringRecursive2Wrapper(n: Int): String = {
randomStringTailRecursive(n, Nil).mkString
}

// 6 - random alphanumeric
def randomAlphaNumericString(length: Int): String = {
val chars = ('a' to 'z') ++ ('A' to 'Z') ++ ('0' to '9')
randomStringFromCharList(length, chars)
}

// 7 - random alpha
def randomAlpha(length: Int): String = {
val chars = ('a' to 'z') ++ ('A' to 'Z')
randomStringFromCharList(length, chars)
}

// used by #6 and #7
def randomStringFromCharList(length: Int, chars: Seq[Char]): String = {
val sb = new StringBuilder
for (i <- 1 to length) {
val randomNum = util.Random.nextInt(chars.length)
sb.append(chars(randomNum))
}
sb.toString
}

def x(length: Int, chars: Seq[Char]): String = {
val list = List.range(1, length)
val arr = new Array[Char](length)
list.foreach{ e => arr(e) = chars(util.Random.nextInt(chars.length)) }
list.mkString
}

// create a fake list so i can use map (or flatMap)
def x2(length: Int, chars: Seq[Char]): String = {
val tmpList = List.range(0, length)
val charList = tmpList.map{ e => chars(util.Random.nextInt(chars.length)) }
return charList.mkString
}

}
</pre>

<pre>
</pre>

[[Category:Scala]]

MongoDB

2026-03-02T09:48:53Z

PeterHarding:

= Overview =

A NoSQL database which used JSON documents as its storage objects.

= Links =

* https://en.wikipedia.org/wiki/MongoDB
* https://www.mongodb.com/
* https://docs.mongodb.com/manual/tutorial/install-mongodb-on-debian/
*

= Use with Python =

* https://stackoverflow.com/questions/9447629/mongokit-vs-mongoengine-vs-flask-mongoalchemy-for-flask
*

[[Category:MongoDB]]

Angular

2026-03-02T09:41:42Z

PeterHarding:

= Setting up a new CLI Project =

<pre>
ng new project-name

...

cd project-name
...
</pre>

[[Category:Angular]]

React

2026-03-02T09:40:34Z

PeterHarding:

= Overview =

= Links =

* https://en.wikipedia.org/wiki/React_(JavaScript_library)
* https://reactjs.org/
* https://github.com/facebook/react
* https://github.com/ReactTraining/react-router/tree/dev/docs
*
* xxx

[[Category:React]]
[[Category:SPA]]
[[Category:Web]]

Kafka

2026-03-02T09:37:56Z

PeterHarding:

= Overview =

Apache Kafka is an implementation of a distributed event streaming platform.

= Links =

* https://kafka.apache.org/
* https://kafka-tutorials.confluent.io/
* https://kafka.apache.org/quickstart
* https://docs.confluent.io/platform/current/overview.html
*
*

= Using with Docker =

* https://docs.confluent.io/platform/current/quickstart/ce-docker-quickstart.html
*
*

[[Category:Kafka]]

Kafka

2026-03-02T09:37:45Z

PeterHarding:

= Overvie w=

Apache Kafka is an implementation of a distributed event streaming platform.

= Links =

* https://kafka.apache.org/
* https://kafka-tutorials.confluent.io/
* https://kafka.apache.org/quickstart
* https://docs.confluent.io/platform/current/overview.html
*
*

= Using with Docker =

* https://docs.confluent.io/platform/current/quickstart/ce-docker-quickstart.html
*
*

[[Category:Kafka]]

3D Imaging Notes

2026-02-27T23:03:28Z

PeterHarding:

=Links =

* https://www.codeproject.com/Articles/1182854/D-Face-Viewer-and-Matcher

[[Category:Imaging]]
[[Category:3D]]
[[Category:Development]]

Markup Notes

2026-02-25T23:02:39Z

PeterHarding:

= Forms of Documentation Markup =

In the past, many solutions have evolved to facilitate the easy creation of documents and documentation. These range from lightweight human-readable formats like Markdown, to highly capable typesetting systems like TeX/LaTeX, to structured data formats like XML. The choice of markup language typically reflects a trade-off between ease of authoring, rendering fidelity, and the intended output medium.

----

== Historical Background ==

The concept of "markup" predates computers — editors and typesetters would literally mark up manuscripts with instructions for printers. With the arrival of electronic publishing in the 1960s and 70s, these conventions were formalised into machine-readable languages. Early systems were tightly coupled to specific hardware (typesetters, printers, terminals), and over time higher-level, more portable formats emerged.

== Markup Languages and Formats ==

=== Runoff / Roff Family (1964 onwards) ===

The roff family traces its roots to the <code>RUNOFF</code> program written by Jerome Saltzer at MIT in 1964. It was the dominant document formatting system on early UNIX systems.

* '''nroff''' — formats text for fixed-width terminal output
* '''troff''' — the typesetting variant, targeting phototypesetting devices
* '''groff''' (GNU roff) — the modern open source successor, still widely used today for Unix man pages

Roff documents use dot-prefixed commands (e.g. <code>.PP</code> for paragraph, <code>.B</code> for bold) and remain the standard format for Linux/Unix manual pages.

=== SGML — Standard Generalised Markup Language (1986) ===

SGML is a meta-language for defining markup languages, standardised as ISO 8879:1986. It introduced the concept of separating document structure from presentation, and was the parent of both HTML and XML. Its complexity limited widespread adoption outside publishing and aerospace/defence industries, but its influence is enormous.

=== TeX and LaTeX (1978 / 1984) ===

Created by Donald Knuth, '''TeX''' is a typesetting system renowned for its precise, beautiful rendering of mathematical and scientific notation. '''LaTeX''', built on top of TeX by Leslie Lamport, added higher-level macros that made document authoring far more approachable. LaTeX remains the dominant format for academic papers, theses, and scientific publishing worldwide. Documents use commands such as <code>\section{}</code>, <code>\textbf{}</code>, and the <code>equation</code> environment.

=== RTF — Rich Text Format (1987) ===

Developed by Microsoft for cross-application and cross-platform document exchange. RTF encodes formatting as plain-text control words (e.g. <code>\b</code> for bold), making it human-readable in theory but verbose in practice. It was the default format for WordPad and early versions of Word, and served as a common interchange format before the dominance of OOXML and PDF.

=== HTML — HyperText Markup Language (1991) ===

Proposed by Tim Berners-Lee at CERN, HTML is an SGML-derived language that became the lingua franca of the World Wide Web. It separates document structure (tags like <code><h1></code>, <code><p></code>, <code><a></code>) from presentation (originally handled inline, later delegated to CSS). HTML5 (2014) significantly expanded its capabilities to include multimedia, semantic elements, and application-level features.

=== DocBook (1991) ===

An XML/SGML-based markup language originally developed by HaL Computer Systems and O'Reilly. DocBook is specifically designed for technical documentation and supports rich semantic tagging (<code><procedure></code>, <code><varlistentry></code>, <code><programlisting></code>, etc.). It can be transformed to HTML, PDF, man pages and other formats via XSLT stylesheets. Widely used in open source projects and technical publishing.

=== XML — eXtensible Markup Language (1998) ===

A simplified subset of SGML designed for general-purpose structured data. While not a document format per se, XML underpins many documentation formats (DocBook, OOXML, DITA). Its strict well-formedness rules and wide tooling support made it a foundational technology for data interchange in the 2000s, though JSON has displaced it for many API use cases.

=== reStructuredText / RST (2002) ===

Developed by David Goodger as part of the Python <code>docutils</code> project. RST is a lightweight markup language designed to be readable as plain text while being processable into HTML, LaTeX, PDF, and man pages. It is the native format of Python's official documentation and the Sphinx documentation generator, making it extremely prevalent in the Python ecosystem.

<pre>
Example RST:
Section Title
=============
Some **bold** text and a `hyperlink <http://example.com>`_.
</pre>

=== AsciiDoc (2002) and Asciidoctor (2013) ===

AsciiDoc fills a niche between Markdown's simplicity and DocBook's power. It was designed for writing books and technical documentation, supporting features like cross-references, includes, callouts, and multiple output formats natively. '''Asciidoctor''', a Ruby reimplementation, significantly revitalised the ecosystem. It is used by the Git project, Spring Framework, and many others for their documentation.

=== Markdown (2004) ===

Created by John Gruber (with input from Aaron Swartz), Markdown was explicitly designed to be readable as-is in plain-text form, with its syntax inspired by email conventions. It converts to HTML and is now the de facto standard for README files, static site generators, wikis, and developer documentation. Its simplicity came at the cost of standardisation — numerous dialects emerged (GitHub Flavored Markdown, CommonMark, MultiMarkdown) with incompatible extensions.

<pre>
Example Markdown:
## Section Title
Some **bold** text and a [hyperlink](http://example.com).
</pre>

=== Wiki Markup ===

Most wiki platforms developed their own lightweight markup languages before Markdown became dominant. Examples include:

* '''MediaWiki markup''' — used by Wikipedia; uses <code>''italic''</code>, <code>'''bold'''</code>, <code>== headings ==</code>
* '''TWiki / Foswiki markup''' — uses <code>---+</code> headings, <code>*bold*</code>, <code>_italic_</code>, and TML (Topic Markup Language) for structured data
* '''Confluence wiki markup''' — Atlassian's proprietary variant

=== Org-mode (2003) ===

An outlining and plain-text markup system embedded within the Emacs text editor, created by Carsten Dominik. Org-mode is exceptionally powerful for note-taking, project planning, literate programming, and publishing. It can export to HTML, LaTeX, PDF, ODT and many other formats, and its <code>babel</code> feature allows executable code blocks in dozens of languages.

=== CommonMark and Pandoc ===

'''CommonMark''' (2014) was an effort to produce a rigorous, unambiguous specification for Markdown to resolve the fragmentation of dialects. '''Pandoc''', created by John MacFarlane, is a universal document converter supporting dozens of input and output formats, and has become an essential tool for anyone working across multiple markup ecosystems.

== Summary Comparison ==

{| class="wikitable sortable"
! Format !! Created !! Primary Use !! Output Targets !! Complexity
|-
| Roff/groff || 1964+ || Man pages, UNIX docs || Terminal, PostScript || Medium
|-
| TeX/LaTeX || 1978/1984 || Academic & scientific publishing || PDF, DVI || High
|-
| SGML || 1986 || Meta-language, publishing || Varies || Very High
|-
| RTF || 1987 || Word processing interchange || Print, screen || Medium
|-
| HTML || 1991 || Web pages || Browser || Low–Medium
|-
| DocBook || 1991 || Technical documentation || HTML, PDF, man || High
|-
| XML || 1998 || Structured data & documents || Varies || Medium
|-
| RST || 2002 || Python/developer docs || HTML, PDF, man || Medium
|-
| AsciiDoc || 2002 || Technical books & docs || HTML, PDF, ePub || Medium
|-
| Org-mode || 2003 || Notes, literate programming || HTML, PDF, ODT || Medium–High
|-
| Markdown || 2004 || READMEs, wikis, web || HTML || Low
|}

== See Also ==

* [[Markdown Syntax|Markdown Syntax Reference]]
* [https://pandoc.org Pandoc — Universal Document Converter]
* [https://commonmark.org CommonMark Specification]
* [https://www.mediawiki.org/wiki/Help:Formatting MediaWiki Formatting Help]

[[Category:Languages]]
[[Category:Documentation]]

Markup Notes

2026-02-25T22:58:57Z

PeterHarding: Created page with "= Forms of Documentation Markup = In the past, many solutions have evolved to facilitate the easy creation of documents and documentation. These range from lightweight human-readable formats like Markdown, to highly capable typesetting systems like TeX/LaTeX, to structured data formats like XML. The choice of markup language typically reflects a trade-off between ease of authoring, rendering fidelity, and the intended output medium. ---++ Historical Background The co..."

= Forms of Documentation Markup =

In the past, many solutions have evolved to facilitate the easy creation of documents and documentation. These range from lightweight human-readable formats like Markdown, to highly capable typesetting systems like TeX/LaTeX, to structured data formats like XML. The choice of markup language typically reflects a trade-off between ease of authoring, rendering fidelity, and the intended output medium.

---++ Historical Background

The concept of "markup" predates computers — editors and typesetters would literally mark up manuscripts with instructions for printers. With the arrival of electronic publishing in the 1960s and 70s, these conventions were formalised into machine-readable languages. Early systems were tightly coupled to specific hardware (typesetters, printers, terminals), and over time higher-level, more portable formats emerged.

---++ Markup Languages and Formats

---+++ Runoff / Roff Family (1964 onwards)
The roff family traces its roots to the =RUNOFF= program written by Jerome Saltzer at MIT in 1964. It was the dominant document formatting system on early UNIX systems.
* *nroff* — formats text for fixed-width terminal output
* *troff* — the typesetting variant, targeting phototypesetting devices
* *groff* (GNU roff) — the modern open source successor, still widely used today for Unix man pages

Roff documents use dot-prefixed commands (e.g. =.PP= for paragraph, =.B= for bold) and remain the standard format for Linux/Unix manual pages.

---+++ SGML — Standard Generalised Markup Language (1986)
SGML is a meta-language for defining markup languages, standardised as ISO 8879:1986. It introduced the concept of separating document structure from presentation, and was the parent of both HTML and XML. Its complexity limited widespread adoption outside publishing and aerospace/defence industries, but its influence is enormous.

---+++ TeX and LaTeX (1978 / 1984)
Created by Donald Knuth, *TeX* is a typesetting system renowned for its precise, beautiful rendering of mathematical and scientific notation. *LaTeX*, built on top of TeX by Leslie Lamport, added higher-level macros that made document authoring far more approachable. LaTeX remains the dominant format for academic papers, theses, and scientific publishing worldwide. Documents use commands such as =\section{}=, =\textbf{}=, and the =equation= environment.

---+++ RTF — Rich Text Format (1987)
Developed by Microsoft for cross-application and cross-platform document exchange. RTF encodes formatting as plain-text control words (e.g. =\b= for bold), making it human-readable in theory but verbose in practice. It was the default format for WordPad and early versions of Word, and served as a common interchange format before the dominance of OOXML and PDF.

---+++ HTML — HyperText Markup Language (1991)
Proposed by Tim Berners-Lee at CERN, HTML is an SGML-derived language that became the lingua franca of the World Wide Web. It separates document structure (tags like =<h1>=, =<p>=, =<a>=) from presentation (originally handled inline, later delegated to CSS). HTML5 (2014) significantly expanded its capabilities to include multimedia, semantic elements, and application-level features.

---+++ DocBook (1991)
An XML/SGML-based markup language originally developed by HaL Computer Systems and O'Reilly. DocBook is specifically designed for technical documentation and supports rich semantic tagging (=<procedure>=, =<varlistentry>=, =<programlisting>=, etc.). It can be transformed to HTML, PDF, man pages and other formats via XSLT stylesheets. Widely used in open source projects and technical publishing.

---+++ XML — eXtensible Markup Language (1998)
A simplified subset of SGML designed for general-purpose structured data. While not a document format per se, XML underpins many documentation formats (DocBook, OOXML, DITA). Its strict well-formedness rules and wide tooling support made it a foundational technology for data interchange in the 2000s, though JSON has displaced it for many API use cases.

---+++ reStructuredText / RST (2002)
Developed by David Goodger as part of the Python =docutils= project. RST is a lightweight markup language designed to be readable as plain text while being processable into HTML, LaTeX, PDF, and man pages. It is the native format of Python's official documentation and the Sphinx documentation generator, making it extremely prevalent in the Python ecosystem.

<verbatim>
Example RST:
Section Title
=============
Some **bold** text and a `hyperlink <http://example.com>`_.
</verbatim>

---+++ Markdown (2004)
Created by John Gruber (with input from Aaron Swartz), Markdown was explicitly designed to be readable as-is in plain-text form, with its syntax inspired by email conventions. It converts to HTML and is now the de facto standard for README files, static site generators, wikis, and developer documentation. Its simplicity came at the cost of standardisation — numerous dialects emerged (GitHub Flavored Markdown, CommonMark, MultiMarkdown) with incompatible extensions.

<verbatim>
Example Markdown:
## Section Title
Some **bold** text and a [hyperlink](http://example.com).
</verbatim>

---+++ AsciiDoc (2002) and Asciidoctor (2013)
AsciiDoc fills a niche between Markdown's simplicity and DocBook's power. It was designed for writing books and technical documentation, supporting features like cross-references, includes, callouts, and multiple output formats natively. *Asciidoctor*, a Ruby reimplementation, significantly revitalised the ecosystem. It is used by the Git project, Spring Framework, and many others for their documentation.

---+++ Wiki Markup
Most wiki platforms developed their own lightweight markup languages before Markdown became dominant. Examples include:
* *MediaWiki markup* — used by Wikipedia; uses =''italic''=, ='''bold'''=, ===headings===
* *TWiki / Foswiki markup* — uses ==---+= headings, =*bold*=, =_italic_=, and TML (Topic Markup Language) for structured data
* *Confluence wiki markup* — Atlassian's proprietary variant

---+++ Org-mode (2003)
An outlining and plain-text markup system embedded within the Emacs text editor, created by Carsten Dominik. Org-mode is exceptionally powerful for note-taking, project planning, literate programming, and publishing. It can export to HTML, LaTeX, PDF, ODT and many other formats, and its =babel= feature allows executable code blocks in dozens of languages.

---+++ CommonMark and Pandoc
*CommonMark* (2014) was an effort to produce a rigorous, unambiguous specification for Markdown to resolve the fragmentation of dialects. *Pandoc*, created by John MacFarlane, is a universal document converter supporting dozens of input and output formats, and has become an essential tool for anyone working across multiple markup ecosystems.

---++ Summary Comparison

| *Format* | *Created* | *Primary Use* | *Output Targets* | *Complexity* |
| Roff/groff | 1964+ | Man pages, UNIX docs | Terminal, PostScript | Medium |
| TeX/LaTeX | 1978/1984 | Academic & scientific publishing | PDF, DVI | High |
| SGML | 1986 | Meta-language, publishing | Varies | Very High |
| RTF | 1987 | Word processing interchange | Print, screen | Medium |
| HTML | 1991 | Web pages | Browser | Low–Medium |
| DocBook | 1991 | Technical documentation | HTML, PDF, man | High |
| XML | 1998 | Structured data & documents | Varies | Medium |
| RST | 2002 | Python/developer docs | HTML, PDF, man | Medium |
| AsciiDoc | 2002 | Technical books & docs | HTML, PDF, ePub | Medium |
| Markdown | 2004 | READMEs, wikis, web | HTML | Low |
| Org-mode | 2003 | Notes, literate programming | HTML, PDF, ODT | Medium–High |

---++ See Also
* [[MarkdownSyntax][Markdown Syntax Reference]]
* [[WikiSyntax][Foswiki Markup Reference]]
* [[https://pandoc.org][Pandoc — Universal Document Converter]]
* [[https://commonmark.org][CommonMark Specification]]

[[Category:Languages]]
[[Category:Documentation]]

Foswiki Notes

2026-01-31T21:11:28Z

PeterHarding:

= Overview =

* https://foswiki.org/Home/WebHome
* https://en.wikipedia.org/wiki/Foswiki
* https://foswiki.web.cern.ch/
* https://www.wikimatrix.org/show/Foswiki
* https://collab.phys.unsw.edu.au:4431/bin/view/System/TwentyMinuteTutorial
*
*

= Summary =

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

* Similar architecture and Perl-based implementation
* Compatible data structures and file formats (at least initially)
* Similar markup syntax and features
* Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

= FosWiki Docker =

* https://hub.docker.com/r/timlegge/docker-foswiki
* https://foswiki.org/Blog/UpdatingDockerFoswikiTo217
*
*
*

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:Foswiki]]

Category:Foswiki

2026-01-30T07:21:20Z

PeterHarding: Created page with "Foswiki links, notes and references..."

Foswiki links, notes and references...

Foswiki Notes

2026-01-30T07:21:06Z

PeterHarding: /* FosWiki Docker */

= Overview =

* https://foswiki.org/Home/WebHome
* https://en.wikipedia.org/wiki/Foswiki
* https://foswiki.web.cern.ch/
* https://www.wikimatrix.org/show/Foswiki
* https://collab.phys.unsw.edu.au:4431/bin/view/System/TwentyMinuteTutorial
*
*

= Summary =

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

* Similar architecture and Perl-based implementation
* Compatible data structures and file formats (at least initially)
* Similar markup syntax and features
* Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

= FosWiki Docker =

* https://hub.docker.com/r/timlegge/docker-foswiki

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:Foswiki]]

Category:FosWiki

2026-01-30T07:20:52Z

PeterHarding: Created page with "Foswiki links, notes and references..."

Foswiki links, notes and references...

Category:TWiki

2026-01-30T07:20:29Z

PeterHarding: Created page with "TWiki links, notes and references..."

TWiki links, notes and references...

Foswiki Notes

2026-01-30T07:20:12Z

PeterHarding:

= Overview =

* https://foswiki.org/Home/WebHome
* https://en.wikipedia.org/wiki/Foswiki
* https://foswiki.web.cern.ch/
* https://www.wikimatrix.org/show/Foswiki
* https://collab.phys.unsw.edu.au:4431/bin/view/System/TwentyMinuteTutorial
*
*

= Summary =

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

* Similar architecture and Perl-based implementation
* Compatible data structures and file formats (at least initially)
* Similar markup syntax and features
* Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

= FosWiki Docker =

* https://hub.docker.com/r/timlegge/docker-foswiki

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:FosWiki]]

Foswiki Notes

2026-01-30T07:19:07Z

PeterHarding:

= Overview =

* https://foswiki.org/Home/WebHome
* https://en.wikipedia.org/wiki/Foswiki
* https://foswiki.web.cern.ch/
* https://www.wikimatrix.org/show/Foswiki
* https://collab.phys.unsw.edu.au:4431/bin/view/System/TwentyMinuteTutorial
*
*

= Summary =

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

Similar architecture and Perl-based implementation
Compatible data structures and file formats (at least initially)
Similar markup syntax and features
Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

= FosWiki Docker =

* https://hub.docker.com/r/timlegge/docker-foswiki

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:FosWiki]]

Foswiki Notes

2026-01-30T07:18:43Z

PeterHarding:

= Overview =

* https://foswiki.org/Home/WebHome
* https://en.wikipedia.org/wiki/Foswiki
* https://foswiki.web.cern.ch/
* https://www.wikimatrix.org/show/Foswiki
*
*
*

= Summary =

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

Similar architecture and Perl-based implementation
Compatible data structures and file formats (at least initially)
Similar markup syntax and features
Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

= FosWiki Docker =

* https://hub.docker.com/r/timlegge/docker-foswiki

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:FosWiki]]

Foswiki Notes

2026-01-30T07:13:54Z

PeterHarding:

= Overview =

* https://foswiki.org/Home/WebHome
* https://en.wikipedia.org/wiki/Foswiki
* https://foswiki.web.cern.ch/
*

= Summary =

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

Similar architecture and Perl-based implementation
Compatible data structures and file formats (at least initially)
Similar markup syntax and features
Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

= FosWiki Docker =

* https://hub.docker.com/r/timlegge/docker-foswiki

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:FosWiki]]

Foswiki Notes

2026-01-30T07:13:06Z

PeterHarding:

= Overview =

* https://foswiki.org/Home/WebHome
* https://en.wikipedia.org/wiki/Foswiki
*
*

= Summary =

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

Similar architecture and Perl-based implementation
Compatible data structures and file formats (at least initially)
Similar markup syntax and features
Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

= FosWiki Docker =

* https://hub.docker.com/r/timlegge/docker-foswiki

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:FosWiki]]

Foswiki Notes

2026-01-30T07:11:44Z

PeterHarding:

Foswiki Notes

2026-01-30T07:11:22Z

PeterHarding:

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

Similar architecture and Perl-based implementation
Compatible data structures and file formats (at least initially)
Similar markup syntax and features
Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

Since you've been working on TWiki migration and containerization, you might find that Foswiki could be a potential migration target - the shared ancestry means there are tools and documentation for migrating from TWiki to Foswiki, though the projects have diverged over the years since 2008.

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:FosWiki]]

Foswiki Notes

2026-01-30T07:10:57Z

PeterHarding: Created page with " Foswiki is a fork of TWiki that was created in 2008. The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform. The key connection is that Foswiki started from the same TWiki codebase, so they share: Similar architecture and Perl-bas..."

Foswiki is a fork of TWiki that was created in 2008.

The split happened due to disagreements within the TWiki community about governance and development direction. A significant portion of TWiki's core development team and community members decided to fork the project, creating Foswiki as a separate open-source wiki platform.

The key connection is that Foswiki started from the same TWiki codebase, so they share:

Similar architecture and Perl-based implementation
Compatible data structures and file formats (at least initially)
Similar markup syntax and features
Many of the same concepts (webs, topics, plugins, etc.)

After the fork, both projects continued independent development. Foswiki was positioned as having a more community-driven governance model, while TWiki continued under its existing leadership.

Since you've been working on TWiki migration and containerization, you might find that Foswiki could be a potential migration target - the shared ancestry means there are tools and documentation for migrating from TWiki to Foswiki, though the projects have diverged over the years since 2008.

Is this relevant to your TWiki work, or are you considering Foswiki as an alternative?

[[Category:Wiki]]
[[Category:TWiki]]
[[Category:FosWiki]]

Category:Rust

2026-01-28T05:47:56Z

PeterHarding: Created page with "Rust links, notes and references..."

Rust links, notes and references...

Rust Examples

2026-01-28T05:47:35Z

PeterHarding: Created page with " * https://medium.com/@toyezyadav/i-replaced-my-spring-boot-microservice-with-rust-and-go-heres-the-system-design-that-saved-my-f3ccedd6e494 <pre> // src/lib.rs (Rust Service) use std::time::Instant; use sha2::{Sha256, Digest}; // Simulating the same heavy, synchronous transformation/hashing operation pub fn calculate_user_partition_key(user_id: &str, complexity: u32) -> String { let start = Instant::now(); let mut base = user_id.to_string(); for i in 0..c..."

* https://medium.com/@toyezyadav/i-replaced-my-spring-boot-microservice-with-rust-and-go-heres-the-system-design-that-saved-my-f3ccedd6e494

<pre>
// src/lib.rs (Rust Service)
use std::time::Instant;
use sha2::{Sha256, Digest};

// Simulating the same heavy, synchronous transformation/hashing operation
pub fn calculate_user_partition_key(user_id: &str, complexity: u32) -> String {
let start = Instant::now();
let mut base = user_id.to_string();

for i in 0..complexity {
let mut hasher = Sha256::new();
// Rust's zero-cost abstractions and memory safety shine here
hasher.update(base.as_bytes());
hasher.update(i.to_string().as_bytes());
base = format!("{:x}", hasher.finalize());
}

let duration = start.elapsed();
// This is the "hot path" code. It's clean, safe, and ridiculously fast.
base[0..16].to_string()
}
</pre>

[[Category:Rust]]