Repos / s4g / f50569fa76
commit f50569fa76d38dac4e5e9895ffbcb8d91037ffbc
Author: Nhân <hi@imnhan.com>
Date: Mon Jul 10 22:12:16 2023 +0700
add more... interesting example post
diff --git a/www/about/index.html b/www/about/index.html
index f1f52cf..823e3b3 100644
--- a/www/about/index.html
+++ b/www/about/index.html
@@ -34,7 +34,7 @@ <h2>No really</h2>
</content>
<footer>
-© 2022–2023 Coolio McCool<br>
+© 2008–2023 Coolio McCool<br>
Made with <a href="https://github.com/nhanb/webmaker2000">WebMaker2000</a>
</footer>
diff --git a/www/feed.xml b/www/feed.xml
index 59e37b0..9f59f07 100644
--- a/www/feed.xml
+++ b/www/feed.xml
@@ -16,10 +16,10 @@
<updated>2023-04-05T00:00:00+07:00</updated>
</entry>
<entry>
- <title>Hello</title>
- <id>https://coolzone.example.com/hello/</id>
- <link href="https://coolzone.example.com/hello/"></link>
- <published>2022-01-02T00:00:00+07:00</published>
- <updated>2022-01-02T00:00:00+07:00</updated>
+ <title>I'm Going To Scale My Foot Up Your Ass</title>
+ <id>https://coolzone.example.com/scale/</id>
+ <link href="https://coolzone.example.com/scale/"></link>
+ <published>2008-04-24T00:00:00+07:00</published>
+ <updated>2008-04-24T00:00:00+07:00</updated>
</entry>
</feed>
\ No newline at end of file
diff --git a/www/hello/index.dj b/www/hello/index.dj
deleted file mode 100644
index 7209c9c..0000000
--- a/www/hello/index.dj
+++ /dev/null
@@ -1,5 +0,0 @@
-Title: Hello
-PostedAt: 2022-01-02
----
-
-Hello world.
diff --git a/www/hello/index.html b/www/hello/index.html
deleted file mode 100644
index a2df623..0000000
--- a/www/hello/index.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<!DOCTYPE html>
-<html>
-
-<head>
- <meta charset="utf-8" />
- <title>Hello | CoolZone</title>
- <meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <link rel="alternate" type="application/atom+xml" title="Atom feed" href="/feed.xml">
- <link rel="stylesheet" href="/_theme/base.css">
- <link rel="stylesheet" href="/_theme/post.css">
-</head>
-
-<body>
-
-<nav>
- <a href="/">Home</a>
- <a href="/about/">About</a>
- <span class="posted-on">
- Posted on
- <time datetime="2022-01-02">
- Sunday, 02 Jan 2022
- </time>
- </span>
-
-</nav>
-
-<hr>
-
-<h1 class="post-title">Hello</h1>
-<content>
-<p>Hello world.</p>
-
-</content>
-<footer>
-© 2022–2023 Coolio McCool<br>
-Made with <a href="https://github.com/nhanb/webmaker2000">WebMaker2000</a>
-</footer>
-
-</body>
-
-</html>
diff --git a/www/index.html b/www/index.html
index 4ce2c50..727f37c 100644
--- a/www/index.html
+++ b/www/index.html
@@ -36,8 +36,8 @@ <h1 class="site-title">CoolZone</h1>
<a href="mfws.html">This is a motherfucking website.</a>
</li>
<li>
- 2022-01-02 —
- <a href="hello/">Hello</a>
+ 2008-04-24 —
+ <a href="scale/">I'm Going To Scale My Foot Up Your Ass</a>
</li>
</ul>
@@ -71,7 +71,7 @@ <h1 class="site-title">CoolZone</h1>
</style>
<footer>
-© 2022–2023 Coolio McCool<br>
+© 2008–2023 Coolio McCool<br>
Made with <a href="https://github.com/nhanb/webmaker2000">WebMaker2000</a>
</footer>
diff --git a/www/manifest.txt b/www/manifest.txt
index 73c6c86..207b13f 100644
--- a/www/manifest.txt
+++ b/www/manifest.txt
@@ -1,5 +1,5 @@
about/index.html
feed.xml
-hello/index.html
index.html
-mfws.html
\ No newline at end of file
+mfws.html
+scale/index.html
\ No newline at end of file
diff --git a/www/mfws.html b/www/mfws.html
index dd9cd83..26d4a8d 100644
--- a/www/mfws.html
+++ b/www/mfws.html
@@ -121,7 +121,7 @@ <h2>Epilogue</h2>
</content>
<footer>
-© 2022–2023 Coolio McCool<br>
+© 2008–2023 Coolio McCool<br>
Made with <a href="https://github.com/nhanb/webmaker2000">WebMaker2000</a>
</footer>
diff --git a/www/scale/bill.jpg b/www/scale/bill.jpg
new file mode 100644
index 0000000..4a4a0ff
Binary files /dev/null and b/www/scale/bill.jpg differ
diff --git a/www/scale/index.dj b/www/scale/index.dj
new file mode 100644
index 0000000..2b74faa
--- /dev/null
+++ b/www/scale/index.dj
@@ -0,0 +1,83 @@
+Title: I'm Going To Scale My Foot Up Your Ass
+PostedAt: 2008-04-24
+---
+
+
+
+_by [Ted Dziuba][1]_
+
+Engineers love to talk about scalability. It makes us feel like the bad ass,
+dick-swingin' motherfuckers that we wish we could be.
+
+After we talk about scalability with our co-workers (_Yeah, Rails doesn't
+scale!_), we flex our true engineering prowess by writing a post about it on
+our blog. Once that post hits Reddit, son, everyone will know how hardcore you
+really are. Respect.
+
+## People Who Talk Big About Scalability Don't Need To Worry About It
+
+Fact: every chest-thumping blog post I have seen written about scalability is
+either about architecture, Memcached, or both. Some asshole who writes shitty
+code starts pontificating about _"scalable architecture"_ with data storage,
+web frontends, whatever-the-fuck. Dude, your app isn't having scalability
+problems because of the _architecture_. It's having scalability problems
+because you coded a ton of N^2 loops into it and you're too self-important to
+get peer reviews on your commits.
+
+And let's not forget the tools who discover Memcached for the first time,
+install it on a web server, and notice how fast their app runs now. Yeah,
+welcome to the modern age. Hope you know what a cache expiry policy is.
+
+## If You Haven't Discussed Capacity Planning, You Can't Discuss Scalability
+
+You don't need to worry about scalability on your Rails-over-Mysql application
+because nobody is going to use it. Really. Believe me. You're going to get,
+at most, 1,000 people on your app, and maybe 1% of them will be 7-day active.
+Scalability is not your problem, getting people to give a shit is.
+
+Unless you know what you need to scale _to_, you can't even begin to talk about
+scalability. How many users do you want your system to handle? A thousand?
+Hundred thousand? Ten million? Here's a hint: the system you design to handle
+a quarter million users is going to be different from the system you design to
+handle ten million users.
+
+Of course you'll point to the engineer's wet dream: linear scalability. _Lulz
+but when we get more users we just add more machines you are so stupid ted.
+uncov sucks._
+
+Yeah, great, well it doesn't exist. Oh no, go ahead and try out Amazon
+SimpleDB and think to yourself that it will scale linearly. Then, when you get
+enough users that the latency becomes a problem, blame it on "those shitty
+Amazon datacenters".
+
+## Choosing Technology Don't Mean Shit If You Don't Know How To Use It
+
+The most common butthurt about scalability is this: choose a technology. If
+you like the technology, claim _"technology X scales better!"_ If you don't
+like it, claim _"technology X doesn't scale!"_
+
+Saying "Rails doesn't scale" is like saying "my car doesn't go infinitely
+fast". Alternatively, saying "We'll have no problems scaling because we're
+using Django" is like saying "I will win every race because my car is the most
+powerful". Maybe so, but you suck at driving, and you're up against
+professionals.
+
+If you're having scalability problems and blaming it on a single technology,
+chances are, you're doing it wrong.
+
+## tl;dr
+
+Shut up about scalability, no one is using your app anyway.
+
+``` =html
+<style>
+h2 { font-size: 1em; }
+body {
+ background: linear-gradient(white, lightgrey);
+ font-family: sans-serif;
+}
+img[alt="scaleboner"] { float: right; }
+</style>
+```
+
+[1]: http://widgetsandshit.com/teddziuba/2008/04/im-going-to-scale-my-foot-up-y.html
diff --git a/www/scale/index.html b/www/scale/index.html
new file mode 100644
index 0000000..b9ee5b8
--- /dev/null
+++ b/www/scale/index.html
@@ -0,0 +1,105 @@
+<!DOCTYPE html>
+<html>
+
+<head>
+ <meta charset="utf-8" />
+ <title>I'm Going To Scale My Foot Up Your Ass | CoolZone</title>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+ <link rel="alternate" type="application/atom+xml" title="Atom feed" href="/feed.xml">
+ <link rel="stylesheet" href="/_theme/base.css">
+ <link rel="stylesheet" href="/_theme/post.css">
+</head>
+
+<body>
+
+<nav>
+ <a href="/">Home</a>
+ <a href="/about/">About</a>
+ <span class="posted-on">
+ Posted on
+ <time datetime="2008-04-24">
+ Thursday, 24 Apr 2008
+ </time>
+ </span>
+
+</nav>
+
+<hr>
+
+<h1 class="post-title">I'm Going To Scale My Foot Up Your Ass</h1>
+<content>
+<p><img alt="scaleboner" src="bill.jpg"></p>
+<p><em>by <a href="http://widgetsandshit.com/teddziuba/2008/04/im-going-to-scale-my-foot-up-y.html">Ted Dziuba</a></em></p>
+<p>Engineers love to talk about scalability. It makes us feel like the bad ass,
+dick-swingin’ motherfuckers that we wish we could be.</p>
+<p>After we talk about scalability with our co-workers (<em>Yeah, Rails doesn’t
+scale!</em>), we flex our true engineering prowess by writing a post about it on
+our blog. Once that post hits Reddit, son, everyone will know how hardcore you
+really are. Respect.</p>
+<section id="People-Who-Talk-Big-About-Scalability-Don-t-Need-To-Worry-About-It">
+<h2>People Who Talk Big About Scalability Don’t Need To Worry About It</h2>
+<p>Fact: every chest-thumping blog post I have seen written about scalability is
+either about architecture, Memcached, or both. Some asshole who writes shitty
+code starts pontificating about <em>“scalable architecture”</em> with data storage,
+web frontends, whatever-the-fuck. Dude, your app isn’t having scalability
+problems because of the <em>architecture</em>. It’s having scalability problems
+because you coded a ton of N^2 loops into it and you’re too self-important to
+get peer reviews on your commits.</p>
+<p>And let’s not forget the tools who discover Memcached for the first time,
+install it on a web server, and notice how fast their app runs now. Yeah,
+welcome to the modern age. Hope you know what a cache expiry policy is.</p>
+</section>
+<section id="If-You-Haven-t-Discussed-Capacity-Planning-You-Can-t-Discuss-Scalability">
+<h2>If You Haven’t Discussed Capacity Planning, You Can’t Discuss Scalability</h2>
+<p>You don’t need to worry about scalability on your Rails-over-Mysql application
+because nobody is going to use it. Really. Believe me. You’re going to get,
+at most, 1,000 people on your app, and maybe 1% of them will be 7-day active.
+Scalability is not your problem, getting people to give a shit is.</p>
+<p>Unless you know what you need to scale <em>to</em>, you can’t even begin to talk about
+scalability. How many users do you want your system to handle? A thousand?
+Hundred thousand? Ten million? Here’s a hint: the system you design to handle
+a quarter million users is going to be different from the system you design to
+handle ten million users.</p>
+<p>Of course you’ll point to the engineer’s wet dream: linear scalability. <em>Lulz
+but when we get more users we just add more machines you are so stupid ted.
+uncov sucks.</em></p>
+<p>Yeah, great, well it doesn’t exist. Oh no, go ahead and try out Amazon
+SimpleDB and think to yourself that it will scale linearly. Then, when you get
+enough users that the latency becomes a problem, blame it on “those shitty
+Amazon datacenters”.</p>
+</section>
+<section id="Choosing-Technology-Don-t-Mean-Shit-If-You-Don-t-Know-How-To-Use-It">
+<h2>Choosing Technology Don’t Mean Shit If You Don’t Know How To Use It</h2>
+<p>The most common butthurt about scalability is this: choose a technology. If
+you like the technology, claim <em>“technology X scales better!”</em> If you don’t
+like it, claim <em>“technology X doesn’t scale!”</em></p>
+<p>Saying “Rails doesn’t scale” is like saying “my car doesn’t go infinitely
+fast”. Alternatively, saying “We’ll have no problems scaling because we’re
+using Django” is like saying “I will win every race because my car is the most
+powerful”. Maybe so, but you suck at driving, and you’re up against
+professionals.</p>
+<p>If you’re having scalability problems and blaming it on a single technology,
+chances are, you’re doing it wrong.</p>
+</section>
+<section id="tl-dr">
+<h2>tl;dr</h2>
+<p>Shut up about scalability, no one is using your app anyway.</p>
+<style>
+h2 { font-size: 1em; }
+body {
+background: linear-gradient(white, lightgrey);
+font-family: sans-serif;
+}
+img[alt="scaleboner"] { float: right; }
+</style>
+</section>
+
+</content>
+<footer>
+© 2008–2023 Coolio McCool<br>
+Made with <a href="https://github.com/nhanb/webmaker2000">WebMaker2000</a>
+</footer>
+
+</body>
+
+</html>