I appreciate the fact that this isn't some biased "vim is God" type post. It has good points too about how editors do tend to follow the Emacs style where "command x does y". To me, that works fine because most of the commands you run will turn into muscle memory and never ends up being a problem. However, there is definitely a lot of use cases with VIM's way by being able to build up commands. It definitely cuts down the learning curve. Honestly, I'm not terribly psyched about Atom. It doesn't appear to offer anything knew other than instead of being extensible through VIM script, Emacs Lisp, or Python, it's extensible via Coffeescript.
The way I've typically worked is static pages are allowed to be done in IB, but everything else is done in code. The reasoning is that doing things in code makes for much easier diffs and merges and also allows you to easily edit code in things outside of XCode (I personally prefer AppCode). Doing things in code makes thing a lot more explicit and can be setup so that the view code doesn't have to interfere and floor the view controller's code. The main problem is there are lots of things you can do in code that IB can't do, but not much (if anything) the other way around. You should always be able to write your views using pure code.
It sounds like you were kind of against it from the start in which case you would never end up liking it. There is a huge learning curve and, to make the most of it, you really do need to learn Emacs Lisp. As for keybindings, you are free to remap them to whatever you want. Sublime's keybindings aren't exactly normal either and go against a lot of the standard keys for operating systems (I'm basing that off of Mac since that's what I use). I don't find them bad ergonomically, especially after setting the option key to be "meta". I actually prefer the Emac's keys in other applications like IntelliJ and AppCode.
I'd have a hard time using Emacs for a large project, especially one that is contributed to by many different people. IDE's just make life so much easier. The people who disagree with that statement are typically the Emacs (or VIM) gurus who have customized it so much that they would probably die if they had to use a stock installation.
Modes definitely add complication, but again, that's why Emacs is so customizable. It takes time, but you can set things up to where it's the best experience possible.
Hah, that basically does some it up. This post isn't very front page worthy as it has zero content with the exception of emacs being more extensible. The author should have given some specific examples about which things Emacs can do that others like Sublime (and others) can't. In the end, use whatever editor makes you the most productive.
I agree completely. Its use case is highly specialized and all it does is make a bunch of code nicely split up into methods and crams it into fewer methods with a ton of blocks. Even the example of "before" and "after" on the github page shows that how complicated it makes things look.
You'll have to redefine the properties in the subclass's class and specify @dynamic so that it knows the properties were synthesized in the parent class
Which is fine. But you're specifically saying that you are building Git to learn how it works. All I'm saying is, based on your wording, you need a disclaimer that this is not how Git works internally. You can already get the gist from a lot of the comments that they think they now know how Git works after reading this post.
I appreciate the effort and think it's a great idea to implement something your own way, I'm just trying to point out that you're saying this is how THE Git works, which it isn't. Nice write up as a whole though
I 100% agree. It's always great to try to implement complicated things, but it misses the point if what you're implementing is nothing like the original system. You aren't learning how Git works if you do it that way are instead just mimicking API names
So I've never used Evernote before, but after reading this article I decided to try it out since I know a lot of people who swear buy it. My first time user experience was awful... I immediately started creating test notebooks, test notes, etc just to get a feel for how it worked. Within seconds the app was freezing on me every time I tried to delete something (this was on a brand new iPad Air). I had to either rotate the device or put the app into the background in order to unfreeze it. This is a common scenario and I can't believe there isn't quality control for that. I'm a developer and I understand not having time for edge cases...but freezing on delete? I can repro it 100% of the time
Yeah I think most people just see the offer and get too excited, especially if it's their only offer. It's a real shame because culture plays such a huge part in how happy you will be at a place. It wastes both the company's time and the new hire's time to join, hate the environment, and then quit a few months later
There are a number of good questions in here. It's too bad that companies don't send out these types of questions with the answers to them to people coming in for an interview. It would be hard to choose just a few to ask, especially since you as the interviewee doesn't have a lot of time to ask questions themselves.
Kudos for learning to program at such a young age. It'll give you a leg up when you decide to get a job or start a company and need funding. However, I'd suggest taking some time and working on the quality and originality of the apps over the sheer number of apps that you can churn out in a year. A number of the apps seem almost identical. You want to get known for high quality apps and not as someone who just fills the app store with small apps.
A contributor is supposed to be following the coding guidelines of the project from the start. If they don't bother to do that, they absolutely should be rejected. Why is it hard to follow a consistent style?
I'm always curious why people remap the caps lock to be control. For me, extending my pinky to the caps lock makes the second key press hard. Like quitting emacs would be harder for me. I should make command the meta key though. That seems super beneficial
I agree. This post isn't the best explanation and is riddled with grammatical errors that caused me to reread sentences multiple times. Regardless of the age of the author, if you put up a blog post that is supposed to explain a concept to other people, it needs to be well thought out and proof read.
Mike Ash is an excellent example of how to write blog posts about how things work
It was more of an ironical statement, however the legality you brought up is definitely interesting. At least in California it's not legal to record conversations without the entire party's consent (except in rare circumstances). A number of other states have the same laws but I'm not sure if it's completely nation wide.
The main issues are that gestures are not consistent across apps. So if I teacher her pinch gesture in one app, it might not zoom in another. If it doesn't do anything, she is most likely to get frustrated because to her, pinch gestures should zoom. I personally love gestures, but an interface that revolves around gestures might not be good for people who are already a bit afraid of technology
In my experience with my own grandmother, gesture driven interfaces are significantly harder for older people to learn. Think about safari where you have double tap to zoom in. My grandmother does a bit of a hesitant tap when I give her my iPad to play games which sometimes leads to an accidental double tap. It would be disorienting to have it zoom in to a random spot.
I was going to say the same thing. Allow screen sharing for his user so that he can easily jump in and do updates or fix problems.
I'd also add in disabling all the function key buttons, especially Dashboard since the author was correct in assuming that any button/gesture that changes the screen you are looking at will only lead to mass confusion.
Oh, and lock the dock so that they can't easily move, remove, or add new things to the dock.
If you're going to post a giant list like this without any screens or up-to-date links, at least add some bullet points about positive and negative things for each app or something. Otherwise I might as well just search "hacker news" in my iPhone's app store (or just Google).