Skip to content

Commit 1ca665c

Browse files
committed
brush up
1 parent 4e10231 commit 1ca665c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

en/news/_posts/2013-06-30-we-retire-1-8-7.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ I wish I could say something epic but sadly my English skill is very limited, so
1212

1313
## About ruby 1.8.7
1414

15-
Now, majority of you are using ruby 1.9.x or 2.0.0 (**IF NOT PLEASE DO**). In the past however, there were other versions like 1.4.x, 1.6.x, and 1.8.x. They were the lineal descendents of original ruby 1.0, so called MRI. When matz released 1.8.0 it was the state-of-art release. 1.8.7 was the last scion of that clan.
15+
Now, a majority of you are using ruby 1.9.x or 2.0.0 (**IF NOT PLEASE DO**). In the past however, there were other versions like 1.4.x, 1.6.x, and 1.8.x. They were the lineal descendents of original ruby 1.0, so-called MRI. When matz released 1.8.0 it was the state-of-art release. 1.8.7 was the last scion of that clan.
1616

1717
Technically speaking, it's been a decade since we released 1.8.0, and 5 years since we released 1.8.7. Back then, ruby was used to write CGI scripts. Then the situation changed dramatically with the raise of Rails. So many users started using ruby. And internally, we finally merged ko1's new engine (called YARV back then). The engine became the canonical ruby that you use today.
1818

@@ -22,4 +22,4 @@ Thank you 1.8.7, it was a good life for a program.
2222

2323
## About YOUR ruby 1.8.7
2424

25-
You might still have an executable of ruby 1.8.7 somewhere in your system. Depending on how you installed it, your ruby 1.8.7 might or might not be supported by someone else, because there're some 3rd-parties that do continue supporting 1.8.7. The only thing I can say is _I_ won't support it any longer. So if you're using what I've released, watch out and find a solution that suits your situation.
25+
You might still have an executable of ruby 1.8.7 somewhere in your system. Depending on how you installed it, your ruby 1.8.7 might or might not be supported by someone else, because there are some 3rd-parties that do continue supporting 1.8.7. The only thing I can say is _I_ won't support it any longer. So if you're using what I've released, watch out and find a solution that suits your situation.

0 commit comments

Comments
 (0)