$ cloc
count lines of code.
Use as:
$ cloc ./
or$ cloc ./*.py
$ convert
convert .gif or .mp4 to many png frames
Use as:
$ convert -coalesce my_animatedfile.gif my_pngfiles.png
import { useState, useEffect, useRef } from 'react'; | |
import { useTracker } from 'meteor/react-meteor-data'; | |
import { Grapher } from 'meteor/cultofcoders:grapher'; | |
import { Meteor } from 'meteor/meteor'; | |
interface QueryInfo<T> { | |
loading: boolean | |
ready: boolean | |
data: T[] | |
error: Meteor.Error | null |
These are not to be blindly followed; strive to understand these and ask
when in doubt. Sometimes standards are a bad idea.
Don't duplicate the functionality of a built-in library.
ruby '2.7.1' | |
gem 'rails', github: 'rails/rails' | |
gem 'tzinfo-data', '>= 1.2016.7' # Don't rely on OSX/Linux timezone data | |
# Action Text | |
gem 'actiontext', github: 'basecamp/actiontext', ref: 'okra' | |
gem 'okra', github: 'basecamp/okra' | |
# Drivers |
# It is recommended that you save this script as an application, so you don't have to open Script editor. | |
(* | |
It all started when I wanted to join zoom faster than a human could do with no prompt like how I expected like this. | |
I first discovered zoom.us's URL scheme to join meeting, but when I found out it doesn't work, I started to make this program. | |
After this all of stuff, I finally have something that is constantly updated. | |
After this pandemic is over, development might slow down or become discontinued. | |
*) | |
global meetingNames, meetingIDs, meetingPwds, wname | |
# Compiling the app will reset all your saved meetings! | |
property meetingNames : {} |
// Backend | |
import formidable from 'formidable'; | |
export const config = { | |
api: { | |
bodyParser: false, | |
}, | |
}; | |
export default async (req, res) => { |
TypeScript 21 hrs 47 mins ████████████████▒░░░ 67.1% | |
Vue.js 6 hrs 21 mins ██████▓░░░░░░░░░░░░░ 19.6% | |
JSON 2 hrs 10 mins ████▒░░░░░░░░░░░░░░░ 6.7% | |
JavaScript 46 mins ███▒░░░░░░░░░░░░░░░░ 2.4% |
I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.
I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.
"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr
This fork of JamieMason's implementation changes the key
parameter to be an array of keys instead of just a single key. This makes it possible to group by multiple properties instead of just one.
const groupBy = keys => array =>
array.reduce((objectsByKeyValue, obj) => {
const value = keys.map(key => obj[key]).join('-');