1,623 karma · joined October 30, 2014
Edit: I feel a bit bad about this joke. I know that Front End Frameworks take time too. For example React wasn't deployed internally in Facebook till 2011 and that was after two years of research and development on it. Then it was open sourced in 2013, so that's like 4 years of development before it was ready for public use. But jokes depend on culture and the culture of HN is: "Front End frameworks: lol".
Edit: You haven't heard from them because they are aiming very high so it will take years before any of their work hits the general public.
Edit 2: From my understanding, they are still working on their Universal Basic Income Research as well and have chosen Oakland as the testbed: http://basicincome.org/news/2017/04/httpswww-youtube-comwatc....
I haven't dug into Pinterest's code but I imagine it's most likely a mix of Flexbox and Multi-column layouts: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Columns....
Edit: See this blog post on how to combine them to achieve the staggered effect: https://medium.com/@_jh3y/how-to-pure-css-masonry-layouts-a8....
These come up quite a bit. Look at Pinterest, it is all staggered/made of nonuniform cells.
(See: https://qz.com/807419/is-it-even-possible-to-sell-luxury-on-..., among other articles that you can find from googling.)
But I agree that it's very strange that Amazon is buying Whole Foods, which is a luxury grocery store, to then try to replicate Walmart. This will just alienate the customer base and drive them to Traders Joes, Coops, etc.
I'd edit my comment if I could but it's been to long. Sorry about that.
Also, make sure to read his descriptions where he talks in more detail about these ancient techniques in tool building.
'env': {
'memoryBase': 0,
'tableBase': 0,
'memory': new WebAssembly.Memory({initial: 256}),
'table': new WebAssembly.Table({initial: 0, element: 'anyfunc'})
}
But it is really early on and if the Portable updating SDK is any indication it seems like they want to make it easy to get started.So if you are enjoying this article consider purchasing a subscription and supporting more work like this.
Joking aside, it does seem that a mix of the two is nice. Bottom Up is boring when you just want to get things done and Top Down is magic until you try to leave the playground. The problem arises that each student will have different tolerances of each of those approaches.
Edit: Maybe an interactive book, or app, that lets you see a problem from both angles and let's you pick the problem you want to solve. Here is a problem: "Given this graph data summarize and display it". Bottom Up you learn DFS and Top Down you learn d3. With if you pick one or the other your given a library to fill in the part you don't like. You could always return and do the other part latter as well.
https://confluence.atlassian.com/sourcetreekb/sourcetree-sec...
One thing that worrying to me is that you include an 'undo' button that rewrites history. This is bad, as it could affect everyone downstream of you. That button should be turned into a 'revert' button.
Note: Not on the team, just searched the docs.
I'm curious about if you've done any research with this experiment yet and if so where can I find it? I'm very curious on ways to make programming more friendly/approachable, but I have found very little research that even begins to examine what a friendly/approachable programming language would even look like.
http://redux.js.org/docs/recipes/reducers/BasicReducerStruct....
Here are a few gotchas to avoid:
1. Define your state shape in terms of your domain data and app state, not your UI component tree.
2. Your reducers do not need to have a 1 to 1 mapping to actions. If you need to fire multiple actions to change the data you need then rethink your reducers.