Maybe a century down the road we will have vim-customized keyboards. Tangible keyboards will always have a place, I think, because they provide tactile feedback, unlike "pictures under glass" like you get with touch screens.
386 karma · joined January 26, 2012
http://www.biblegateway.com/passage/?search=Revelation+21:4&version=ESV
Everyone will live forever in heaven or die forever in hell.
In Romans 3:26, the Bible explains the three J's you must know to live forever:
1. God is Just, or righteous. God cannot allow sin in heaven. If God let sinful people into heaven, it wouldn't be heaven anymore. However, people are sinful. When people created the internet, we programmed computer viruses in our new world. If God let sinners into heaven, they would program computer viruses there too. Definitely not heaven.
So no one can get into heaven unless you are absolutely perfect. Otherwise it wouldn't be heaven.
2. God is a Justifier -- God justifies people. He makes us righteous. He can free us from our guilt right now, today. He can also deliver us from eternal death. And He wants to do this.
3. God justifies those who believe in Jesus -- God has a son, Jesus Christ. God loves his son. Therefore, God decided to justify people when they believe in Christ.
You must believe that Christ died for you and took the punishment you deserve. He also lived a righteous life in your place. That means God will let you go to heaven even though you have done wrong things. When you believe this and decide you want to stop being a sinner and stop sinning, God will save you. He will consider you to be as righteous as Jesus Christ. He will no longer consider you to be sinful, since Christ took your sin. He will begin changing you to be like His Son until you reach heaven (Romans 8:29).
Please read this too: http://www.bju.edu/about-bju/salvation.php
Maybe a century down the road we will have vim-customized keyboards. Tangible keyboards will always have a place, I think, because they provide tactile feedback, unlike "pictures under glass" like you get with touch screens.
Don't do business with a company designed to take advantage of you. Problem solved.
It immensely benefited me -- a web developer familiar with the craft but lacking depth. It could be a difficult introduction to read cover to cover! By all means get it if you plan a deep relationship with web programming.
But isn't it fascinating? Some information moved from the link node into the state of the program processing it. This halves the link redundancy of a doubly linked list. Suddenly a doubly linked list has the footprint of a singly linked list. How did that happen? :-)
It taught me. Tricks like this make me a better programmer. Even if I won't use the principle involved in this exact way.
Error correction simply means "add a semicolon if it's necessary."
The Google+ design will continue to evolve, I'm sure (it is not quite there yet).
Technology makes us more human, not less.
Technology creates new verbs ("email" me; "like" me, "follow" me). But we embrace only language that makes us more human, not less.
People think that technology colonizes us. On the contrary, we colonize technology.
However, humanity has good and evil sides. Trouble brews when the evil colonizes more effectively than the good. Preventing this is itself a "wicked problem."
I use ^[ to end insert mode.
This only happens when you use macros like I do. I took a look at my registers and here's a random one I did four months ago (using Surround.vim to wrap an indented area in div tags).
V/^[ ]\{0,2}[^ ]/-1^MS<div class="question"^M
Create a "quiz" every day. For every article, formulate a question answered by the article that is actually important.
Later on, you can go back to your quiz and review your questions.
However, the most interesting part is that you will learn to instantly recognize cruft you don't need.
In the long run, Perl6 could be as influential as Perl Regular Expressions have been. Definitely something to watch.
2. JS files that get a certain number of uses get marked for compilation.
3. On browser startup, the marked files are recompiled into the binary.
4. The modules are pulled in when the browser detects an HTTP requested file matches an existing file.
MD5 hashing couldn't be used, due to collision vulnerabilities!
I guess the question is whether the browser's JITter is already as fast as compiling javascript into the binary.
"Node does not modify the JavaScript runtime. This is for the ECMA committee and V8 to decide. If they add coroutines (which they won't) then we will include it. If they add generators we will include them."
See Tim's thread, My Humble Coroutine Proposal (https://groups.google.com/forum/#!topic/nodejs/HJOyNMKLgB8). Warning: long.
So, you don't like javascript? Don't use it.
But you won't beat the control over program state offered by javascript -- not until computers understand their programmers well enough to reason about program state. We need better computers, better computer science, and better programmers -- that's all. Then we can replace NodeJS with something better.
Until then, NodeJS is almost certainly the most tasteful solution to the most common problems. I hope its replacement meets so high a standard.