, and this portrait of a dead person in this room! I now finally understood, I didn’t marry a blind person, but a dead person, a person that does not even belong to this world anymore!
I cried till my eyes hurt, then rushed to the table and swept everything off of it. The sound of china breaking was like my heart. I had never thought that my biological father would be so cruel, as to sell me as a wife for a dead person. Now I also knew while my uncles were pointing at me and gossiping.
I picked up the chair besides me and threw it against the door. Until the chair, twisted, fell to the floor, did I start crying, “Let me out! Let me out!” I tugged at the doorknob with all my might, but it didn’t budge! Like I thought, it was locked from the outside.
“Let me out!” I curled up against the door and started crying. Lost, helpless, my life wasn’t supposed to be this way.
Bang! A heavy noise sounded inside the room. I wiped my tears and looked over, and saw a small door inside the room suddenly opened. It was dark inside.
I watched it carefully, afraid that something might walk out. Even though I knew clearly there was no one in this room but me, still, all the hairs on my body stood on end, because I kept feeling that someone in this room was looking at me!
Yes, this was what I felt, and I noticed just now that the temperature in the room had become colder, cold enough that when I exhaled, I could see a faint puff of white.
Frightened, I curled myself up even tighter. It shouldn’t be like this, it’s summer right now, how could I see the breath from my own mouth! I exhaled lightly again, and that faint mist made me almost faint.
I turned my eyes towards the table that held the portrait. It couldn’t be! There are no ghosts in this world!  How could I believe in ghosts and spirits.
When the door to the bathroom banged once again, I let out a scream. My heart felt like it was on a spring, jumping faster and faster. I stared unbelieving at the bathroom door. Just now, that door was open.
“Wind! It must be the wind!” I told myself in a small voice, but I understood perfectly that even if the closed door was blown open by the wind, this door could not be shut by the wind! Because except for a wall of french windows on one side, there wasn’t a single window that could open in this room!
I scanned the room nervously. It’s impossible, I repeated in my mind, it’s impossible to have ghosts in this world! I tried my best to calm myself, but at last I put my head on my knees, my hands hugging my head tightly.
The old saying goes that if you didn’t do anything bad, you wouldn’t be afraid even if a ghost knocked on your door at midnight. I never hurt anyone, so why would I feel scared? Even if there really was a ghost, so what? Hate has its target and debts have their owners. If he had unfinished business, it has nothing to do with me, a total stranger!
“Mother!” I cried out, crying, my head between my knees. Fear doesn’t go away just by talking, not to mention that the air around me was even colder than before.
The btrfsck command is a filesystem-check command like fsck, but it works with the btrfs file system.
First a little bit about btrfs. As the name implies, btrfs uses a B-tree data structure that is self-balancing and maintains sorted data, facilitating searches, sequential access, insertions, and deletions. It is also often referred to as the “better file system”. Oracle developed it and first used it about 15 years ago. By November 2013, it was declared adequately stable and began to be used by other distributions as well, and now its use is quite common.
The benefits of btrfs are impressive, although it’s still a work in progress and some concerns have kept it from playing a more dominant role on Linux systems. It keeps 2 copies of metadata on a volume, allowing for data recovery if and when the hard drive is damaged or suffers from bad sectors. It uses checksums and verifies them with each read. In addition, compared to ext4 volumes, btrfs does not require double the storage space to accommodate file versioning and history data.
When you list file systems as shown below for a Fedora system, you may see that some of them are btrfs. The -T option provides the file system type while the -h option adjusts the sizes to be displayed in a human-friendly (size appropriate units) fashion.
To use btrfsck, the targeted file system should first be unmounted from the system.
The unmount can then be confirmed.
At this point, it is OK to run the file system check. The file system shown in this example is quite large, but only a small portion of it is in use. The output below shows the phases that the check runs through.
As you can see, no errors were found.
Unmounting file systems before running btrfsck is the recommended approach. When you cannot—such as when the file system is your root (/) file system—it is possible to force a check using the --force option as shown below.
The devtmpfs file system is one with includes automated device nodes populated by the kernel.
The tmpfs file system is one which keeps all of its files in virtual memory.
The ext4 file system is a journaling file system developed as the successor to ext3. A journaling file system is one that keeps track of changes not yet committed to the file system by recording the goal of such changes. Ext4 also provides large file system support, improved resistance to fragmentation, higher performance and improved timestamps.Q: What (if any) technical debt am I incurring with Ruby on Rails? I'm a big fan of ruby on rails, and it seems to incorporate many of the 'greatest hits' of web application programming techniques. Convention over configuration in particular is a big win to my mind.
However I also have the feeling that some of the convenience I am getting is coming at the expense of technical debt that will need to be repaid down the road. It's not that I think ROR is quick and dirty, as I think it incorporates a lot of best practices and good default options in many cases. However, it seems to me that just doesn't cover some things yet (in particular there is little direct support for security in the framework, and plugins that I have seen are variable in quality).
I'm not looking for religious opinions or flamewars here, but I'd be interested to know the community's opinion on what areas Rails needs to improve on, and/or things that users of Rails need to watch out for on their own because the framework won't hold their hand and guide them to do the right thing.

A: Regardless of framework the programmer needs to know what she's doing. I'd say that it's much easier to build a secure web application using something as mature, well designed and widely adapted as Ruby on Rails than going without the framework support.
Take care with plugins and find out how they work (know what you do, again).

A: I love Rails too, but its important for us to understand the shortcomings of the framework that we use.  Though it might be a broad topic addressing these issues wont hurt anyone.
Aside from security issues, one other big issue is DEPLOYMENT on Shared Hosts.  PHP thrives in shared hosting environments but Rails is still lagging behind.
Of course most professional Rails developers know that their apps need fine-tuned servers for production and they will obviously deploy on Rails-Specific hosts.
In order for Rails to continue success the core team should address this issue, especially with Rails 3.0 (Merb +Rails) coming..
An example of this is simple:  I have a bluehost account, and i noticed the Rails icon in my cpanel.  I talked to the bluehost support and they said its more or less a dummy icon, and that it doesn't function properly.
Having said that any professional who wanted to deploy a Rails App would not use bluehost.    , but it does hurt Rails, when hosts say that they support it and then users run into problems which their support know nothing about..

A: The article you refer to defines technical debt as 

[the] eventual consequences of
  slapdash software architecture and
  hasty software development

With rails, any development that is not test driven incurs technical debt. But that is the case with any platform.
At an architectural level Rails provides some deployment challenges. A busy site must scale with lots of hardware or use intelligent caching strategies.
My advice to anyone adapting Rails would be to:


*

*use TDD for all your development

*verify the quality off any plugin
you use by reading its tests. If
they are not clear and complete,
avoid the plugin 

*read "Rails
Recipes" and "Advanced Rails
Recipes" (Advanced Rails Recipes has
a good recipe for adding
authentication in a RESTful way)

*be prepared to pay for hardware to scale your site (hardware is cheaper than development time)


A: From my experience, by far the biggest tolls you end up paying with RoR