Give it a whirl.
341 karma · joined November 27, 2019
Give it a whirl.
- After a while you associate the number with the subject so it becomes faster to visually scan a list.
- You can type the number faster. They are shorter to reference.
Eg Beetle observes kin dying via termite melee, encodes a potential solution in the DNA for the next generation.
The generator function keeps track of the current page.
This allows you to use a `for await` loop which is quite concise.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
You can do it without generator functions, but generator functions allows the caller to not have to know about the underlying pagination API.
I feel like this build step would still work in 5 to 10 years:
- esbuild is compiled into a single binary for each target system so has minimal dependencies.
- NPM makes the version immutable, and will download the same binary version on ‘npm install’.
- I will use .tsx as my extension but use only pure JS, this gets me IDE suggestions without writing TS types, which works well for small projects.
Compared to webpack, esbuild seems unbreakable.
What are the benefits over converting the CSV to a SQLite DB and using a DB GUI?
It works best when you are logging structured data in the form of JSON lines though, so you can query the JSON structure.
I quite like IndexedDB as it is widely supported by browsers.
Although for simple data I prefer the sync localStorage API.
IndexedDB can be shared amongst Web Workers for the same origin (localStorage cannot).
https://dexie.org is a nice IndexedDB library.
As an example, if you have many web workers, each can write their current state or use transactions to take items from a queue, and a central UI can just query the single IndexedDB.
Side note: I released https://tabserve.dev a few months ago.
It uses a browser tab and web workers as a reverse proxy to get a https url to localhost.
I released https://stay100.app recently.
It lets you view all stays in a grid with the final price you'll pay.
It gives you a https url for localhost by using your browser as a reverse proxy.
Take a look: https://tabserve.dev
I think there are options for adding the note folder to the PDF header too.
This gets you a read only archive that should be readable far into the future without needing a note reading app that understands Evernote’s export XML (just files and PDF).
Apple notes let’s you import Evernote XML too.
I think you either:
(1) start with the runtime code and derive the types (what TS does by default).
or (2) start with the types and derive the runtime code (like "macros" in some languages).
Does anyone have any suggestions for the best way to do this in a Node runtime?
You need to debounce/throttle the change event handler to not fire too many re renders when typing.
I used this approach for https://bigwav.app for highlighting text.
You can click the demo .bigwav file to take a look.
Tabserve adds a few extras:
- No need to install a CLI, safer as it is in the browser sandbox.
- Use the Chrome dev tools for observing requests.
- Config multiple reverse proxies on different browsers remotely.
- GUI.
The cloudflared tunnel also supports any TCP/UDP traffic, tabserve is just for http.
I think streaming HTTP responses may currently work. The client forwards the response back to the original client chunk by chunk (it does not wait for the entire response). I still have more testing to do.
You would take the same precautions as putting any other web server on the web - you might want to use a password or a hard to guess subdomain if you do not want others to access it. But I would assume you would be using test data in your dev environment.
The Cloudflare WAF (Web Application Firewall) also blocks requests to your web server. I think that is just DDOS protection.
Yes, `Access-Control-Allow-Origin: app.tabserve.dev` is correct, app.tabserve.dev is the origin where the fetch requests are made to your localhost.
- System calls call into the Linux kernel for things like disk and network access. These are highly tested and reliable.
To keep WASMs isolation and portability it would need to replace these APIs with new message passing ones which would kill performance.
- C FFI
- Dynamic libs
Being able to integrate with existing C libraries in the way they are intended to be used.
- Better VMs/OS level sandboxing
MicroVMs like Firecracker that let you run your code unmodified as if it is running directly on the OS.
I like WASM, but feel it is over hyped and the alternatives are “good enough” and already widely used.
In the browser it is great though.
I think what you mean is they are not meaningful to guide health decisions as they are too broad and can be further subdivided into more specific categories.
It allows you to observe and query your state in dev and prod.
Take a look: https://durafetch.com
It consists of server functions to add to your Cloudflare Worker and a CLI to download all Durable Object state to a local SQLite database.
Take a look: https://github.com/emadda/durafetch-server
Generally they seem quite expensive. I use GCP, very reliable though.