xatxat

The AQ2 community perceived CS as way too slow though. No wonder when you are used to strafe jumping through team jungle and urban :-)

congratulations on launching! we created a website builder for nft artists called butiq.art where we will test the simplehash api in the next weeks.

on a side note, if you ever need nft data for the tezos blockchain, feel free to shoot me a message. i developed an nft indexer that covers that chain very well.

I think people with enough experience in software development know quite well if the code they are currently writing is going to be testable or not.

In Germany they are tracking down clusters. As a random person you won't get tested, unless you visited a risky region, had contact with an infected person or your doctor orders a test for you. As a German, this strategy makes sense to me.

I use this stack:

Frontend: React - Unstated (or just setState) - Axios - Plain CSS (with BEM notation) - Create React App - Prettier - Jest

Backend: Node.JS - Express - Knex - PostgreSQL - Tape

You can do that, but you will need to find a way to re-render the components which use that service, after something changed.

They are used to create arrays. You are able to subscribe to multiple containers:

  <Subscribe to={[CounterContainer, SomeOtherContainer]}>
      {(counter, someOther) => ()}
  </Subscribe>

Yeah, I agree that this is an edge case (nothing that I run into on a daily base) and the ContinentLists example might not be the best in this context. Something like a Dashboard with dynamic widgets would probably be a more realistic case.

I wouldn't store it as array in Redux because that would be too limiting (e.g. let's say I want a continent-list which is decoupled from the other continent-lists). If I would be forced to use redux in this case then I would create some random id for each ComponentList where I would store the UI state (but keep the continents data separated). Something like:

  {
    '<randomId>':
    {
        Asia:
        {
            collapsed: true
        }
    }
  }

Probably the ContinentsList component would somehow look like this:

  <ContinentsList
    continents={<continents data>}
    renderItem={({ collapse, isCollapsed, continent }) => {
        return <ContinentItem onCollapseClick={collapse} isCollapsed={isCollapsed} continent={continent} />
    }}
  />

For example if you have multiple lists of continents and each one needs its own collapsed state. Maybe the user can even dynamically add/remove such continent lists in the UI. IMHO in most of these cases it's best to keep the continents data inside of redux and have the collapsed state being managed by the "ContinentsList" component.

This one is also nice: https://github.com/sindresorhus/noop3 It has a noop factory :-)

Checkout the import() proposal:

https://github.com/tc39/proposal-dynamic-import

It basicly is what you are describing.

This could be a really nice replacement of Backbone.View.

http://dropandload.com Site for sending files to other people. Server just streams files through from the uploader to the downloader. Build with node.

I love this idea.

Is there a reason why you developed this as android app and not as a "normal" mobile website (navigator.geolocation)?