Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

The output is considered to be a derivative work of the input, so the same copyright as the input applies. In the case of Pixar, the original models are definitely an original creative work, so the output is as well.

If you are simply using public domain databases as the input, and passing them through an automated process with no creative input, then you probably won't be able to get (or more to the point, enforce) a copyright on it.

Now, whether the databases he's using are copyrighted or not is an interesting question; as well as whether database copyrights even apply. Not all jurisdictions have the notion of database copyrights. Individual facts cannot be copyrighted; but collections of them can, at least in some jurisdictions. However, I don't know if the databases he is using are copyrighted or not.


In the US at least, facts cannot be copyrighted. Various cites have tried to stop alternate subway maps or transit apps from being sold, but courts have ruled that mass transit routes and schedules are facts and not protected by copyright.

I guess it makes sense that these auto generated books may fall under the same umbrella.


Just buy an Android. You can configure what browser opens links. You can configure what map application opens maps. You can configure what video player opens videos.

Yes, this is much like Microsoft a decade ago; in fact, it's worse, the iOS offers significantly less choice than Windows did back then; you could develop your own software for your own computer without joining a restrictive developer program from Microsoft.

If you don't like it, my recommendation is that you don't buy into it. Get an Android. I've been perfectly happy with mine.


<<nothing related to what you said, just a general comment>>

If more people just bought what they liked, shut the hell about it, and didn't rage jihad against the opposite platform, the internet would be WAY better.


No, it won't be. Bad things must be criticized (or boycotted), to force them to become good. Your use of Apple is affecting my life badly - it's just like passive smoking. No one promoted the culture of ridiculous patent law exploitation as much as Apple did. They are not just doing their own work, but indulging in UGLY competition killing tactics(like they don't want anyone to make rectangular phone with rounded corners). To give you some insight of your own logic, if everyone "not killing someone" will just not kill people as they like it, and didn't say a word to the 'opposite party' - who kill (as they like it as well), according to your logic the world would be WAY better. Jihad is a bad word, but I'll fight against the injustice to my world of technology that Apple is doing.


Remind us how snarky zealotry tells Apple to stop (ab)using the patent system. If that's the problem you have with them, I think the world would be improved if you directed your energy at patent reform.

And comparing IP litigation to murder is just ridiculous, not that you didn't already know that. Among all the other problems, you can fix a bad call from a judge. Murder, not so much.


It's not ridiculous. I explained and it's not hard to understand why opposing bad things (any) is important. And it's always a good test to validate your logic with extreme cases. It helps - if a logic suddenly breaks by increasing the 'intensity' of the subject, then there's something wrong in it.

Again, I don't think the patent law is getting 'reformed' overnight. I have written to state officials to improve it, have signed petitions, and have written to Apple as well. But on top of that, if more and more people stop using their products for this reason, they will understand it much more quickly.


> And it's always a good test to validate your logic with extreme cases. It helps - if a logic suddenly breaks by increasing the 'intensity' of the subject, then there's something wrong in it.

I would suggest avoiding doing so publicly. People can come to the same conclusions if they want to apply theory of extremes, but when you jump to that kind of thing in your initial comparison (especially without a disclaimer) it just makes you come off as a crazy person. Doubly so since the extreme didn't hold up.

It didn't help that some of the more rational points are easily countered (even if not wrong). Stating that my use of Apple harms you because of my "support" of their business and legal decisions may not be entirely false; however, it's a) unreasonable to expect consumers to know about the operational choices of every company they do business with and b) also helpful because it promotes competition in the market. Again, your points had merit, but so does the other side of the equation.

The unfortunate reality of being a publicly-traded US company is that you are more or less legally required to try to litigate your competition out of existence if the numbers support it. This instance is unfortunate because Apple was granted some patents that they should not have been, and there was inept jury in deciding to uphold them (never mind the fact that it was a jury-based trial at all). The Apple/Samsung thing should have been a trademark case which I think actually had some merit, but patent litigation has a higher potential upside so the finances said that was the way to go.


>>and it's always a good test to validate your logic with extreme cases

Uh, no. Hyperbole weakens your argument. If you want to be taken seriously in discussions among adults, I suggest you avoid it.


Patent law exploitation? They are going after people who take their products, sit down with a drawing board, and copy them feature by feature, logo by logo, and interaction by interaction. It's exactly what the patent system is designed to make legally actionable.

This isn't a case of Amazon suing every online shopping cart with a "click to buy" button.

(Fifthly, why does a game of multi-hundred-billion-dollar corporate chicken impact your life at all? They aren't going after a kid on the street corner -- they are going after themselves dressed in different clothing. This does not change anything in your world except an extreme branching narrative in your mind which you think the world cares about.)


You have to be pretty naive to think it's not affecting my small world, OR to believe that Apple is only litigating against those who "copy them feature by feature". You probably didn't even read my full message. Now any company I prefer can't make phones without fearing about how to save themselves from a useless litigation of rounded rectangles. And in my small world, I might have wanted to open that coffee shop whose logo is just a plain old red apple fruit made by nature, with a child's head in that. But it seems I can't do that now.


I respectfully disagree.

I used the word Jihad as it best reflects how personal it becomes to some people. It's not a matter of taste, but a matter of "being".

My main point, which clearly wasn't well articulated, was STEP YELLING AT ME. I can't change it. Nor do I care.

Yell at Apple, or Google, or whoever can act on it. Boycott them all you want. Just don't vilify me simply because I happen to like the platform you happen to hate.

You do that, and I promise to not yell at you for the platform you like that I happen to hate (as an example, I honestly could give two shits about Apple or Android .... it's a god damn phone).


The thing is, Apple makes really nice hardware. Really, really, nice hardware. There are some pretty good Android phones, but Apple nails it in a way that nobody else seems quite able to pull off.

I'd love to have an iphone 5 running Android! :]


Hmm.. Are there hardware level-blocks on jail breaking an iPhone so far as to run android on it?


No, surprisingly.

And yes, the Android port is well underway: http://www.idroidproject.org/


According to the site, the project is pretty much dead. Shame, as I agree with the OP that Apple hardware is better than anything an Android manufacturer has turned out - or is interested in turning out. I can't remember the last time I saw an Android phone under 4.3" big.


It's a years old version of Andriod. I tried to install it on my old iPhone 3G a couple of months back and it barely worked and couldn't make phone calls. There hasn't been updates for years. It's an abandoned project.


From the link it looks like it's pretty dead.


Yep.

It's not quite like that, but essentially that's true (I think it's possible to run Android on iPhone 3G S and older, but that was a long time ago and I don't think you could use it as a phone).


Have you looked at the Nexus 4? Feels a lot nicer and the screen seems a lot better than the iPhone 5 to me.


Never seen the nexus 4; it's too huge and heavy for my tastes anyway (the iphone 5 is already pushing it)...

Can't speak to the feel, but I do like the aluminum of the iphone 5 a lot.


Not available on Verizon.


I don't think this was as much of a complaint about the situation a question, so your recommendation doesn't offer much in regards to the question in general. I do understand what you're saying, I just don't think it's really what robbiep was asking nor is it the place for it.


The App Store adds restrictions that are incompatible with the GPL. Who exactly "cares" is somewhat irrelevant.


I fell like there's an awful lot of confirmation bias in people's reports of how well low-carb diets work, just like there was back when low-fat diets were the big fad. In general, any deliberate change in your diet is likely to lead to results, at least in the short term, as you're paying that much more attention to what you're eating. This is similar to the strength of the placebo effect in medical studies; one reason it's so strong is that even the people getting the placebo in the study are getting a lot more medical attention, and are paying more attention to their health.

Now, I suspect that low-carb diets do actually work better than low-fat, merely because it's easier to keep the calories down on a low-carb diet. "Carb-loading" is a popular way for athletes to give themselves plenty of energy to perform for a reason; carbs are the easiest way to boost calorie intake. So if you have an extreme low-fat diet, you wind up replacing the fat with even more calories in carbs; I can't count how many low-fat foods I've seen that just add a bunch of sugar to make it taste better.

But that doesn't mean that low-carb is a magic wand. In fact, it's fairly dangerous in some ways. Low-carb means you wind up replacing the calories from carbs with fats and proteins; a lot of people eat more meat as a result. Eating a lot of meat can increase your chances of getting certain kinds of cancer. I've seen studies that showed that in the long run, low-carb and low-calorie diets had about the same effects for weight loss, but the low-carb dieters were at a slightly higher risk for cancer due to the extra meat they ate.

I actually think that a large amount of the value of low-carb comes from cutting out the worst form of carbs, sugars. There is an awful lot of modern food that is being loaded with more and more sugar, especially given how cheap HFCS is. It's a very cheap and easy way to make mediocre food taste better; so we wind up eating a lot more sugar than our bodies can handle. Avoiding foods that have sugar added can help a lot.

There has also been a lot of diet fearmongering over something else that has traditionally been used to make food taste better: salt. Lots of foods are sold as "low-sodium" ever since people started blaming salt for heart disease. The problem is, most of the reason for that was based on correlation, where causation had never been shown; some groups of people at higher risk of heart disease were eating more salt, but there was never any good evidence that the salt was the reason for the risk. Reducing salt in food has meant replacing it with other things to make the food taste better, like sugars and fats.

There have been an awful lot of diet fads over the years. Many of them lead to more problems than they solve, as people take them to an extreme, and wind up replacing what they're cutting out with something equally bad or worse. And many of them have lots of adherents who proclaim their advantages, due to confirmation bias, while dismissing anyone for whom the diet doesn't work as not doing it properly (the "no true Scotsman" fallacy).

In the end, "eat less, exercise more" is the best way to lose weight. Yes, exactly what you eat can make a difference, but eating less (fewer calories) is a pretty good first step on the way to losing weight, rather than focusing on one particular source and winding up eating more or eating worse by doing so.


"with fats and proteins; a lot of people eat more meat as a result. Eating a lot of meat can increase your chances of getting certain kinds of cancer. I've seen studies that showed that in the long run, low-carb and low-calorie diets had about the same effects for weight loss, but the low-carb dieters were at a slightly higher risk for cancer due to the extra meat they ate."

I have yet to see a true scientific study that attributes cancer to high meat intake. The "studies" that I've seen which attribute high meat intake to cancer are observational in nature, following tens of thousands of people over 30 years, and pretending that the people who ate lots of red meat in the 70's and 80's have the same lifestyles as those who listened to doctors and ate more salads and fish. The kind of person who ate lots of red meat in the 80's was the same kind of person who probably ignored all sorts of medical advice. This inability to control for other variables is why observational studies are horrible. I'm a huge coffee drinker, but I'm not stupid enough to fall for the observational studies which link coffee consumption to living longer. All too often, the people who DON'T drink coffee DO drink soda, which is a simple example of how these ridiculous observational studies can be misinterpreted.


"following tens of thousands of people over 30 years"

That's called a cohort, it's a well studied method in statistics and depending on the size of the sample and the number of studies you can build correlations out of these.

As your sample gets larger the population for the proportion of heavy meat eaters and the rest of your sample tend to normalize in almost every variable[1], that means the median of every other observable variable will be close to the general population's value for both groups, and you can assume that the quantity of meat is the sole variable worthy of analysis.

Mind you that the use of statistics in health and social sciences is because these fields are not physics, we can't find general solutions based on the present state of affairs putting some number on a equation. How many people will get cancer or whatever.

I doubt this was the type of study that are used in this case because a cohort study is really expensive to conduct, generally this type of study is conducted more using the Case-control method which makes than more affordable.

The fact that if you conduct such a study and find that heavy meat eaters get more cancer or heavy coffee drinkers live more doesn't mean that every coffee drinker will live more or that there will be much more heavy meat eaters with cancer than the rest of the population, it will only means that some epidemiological indices are higher in a group than in the other.

If you really wish to test both hypothesis you must do the same study as many times as you can and try to use the median of these indices obtained in the same study for both populations, the median is a robust measure and see if they are too distant numerically one from the other.

Of course, this can still proves nothing and only find that correlations are in fact established. It can simply be that rich people live longer and get more cancer than the rest and both drinking coffee and eating too much meat be associated with income.

[1]: That's not exactly true you can have confounding variables in your data, which sadly sometimes are not included in the data, when they are you could read the methods of controlling this developed by Mantel and Haenszel.


> In general, any deliberate change in your diet is likely to lead to results, at least in the short term, as you're paying that much more attention to what you're eating.

The graphs in my original post were over the course of a year


This is why I hate the Web Content Accessibility Guidelines:

> In the following code examples, the names associated with the text input controls are not properly determined by assistive technology.

Which assistive technology? Why doesn't the assistive technology simply implement HTML properly? Associating a label with an element by nesting has been standardized since HTML 4.01 at least (I haven't bothered to check further back), and I'm pretty sure all of the browsers implement it properly.

Now, instead of simply writing a bunch of guidelines that say vaguely "not properly determined by assistive technology", they could show the results of testing, in a format similar to http://caniuse.com/. That would actually be useful; you could determine if the problem still exists or not, based on how many people are using some old buggy version of assistive technology.

But, rather, the WCAG are simply a bunch of prescriptive rules with vague justifications, and then various people on standards list try to argue that because there are laws that have been written that specify that certain things must comply with accessibility standards, these kinds of guidelines have the force of law and thus trump all other interests in standardization.


In the United States accessibility can not be ignored because the enables only a small portion of the public (see: The Americans with Disabilities Act). I agree that the guidelines could do a better job of explaining which technologies to support so as to enable accessibility. But I worry that some people would be led to think that disabled populations, who are in a minority, can be ignored if the site owner desires. This is rightly illegal.


It is not illegal to have a website that's not accessible. It's illegal for the government to use or mandate software that's not accessible; and thus anyone who wants to sell to the government must make their software comply. But of course, in many cases this means that people either find some exemption or workaround, or do a cursory and not very useful job of making it accessible.

I am not arguing that you should ignore accessibility, or that it's not a good thing. What I'm saying is that there's a certain group of people in web standards who put accessibility over everything else, and refuse to adopt newer, better technologies for providing accessibility because some older, broken technology was already standardized on years ago.

For instance, there's the whole fight over longdesc in HTML5. longdesc has been standardized for a while, and lots of accessibility standards require or recommend it. It's supposed to contain a link to a page containing a textual description of the image; it is intended for cases in which you can't fit a full description into the "alt" attribute. But so many authors use it incorrectly; some just put the long description right in the longdesc attribute, some had broken links, and so on, that most screen reader users either ignored it or didn't even know it existed in the first place. One reason it's so badly broken is that normal user agents don't provide any way to access a longdesc attribute, so you never see that it's broken unless you try to use a screenreader and specifically test the longdesc.

So the HTML5 authors decided to deprecate longdesc in favor of newer solutions that were more likely to provide working description, like aria-describedby, which refers to another element on the page. That element is much more likely to work as it's already there on the page, visible to people using ordinary visual user agents, unless it's explicitly hidden. If you still want to provide a link to another page, you can just point aria-describedby at a link.

But many of the accessibility crowd complained loudly at deprecating the severely broken longdesc attribute, merely because it had already been included in so many accessibility guidelines like this, not because it was actually technically the best solution.


Wait... It's illegal to have a website that's not accessible? That's news to me.

http://news.cnet.com/2100-1023-962761.html


Wow, I remember Agora from back when I used to play Nomic. If it's still around, it is indeed the oldest living Nomic, as far as I'm aware.


Ah, I remember playing an online game of Nomic back in high school. Someone actually keeps an archive of dead Nomic games, so the eye-bleeding '90s web design is still alive: http://www.nomic.net/deadgames/macronomic/. I take full credit for the painful color scheme. All static HTML hand-edited in BBEdit; I think I had a bunch of macros defined to help make it easier to maintain.


This applies to more than just Google. Your income should not solely depend on one party, unless you're in an employment relationship with them, which carries with it various sorts of legal and social obligations that are a lot harder to simply end on a whim.

Does your revenue depend entirely on being in Apple's good graces, and being dropped from the App Store would end it? Does it depend solely on Google's advertising money? Or even if not solely, if 75% of your revenue comes from one source, it will be game changing if you lose that.

This is why monopolies are a bad idea, and duopolies aren't much better. A healthy market will have at least three viable players, with none controlling over 50% of the market, allowing you to diversify and be save from any one of them deciding not to play.


Problem is that in some markets (e.g games) you can't really help but be beholden to some large publisher. Whether it be Apple, Steam or MS. You can hedge your risk a little by releasing across multiple platforms but then there is still the risk that one platform in particular accounts for 50%+ of your sales and you could lose that at the drop of a hat.


Isn't this basically an argument against ever creating any iPhone app?


No. It's an argument against having all of your income based on an iPhone app. Now, sure, you might start out on the iPhone; but rather than focusing all of your effort there, once you've got some traction, it might be good to work on porting it to Android, and possibly Windows Phone or Blackberry. Of course, even there, it's mostly a duopoly; I don't think that Windows Phone or Blackberry are really viable platforms at this point, so you are going to have to deal with the duopoly nature of the business for now.


I would add that it's also an argument against being dependent on the income from an iphone app.

If your income is from one source, you should default to saving more of it than you would if you had a diversified income base.


It is a good argument against creating a native iOS app, certainly. If Apple decides to drop you, your app's code is virtually worthless.


While you're absolutely right, there's still one problem:

There aren't much, if any, advertising providers with ads as accepted and unintrusive as Googles AdSense...

Not to forget their huge portfolio of ads that will fit almost every context - so yes, AdSense is the go-to provider for most.


>Your income should not solely depend on one party

The networking effect is naturally monopolistic.

There aren't any practical alternatives to facebook and youtube. Being kicked from either would be disastrous and neither has to offer an alternate ad network or even need a good reason to get rid of you.

I imagine a simple mediation or ombudsman process is all these companies need, but they have no incentive to really make that work. They're still making money hand over fist.

From a regulator perspective, these are major issues, especially since we've officially entered the age of the walled garden/centralized store. I don't think this is the kind of thing the free market will magically be able to fix if we sit and our hands and wait. I imagine its going to get worse once MS and other big players start making it much more difficult or impossible to install unsigned software or software from outside their store.


But don't most machines that will be using CPUs that big have two sockets? Big servers these days come with 2 CPU sockets, 6 cores per CPU, 2 threads per code. So you do see 24 way parallelism pretty often, for server-side code at least.

Now, this was pretty much the low end of his original prediction: 'If we stick with "just more of the same" as in Figure 2's extrapolation, we'd expect aggressive early hardware adopters to be running 16-core machines (possibly double that if they're aggressive enough to run dual-CPU workstations with two sockets), and we'd likely expect most general mainstream users to have 4-, 8- or maybe a smattering of 16-core machines (accounting for the time for new chips to be adopted in the marketplace).'

It is true that new, mainstream systems offer 4 to 8 way parallelism, and that you see up to 24 way parallelism on the high end. So, his "more of the same" prediction was perfectly correct.

We did not see the large jump that he hypothesized might happen. But if you notice, he said "But the gating factor is software that can use them effectively; specifically, the availability of scalable parallel mainstream killer applications. The only thing I can foresee that could prevent the widespread adoption of manycore mainstream systems in the next decade would be a complete failure to find and build some key parallel killer apps, ones that large numbers of people want and that work better with lots of cores."

As you say, most programmers don't develop for these big many-core monstrosities. So he was right; software that takes advantage of multi-core machines is still a gating factor. The chips are available, but because that many cores does not help most software that hasn't been specially crafted for it, they are not mainstream.

I think the one major fault is in his optimism that it's possible for most software to take good advantage of that many cores. Parallelism is hard. Correct software is more important than fast software. Heck, a lot of software these days is written in languages like JavaScript, Python, and Ruby, which are not known for their speed, but rather their ease of development. Telling people to get with the multi-core bandwagon, when really just writing large, correct software is in most cases more important that squeezing out the last ounce of performance, is not exactly productive.

As GPUs have shown us, the best way to take advantage of that extra parallelism is to write special purpose libraries for the computationally intensive parts, and then just call out to that from simpler, less parallel code. So I'm not sure that the average programmer is going to spend that much time adapting their code for the parallel world, other than using existing libraries and frameworks for taking advantage of that.

A database backed web app is a great example of this kind of parallelism. The hard parts of parallelism are generally handled by the database itself. The web app is usually written completely single threaded, but you can spin up multiple processes all talking to the same database to take advantage of your multiple cores.

I suspect that is how we'll see parallelism play out in general. Most software written single threaded, with parallelism only by running multiple processes, talking to specially tailored databases, message queues, rendering libraries, numerical computing libraries, and the like.


Good points. Parallel code is getting easier to write, e.g. the Go language, thus likely more common. I think web servers alone (serving more users per machine) could drive multi-core advances.


What's with the "word-break: break-all" in the CSS? It's really weird to wrap English text that way; and removing that doesn't seem to affect how the Japanese text is wrapped.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: