If you believe that, then what's so wrong about the guy having more than half the shares getting his way?
The fact that he doesn't have more than half the shares? He has 10% of the shares, but they are tagged so that they have 10 times the voting rights of the other shares, so with only 10% of the company, he still gets 50% of the control.
An argument could be made that, given the knowledge of a particular hardware vulnerability, software can eliminate the risk when being run on that hardware by working around that vulnerability (to whatever extent is possible).
You realise the bubbles are the "tabs" right?
When you click on a bubble, the relevant window covers the screen, you use it, then dismiss it back to the bubble. That's essentially what switching tabs in a tabbed interface does...
Sure, but what percentage of the income do they make? If they're taking home 80% of the income and paying 46% of the income tax, that seems to be underpaying.
Also, per your link, that statistic is not from the Cuomo, but is stated editorialising by investors.com after his quote.
Calling out flaws in the original study is acceptable.
Publishing another flawed study by cutting out 90% of the data and cherry-picking the outcome you want is not acceptable.
If that means creating terrible patches and not integrating with the flow of the OSS project itself, they may do that... The choice may be to attempt to get changes harmonized with the community or just publish whatever they come up with at the end. I suspect that there's a latent annoyance about this particular thing coming from the OSS volunteers. But
Except, they're missing out on some of the benefits by doing that. If they get their patches into mainline more easily, it's more likely that the next few releases will have their patches in them, and they won't have to keep updating their patches for the newer versions. Even more so if they contribute a unit test along with the patch - then they can have the comfort of knowing that their special case will be fixed for all time!
Because companies are focused on the short term benefits, they are losing out on the long term benefits for themselves.
And if they put the project "out of business" because it can't manage to handle all these out-of-flow patches, then the project goes away, and the company has to support the legacy system themselves.
https://issuehunt.io/ is a site which enables one to place bounties on Github issues.
BountySource https://www.bountysource.com/ is a similar bounty system, which can front-end a variety of trackers including bugzilla and Github.
I dug a ditch on my street for free, because it benefited me.
As a side effect, it also benefited my neighbours, and I am okay with them getting that benefit for free.
However, now the neighbour whose house fronts two streets wants me to dig a ditch on the other street for free too, and the house next door wants the ditch to run along their driveway as well for free, and the neighbour next door to them wants me to widen the section in front of their house for free, and they all get upset if I say no, because I dug the first ditch for free.
Someone needs to read the Little Red Hen again.
Contributions are only expected in proportion to demand for more work.
If millions of users take the project as it is, use it in its current form, possibly tweak it for themselves, take it apart, add new features for their own use, or do whatever they want with it within the license terms, that's fine - no contribution required. (Although it is always appreciated!)
However, if users start demanding new features, and customizations, and bug fixes, and support requests, on strict timelines, without offering anything back in return for their heightened expectations, that is when the project team starts to expect the users to contribute to the community beyond just issuing demands.
It is unreasonable for the users to expect and demand that the project team do work for the users benefit for free with no contribution back from those users to the community.
Trash thrown *into* the volcano, sure. Trash left littered around the mouth of the volcano will remain there until the next eruption...
The major reason is that if you want to advertisers to pay per ad viewed by the audience, then the advertiser (or rather, the ad network) generally wants to measure the number of views themselves to ensure that you aren't inflating the number.
There are a number of people who instead monetize their site with ads as part of their content. These people generally get paid per click, rather than per view, often through an "affiliate" style arrangement.
However, that requires the site owner to manage their advertising themselves, either by putting the fixed ad in a fixed place in their content, or by constantly updating the ad themselves. If you want to keep your ads "fresh", i.e. ensure that you're not advertising superseded products, which generate no revenue for the advertiser or yourself, you need to be constantly updating your ad catalog.
In theory, this would be something you could outsource to an agent who specializes in ad sales, however the agents have proven themselves to be unscrupulous in that regard.
Google Fiber’s attempt to roll out its gigabit internet across the city of Louisville, Kentucky has apparently failed so spectacularly that the company has decided to completely shut down the service and leave town altogether. CNET has a report on the news, which Alphabet’s Access division confirmed in a blog post on Thursday. “We’ll work with our customers and partners to minimize disruption, and we’re committed to doing right by the community, which welcomed us as we tested methods of delivering high-speed internet in new and different ways,” the Fiber team said.
TechCrunch's take is that:
It’s a rare admission of defeat for Google Fiber, though it’s no secret that the company isn’t exactly bullish on the prospect of the service anymore. Louisville was supposed to be somewhat of a comeback for Google Fiber, which like so many Google services is now under more pressure to generate a profit. Clearly, that didn’t work out.
Remember to say hello to your bank teller.
