adam77

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."

[1] https://andreasgal.com/2017/05/25/chrome-won/

Sadly wkhtmltopdf's version of Webkit is ancient :( No flexbox, no es6, etc...

is it really smaller and faster. i got the impression the payload size reduction might come at a cost to render performance?

'Pretigious Technologies'

typo?

i got a taste after reading this...

https://ia601208.us.archive.org/16/items/vmss16/titzer.pdf

that's where the milestones can help; it gives concrete visibility to stakeholders of what the technical debt actually is

"oh we've loads of technical debt, it's such a pain", becomes "well we ticked off 4 big TD milestones last quarter and accrued a new small one"

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

not just everyday but part of US legal framework...

http://en.wikipedia.org/wiki/Authorization_for_Use_of_Milita...

No not in the constitutional sense [Article I, Section 8, Clause 11] but this...

http://en.wikipedia.org/wiki/Authorization_for_Use_of_Milita...

I think there's more to it than that, particularly legal interpretation of 'where is the battlefield' and 'preparing the battlefield'.

I think technically the US is 'at war' with certain terrorist groups, allowing certain tools of war to be employed (esp. in the middle east).

Something along the lines of: "In times of war...

* the battlefield is wherever the enemy is (just about anywhere you can draw a link to terrorist activity);

* the battlefield may be 'prepared' (drone strikes, assassinations, covert ops, etc).

[The reason the "War on Terror" is still treated as a war...]

...is for its legal status (empowering the US executive to carry out certain actions it otherwise couldn't).

A number of laws were changed/reinterpreted following 9/11 with respect to what constitutes war and how it may be implemented.

Also, improvements in the Java language are eroding it's raison d'être.

1. could make vote enticements illegal?

2. make any aggregate votes with greater than block size x (e.g. 100) public?