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
| /** | |
| * return HH:mm:ss format | |
| * | |
| * @param milliseconds time in milliseconds | |
| * @return the string time format with HH:mm:ss | |
| * @throws ParseException | |
| */ | |
| private static String getTimeFormat(long milliseconds) throws ParseException { | |
| long totalsec = milliseconds / 1000; | |
| long hourPart = totalsec / 3600; |
This is the CFP for my React Rally talk, which was eventually accepted and given here: https://www.youtube.com/watch?v=nyFHR0dDZo0.
If you are a first time speaker, my CFP advice for new speakers is here.
Functional-reactive libraries like RxJS make it easy to understand how data changes, giving us tools to declaratively handle events and manage state. But while our render methods react to state changes, React isn’t reactive. Instead, we write imperative event-handlers, and trip up on gotchas like async setState and race conditions. Why? In this talk we build a Reactive React to show the difference between the "push" and "pull" paradigms of data flow and understand why React chooses to manage Scheduling as a core Design Principle, enabling awesome features like async rendering and Suspense!
Theme: This talk is a deep dive into React's core design principle around scheduling. Instead of abstr
This is work in progress
I read about the .NET Generic Host for the first time in a Tweet of David Fowler. And I was hooked by the idea, it was just what I was looking for.
I like modules making things small but fit together like pieces of a puzzle, if possible being able to reuse them. I started refactoring Greenshot over a year ago, and was making modules out of the spaghetti code that it was. Trying to extract the modules into their own nuget packages, making them more generic and testable. I glued them together with some code I wrote, which is availble in Dapplo.Addons, but I knew that this was just a journey, until I found something that is a better with more potential.
I found the following description: _The purpose of Generic Host is to enable a wider array of host scenarios. Messaging, backg
The response to my first few posts has been much larger than I’d imagined and I’d like to thank everyone for the encouragement.
If you’re interested in building a trading system I recommend first reading my previous post on general ideas to keep in mind.
My first really technical post will be on how to build a limit order book, probably the single most important component of a trading system. Because the data structure chosen to represent the limit order book will be the primary source of market information for trading models, it is important to make it both absolutely correct and extremely fast.
To give some idea of the data volumes, the Nasdaq TotalView ITCH feed, which is every event in every instrument traded on the Nasdaq, can have data rates of 20+ gigabytes/day with spikes of 3 megabytes/second or more. The individual messages average about 20 bytes each so this means handling
p5.js sketch that finds eye positions from the webcam and draws a representation of their movement, with random colors for the irises.
Click on the canvas to save an image; press a key to clear the canvas.
This sketch was very helpful in getting started with clmtrackr 🙏
Like PHP's htmlentities()/htmlspecialchars() functions, JavaScript is easy to implement it.
/**| import boto3 | |
| from PIL import Image | |
| from io import BytesIO | |
| import os | |
| class S3ImagesInvalidExtension(Exception): | |
| pass | |
| class S3ImagesUploadFailed(Exception): | |
| pass |
| #!/usr/bin/env python | |
| # details on rabbitMQ password hashing | |
| # https://www.rabbitmq.com/passwords.html#computing-password-hash | |
| from __future__ import print_function | |
| import base64 | |
| import os | |
| import hashlib | |
| import struct | |
| import getpass |
<path to chrome>/chrome.exe --remote-debugging-port=9222/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222google-chrome --remote-debugging-port=9222