Comments URL: https://news.ycombinator.com/item?id=32665559

Points: 1

# Comments: 1

We have tried to show the most important events in the history of space exploration: first spacecrafts, flights to other planets and landings on celestial bodies.

We believe that achievements in space belong to all mankind. We believe that space exploration is a significant step in the evolution of our civilization.

Comments URL: https://news.ycombinator.com/item?id=22348417

Points: 1

# Comments: 1

> Until today’s meeting, the friendly Agile consultant at my company has spent his time photoshopping the team leader’s face onto pictures of Yoda, and researching the motivational properties of various colours of magic marker. And he gets paid for it.

Comments URL: https://news.ycombinator.com/item?id=20894000

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=20500960

Points: 3

# Comments: 3

Functional UI is still need some sort of imperative shell [1] to manage state. You can use OOP and Remold just for "reactive" behaviour, and implement all state transitions inside object in a functional way. For example:

    // Pure function
    const addProduct = (order, product) => ({
        total: order.total + product.price,
    });
    
    // Imperative state
    class Order extends Remold {
        state = {
            total: 0
        };        

        @act setState(newState) { this.state = newState; }

        addProduct(p) { this.setState(addProduct(this.state, p)); }
    }

From the React Documentation about Context feature [2]:

> Apply it sparingly because it makes component reuse more difficult.

With Remold you don't have any problems with component's reusability. You just attach pure component to an object and "connect" object's state into component's props:

    // Pure component
    const OrderWidget = ({ total }) => 
{total}
;
    
    // Pure function
    const addProduct = (order, product) => ({
        total: order.total + product.price,
    });
    
    // Imperative state
    class Order extends Remold {
        state = {
            total: 0
        };        

        @act setState(newState) { this.state = newState; }

        addProduct(p) { this.setState(addProduct(this.state, p)); }
        
        @mold(OrderWidget) asWidget() { return { total: this.state.total }; }
    }

[2] https://reactjs.org/docs/context.html?no-cache=1#before-you-...

I realised that I just want to have many views connected to one dataset, and I want to re-render all connected views when dataset was changed. This is a simple pub-sub pattern which everyone can implement himself. So, I implemented it myself in just 65 lines of code. I use this solution in production for 6 months and don't see any drawbacks.

What are the advantages of Redux or MobX over this solution?

Comments URL: https://news.ycombinator.com/item?id=19770423

Points: 12

# Comments: 5

I've read "Code Complete", "Clean Code", "Extreme Programming Explained" and thought that "real" developers solve interesting problems and write maintainable and high-quality code covered by unit tests. I was wrong.

"Real" development and "real" products are crap. When you develop an internal tool you do it because of necessity. In contrast, when you develop a new feature for a "real" product you do it because of a manager's whim. After two years in web development and after reading HN I conclude that "real" development almost always goes together with inadequate deadlines, shitty requirements, and high level of stress. I'm one step away from burning out.

I want to change something in my career. Should I move back to Automation QA/Programming of Internal Tools? Have you had the same problem in your career and what decisions have you made?

Comments URL: https://news.ycombinator.com/item?id=19708875

Points: 1

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=19681114

Points: 1

# Comments: 0

Vue is different. With it, you can't confidently use your previous programming experience.

Comments URL: https://news.ycombinator.com/item?id=18959957

Points: 1

# Comments: 0

  const

  create_store = ({state, actions}) => {
    const

    after_update_do = [],

    subscribe = fn => after_update_do.push(fn),

    notify = () => after_update_do.forEach(fn => fn(state)),

    create_action = action => (...args) => {
      state = action(state, ...args);
      notify()
    };

    return Object.entries(actions).reduce((bound_actions, [action_name, action]) => 
      Object.assign({}, bound_actions, {[action_name]: create_action(action)}), 
      {subscribe})
  },

  counter = create_store({
    state: 0,
    actions: {
      increase: state => state + 1,
      
      decrease: state => state - 1,

      multiply_add: (state, a, b) => state * a + b,
    },
  });

  counter.subscribe(state => console.log('First reactive component was updated with: ' + state));
  counter.subscribe(state => console.log('Second reactive component was updated with: ' + state));

  counter.increase();
  // First reactive component was updated with: 1
  // Second reactive component was updated with: 1

  counter.multiply_add(2, 3)
  // First reactive component was updated with: 5
  // Second reactive component was updated with: 5

Comments URL: https://news.ycombinator.com/item?id=18254214

Points: 101

# Comments: 28

Comments URL: https://news.ycombinator.com/item?id=18227705

Points: 4

# Comments: 0