shortstuffsushi

I could go either way. I've used both where I work, and I haven't found that one works particularly better than the other. In most cases, inline is sufficient, you can get the gist of a change (especially a one line change) just looking at them inline instead of a full side by side window. In the case of a real big, messy, merge-y diff, you're gonna have a rough time with either style.

The analogy to me seems similar to that of programmers and compilers. I want to write programs to do xyz, but I don't particularly care to know the lower-level to machine level implementation. Instead, I know a roughly-english set of instructions to tell the compiler what I want to do, and it takes care of the rest for me.

Could it not be possible to take this even further, to the point where I say "I want to do ..." and all of the "code," be it high or low level is generated for me.

I realize making something capable of this level of abstraction would be incredibly difficult, but it would certainly be fun to try.

Came to say the same thing. "Innocent until proven guilty" when it comes to others' codebases. If you can strip an issue down to the bare minimum, and then prove that the issue is not within your own code, then it's time to start digging elsewhere. Rarely is that the right place to start, though.

ExtJS/Sencha Touch has been the framework of choice where I work. We complain about it a lot, it has a lot of bloat for probably 90% of use cases, a number of bugs, an extremely poor forum community (I'm looking at you, Mitchell Simoens), and you have to pay for it, but...

Well, I was going to say something good about it, but nothing comes to mind. To be fair, we've built some pretty complex applications on it, so clearly it can be made to work. It just doesn't feel natural, and you have to work around a lot of issues.

For some of the mobile development, we evaluated Angular, Knockout, and even briefly Meteor, but there was a desire for pre-canned view components available in the framework instead of writing HTML snippets/templates. It's too bad, because I really liked Angular and Ember (I didn't personally look at Meteor). I'm hoping to be able to use one of these on future projects.

Wow. That's actually something that hadn't really struck me until reading this comment. While there is development to be done in ever project still, the upfront amount is growing smaller and smaller with the (P|I|S)aaS techs available to companies. A lot of it does really come down to making the front end of a product.

The company I'm working for suffers from the same problem, but it's compounded by the fact that our IT is now almost 100% offshore. This means on top of having to wait for new VMs, we also have to fight a language barrier to explain what we need and why.

As a developer who has to wait weeks for instances that I could spin up myself in a day or less, and instead has to wait for literal weeks, I really don't see how this cuts costs. Perhaps, as you mentioned, it makes monitoring the systems easy, but for internal instances that have no internet access, how valuable is this?

I feel exactly the same way. I always end up cursing Atlassian's software (specifically Jira and Confluence), but when I look for an alternative (primarily for Jira), I can't ever find anything that does it quite as well or attractively as Jira. Even with its problems, it still does what I want, and does it well. I would, however, love to see something try to compete with it. There are a lot of decent alternatives, but it would be cool to see a bit more competition.

Care to comment down voters? If you're voting because of my rust comment, maybe read the part where I said "not sure, haven't read much about it."

If you vote because you think C is unsafe, carry on. You're wrong, though.

I think Servo's "safety" is ultimately due to the fact that it's built on Rust. Rust, however, seems to be ultimately built on C, unless I'm mistaken (having a hard time telling by briefly glancing through their Github, but it looks that way).

My point was that it's not a C specific problem, though. Most browsers are in fact built on C, I agree. This is due primarily to the speed and performance of the language that is harder to reach with other languages.

It is definitely a more difficult language to write, as it is much more "raw," but that doesn't make it inherently unsafe to use, or any more unsafe than other languages.

While some of the vectors you've mentioned could potentially be exploitable, blaming a "very unsafe programming language," isn't really a good explanation. These issues could occur in any program and any programming language -- it's not a problem specific to C languages.

That actually brings an interesting question to mind. As someone who hasn't forked anyone's repository, I am not familiar with the licensing expectations of doing so. Obviously the code you've forked belonged to someone else, but at what point can you say "this is now my creation," or at least, "I own modifications to my fork of this guy's work?"

How do you fork and re-license appropriately?

We're experiencing this quite a bit, and have only been in development several weeks. After writing native for so long, I just feel so dirty having to create a plugin for every little thing I need, and the code becomes callback hell since plugin execution is asynchronous...

I wasn't sure if it was Xamarin or another framework that was ultimately using Cordova underneath. After reviewing their docs a bit more, it appears Xamarin was not the framework where this was the case.

We hadn't, but as one of the other comments mentioned, that seems to be game-development focused, which is unfortunately not what I'm working on. I'll keep it in mind for side projects, though.

The company I work for recently decided to develop some cross-platform apps. After researching a few different things, we decided Cordova (Phonegap, but not branded) best fit our needs.

Aside from Titanium, we also looked at MonoTouch[0] and Xamarin[1], which I believe (didn't completely read through) is built on both Cordova and Mono.

If you were building from scratch, maybe another one of those would make sense for you. We are working within an existing project (mixed native and webview), and Cordova seemed to best fit our requirements there.

[0] http://www.mono-project.com/Main_Page [1] https://xamarin.com/

So something along the lines of tracking incoming requests, then doing a DNS lookup on the incoming IP? Isn't that something that something like Google Analytics could do for you? And in that case, would this be more for people who are avoiding GA?

Out of curiosity, what are you doing that requires that many IP lookups?

Pun intended?

This is actually really funny to me. I got an email from them a week ago telling me that my "auto billing renewal" had failed because my card expired.

I checked "don't automatically renew" when I first signed up.

I removed my credit card a month ago, when I realized it had been saved.

Thanks for the feedback. It's interesting you mention CoC specifically, as my unwillingness to pay for the in game currency is what had made me think to ask this question :)

That's fair. I actually had a similar experience with our publications team replacing a word across multiple pages on multiple spaces of our wiki. I can hardly imagine not immediately seeking/knowing to try to seek a better solution.

>> On average, it took 20 to 30 minutes to purge a month’s worth of posts. After about 12 hours of hand-deleting stories, I decided it was time to automate.

12 hours of deleting by hand? I don't know if I could even do 20-30 minutes worth without seeking a tool.

That's dedication, or something.

Closed as not a real question.

150 question upvotes.

I agree with that. Whenever I use the site, the 'description' from "Whose Line is it Anyway?" plays in my head.[0] However, it's the same as any website where there is a "karma" system (like this one for instance ;) ). It feel good getting points, it feels bad losing points. It feels good knowing you have tons, and are in the "Top x% of answerers" or whatever.

Do I think that's necessarily the right way to get people to come to your site and answer programming questions? Maybe not (no, I don't really), but it certainly does keep people coming back to the site. That and the fact that it's probably the biggest answer repository on the net.

Oh, and here's an upvote for you to show no hard feelings. I believe your general statement is correct, I'm just not sure that's what the author is going for.

[0]http://www.youtube.com/watch?v=9KAGwNtI26w

That actually seems to be just the opposite of what he was saying. He stated that he believes this mechanism is broken, to the point that after two years of inactivity, the votes he receives his old answers have kept him in the top 3% of scorers.

He's not looking for votes, he's saying it's silly how trivial it is to get them, and also how many points he gets off of a simple LMGTFY answer (your quote), vs how few he gets off a well thought out and explained one (the kernel answer, I believe).

I disagree pretty fundamentally with your first line. "Having a backbone" is in no way equivalent to being reasonable when someone (or an organization) makes a mistake.

> If you're fine with someone going into your account and pulling money at will, all the power to you

If you've got a Google AdMob, you've already done this, right? You've given them the ability to push/pull from your account, and signed whatever agreement about "we're not responsible for xyz."

I don't have an account, but presumably there was some line in there about not being liable for mischarges, or something along those lines.

This is exactly what I have wrong with the parent to this post. "Dispute for the principle of it," so that some lawyer(s) can make big money off a mistake Google made. How is that helpful to anyone (except the lawyers)? It ends up making everyone more reserved, or even killing a company off (probably not in the case of Google).

I reiterate, if it was a major amount of money, I can see that. Pursuing actions against someone who made a mistake just seems unnecessary. They've already publicly admitted they screwed something up. Someone on their end probably got into major trouble, if not fired, for said mistake.

The instinct to say, "you screwed up and now you're going to pay" baffles me every time. Why does everyone feel entitled to seek compensation for inconvenience? When did that become ok?

I see this on here constantly, and whenever it's pointed out, it's immediately down voted. And yeah, I'm expecting this to get down voted, again.

> I would dispute it based on principle.

What principle exactly? You had an accident that (minimally) affected me, so I'm going to charge you for it? I could understand if it was something major, but for the hypothetical dollar, really?

To all the Android users -- isn't this only an iPhone issue? The author seemed to mention it coming from the original, and persisting to the latest, but doesn't mention it affecting the Android (unless it has been edited).