Tradeoffs of Markdown as code files:

- notice I didn't use code fencing backticks around the Ruby code… that would get noisy

- default would be to treat text between ## h2 headings as code?

- comments have to be… blockquotes? wrapped in --- HRs? or something

- what syntax for code comments? //

Really REALLY hare brained idea—

Multiple programming languages

- in the same file!?

- with file extension? eg, foo.rb.md

- …

Bonus hare brained programming idea— what if we inferred the conventional class name/namespace from its filename/folder?

foo.rb:

def bar
puts “ab”
end

def baz
puts “xy"
end

def whoami
puts class.name
end

———

foo.md:

## bar
puts "ab

## baz
puts “xy

## whoami
puts class.name

Benefits of Markdown as code files:

- docs / code are the same thing

- pretty formatting of comments

- all of the Markdown editors already Just Work

- flatter file / two levels less indentation

- inferred ends/closers from starting the next heading

- directly linkable with href=#___ links

Today in hare brained programming ideas— what if we wrote code in Markdown files?

Hear me out…

A simple Ruby class (PORO): Foo
w/ methods: bar & baz

foo.rb:

class Foo
def bar
puts “ab”
end

def baz
puts “xy”
end
end

———

foo.md:

# Foo

## bar
puts "ab

## baz
puts “xy