iotscale

It's probably good that it's possible to opt-out of being archived but what annoys me is a useful domain changing hands and the new owners deciding to wipe its history.

The movie eXistenz made the exact same prediction in 1999.

I guess that was my only exposure to it with that meaning, so I had assumed it was something specific to Firefox. Many others were too, I remember some people suggesting that Google stole the name Chrome from Firefox on some forums back when it first came out. Yes, it sounds ridiculous, especially in the light of this knowledge, I know.

TIL, thanks for the clarification.

I think Chrome was (maybe still is?) also the name of Firefox's GUI or something like that. I remember being confused when Google Chrome first came out.

Edit: I thought more about this and remembered someone on the Firefox Addons site complained that the author of "lesschrome" (an extension which hides the "chrome" automatically) was being jealous(!) of Google Chrome. Couldn't find the comment and the following funny discussion though.

We use knockout at work but

    <p data-bind="if: foo">foo!</p>

quickly turns into

    <!-- ko if: foo -->
        <p>foo!</p>
        <p>
          because this also depends on foo and I should
          keep it DRY and adding a parent element just
          to contain that "if" is silly.
        </p>
    <!-- /ko -->

Then you start to get comments everywhere and sometimes they don't match and you write server-side helpers to contain them then it becomes a soup of html, your server side templating language and knockout annotations.

JSX is way cleaner.

We are still probably going to migrate to Vue.js though because it will be easier. (We love Knockout but having performance problems on edge cases.)

You give React a state, it diffs that and passes the outcome to the ReactDOM, which can render it on the DOM. At its core React doesn't know what a <div/> is. It just diffs objects and generates instructions to reach the next state (very generally speaking here). The stuff you pass to it is an object and can't be malformed like a string can. Main function of React is maybe loosely related with templating.

For PHP (in its traditional form), everything around the code is just strings, which is also the case for most of the templating engines.

You can't shout "spaghetti code" every time you see XML tags in code. Think Scala or VB.

Or more fine grained permissions.

They could at least make it possible choosing not to upgrade a very simple extension which we may have been personally reviewed.

I want a fixed (read: no updates) extension that does this: On key press, check if the key is backspace, when it is, check if any form element is focused, when not, go back. One line of JS, I guess three with nice formatting. If I create this, I need to submit it to the Chrome Store so Chrome won't complain about untrusted extensions.

Of course they also removed the ability to tell it that I know what I'm doing.

React is not a templater, it's a differ. The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code.

Edit: After reading my comment again, I feel I must mention; even that similarity is not coming from React directly. It's JSX. Although they go like fish & chips together (Not a great analogy but I guess I'm hungry).

I started reading through the docs and found it very similar to Knockout.js. Is here anyone who used both to tell the advantages of Vue?

FYI, I'm thinking about dropping Knockout because some performance problems I'm having with a very specific use-case.