TN1ck

Almost everyone I know could not solve it correctly without a lot of hints. Even when you say: „It is not the answer you first think it is“. I like to use it when someone feels too smart and won’t acknowledge that he might be wrong about something. For example, a friend was arguing that the moon landing didn’t happen because the capsule was too small to hold the needed fuel. I asked him the paradox, he got it wrong. I followed with: „how can you believe to be right about rocket science, when you weren’t able to get this simple question right?“

I just tried it out and unfortunately it didn't work for my use case. Only certain applications are currently allowed to get accelerated by the eGPU - like Photoshop. I wanted to accelerate WebGL, but it was impossible to make it work. Chrome(ium)/Firefox/Safari, nothing worked. I tried a lot and the browsers showed the eGPU as the card to be used, but it was still the Intel Iris. When someone has any pointers what I made have done wrong, I would be super grateful, but my research was, that it just doesn't work yet.

All submissions where done by different accounts. Are you looking at the wrong page?

lobo_tuerto's other submissions are https://news.ycombinator.com/submitted?id=lobo_tuerto

I've built a lot of charts/visualization with React + D3. I normally use D3 only for the math as rendering with React is much faster, easier to reason about and allows for features like server side rendering. Animations/transitions are not a solved problem with React, which is why it's probably far easier to create an animated chart with D3 exclusively, as the render loop of D3 with its enter/update/exit is really powerful.

> Avoid O(n), try O(1)

Be careful with this, as dictionaries are not really O(1), in the worst case, it can be actually O(n). When your code heavily evolves around the 'fact' that it's O(1) try to make a version with a simple array iteration and compare which is faster.

It's a joke. It's obvious that they want people to contribute, as this follows with:

---

To prevent accidental violation of one of those guidelines, you should never

* learn git

* fork the repo

* learn python

* learn c++14

* read the code and documentation

* contribute anything to the code

* contact us

cheers, happy hecking.

---

The contribution guide in general is pretty well written and welcoming.

What they actually found out:

“Manny has proven that the way in which pendant cords are tied to the top cord indicates which social group an individual belonged to. This is the first time anyone has shown that and it's a big deal,”

The Problem with this whole concept of Microservices for the frontend is, that it can't really work out due to the constraints of the frontend: Every byte counts. It does matter how a component is written and which framework you used, as you don't want to load 2MB of Javascript for every new page. This is in contrast to the classical Microservices, where it absolutely doesn't matter how big each of them is.

So of course I checked their new site, that was written with this architecture (https://www.hellofresh.com/shop/). Could they solve this problem?

In total, they transmit ~770KB of minified JavaScript with an activated adblocker. This is quite a lot, at my last company we had a big react app with 70K LOC and a number of used libraries. It served about 800KB of minified JavaScript.

They load React, ReactDom, Immutabble and Axios separately to avoid having them duplicated, which accounts to ~67KB. So what are the 700KB doing?

219KB for a shop fragment 135KB for the header particle 96KB for the footer particle

The last 250KB is some API stuff called api_static and api_dynamic.

I can't really tell how sophisticated the shop is with its 219KB, but having a 96KB Footer and 135KB Header should raise some doubts, how is this possible? A React Footer should be 1KB or something. As I checked the source code I found mainly vendor code and as far as I can tell it's duplicated among the source files.

For me this shows me, that they couldn't solve the problems that arise with such an architecture and I doubt that there will be anything that solves these issues (without putting a lot of burden on the developers) in the near future.

Cool, really nice execution!

In my bachelor thesis I did some internal search-engine frontend some gamification and the like. I recently came around to build a quick and dirty reddit backend for the content, it also can be considered a visual browser for subreddits. For anyone interested:

Github: https://github.com/TN1ck/bachelor-thesis Runs at: https://bachelor-tom-nick.herokuapp.com/#/

It's in german though, but just click on 'Anmelden' and it should work, there is no auth layer currently.

If it's already a set in the language, use intersect. If the numbers are in a array or sth. similiar, make a set and use intersect. https://en.wikipedia.org/wiki/Intersection_(set_theory)

I think he can easily extend the system to use the missing variables. Scratch marks, color, texture and prickles are easily enhanced by digital image processing. Maybe use a different network for each feature and use this output to feed into another network to get the correct classification-function.

What about a more ambitious example like this: https://github.com/erikras/react-redux-universal-hot-example

I wouldn't, EventSource isn't supported by IE yet[0].

[0] http://caniuse.com/#search=EventSource

> medlars

I love those, too bad they are rarely available in Germany. It's one of the fruits I always show other people if I can.

It's really basic, the last time I needed this level of translation-capabilities, I wrote it myself.

Currently I can recommend http://formatjs.io/. We use it with the react-wrapper and it works really good. It handles everything from ICU-capabilites to formatting dates/currencies.

LIQID | Berlin, Germany | Full time

LIQID is the next-generation private wealth management solution. We combine scientifically proven investment approaches and the expertise of one of Europe’s leading investment teams with a unique, fully digital user experience.

Senior Frontend Dev:

As senior frontend developer, you are responsible for the development of Europe’s most progressive private wealth management solution. Together with our team of highly talented developers, you work on the development and optimization of our platform and the integration of our APIs and algorithms. Your main challenge is to deal with complex data structures and visualizations.

Technologies:

- React

- Redux

- Webpack

- d3

- es6 and jsx via babel

For more information see our job posting: https://www.liqid.de/en/career/senior-frontend-developer

Lead Backend Dev:

Your central duties are to guarantee code quality and manage the security of our systems in an agile environment. You provide guidance to other developers and work alongside our frontend ninjas to build and maintain our technological core. Your main challenges are the integration of third-party APIs and the algorithmic puzzles faced in financial technology.

Technologies:

- JRuby

- Ruby on Rails

- Docker

For more information see our job posting: https://www.liqid.de/en/career/lead-backend-developer

You can use double-tap zooming with the hand you're holding the smartphone with, im using it more often than pinch to zoom.

I think you are searching for something like dat.GUI [1], most WebGL-demos are using it.

[1] http://workshop.chromeexperiments.com/examples/gui/#1--Basic...

You can use babel-eslint [0] and the eslint-loader [1] to catch all errors babel might have.

[0] https://github.com/babel/babel-eslint

[1] https://github.com/MoOx/eslint-loader

I am your fear:

var invertTree = function(root) {

    if (!root) {
        return root;
    }
    
    var left  = root.left;
    var right = root.right;

    root.right = invertTree(left);
    root.left  = invertTree(right);
    
    return root;
    

};

Works pretty good! I really like the symbolic-link-preview. But I think it would be better when you just add -l when you enter things like -h, -T, -b, ... or allow an option for that.

Isn't the way React handles the DOM perfectly to prevent layout-trashing? As far as I understand, the DOM in React is nearly write-only, so layout-trashing should never occur, but I don't know the exact implementation details. Please correct me if this is not correct, I couldn't find any hard information on this.

No - that's awesome. I really enjoyed your post, I'm happy I could contribute a little!

Good idea! I couldn't resist: http://jsfiddle.net/HB7LU/1625/ It's very similiar to the d3 solution, ng-repeat works very well on this data.

I was bored, so I wrote a short visualisation of the solution in d3: http://jsfiddle.net/vdNnJ/

I can't get my Clojure-solution to run there. Anybody knows what's up?

(ns solution (:gen-class)) (defn -main ...)

There is also no Clojure-example :/

EDIT: Fixed it: You had execute the function, just added (-main)

This one too, but it's perfectly static: http://maximecb.github.io/Turing-Drawings/#4,3,2,2,0,3,1,1,3...