This is the main reason it won't happen; app store review is one of the key parts of Apple's positioning.
986 karma · joined December 12, 2010
This is the main reason it won't happen; app store review is one of the key parts of Apple's positioning.
But this strategy for me begs an important question: why the <bleep> is it even possible to write directly to memory over an fd? I get that "everything is a file", sure, but you've already got ptrace for insane use cases that require trashing another other process's memory (i.e. a dev toolchain).
I've been twiddling bits in C(++) almost every day for over a decade and I've never once felt the need for such a feature, except when theorizing about exploits. Alas.
[1] http://www.cs.cmu.edu/~dst/DeCSS/Gallery/decss-haiku.txt
...Yeah, I don't really get it either.
Of course it's technically possible, and Dropbox could probably be compelled by one law or another to make it happen. The question isn't "could it happen", but "would it happen".
Heh, this is pretty much the epitome of hacking: needlessly complicated, ultimately pointless, but still awesome, clever and inspiring.
I don't know how this project is doing it, but adding a buffering/sharding layer for large files would alleviate this problem at the cost of worse delta compression (among other things).
That said, I still don't think git is necessarily the best platform to base a Dropbox alternative upon, but the commit resource hogging is very fixable.
Of course, this is terrible advice to take at face value and I won't suggest that you should go become a C++ master for great good.
But I stand by my theory that it really doesn't matter how you approach the learning. If you work on challenging problems in any area of computing, you'll realize that most of this stuff is just different people solving the same basic problems with different terminology.
Not really... Boycotting GoDaddy made perfect sense: they are an internet company supporting legislation that would ruin the internet. Presumably they knew perfectly well what they were doing (considering this is the core of their business) and they needed to be shown that the world doesn't agree that it's okay.
Whereas I doubt L'Oreal executives knew or cared about this bill beyond someone promising them it would help their business to sign on the dotted line. Boycotting them would be an arbitrary self-righteous waste of time that could be spent pestering your representative -- which actually has a chance of making a difference.
If you haven't done it already, I'd recommend a blog post about this, for everyone's sake. The only way I dodged the GoDaddy bullet was reading about nonsense like this.
And for what it's worth, thank you for being the example or all of us for why these clowns don't deserve our money.
If input processing is complicated enough to have annoying syntax, it gets its own special-purpose class (if not a separate module) written in the language of the domain. Frankly there's probably several things that look like Sugarless in the codebase already. But I consider this a Good Thing:
If I want to change the way operations distribute over an Input object, I can do it in an arbitrary, appropriate way. If I'm using someone else's convenience library, I'm limited to what the library author decided I should be able to do. This happens surprisingly often in my use case and more often than not it means going back to throw away the library in question, and reimplementing what I needed in the first place.
This isn't actually a comment on Sugarless itself -- I haven't gone out and used it. But I'm quite jaded by all of the times I've had to deep dive into other people's 'convenient' JS library when it was subtly broken (or wasn't working as I'd like) to the point that I try to avoid them as best as I can.
This happened with iPhone, cloud hosting, touch/tablet OS's; the list is endless. The only surprising thing is it took them this long to realize that Live Messenger needed to get onboard with Jabber if it's going to survive.
They're not stealing from kids. Kids don't have anything worth stealing. They are using psychology to entice kids to spend their parents' money when they're not looking; that's different.
> True, people who actually participate in penny auctions probably have IQs worse than 7 yr olds.
This is an outrageous statement and I'm sure you realize this. These strategies are profitable precisely because you don't have to be ridiculously stupid to be fooled. It's the same reason casinos work.
Everything these companies are doing is legal and whether we morally agree or not, this is how the business game is played: you find (hopefully legal) ways to get people to give you money.
If one of those ways is enticing people to voluntarily agree to pay app store fees that they incur through their use, and then enticing them (or someone else on their behalf) to incur those fees, you've won the business game and you deserve the profits. Let customers vote with their money elsewhere if they disagree. Welcome to the free market.
Every time you walk into a store, you are being manipulated with psychological tricks centuries in the making. And any parent has paid far more for useless stuff they were psychologically coaxed into getting than their kids will ever spend on the app store.
Yet whenever children are involved, the slightest sign of "sleaze" triggers rage -- a deliciously ironic example of the same psychology these business people use to get your money :).
I'm no PHP guy, but looks like server's getting a 500 on your REST query. The query itself works nicely from my browser though:
<Edit: query string apparently gets munged here, can't paste it...>
Lord help you if you try to write a perfectly conforming compiler for C++ (has it ever been done?), and the U.S. legal system is at least an order of magnitude more complex than that.
Of course if you've been using SQL for years then this probably sounds difficult in comparison. Except what if you're a JS guy with zero SQL experience?
"Ok, it's a database. How do I query it?"
"You learn this completely new language and dynamically compile your questions down to it, but you have to be really careful because the process is notorious for being a first-class attack vector."
"Did you just tell me to go fuck myself?"
I'm not trying to say anything about the merits of SQL. I'm just pointing out that it's a matter of perspective.
But it turns into write-only code pretty fast when you have tons of callbacks flying around for highly interactive elements.
Of course, this isn't a logical argument. But lawmaking isn't fundamentally driven by logic these days anyway.
Twitter defined themselves by trading features and verbosity for accessibility and rapid consumption. And they seem to be doing doing pretty well with that.
At the very least, it will be interesting to see how this pivot plays out for them.
Then, working at a startup taught me that it's not black and white. Several quotes come to mind, but Voltaire's is my favorite:
"The perfect is the enemy of the good."
Although having a more modern browser will help, this is the kind of stuff that only better education can truly protect against.
Because the alternative is massive systemic bias.
This issue has been discussed to death and I won't argue anything here, but the point is that having a thick coat of process encourages a _certain kind_ of editor to participate in Wikipedia. Thus, proponents claim, the largest reference work on the internet is biased, in a very nonobvious way.
This wouldn't be an issue if Wikipedia was some niche forum where "facts" are taken for granted to be opinions. But for (what I suspect is) the majority of people these days, Wikipedia is the de facto source of truth. Therein the problem lies.
Not to say that I agree with this practice (I don't), but someone deliberately implemented this, and there's a good business case for it.
The privacy implications are unfortunate, but what else are we to expect from Facebook these days?
The other day I was stuck on a system with only a C++ (03) compiler, and it was a truly crippling experience without lambdas and the new STL.
Anecdotes aren't worth much, sure, but I find it difficult to disagree with this article.
I don't mean you should start solving equations in your spare time. I just mean find a concrete problem that you're motivated to solve (i.e. something fun), and then solve it.
Maybe you think AI is cool, so try to figure out what it takes to make an interactive chat with the computer (easier than it sounds). Maybe you think computer graphics are cool, so figure out how to make a web page that has a ball bounce when you click it.
Above all, make the path interesting and fun for yourself. You'll get a lot further that way than you will by reading books or watching screencasts that brainwash you into the author's (or the programming language's) way of thinking. Most of programming is a transferable skill set anyway.
That's what I mean by becoming "technical". Just make something you think would be cool, and when you're done, make something cooler.
And if you don't know where to start, just remember this: Google is your friend. Search engines will point you to plenty of material you can copy-paste, and will answer 99% of coding questions you could possibly have. After 15 years of coding, there's still not a day that passes when I don't look up how to do something.