Staying motivated is simple: don't work on boring shit.
That may sound like a shallow phrase, but I've been there. You've convinced yourself that you're working on the most awesome thing in the world. You keep thinking that you're supposed to be motivated, because what you're doing is great. But deep down, you know that you'd rather do something else.
At that point it usually boils down to rewards. Is the reward worth continuing?
If the answer is yes, go on. Shouldn't be a problem.
If the answer is no, you know why you aren't motivated. Drop it, look for something else.
But it's not that simple. Not that simple to drop something when it's 70% complete, not easy to find something new that won't also become boring at 70%, and not easy to start from scratch.
Plus, with every failure, you lose a little bit of trust in yourself and belief that you can get things done.
There's always a point where the motivation is just gone and you have to push through somehow, and if you can't get this thing done, chances are that you won't be able to do it the second or third time, either ...
The problem is not Javascript per se. Personally, I like a good webapp.
What annoys me is the tendency of Javascript guys to rebuild every damn application there is as a webapp, and rave about it like it's the best thing ever.
Javascript has become their hammer, and the whole world looks like it needs a good pounding.
How about not autoplaying the video as soon as I open the page? I frequently open multiple pages in background tabs and Youtube makes this rather annoying.
One of the main reasons I come to HN is to learn how other people feel about certain things, predominantly from the comments section. Else it's just me in my cave.
It's obvious what point the slides were making.
The important part is that it said enough to inspire discussion and that it's qualified by its recency (posted last month) and by the experience of the person that gave the talk (front-end guy at Box).
I agree, but I definitely see the grandparent's point. These slide decks are annoying as hell. They're inconvenient for quoting, reading on-the-go, and they can leave out a whole lot of context. This is a trend that really needs to go.
I'm from Germany, we don't have Netflix here. We'll probably never going to have it.
When I want to (legally) watch a movie, I have to rent the DVD for 4 EUR at my local video store.
We have a local "alternative" called Lovefilm, where you can watch some movies from 5 years ago, but only the bad German synchronised version.
In Germany, Netflix is like some utopian fairyland.
So... you can watch all the movies/shows you want for a laughably low monthly price. And now you don't even need that crappy Silverlight plugin anymore.
I've tried fish a few years ago and wasn't all that impressed with the features.
That said, the new version is just ace! I gave it 30 minutes and it basically does everything I do with zsh right now. All that with about 5% of the configuration effort I put into zsh. Plus, it's so much faster than zsh.
I'll give fish a go as my main shell. Let's see were this goes.
Felt the same. Fish worked out of the box, but left me unimpressed about its abilities compared to zsh (well, I'd give it the same score as to zsh) until I realised I hadn't configured anything beyond generating man-completion files. I'll leave fish lying around so I can alt-tab to it and check it from time to time
Have you ever tried to install and setup PHP on a fresh server? It's almost as painful as writing code in PHP.
The article is talking about managed hosting, were that might still be true (Admins are incredibly conservative and stubborn individuals).
But for everything else? PHP doesn't work 'out of the box'. It's due to the work of a poor admin somewhere that you can just upload your crap and it runs.
In contrast, I can install and setup a complete Ruby server in about 15 minutes.
whatever the packages are - there's about 4-5 core packages (yum/apt/whatever) or other packages like xampp that set up a default environment in about 5 minutes on most modern systems.
There's certainly a lot of configuration that can be done, but getting a LAMP system set up to allow PHP/MySQL to work is trivial these days compared to 2000.
Cue the puppet and chef supporters who would suggest scripted recipes for everything anyway. :)
And since most people in this world use managed hosting for their website projects thats the right thing to compare with.
Also you have MAMP which is as easy as it comes for setting up a PHP/mysql environment on your computer.
But the strength of PHP goes far beyond this simple point.
For developers it's very very simple to get started. The difference between writing a hello world app and a crm app isn't that big. Weaving HTML and PHP together with JavaScript, CSS, JS easy to learn with PHP.
I wouldn't even know where to start in Ruby or Python. Just too many dependencies before you can even get started.
So yes it's by any metrics it matter true.
Take it from someone who had to teach himself how to do it and have tried to get started with several languages.
He could be implying shared hosting is the most common method of hosting. In these cases, they all tend to come pre-configured with a LAMP environment. No setup necessary for CLI scripts.
From scratch, everything is easy to install. I wouldn't say Ruby is any easier to install and setup than PHP. You're talking about installing something like Phusion Passenger on top of Apache. A LAMP stack takes as long as it takes to run `apt-get` or `yum install`. By no means is it 15 minutes; I'd say 5 to 10 with minor Apache configuration and a VirtualHost entry.
