21–30 of 75 posts
Earlier quoted context omitted.
Someone said the same thing in the comments. In a reply, the author does not know why the MD5 fails but confirms that the post is correct: I wondered if anyone would check :-). I'm not sure what the problem is with the first post. It's been a long time. You'll have to take my word for it that the first post is the right text :-).
Different encodings for line endings?
Thank god they eventually “saw the light” and they’re now back on track.
Opera made the bet he proposed and lead themselves down a path to irrelevance.
There was a post from an Opera insider that I can't find but it was basically this: the web's complexity was evolving faster than the Opera team could maintain their proprietary Presto rendering engine.
Switching away from Presto and building on WebKit was a basic matter of survival. Yes, they still became irrelevant but they would have also stayed irrelevant with their Presto engine.
I agree with their assessment because around 2009, I started encountering more and more web pages that broke Opera. The Opera forums had more and more complaints from users reporting broken web pages. The Presto engine was becoming a liability.
It was a vicious feedback loop because web authors wouldn't bother to test their sites with Opera ... which led to more user frustrations. I had to switch to Chrome to get a usable web surfing experience back. I originally paid for Opera because it had the fastest rendering engine which was very helpful for slow dialup connections. As Presto started falling further behind, that speed advantage was negated.
Opera did try to some interesting features such as "Unite" which -- if you squint a certain way -- was a form of p2p decentralization. Yes, it's interesting to have a built-in web server in the browser but not enough people cared about it.
The author's predictions for Firefox's Gecko engine meeting the same irrelevant fate as Presto didn't happen because unlike Opera, Mozilla from 2004-2014 got massive funding from Google. Mozilla could afford to keep programmers enhancing the Gecko engine. Opera couldn't do the same with Presto.
Earlier quoted context omitted.
Different encodings for line endings?
hashed-blog1.txt contains HTML markup for paragraphs, while all others are in plain text.
Neither adding a \n to the last line makes it match
Have they considered rewriting it in R... oh, hang on.
Earlier quoted context omitted.
hashed-blog1.txt contains HTML markup for paragraphs, while all others are in plain text.
Taking them out has not resulted in the correct hash, or maybe I forgot something Neither adding a \n to the last line makes it match
There might be some other slight changes in formatting which is still missing.
Cool idea to just post the hashes for the future. I think I might do it too on my blog :-)
Maybe use SHA256 rather than MD5. A few years hence ease of producing MD5 collisions might render moot anything that you had to say.
I expected an article about 1990s browser wars. 2007-2008 is not ancient in my book.
I expected an article about 1990s browser wars. 2007-2008 is not ancient in my book.
A lot changed in the last ten years. It may not seem like it because most of those changes were refinements on things we already had at the time. We've just been in a long period of revisions. New programming tools, new social networks, new [insert thing we've had since the '90s]. The late '90s and first half of the '00s were full of radical changes, so it seems less significant in context.
We're probably on the brink of another radical upheaval like the '90s. There's lots of money flowing around, lots of amazing and well-refined tools, and all the low hanging fruit is more or less captured. No one's getting rich on "x as a service" anymore. People will have to really change something to capture the next huge payday, and the first few will set off a cascade of changed expectations.
> the more code engines share, the more de facto standardization of bugs we would see, so having genuinely separate implementations is very important. Well it's not like there aren't any bugs in the specs. And whether there are bugs in the code or the specification, it's the same process for fixing them : politics :)
There has been a lot of progress recently on the web-platform-tests project [1]. This is a cross-vendor effort to improve interoperability on the web platform through testing. Historically the process for building web-platform features has been to write a spec and then assume that implementations of the spec would reach compatibility in an ad-hoc manner by patching until sites worked. The big innovation of the last d…