HNHacker News
TopNewBestAskShowJobs

drewcrawford

4,834 karma · joined June 13, 2008

AI tooling and systems/SDK engineer · Rust, WebAssembly, Swift/Apple platforms · wasm-bindgen contributor · building AI Bot Mafia (botmafia.games) · sealedabstract.com · github.com/drewcrawford
submissionscomments
drewcrawford··on Hudson's Lost Mario Trilogy (2010)
I owned one of these. But, if memory serves, I think it was a DOS edition. Maybe a port? It came either on a 3.5" or 5.25" floppy, and the packaging was pretty utilitarian--black text on white, if memory serves.

At the time I figured it was just some unauthorized programmer trying to make a buck on Nintendo's back. It never occurred to me that Nintendo would license the IP.

drewcrawford··on Open Source and the Challenge of Making Money
The problem is that for-pay software that gives you some freedoms manages to piss off everybody. It's not "open source". It's not "free software". It can be characterized as trying to astroturf your way into free goodwill. And you have minimal real protection against someone cloning your software.

I am currently trying to build a product on this model, because I think it is pragmatic. Not sure how it will work out.

drewcrawford··on Popcorntime-desktop repository unavailable due to DMCA takedown
> Just because one of the effects (even the main effect) of the software is facilitating copyright violations, doesn't mean that the code itself is violating any copyright.

I'm not a lawyer, but as far as what the law is currently, I think you are wrong.

The takedown notice cites MGM vs Grokster [0] which held as follows:

> One who distributes a device with the object of promoting its use to infringe copyright, as shown by clear expression or other affirmative steps taken to foster infringement, going beyond mere distribution with knowledge of third-party action, is liable for the resulting acts of infringement by third parties using the device, regardless of the device’s lawful uses. Pp. 10—24.

That case used 3 elements to determine whether the defendant had "clear expression or other affirmative steps taken to foster infringement":

1. That defendant "aim[ed] to satisfy a known source of demand for copyright infringement"

2. Did not develop filtering tools

3. That defendants had a motive (advertising revenue) to increase the use of the software

From my armchair, elements 1 and 2 seem identical to MGM vs Grokster. Popcorn Time has a plausible argument on the third element, but who knows really. This is a question to put before a federal judge.

[0] http://www.law.cornell.edu/supct/html/04-480.ZS.html

drewcrawford··on Amazon Cognito
I'm working on this. Email in profile.
drewcrawford··on EU's right to be forgotten: Guardian articles have been hidden by Google
Maybe you can convince of something.

Most people from the next generation use Facebook. They're not ignorant of how they use it--they use their privacy settings to hide posts from the public.

However Facebook's ToS says [0] Facebook may use any information you share with them "to protect Facebook's or others' rights or property". So hypothetically, if Facebook felt some policy of a presidential candidate threatened "Facebook's rights", they would be in the clear, legally speaking, to publish those photos of you smoking a joint at 18.

So what is the difference exactly between Facebook publishing a photo of a joint and an old Guardian article? They are both expressions of speech. They are both things that the public arguably has a right to know. They are both cases where there is no legal impediment to the speech--other than, in your words, the "right to censor criticism or true facts about yourself." On what basis can we say one is allowed and not the other? I cannot generate a reason for analyzing these situations differently, although I very much want to. I suggest we have to either allow both, or forbid both.

This analysis would suggest that free speech and privacy have a very fundamental conflict--that the gain of one comes at the expense of the other. Increasingly, the right to privacy is really the right to prevent others from publishing information about you that they lawfully and ordinarily collect. I grow increasingly doubtful that we can achieve both outcomes--I think at some point we will have to choose sides.

[0] https://www.facebook.com/about/privacy/your-info#howweuse

drewcrawford··on The Case for Message Passing in Swift
> You could keep some of these optimizations if Swift's message-passing mechanism preserved type information.

Type information isn't what makes this fast. What makes it fast is the very guarantee that dynamic dispatch breaks: knowing, for a certainty, where the function will land.

> As I mentioned, app extensions may be a step towards a more workable solution, but today, the ability to add PGP to mail using method swizzling is important to thousands of Mail.app users.

A fast Mail app is important to millions of Mail users.

If PGP is important then one interim possibility is to write your own mail client. That requires extra work, but one of the hallmarks of important problems is that we are willing to do extra work to solve them.

drewcrawford··on The Case for Message Passing in Swift
So I've actually been doing a lot of thinking about this, because I have a use case that doesn't work as well as in Swift.

You have some problems. The first problem you have, is that static compilation provides so many routes for cross-applicaton optimization that this is one of the major ways that Swift can be faster than its predecessors. For example, if you have this

    func min<T: Comparable>(x: T, y: T) -> T {  //Generic functions
        if x < y {
            return y
        
        return x
    }

    min(3,5)

    min(5.0,2.0)
The compiler has a lot of possibilities. For example it could translate this function very literally, producing the generic min function that you wrote. It could realize that you only use this for floats and ints, and emit 2 particular specializations of the min function. It could specialize the float function and use the generic function for ints, or vice versa. Next, it could inline any of these, none of them, or some of them. Finally it could do three different things depending on if you're x86-64, armv7s, or arm64.

I have no idea what the right thing to do is in this situation, but having all those possibilities gives the compiler a better chance of producing faster code. When you introduce message passing, you basically forbid all of those optimizations, because now the function might be swizzled, go pass a "minX:Y:" string to objcMsgSend to find out what pointer we should jump to today.

Swift already does have a way to opt-in to message passing, it's called the @objc flag (and performSelector:). It works fine, but it's extra work to opt into it and use it. But, I don't think that's bad given that it disables so many useful optimizations.

What may be bad is that the name "@objc" is a dead giveaway that this is a feature with a deprecation date. So I think we need some other, reflectionish system going forward.

For mocks one idea would be to selectively turn on message-passing as the dispatch method at the compiler level. So you could compile your application for unit testing with a "-fmessage-passing" like we have "-fobjc-no-arc" and get all the dynamism in debug builds and turn them off for release builds (or not, as the case may be).

For everyday power programming I think the answer is a lot simpler: functions are first-class objects in Swift, so just take your functions, put them in a dictionary somewhere and implement your own run-time dispatch. Having done this, I can say with certainty that there are some ways the language could improve this use case but it is possible, and if you are Chris Espinosa wrestling a bit with the type system is not a problem.

Things are tricky when you don't have the source code, but here again I see a reflection-ish API as being the key. I expect at some point we will be able to enumerate other classes' public methods, and dynamically dispatch into them, and that is certainly a missing feature with valid use cases.

Finally, I fundamentally and strongly disagree with Michael about method swizzling and OSX extensibility. Adding PGP to Mail via hooking functions sounds like an incredibly deranged idea. The suggestion that programs should cooperate with a badly-misguided reverse engineering effort by disabling optimizations that make the program faster for the other 99% is just insane. The way to approach this is to build new kinds of extensions that provide known, safe, documented extension entrypoints for hooking arbitrary code. Yes that is more work, and yes it requires actually talking with people and convincing them of your point of view, but so do most things.

drewcrawford··on But why can't I send people their passwords?
I think this is easier than it sounds. To a layman, when they type in their password, they are not thinking about how it would be implemented. The idea that "oh, somebody is doing a string compare against a password in the database" is not something that would enter their mind. That is baggage that software developers may have, but ordinary people have not been primed in that way.

Ordinary people are going to be thinking about a key in a lock. Does the lock on your house store the key inside? Maybe in some kind of information-theoretic sense but in the ordinary meaning of the word, no, it has a representation (that may not even be sufficiently specific to recover your key exactly). And if you lose your key you don't break into the lock to recover it--you call a locksmith to replace the lock, and get new keys.

That right there is an intuitive understanding of both hashing and good security principles that goes surprisingly far.

drewcrawford··on Literally worse than EA
Well I'm no lawyer, but one legal theory you could argue is the one from MAI vs Peak. This is the one that holds that loading a computer program into ram for running is a copy that requires permission from the copyright holder. Therefore one would argue that by running this program, they ratified the EULA, or else they blatantly committed copyright infringement, which is probably worse than simple breach of contract.

I know there are lawyers who seem to argue otherwise, for example the GPL states "You are not required to accept this license to receive or run a copy of the program". But I don't know if that statement has any legal basis in general, or if it's just the FSF granting permission to run covered software without accepting the GPL. As far as the US goes, I think it's the latter, but it may be different in other jurisdictions.

I'm not a lawyer, please go hire someone if you really need to know.

drewcrawford··on Only Apple
I don't think you understand HomeKit, or Apple's view of it.

What's important to Apple is that you have a good user experience. As this applies to HomeKit, there are a few important requirements: battery life, and security/privacy. Keep in mind we are in the early days of home automation, and all it takes is one bad story about the hacker adjusting your thermostat to sour the market.

The only way to achieve those objectives is to exercise some control over hardware manufacturers. Sure, you may lose some compatibility this way, but that is infinitely preferable to a security risk in a poorly-understood environment without good security hygiene traditions. As a software developer who works with Bluetooth hardware, the Apple MFI certification process is the only hardware cert for home automation I am aware of. So even if I was an Android dev, I would prefer to purchase hardware that went through MFI as it gives me a basic level of confidence that somebody signed off on this.

Secondly HK explicitly includes measures for compatibility, including a type of "bridge device" that can translate between HK and a manufacturer's proprietary (or open, as the case may be) format.

Thirdly you have to consider HK's target audience. One of the headline features inside the HK Apis is the support for multiple homes. The people who are early adopters of HK in the near future are not hackers sharing an apartment. It's the Tim Cooks of the world where throwing out the existing automation hardware is not of any concern.

Sure, at some point it will become ubiquitous, and as the market matures news stories about the dangerous thermostat hackers will be less of a concern. But that's not this release, and it may not be within the next five years. That's more than enough time to create HK bridges and poly lingual lightbulbs that speak multiple APIs and so on.

drewcrawford··on Everything you need to know about cryptography in 1 hour (2010) [pdf]
Would be interested in hearing more detail about your objections to both Poly1305 and ECC.
drewcrawford··on Clearing the Air
For context, the video they are referring to is here: https://www.youtube.com/watch?v=H901KdXgHs4

This really is a textbook case of how not to respond to criticism. There's a little bit of everything. You've got the incredibly bad misunderstanding of fair use:

> One unscrupulous individual even took our viral Solar Freakin' Roadways video (by volunteer Michael Naphan) without our permission, and has used it to create another video, in which he has embedded deliberately misleading information. He is even making money by placing advertising on it to make a profit!

The paranoid delusions:

> the naysayers began coming out in force trying to grab some attention. They use non-scientific "facts", misquote and mislead, and sometimes flat out lie. They write unprofessional articles and create deceiving videos to lead people astray... And there are other journalists who have written articles with really irresponsibly misleading information.

The labeling of other people's cost figures as "false" when they admit they have no idea whether they are false or not:

> We are still in R & D, and we haven't even calculated the cost for our prototype.

Presenting a false dilemma: either heat the roads or your children will die:

> Does the current system of snow removal sound cheap to anyone? What would saving over 1300 lives and preventing over 115,000 injuries per year be worth?

(No mention of the original context of the criticism, which was that heating roads are expensive relative to plowing the snow, the existing way we get snow off roads)

Presenting a traffic light as evidence that LEDs can be seen in bright sunlight, completely forgetting the fact that traffic lights require sun visors for the sole purpose of making the LEDs visible. Not to mention that they have Fresnel lenses, louvers, and all other kinds of special engineering that makes them visible in sunlight. No mention of what kind of analogous techniques they will use. And a picture of the LEDs in a very dark room, to drive the point home that they will work in sunlight, trust us.

A claim that glass is a suitable material for roads because of its moh's hardness rating. By that logic, tungsten carbide wedding rings would be indestructible, and in reality, one bad drop from waist height can destroy them [0]. This is an an argument so bad I can't believe an actual scientist wrote it. Hell, Wikipedia even says in the first paragraph "the Mohs scale is not suitable for accurately gauging the hardness of industrial materials." This argument doesn't even reflect a first-paragraph-Wikipedia-level understanding of the topic.

Long discussion of the troubles of the existing road system with the hidden implication that pretty much anything would be better (except, you know, all the stuff that would be worse).

Seriously, this is really, really bad. I was hoping they had some novel surface protectant they would pull out and say "sure, this would be bad with ordinary glass, but we've got this special coating that is cheap to produce and will change materials science and we're putting it through final testing now." But no, they literally intend to do this with off-the-shelf tech, appeal to a hardness argument that wouldn't pass a high school chemistry test, and brand everybody who disagrees with them as "irresponsibly misleading" "naysayers".

[0] http://www.examiner.com/article/exclusive-handle-with-care-t...

drewcrawford··on Netflix replies to Verizon cease and desist letter
The reason that Americans view Internet access as a natural monopoly is because there is a monopoly--the city. ISPs have to negotiate rents from the city government. While it is possible for a city to offer fair-access terms they have largely discovered that they can demand rents much higher than you would expect by keeping the number of tenants small.

These rents comprise something like 5-10% of city revenue. And so everybody gets what they want:

* The city gets a free 7% budget bump, and doesn't care who pays for it as long as it's too complex to be an election issue

* ISPs get a monopoly, and don't care that they play the scapegoat because consumers have no other choices anyway

* Citizens get better government services at lower tax rates. Sure, they pay for it via a backdoor tax on internet access but nobody really notices that and they direct their anger at the ISP rather than the elected government

Really the only way to throw a wrench in this system is something like Google Fiber. Nobody wants to be the elected official that turned Google away, because that is actually a sound-bytey enough issue that could come up at re-election. And Google, as a company that doesn't really care about being a profitable ISP, will only move in to a city if it gets a pretty good deal on the rents.

drewcrawford··on Dealing With The Loneliness of Working Alone
I run a HipChat for a few work-alone iOS devs. We've got about 3 active users that are somewhat timezone-disjoint and so we can afford to take on a few more. Some of us know each other IRL but some don't. Most are contractors with products on the side.

It's low-volume, most of the traffic ATM is discussing new WWDC features or asking for help debugging something. Occasionally we hit each other up for longer software architecture or product discussions.

If interested, e-mail is in my profile. Also I would totally recommend starting groups like this if you're a workalone server guy or whatever. It's pretty useful to have that daily interaction.

drewcrawford··on Runnable – jsfiddle for everything
Python 3 please...
drewcrawford··on Ask HN: client reporting bugs that don't exist, causing me hours of unpaid work
> Having all their business data logged doesn't sound like a condition that any reasonable customer should agree to.

Any business that uses SaaS or externally-hosted software agrees to this. The question is whether your vendor has a reasonable access policy for that data, and what "reasonable" means hinges a lot on your vertical and the kind of data you're storing. PCI is a completely different ballgame than button clicks for example.

Increasingly, plenty of non-SaaS products work this way (e.g. Tesla cars, OnStar, your iPhone, apps in the Windows Store, etc.) Again the question isn't so much about "whether" to collect usage and bug reporting data, it's about getting the defaults right and educating concerned users to tweak them to a level where they are more comfortable.

> also tells them that you think they're so stupid that they don't know the difference between a bug and a user error

This is literally the case that OP came to us to solve

drewcrawford··on Ask HN: client reporting bugs that don't exist, causing me hours of unpaid work
There are a variety of better deal structures available to you.

One is to cap your hours/cost. Just build in 40 hours (or whatever) of bug fixing for the first month into the price. Line item it, so the customer knows what he's getting and what it costs. Often customers will complain about this cost, and say they'd rather pay a la carte. Bingo. But if they don't, you have now set clear expectations about what is being provided.

Another is to make bug reports consumable. For reference, Apple has a bug fix consumable called a DTS Incident where you pay in advance to have N bugs investigated. Something you may want to consider if the bugs are all invalid is requiring somebody to pay to file a report, and if it turns out valid you refund their money. This may lead to more disputes though it's unclear if disputes are a problem in your situation. In that case you may want 2 hours of your time no refundable for every report.

The third thing is technical, and it works even if you don't have a good contract in place. Become omniscient. Log really detailed, invasive things and phone them home. Every user action, all the user's data, etc. Then when the bug comes in you cross-check against the logs and can verify quickly. "No you pressed the delete button, that's why you don't have any data. Not because a bug in the app destroyed it." Make it clear that you are doing this and make it clear that you will disable it, but disabling it voids the warranty.

drewcrawford··on Goodbye, IPv4 IANA Starts Allocating Final Address Blocks
No. "LTE does not require or even help IPv6 deployment." http://www.ietf.org/mail-archive/web/v6ops/current/msg15116....
drewcrawford··on The Indie Bubble Is Popping
I was doing some background research for another essay and this is as good a time as any to produce an actual journal article on point.

There's a common talking point I've seen both in this comment thread and elsewhere that the number of entrants isn't the problem at all and the real problem is game developers aren't innovating, and if they just innovated more things would be fine.

Kevin Boudreau [1] is one of the earliest researches on this scene, who concludes that "incremental increases in the number of application producers in this context led to a decrease in innovation incentives, on average, as measured by the rate at which new versions of existing titles were generated" and further that "the strength of descriptive patterns alone suggests that marginal entrants curtailed overall innovation".

Kevin's research, while it has many limitations, suggests that innovation decline is actually a symptom of an overcrowded market, not an independent factor in its own right. If true, this could mean that the practical way to address an innovation crisis is to first solve the problem of the overcrowded market.

The idea that market crowding depresses the innovation of individual independent developers is sort of a surprising result, but once accepted there are many possible feedback mechanisms that may explain the effect. For example, market crowding may drive innovators to go innovate somewhere else. Crowding may also limit available funding which may be disproportionately required by innovative titles rather than non-innovative titles which can be more cheaply manufactured.

[1] preprint: http://papers.ssrn.com/sol3/papers.cfm?abstract_id=%20182670...

jstor: http://www.jstor.org/discover/10.2307/23252315?searchUri=%2F...

drewcrawford··on Show HN: Cold Call Manager
> actually I was thinking about people who do not have the discipline to properly register all the relevant info after every single call

For me at least, I take notes during calls in a notebook. So recording the info isn't hard. It's actually an important part of my procrastination workflow, because if I don't have my notebook handy I "can't" make calls, ha ha. The hard part is more about planning followup calls and actually making them.

I've tried using issue tracking systems with due dates for this, but those are both at once overkill and underkill. Overkill because they have way too many features and inevitably get infected with things that issue tracking systems are actually built to track. And underkill because they don't have things that sales calls need like "snooze this alert until the next overlap of my office hours and the contact's business hours".

drewcrawford··on Show HN: Cold Call Manager
I'm in your market

Name - it's ok. But most of my calls are "warm calls"--following up on inbound. This product appears to solve my problems, which is interesting, given that is named for something different.

Run, don't walk, and implement email import. All my lead generation systems speak email, and if I could pipe them to you I would become a customer in about 10 seconds. Plus you have a strong lock-in effect with that, who is going to mess with 5 lead systems' configuration to move away from you?

Your marketing targets people who procrastinate at sales calls, but just making the calls easier fundamentally misunderstands why that procrastination occurs. You need options to nag me to make calls via email, timed to when people get back from lunch in their timezone. Probably integrate with heavier-duty procrastination services like Beeminder or Rescuetime, which may end up being a reliable sales channel for you.

drewcrawford··on Clib: Package manager for C
Distro packages don't solve the needs of software developers. They solve the need of distros, which are different (and conflicting) with the needs of software developers. Therefore you will always have an eternal struggle between language-level package managers who work for developers and system ones that work for distros.

If there was some simple way to lob a tarball over the wall and get package inclusion on Debian, Fedora, Gentoo, etc., then that would be one thing. In reality however the number of random GitHub repos >> the number of package maintainers. I know that Debian uses a variety of technical and social methods to discourage new packages, and most people's software just isn't popular enough to overcome those barriers, even if some of the reason they're not popular is because they're not well-packaged (sort of a catch-22 there). Not to mention people who install via apt or rpm are perpetually out of date.

Now compare that with pip or rubygems--one package to maintain, installs more-or-less everywhere, accepts packages regardless of popularity, end users are more often up-to-date. Better for software developers' problems in every single dimension.

Sure that's bad for Fedora maintainers, but what are Fedora maintainers doing for me?

drewcrawford··on FCC approves plan to consider paid priority on Internet
Another nice narrative that doesn't fit with experimental data.

In spite of the fact that one would imagine a Texas city to be less regulated than a California city, it isn't really that simple.

In Austin a strong majority of the utility poles are owned by the city. The ones that aren't are largely owned by AT&T, which complains very loudly that it is required to sell access to anyone who wants it at a price dictated by the Federal Communications Commission nationwide.

Meanwhile California (get this) opted out of much of the FCC regulation around utility poles and effectively allows a large private company to own and control the poles. This private company is made up of all the usual suspects like AT&T, Sprint, PG&E, T-Mobile, Verizon, etc., who seem to have formed a holding company to buy utility poles without anyone at the state being concerned about antitrust concerns. I'm not exactly sure what the requirements are to join--if access is "open" (for some definition of open) this may be how they circumvent the Sherman Antitrust Act etc.

California did pass "fair access" laws in 2011 [1] but as far as I can tell they only apply to "local publicly owned electric utilities" which presumably would not include AT&T and its utility pole holding company. There probably is some kind of regulation that in principle regulates competitive access to poles but how it compares to the FCC's jurisdiction in Texas it is difficult to say.

This is a side note, but we should really be having less talk about how we think regulation works and more case studies about how it does or doesn't work in these comment threads. "Less regulation == better internet" is a plausible model but so was the Bohr Model of the atom. "Is it correct?" is the question and that question can only be answered by looking at empirically what happens.

[1] http://leginfo.legislature.ca.gov/faces/billStatusClient.xht...

drewcrawford··on FCC approves plan to consider paid priority on Internet
I live in Austin which is a very densely-populated regional tech hub. Here we have three 30-mbit FTTN ISPs which is more competition than pretty much anywhere else in the US.

Earlier this year Google announced they were bringing Google Fiber here. Immediately all the ISPs announced that they, too, would be offering FTTH speeds. One company announced 300mbit, another rolled out 300mbit as part of a roadmap to gigabit, and the third actually rolled out gigabit well ahead of Google Fiber, which is still applying for permits.

I agree with you in principle that there is some margin below which companies will not invest in expensive capital expenditures. However there is also a margin above which companies will not invest in capital expenditures, because they have a sure thing going. The question is where those lines are.

The data from Austin show that in a market considered "exceptionally competitive" by American standards, companies are willing to invest an order of magnitude more in capital expenditures than they currently do just by threatening to create a lower-margin market. Google's work here, which so far consists of exactly 0 fiber installs, a landing page, and a contract with the city, has been so effective at transforming the market here that it's being argued by locals that it would be more efficient to forget about actually installing any fiber and they should just make announcements in one city after another and wait for the ISPs to do it for them.

drewcrawford··on Show HN: Progressive paywall using bitcoin microtransactions
Somebody in the media industry tell me I'm wrong, but I don't think news companies (e.g. your customers) actually want this.

If I subscribe to the NYT for $5/month, then in order to "get my money's worth", I use NYT as my primary source for news. I visit newyorktimes.com every day and see what today's stories are.

After 30 days of that, I am an NYT user "by habit" and thus a loyal customer. I'm not clicking through news aggregators as much anymore, because NYT.com is obviously better I tell myself, or else why am I paying $5/month for it? NYT wants customer loyalty to their brand so they get that consistent income and sign long deals with their advertisers.

This sounds a lot like cable "unbundling", which consumers want (or say they want) but Comcast will offer it over its dead body.

Now maybe you can sell this to independent blogs. But TipJoy (YC 08) tried that and went bust, so it's an uphill road.

drewcrawford··on Noise: Box and pipe cryptographic core
I know you are waiting for the curve thing to get settled but it's too bad there's not a C implementation in the repo right now. Today I'm working on a project that could clearly benefit from Noise but since it doesn't exist I have to use CurveCP and try to work around the problems you've identified myself.

I completely get where you're coming from on the "one ciphersuite to rule them all" problem but as an early adopter I would happily use curve25519 as a stopgap until you decide what the One True Curve should be. Instead I have to do my own CurveCP implementation now and then maybe rip it out later.

drewcrawford··on What is an appropriate level of Basic Income?
> as they couldn't pay for medical services or medication on $12K

While their numbers do seem a bit low, they are not off by an order of magnitude. Canada's healthcare system averages $375/month expenses across all citizens. [0]

> tax revenue would decrease as at least a portion of the population would simply drop out of the workforce.

Even if the bottom 50% of earners drop out of the workforce, this is a loss of tax revenue of 2.25% [1]. So the first-order effect of reduced tax revenue isn't meaningful.

> It won't work in the real world. I have always wondered why otherwise intelligent and successful people keep bringing up ideas

It would be one thing if there was broad empirically-based consensus that BI "won't work in the real world" but if so you have not brought that evidence with you today. It is probably best to refrain from unsourced assertions that people who disagree with you are stupid.

[0] http://en.wikipedia.org/wiki/List_of_countries_by_total_heal...

[1] http://www.ntu.org/tax-basics/who-pays-income-taxes.html

drewcrawford··on HTML5 Gaming Performance Test
Point of order on the methodology here.

This benchmark gets harder the longer it runs. Which is not in itself terribly unusual. It is pretty smooth for the first bit, where the benchmark runs, but right about where things get hard on my iPad Air is when the test stops.

So this raises a question about how the test endpoint was decided. Because of course if you run longer, the performance would be worse, if you run shorter, the performance will be better, etc.

Now according to the previous article [1], this endpoint is exactly 60 seconds, and an average is taken over that entire period except some time at the beginning for JIT. Now 60 is a suspiciously round number to arrive at by trying to hit X many sprites on the screen or numerically deriving some benchmark objective. Probably, somebody just eyeballed what a Space Blaster game looked like and one minute of runtime was about right.

That probably is a reasonable predictor for Space Blaster, but it is quite the leap to use these results to predict "most other HTML5 games" as asserted in this article. Some games will have half the sprites and others will have double, some games will be more spikey, and others will be more well-behaved, etc.

If I was going to use this benchmark to predict my game's performance, I would do what the benchmark designer probably did. I would ignore the results table, run the benchmark until the sprite count/size looked about right, and take my own average of the FPS indicator around that time.

[1] https://www.scirra.com/blog/107/boosting-mobile-html5-game-p...

drewcrawford··on Show HN: CodeReview – An iPad app for reviewing, editing, merging pull requests
If this was free + IAP I would install it. Maybe the free version supports 1 repo or (following the GitHub model) unlimited public repos.

I think $20 is a great price point (honestly I think you have room to grow) but you need to give people an opportunity to experience the benefits of the product.

drewcrawford··on The Scraping Problem and Ethics
I think there is a great meta-question in here, about business models for digital data and software.

Here you have a great case study, about an organization that tried to do a volunteer model, and it didn't work. Then they pivoted to a commercial model, but fundamentally they still believe in a free tier. But they have to cripple that free tier pretty thoroughly, and even still people abuse it.

I have a product I'm working on, that some people are apparently willing to spend lots of money on. Ideally I would have some kind of low tier, so that people without lots of money would be able to use it too. But I can't figure out a way to segment the product so that everybody pays what they can afford without bad apples abusing the low tier and ruining it for everybody. The result is that I may end up only selling it to customers with deep pockets, even though the product is much more broadly applicable.

← PreviousPage 7 of 29Next →