mihaiserban

import React, { useState } from "react";
import { SafeAreaView, Text } from "react-native";
import {
  Gesture,
  GestureDetector,
  GestureHandlerRootView,
} from "react-native-gesture-handler";

export default function GestureDemo() {
  const [tGestureStart, setTGestureStart] = useState<undefined | string>();

mihaiserban

import * as web3 from "@solana/web3.js";
import * as metadata from "./metadata"; // see metadata.ts

const tokenAddress = new web3.PublicKey(
  "CxkKDaBvtHqg8aHBVY8E4YYBsCfJkJVsTAEdTo5k4SEw"
);

(async () => {
  // Connect to cluster
  var connection = new web3.Connection(

mihaiserban

import {
  Account,
  clusterApiUrl,
  Connection,
  PublicKey,
  sendAndConfirmTransaction,
  SystemProgram,
  Transaction,
} from '@solana/web3.js';

mihaiserban

const web3 =  require('@solana/web3.js');
const splToken = require('@solana/spl-token');

(async () => {

    //create connection to devnet
    const connection = new web3.Connection(web3.clusterApiUrl("devnet"));

    //generate keypair and airdrop 1000000000 Lamports (1 SOL)
    const myKeypair = web3.Keypair.generate();

mihaiserban

Node.js on Apple Silicon

Node Version Manager (https://github.com/nvm-sh/nvm) works perfectly across native node installations as well as emulated Rosetta installations. The trick I am using here is to install one LTS version of node under Rosetta and another stable version as native binary.

TODO

• find a way how to run the same node version on both platforms

mihaiserban

'use strict';

const crypto = require('crypto');

const ENCRYPTION_KEY = process.env.ENCRYPTION_KEY; // Must be 256 bytes (32 characters)
const IV_LENGTH = 16; // For AES, this is always 16

function encrypt(text) {
  let iv = crypto.randomBytes(IV_LENGTH);
  let cipher = crypto.createCipheriv('aes-256-cbc', new Buffer(ENCRYPTION_KEY), iv);

mihaiserban

machine:
  node:
    version: 8
deployment:
  staging:
    branch: master
    owner: my-company
    commands:
      - ./deploy-staging.sh
  production:

mihaiserban

React Component Lifecycle

• getInitialState
• getDefaultProps
• componentWillMount
• componentDidMount
• shouldComponentUpdate (Update only)
• componentWillUpdate (Update only)
• componentWillReceiveProps (Update only)
• render

mihaiserban

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

mihaiserban

#Creating a Twitter bot with Node.js Learn how you can create your own Twitter bot using Node.js and the new Twitter API. The bot will auto retweet in response to tweets with some particular hashtags. (https://goo.gl/4whEIt)

##Tools we need Here are the tools we’ll be using to create the bot — 

• Node.js installed in your machine
• A registered Twitter account

Create a Twitter application