It's interesting that these recent posts from the FF top ranks don't address this bundling issue.
It seems as though the world is moving to an 'appliance' plus app-store model. In that world the browser is part of the appliance and considered part of the purchase by the consumer. In that world, the only way for FF to have a presence is via hardware partnerships.
Yet another FF alumni alludes to the threat in a comment on the 'Chrome won' post [1] (my emphasis)...
"...for historical reasons Web sites targeting large-screen non-touch devices tend to configure themselves in a more standards-friendly way. ChromeOS is changing that; it has the form factor of a desktop platform, but not the third-party browser viability. If Android expands into that space, or Windows and MacOS get locked down a lot more, then that also closes up the window for Firefox."
I think it just means that the site is poorly designed. I think websites should work correctly everywhere where CSS2.1 and ES3 is supported. Otherwise some users won't be able to view those sites.
have the team come up with a list of achievable meaningful milestones (eg. 'eliminate use of nasty obsolete library X'), ensure some time is spared to progress them; it'll become clear if the team is net paying off or accruing
also, find someone who thrives on eliminating crap and let them get stuck in
Also make sure that person's work is recognized as being important.
I really like to eliminate crap, but I also try to avoid doing it as much as possible because it's something that never earns any recognition or praise. Historically I've had to really push to even get my boss to recognize it as an accomplishment during my quarterly reviews. Maybe management says they don't like technical debt, but that doesn't mean anything if incentive structures are designed in ways that encourage me to pile it on ever higher.
We have allowed the word "War" to be bastardized in everyday usage with things like "The War on Drugs" or "The War on Poverty" and now the "War on Terror" but "War" is something very specific.
The United States of America is not at "War" unless there is a Declaration of War from the Congress. The Congress of the United States of America has not declared war in over 70 years.
It's not likely to happen unless this country is facing a very real, existential threat. Declaring war is like flipping a switch on our Constitutional and economic systems.
> The United States of America is not at "War" unless there is a Declaration of War from the Congress.
The Constitution gives the Congress the power to declare war, but the extension of that to "war doesn't exist unless Congress declares it" is reading something into the Constitution which is not expressly there, and which there is a fairly good historical argument (which every Supreme Court case to take up the issue, starting fairly early on in the Republic, also sided with) is not at all intended.
> The Congress of the United States of America has not declared war in over 70 years.
This is not true; just as Congress doesn't have to use magic words when it invokes, say, its interstate commerce power, or its taxation power, neither does it when it choses to exercise its power to declare war; acts of Congress like the 2001 "9/11 AUMF" and the 2003 "Iraq AUMF" are both examples of exercises of the power to declare war (in both cases, declarations made conditional on executive acts.)
> Declaring war is like flipping a switch on our Constitutional and economic systems.
Declaring war is not like flipping a switch on the Constitution. Nor the economic system, really, though separate radical acts in the economic arena may be premised on the existence of a state of war.
What do you mean by 'technically'? If you mean by the definition that the Constitution follows, the US is not at war. If it was, Congress would be required to declare it.
Not really. NATO Article 5 was invoked on 12 September 2001. In that way every country in the NATO alliance was de-facto at war as an attack on one is an attack on all. This go-ahead was given on the basis that evidence proving the guilt of Osama bin Laden would be provided later, so that was a 'provisional go-ahead'.
The effect of this NATO 'trick' was that no presidents or prime ministers had to show evidence or get their parliaments to vote for the war. In effect Tony Blair's mate at NATO made the war possible with one meeting and one press conference, claiming that he had seen the evidence proving Osama bin Laden's guilt. Whatever that evidence was is something that the world didn't follow up on with NATO.
Regarding 1, if you're directly attempting to intimidate/coerce/bribe enough people that it will make a difference, that's a lot of chances for something to go wrong.
It seems as though the world is moving to an 'appliance' plus app-store model. In that world the browser is part of the appliance and considered part of the purchase by the consumer. In that world, the only way for FF to have a presence is via hardware partnerships.
Yet another FF alumni alludes to the threat in a comment on the 'Chrome won' post [1] (my emphasis)...
"...for historical reasons Web sites targeting large-screen non-touch devices tend to configure themselves in a more standards-friendly way. ChromeOS is changing that; it has the form factor of a desktop platform, but not the third-party browser viability. If Android expands into that space, or Windows and MacOS get locked down a lot more, then that also closes up the window for Firefox."
[1] https://andreasgal.com/2017/05/25/chrome-won/