+972 52-548-6969
I just read a few of my posts from 2004.
They are... an education. I forgot how I was then.
My project at the time was creating a writable configuration file API and rambling about bad OSS is.
Markdown turns plain text formatting into fancy HTML formatting.
*italic* **bold**
_italic_ __bold__
Inline:
An [example](http://url.com/ "Title")
Reference-style labels (titles are optional):
An [example][id]. Then, anywhere
else in the doc, define the link:
[id]: http://example.com/ "Title"
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Ordered, without paragraphs:
1. Foo
2. Bar
Unordered, with paragraphs:
* A list item.
With multiple paragraphs.
* Bar
You can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Three or more dashes or asterisks:
---
* * *
- - - -
End a line with two or more spaces:
Roses are red,
Violets are blue.
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowTerm 1
: Definition 1
Term 2
: Definition 2Body text with a footnote [^1]
[^1]: Footnote text here
MDD <- will have title
*[MDD]: MarkdownDeep
There are posts all the way to Oct 07, 2016
| Main feed |
|
| Comments feed | |
Comments
OSS still has hurt feelings from that post. I hear that, to this day, she is still waiting for a public apology and retraction. :)
Actually, though, I think your statement is fairly accurate. Open Source Software is bad. It's just that closed source software is much, much worse!
A while back I spent some time going through some of your older posts and there is some absolute gold in there. In terms of technical coverage, I would rate a dump of your site better than most textbooks. Have you ever thought about releasing your blog posts as a collection for offline reading? I'd pay for something like that. Especially if it were in a decent format (xml for transforming into chm / pdf / word / something readable on my Tytn II / rss for the offline feed reader / ... ).
These posts... They are lovely :)
But what you said in the bad OSS post is just plain wrong, or complaining about life.
I mean, that is not an opensource limitation in the sense that a non-open-source program doesn't have it. A non OSS program just have a tons more limitations.
The statements said there even contradict what you're current blog slogan is: "That is a great idea, send me a patch for it".
Regards.
Knocte,
Yes, that is the point of pointing that out.
It has been four years, I learned a bit
@Ayende
Some people just don't understand this concept of "I've grown as a person, see what I used to be like" ;)
I hear you.
I cringe when I read the kinds of drivel I wrote 15 years ago... Times have changed.
Anyways, I think very few people come to realize your level of maturity with respect to their work as you have in the past 4 years. Some never get there.
So nice going!
Also, I second the suggestion that you should collect your best writings and publish a little collection of essays. You have said some very insightful things on this blog and elsewhere.
@Jeff - Why the need to cull? If it were dead trees spolsky style, I would understand, but most of the posts Ayende's ever written are insightful enough to be seen as a collection, the conversations in the comments really add to that.
Comment preview