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
$350 is about an hour and a half of work, at $215 per hour. That's chump change. Most significant conferences are about $300, such as ConvergeSE which happened just a couple weeks ago.
Dropbox knows that people will buy tickets because they believe in Dropbox, and then Dropbox will make it awesome. Then everyone will know that when you've got a company that does things right, you can trust them with a tiny percentage of a typical webshop's daily paycheck, which they already knew anyway. And if $350 seems like a lot per person, when you add up all the costs involved it's really not that much. Money adds up quickly when a conference is done right. Most conferences pay a full-time employee for months just to make sure that the wifi won't melt under the load of hundreds of conference goers. There are a huge number of things to think about and make sure that everything goes right.
I'm shocked at this thread. Utterly shocked. Someone else actually complained that the three letters DBX are already taken. Come on! Every possible three or four letter acronym is taken. This thread is crazy. There is nothing of value here, at all, period. Not sure what happened to HN here.
Over time it was so disappointing, though, that the system never went anywhere. My biggest takeaway was to not be such a programming language purist. Now I'm a javascript fan. It's not pure or perfect, but it's simple and it nails the important things. Plus for the foreseeable future it's the most widely supported computer language in existence. Simplicity and pragmatism are really key.
Of course, the reason they use "2.5 million per day" is to give you a classic Scrooge McDuck kind of visual, with a big semi trailer packed with money entering your palace every day.
However, I would just offer a quick point of advice. Don't spend keystrokes saying you might be down-voted for something. It's actually bolder to just say what you're going to say. When you reference downvoting, you stigmatize it and influence people not to do so. I would rather know if people are going to have a downvote reaction to my comment than shame them into not downvoting me. I've had the exact same tendency to observe "well I might get downvoted for this," but I think it's a tendency that should be resisted.
Apple fanboys insist that Android features, such as widgets, are unnecessary. Then they go crazy over iPad dashboard apps that weakly simulate Android functionality.
Note also that the broken English here is not the author, but it's Google Translate. The text has been machine translated from Russian. Also interesting that Google Translate is much more effective translating the mathematical portions than the other portions of the text. Another case of what people find hard computers find easy, and vice versa.
Also, here are some articles I found in my links list:
CSS Stress Tester Bookmarklet (Copy into a bookmarklet. Then it will tell you the rules that are causing the most lag.)
javascript:(function(d){var s=d.createElement('script');s.src='http://andy.edinborough.org/Demos/css-stress/stressTest.js?_... es=d.getElementsByTagName('script')[0];es.parentNode.insertBefore(s,es);var doit=function(){if(window.stressTest){stressTest.bookmarklet();}else{setTimeout(doit,100);}};doit();})(document);
Old but still relevant I think: http://www.stevesouders.com/blog/2009/06/18/simplifying-css-... Text makes CSS slow (don't render too much): https://news.ycombinator.com/item?id=2232212 In general, following good guidelines might help: https://github.com/csswizardry/CSS-Guidelines
I can't believe an app requires 8M RAM just for method names! That's 3% of my entire usable memory (what's left after Motorola Blur takes its share) -- just for the method names for a single app. Surely I must be misunderstanding what goes into that buffer. It's unimaginable to me that they really need such a vast amount of space. It's unimaginable that they really expect their app to work at all on an old phone without choking it to death.
If I grasp this correctly, printing just the method names would create a book double the size of the King James Version of the Bible. Maybe you are going to argue having so many methods is good programming practice, not bloat. But don't argue that you "support" a system when just the method names total around 3% of usable memory for that system. And there are a lot of devices with considerably less memory than what I've got.
Why don't you release a stripped down, "lite" version of the app that works on an Android 2 phone even if it has more than 5 applications installed? Some phones don't even allow uninstalling facebook. They are simply stuck with the bloat (I mean, good programming practices :-).
We like dull models. They're easier to reason about. Programs should
be boring dull things that solve problems in predictable ways. [1]
[1] The whole discussion is most instructive. https://groups.google.com/forum/?fromgroups=#!msg/nodejs/kxw...Of course, you may easily download a framework that makes foolish choices as a number of Rails developers have migrated to javascript :-p. Actually, I don't have a "thing" about Ruby or Rails developers, but some aspects of their mindset are very dangerous. The first time I heard that YAML could initialize objects from the serialization structure, I was absolutely shocked. How could that NOT be a disaster?
Take care. You're responsible for your code and its security. You're not playing a game. Your business is not a hackathon. Don't claim to offer "services" unless you are plan to be a servant of others. Servants don't code recklessly. You are the custodian of your clients' digital life and wellbeing. Choose projects run by grownups -- like izs and ry (the people who have run nodejs). Again, getting hacked is NOT okay.
By the way, if you want to learn how to run a project, subscribe to the nodejs-dev thread. That's a first-rate education in how to manage a large project with a lot of hype and growing pains. Watch and take notes.
The level of inefficiency and unused territory in the world is mindboggling. I think the national park system ties up one-third of land in the US -- land that's absolutely unused. If worst comes to worst, I'm guessing we will start cutting into that resource little by little. It would take many, many decades or centuries to exhaust all of that.
Some are speculating about needing to work less or not at all. I would argue that we WILL work less, only because we will have to spend more time in education. It seems like however much society & science advances, we still need people to sort things out and run the whole huge machine of society. For example, machines can't parse Mochizuki's conjectured proof of the ABC conjecture. That requires clever humans to wade through hundreds of pages of analysis, carefully inspecting for holes. It takes more clever humans to program clever machines.
The little work that we do becomes incredibly powerful, but most of our time is spent learning. We will learn as teams instead of as individuals, where each person takes a tiny wedge of the pie and learns to master it and learns to master the tools necessary to deal with the wedge. This already happens with scientific papers. New scientific papers are published by teams of old people, but almost never by young people. This pattern is going to spread from the hard sciences into every line of work, until everything operates like science. Construction, engineering, marketing design -- everything will be huge dollops of education to a small speck of actual application, but that speck will be incredibly powerful.
Now, if we eventually unlock a new frontier, like exploring other planets or underwater / underground cities, then we'll probably have a place for people who simply thirst for adventure. (So far information technology has been basically a place for adventure-seekers -- an immature discipline where you can get by without following the dictates of some elite, because even the elites do not fully understand this discipline yet.) The conditions those societies will experience will be extremely new and different, and may require new tools and new ways of making things happen. But for the most part, I see the (comfortable) person of the future on the one hand being a great generalist, able to switch directions when a position becomes unnecessary, and on the other hand a great specialist, learning everything there is to know about less and less, and that's what he actually lives off of.
What if there's a reversal? The whole thing may come crashing down, and we might have to start over. We would live in a bizarre world where life is about recycling all the astonishing things synthesized in a previous culture, instead of being about making new things at a blistering pace. We make more and more things that are better and better, and we're just throwing away astonishing amounts of stuff. Rummaging through garbage cans and land fills might be the work of the future, if the higher class (1%) were to collapse permanently. If there's no one to spearhead the increasingly difficult march to technology, it may become cheaper to reuse previous things instead of inventing new ones.
Of course, he might still type in his password even if he decides not to go through and submit the form, in which case his data is still compromised.
I agree that there are performance issues with Ruby implementations such as the MRI. That's really part and parcel of an immature implementation, that is, it hasn't received the millions of developer man hours spent fine-tuning it, such as the Java ecosystem has received. However, I would observe that it's still easy to get Java performance very wrong. It turns out that efficient GC is hard -- really, really hard.
However, I would note that Google changed the old search button into a "swipe up from bottom" approach for Android 4.1. This brings up Google Now + voice search. So there is some "swipe from edge" functionality.
For Ubuntu Phone, the functions of the different edges will take getting used to. Of course, power users will eat it up.
Getting off track, Apple design is simply not a monolithic, "zen" one-stroke entity. Apple design amalgamates understated hardware with loud, lickable user interfaces. To see my point, consider that Apple hardware is definitely NOT lickable, whereas software generally is. Historically this may be due to the dissonance between Forstall (software design) and Ive (engineering design).
(Feel free to shred me as I don't really know anything about Apple design.)
I would like to talk about one idea you brought up: the idea that the Christian Gospel involves some sort of coercion. In particular, the little story you told about God vs. the devil.
This is what the gospel says. "For God so loved the world, that He gave His only begotten son, that whoever believes in him would not perish but have everlasting life." John 3:16
We're sinking in quicksand. God reached out His hand to save us. But if we refuse, we will die. Does that make God a monster?
Indeed, if you refuse God's love, the consequences are not good. If you refuse my offer of a kidney transplant to you, the consequences are not good. Does that mean I'm raping you by offering to save your life?
Please do not blame God that there are people in hell. God doesn't use hell as an instrument of coercion. We sink into hell under the weight of our own evil. We put ourselves there. We wouldn't be happy in heaven, if we don't like God's rules here on earth.
But God loved us even though we could not repay him in the least. He is rich in mercy. God gave the world an unspeakably wonderful gift that we can never, ever repay. Jesus Christ took my hell upon himself. He took all the punishment I deserved on Himself. How can I repay that? That's the essence of unconditional love. And He offers this gift to you.
Christ is my brother, my friend. He died for me. He forgives my sins against Him and helps me every day with my pride and my bent toward sin. Do you realize this is not a game? He has seen what you wrote -- don't you think it hurts Him?
I'm genuinely confused why you insert such strong language in a thoughtful post about loving life and valuing the right things. If you disagree with the Gospel, feel free to say so. But why do you want to vilify the God I love, call Him "the devil," call Him a rapist? He is grieved by these remarks. I am grieved as well.
I will pray for you. You seem to be lashing out at God with the grief and difficulty you have experienced. That's an awful place to be in. I know from personal experience that my words are not able to help you, but God is able to help you. I hope that some day, you believe in Christ and come to understand that Christ is the way, the truth, and the life. No one can go to God the Father except through Him.
Apparently, they developed iteratively and failed to do "premature optimization." Fact is, hosting servers costs money, and developing optimized software costs money and time. The pirated copies are costing them money without giving them anything in return. On top of that, a lot of these people might have paid for the game if they had not been able to get it free.
As a game dev you are going to have an awful lot of things on your mind that are more important than optimizing a system that currently works. This is business reality. Obviously, this could have been an "excuse" to shutter a poorly-constructed game, but I totally believe that the load from copies freely obtained (against the developers' wishes) made their product untenable. All their blood, sweat, and tears, wasted.
I feel deeply about software piracy.
Piracy disrespects the software developers. The developers worked hard to produce something and you tell them that there code is worth $0.00. I'm extremely offended that people pirate code.
The key is that they asked for money and you told them no. It's one thing for someone to offer their software for free, it's another thing for someone to say, "I need money to develop this," and you tell them "No, your software isn't worth that." Maybe you didn't mean that. It's like slapping someone in the face and telling them that you really didn't mean it that way.
I'm absolutely shocked that comments in this thread insist that it's the responsibility of the developers to either throw up an authentication wall (think about the conversion losses!) or just handle thousands of people using their software for free. That's precious development time that they've spent on premature optimization when they could have built better features for paying customers.
I'll wager that 95% of the developers commenting here actually get paid for their code in some way, shape, or fashion. Why wouldn't you want to pay for someone else's code? Why do you have a kneejerk reaction when other people don't want to pay to use others' code?
I go out of my way to support free code if there's a donate button. Nearly every time I see a donate button I click it. I used Readability before their donations fell apart. I have a gittip account. I respect developers and the time it takes to create code, so I pay the price.
I assume the people reading this are like me. You also donate to open source projects and buy the paid version when possible, once you've tried the game. However, the rank and file of people who are pirating software probably do not.
Even though copying code is cheap, piracy takes a toll on the company: - It often takes away potential sales. - Pirated copies are often sub-par and can tarnish your brand. Some developers might not realize how important brand is, but just consider how many millions of dollars are spent to build brand for these companies. - In this case, pirating imposed an unbearable load on servers. They had to shutter the game.
I am all about open source and donate whenever possible. I totally understand that, for example, patents are just ridiculously overplayed in today's world. However, software piracy offends me deeply. I think it ought to offend other developers as well, but you are free to hold whatever opinion you like.
If you're interested, drop me a line at 1.800.GOAT.API and I will license my patent for your app.
[1] Cf. http://stackoverflow.com/questions/13248493/detect-ipad-mini... [2] Also relevant: http://xkcd.com/378/