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

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


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.


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


That's discussed in the doc (and there's some metrics). Update speed takes a (minimal) performance hit, in exchange for code size reductions.

We (and our colleagues at Google working on the web in general) find that the largest impact on performance comes from simply shipping less code.

Edit: correction: turns out our tests show we didn't take a perf hit on updates at all, and in fact ever-so-slightly improved. So win win :D


'Pretigious Technologies'

typo?


Or just awesome joke?


Nope. The name of my 'company'. Yes it's prestigious without the s in the middle.


Why? A google search only shows misspellings and an urban dictionary entry you do not want to be associated with.



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.


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"


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


None of the legal mechanisms of war apply to what the US is doing in the middle-east.

Congress has authorized certain actions but there has been no declaration of war.


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


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.


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

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


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.


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

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


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.


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


What is the point of having laws curbing the government if the government can change those laws when it pleases?


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


Even with a big step like Java 8, Java is very very far from being comparable to more modern, expressive languages.


1. could make vote enticements illegal?

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


1. Maybe, but that could prove difficult in practice.

2. The ballot is no longer secret and subject to the problems of bribery etc.


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.


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

Search: