Kwastie

I am not sure this is even required. A (German) legal court order could also be used across the EU as a case law.

Generally expensive watches are associated with longevity, but I can't imagine someone buying this and expecting lifelong support.

This great (mini) YouTube documentary gives some background what lead up to the lawsuit. (https://www.youtube.com/watch?v=SrDEtSlqJC4)

Am I assuming correctly that this only applies for type 1 diabetes?

With type 2 diabetes the body is in general less sensitive to insulin, more insulin producing cells won't fix the underlying insensitivity issue, right?

With pure Reason (No JS bindings) it should be possible to skip Node / Bucklescript on the server and compile straight to binary.

This should be possible with something like bsb-native (https://github.com/bsansouci/bsb-native)

I haven't tried this because I don't have a pure Reason project

Minifiers don't output any readable JavaScript anyway. Yes, it can be "decompiled" back to something readable, but so can WASM.

interestingly enough some implementations are broken because of buggy UEFI (AMI) https://embedi.com/blog/bypassing-intel-boot-guard

Even though React 16 is almost a complete rewrite, it's amazing how they kept an almost complete compatible api between releases.

Congrats on shipping!

I agree, this article doesn't make any sense without proposing an alternative. Sure, I think most people would agree that the web is still a bit rough for (large) apps. (compared to desktop apps) But nothing that can't be fixed, right?

I can't imaging that native phone apps will still be popular in 10 years. I think that they will be replaced by the web in a similar fashion as web-apps have replaced desktop apps.

Someone at https://puri.sm almost completely removed the ME. https://puri.sm/posts/neutralizing-intel-management-engine-o...

I guess Google put more effort into TypeScript, this project seems like it's almost dead.

I am not a lawyer, but "not bringing a patent infringement lawsuit against Facebook or its affiliates" suggest that anyone using React can't file a lawsuit against Facebook over patents and NOT vice versa as you suggest.

Since the announcement of GraphQL I've been waiting for some 'real world' apis. (Sure the Star Wars GraphQL apis are fun)

Does anyone know any best practices if you want to adopt this is in an existing application using a relation database (i.e. PostgreSQL). I don't know how to implement this without causing N+1 queries. (or Worse).

For example:

{ Post {

    title,
    content,
    Author {
      name,
      avatar,
    },

    Comments(first:10) {

.. } } }

A naive implementation would cause a lot of query, for each "edge" a query.

Why does a respectable news outlet/paper like the Washington Post lower itself to clickbait titles.. I don't get it.

> manually updating the DOM is as optimized as you can possibly be.

Optimized in the sense that it uses less memory and cpu. But the code isn't optimized for humans to reason about (not to mention changing it.)

React was never about performance, it's about maintainability, readability and reasonability.

For me readable and maintainable code is (almost always) more important than fast code.

Sorry about my kinda harsh comment, good to see you fixed it!

kindly check the attached LOVELETTER coming from me.

LOVE-LETTER-FOR-YOU.TXT.json

I like the idea of building apps in a drag-and-drop ui-builders for prototyping. But I can't imaging using this for real products other than maybe a static app. How do you even connect to an existing backend? The 'demo' video suggests connecting directly to a database... So much for security.

I love how the author exposed every 'hash' function as 'encrypt'. Clueless

My comment is about React. I am not defending AngularJS.

>lack of best practices

How many 'best practices' do you need? What about 'higher order components'? Use proptypes in development? 'Avoid local state'?

>constantly breaking changes

I call bullshit, what was the last breaking change? Every large release still supports the old deprecated syntax, but with warnings.

>Every tutorial before the last month is already outdated

That is a big exaggeration; I wouldn't advice anyone to use 'pre es6' tutorials, but the concepts still apply.

>everybody has a different way of setting up webpack / isomorphism / templating.

No they don't, maybe a small differences and what do you mean with 'templating'? It's not Angular.

Why did Google create Polymer? Google isn't using it. This is almost the same 'problem' with "AngularJS by Google", it's almost never used by Google.

Edit: The reason I like React more is the fact that Facebook uses it in a high traffic production setting.

Edit 2: I think the whole Javascript (or framework) fatigue is just a 'transition problem'. Old tools are getting replaced by new tools, causing confusion..

This is general question, not directly related to this post (Sorry)

I get the feeling that "full Configuration/Deployment" tools like Ansible (Puppet, Chef and Salt) are getting eclipsed by tools like Docker.

For me Ansible was just a "half-way" station. 1. Manual software installs 2. Script assisted software installs 3. (some) server Configuration/Deployment with Ansible 4. Docker (Rkt, appc) 5. ??

Is this a fair assume that tools like Ansible are on the way back out? Or should you keep it to configure the Docker hosts?

The author is missing the point. The fact that Optional can result in a nullpointer doesn't mean you should use in the same manner as null-checks.

You shouldn't replace:

  if(x == null)
  {
    y = x.doSomething();
  }

with

  if(optionalX.isPresent())
  {
    y = x.doSomething();
  }

You should replace it with:

  y = Optional.ofNullable(x)
    .map(ClassX::doSomething)
    .orElse(null);

To be fair, nobody will choose React because of the virtual dom. The virutal dom is just a tool to make React perform faster.

You should choose React because it makes building reusable (web)components for applications much easier.

It works quite well actually, I tested it for a bit using the tutorial. I haven't found any real issues. Only the chrome inspector isn't working for me, but that might be caused by the Android emulator.