Petri Kola pe3

## README.md

      
              4 files
            
          
              4 forks
            
          
              1 comment
            
          
              169 stars
            
          
                acutmore
                / README.md
            
            
              Last active
              January 21, 2024 20:30
            
              
                Emulating a 4-Bit Virtual Machine in (TypeScript\JavaScript) (just Types no Script)
              
          
    A compile-time 4-Bit Virtual Machine implemented in TypeScript's type system. Capable of running a sample 'FizzBuzz' program.
Syntax emits zero JavaScript.
type RESULT = VM<
  [
    ["push", N_1],         // 1
    ["push", False],       // 2
 ["peek", _], // 3

  
## adaptive_intent.md

      
              1 file
            
          
              1 fork
            
          
              3 comments
            
          
              10 stars
            
          
                swyxio
                / adaptive_intent.md
            
            
              Created
              May 3, 2019 08:04
            
              
                an adaptive, intent based CLI "state machine"
              
          
    an adaptive, intent based CLI "state machine"

one realization from working on Netlify's CLI is that the CLI framework we used, oclif, didn't provide a great user experience out of the box.
Emphasis on great: it does a lot of nice things, like offering flag and argument parsing, help documentation, and pluggability. That's good for the CLI developer. But what about the CLI user?

Idiomatic oclif code often checks for required preconditions, and if it doesn't exist, it prints a warning and then process.exit(1).
Decent code prints a helpful warning telling the user what they got wrong. It is informative.
Better code offers a prompt, creates a file, or something similar to solve the precondition before proceeding. (possibly recursively). It is intent-based.
Great code remembers past inputs to prompts and uses that to offer useful defaults. It is adaptive.


## disease_outbreaks_camelot.ipynb

      
              1 file
            
          
              7 forks
            
          
              2 comments
            
          
              18 stars
            
          
                vinayak-mehta
                / disease_outbreaks_camelot.ipynb
            
            
              Last active
              November 5, 2023 18:54
            
              
                A jupyter notebook showing how Camelot can be used to extract tables from PDFs scraped from the IDSP website.
              
          
      Sorry, something went wrong. Reload?
      Sorry, we cannot display this file.
      Sorry, this file is invalid so it cannot be displayed.
      
          Viewer requires iframe.
      
    
## index.html
<body>
<div id="⚛️"></div>
<script src="https://unpkg.com/react@16.0.0/umd/react.development.js"></script>
<script src="https://unpkg.com/react-dom@16.0.0/umd/react-dom.development.js"></script>
<script src="https://unpkg.com/babel-standalone@6.26.0/babel.js"></script>
<script type="text/babel">
ReactDOM.render(<div>Hello World!</div>, document.getElementById('⚛️'))
</script>
</body>

## data-interchange.md

      
              1 file
            
          
              4 forks
            
          
              7 comments
            
          
              163 stars
            
          
                evancz
                / data-interchange.md
            
            
              Last active
              April 29, 2024 16:53
            
              
                Why do I have to write JSON decoders in Elm?
              
          
    A vision for data interchange in Elm

How do you send information between clients and servers? What format should that information be in? What happens when the server changes the format, but the client has not been updated yet? What happens when the server changes the format, but the database cannot be updated?
These are difficult questions. It is not just about picking a format, but rather picking a format that can evolve as your application evolves.
Literature Review

By now there are many approaches to communicating between client and server. These approaches tend to be known within specific companies and language communities, but the techniques do not cross borders. I will outline JSON, ProtoBuf, and GraphQL here so we can learn from them all.

  
## *tracked.md

      
              5 files
            
          
              3 forks
            
          
              7 comments
            
          
              49 stars
            
          
                developit
                / *tracked.md
            
            
              Last active
              December 10, 2020 18:48
            
          
    tracked 

@tracked is a decorator for Preact that makes working with state values no different than properties on your component instance.
It's one 300 byte function that creates a getter/setter alias into state/setState() for a given key, with an optional initial value.  The "magic" here is simply that it works as a property decorator rather than a function, so it appears to integrate directly into the language.
tracked has no dependencies and works with any component implementation that uses this.state and this.setState().
Installation


## direcorySize.ts
export function directorySize(path: string): Promise<number> {
  return readdirRecursive(path)
  .reduce((result: any, a: any) => {
    result += a.stat.size
    return result
  }, 0)
}

directorySize('./node_modules')
.then((size) => {

## 100+ different counter apps...
100+ different js counter apps...

## react-ramda-example2.js
import React from 'react'
import ReactDOM from 'react-dom'
import { createStore, combineReducers } from 'redux'
import * as R from 'ramda'

// composition helper
const combine = R.curry((c, o) => x => (<div>{c(x)} {o(x)}</div>))
const combineComponents = (...args) => {
  const [first, ...rest] = args
  return R.reduce((acc, c) => combine(acc, c), first, rest)

## fetchUser.js
async function fetchUser(username) {
    const [user, orgs, repos, starred] = await Promise.all([
        fetch(`${api}/users/${username}`),
        fetch(`${api}/users/${username}/orgs`),
        fetch(`${api}/users/${username}/repos`),
        fetch(`${api}/users/${username}/starred`),
    ].map(p => p.then(r => r.json())));
    return {user, orgs, repos, starred};
}
	<body>
	<div id="⚛️"></div>
	<script src="https://unpkg.com/react@16.0.0/umd/react.development.js"></script>
	<script src="https://unpkg.com/react-dom@16.0.0/umd/react-dom.development.js"></script>
	<script src="https://unpkg.com/babel-standalone@6.26.0/babel.js"></script>
	<script type="text/babel">
	ReactDOM.render(<div>Hello World!</div>, document.getElementById('⚛️'))
	</script>
	</body>
	export function directorySize(path: string): Promise<number> {
	return readdirRecursive(path)
	.reduce((result: any, a: any) => {
	result += a.stat.size
	return result
	}, 0)
	}

	directorySize('./node_modules')
	.then((size) => {
	import React from 'react'
	import ReactDOM from 'react-dom'
	import { createStore, combineReducers } from 'redux'
	import * as R from 'ramda'

	// composition helper
	const combine = R.curry((c, o) => x => (<div>{c(x)} {o(x)}</div>))
	const combineComponents = (...args) => {
	const [first, ...rest] = args
	return R.reduce((acc, c) => combine(acc, c), first, rest)
	async function fetchUser(username) {
	const [user, orgs, repos, starred] = await Promise.all([
	fetch(`${api}/users/${username}`),
	fetch(`${api}/users/${username}/orgs`),
	fetch(`${api}/users/${username}/repos`),
	fetch(`${api}/users/${username}/starred`),
	].map(p => p.then(r => r.json())));
	return {user, orgs, repos, starred};
	}