Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jitl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
23 ms
·
481.
▲
by
jitl
1y ago
Because building local first with web technologies is like infinity harder than building local first with native app toolkits. Native app is installed and available offline by default . Website needs a bunch of weird shenanigans to use App
482.
▲
by
jitl
1y ago
A web request to a data center even with a very fast backend server will struggle to beat 8ms (120hz display) or even 16ms (60hz display), the budget for next frame painting a navigation. You need to have the data local to the device and id
483.
▲
by
jitl
1y ago
people say this about inline styles too but Notion built a 100 million user business with them ¯\_(ツ)_/¯
484.
▲
by
jitl
1y ago
You can still do this if you want, table element still exists and works the same way.
485.
▲
by
jitl
1y ago
I would only expect type stripping, although it seems you already have the TypeScript language server hanging out in the editor for completion and docs and such, it’s not much extra challenge to get the VFS hooked up enough to show red squi
486.
▲
by
jitl
1y ago
it’s so much easier to fix this in NextJS compared to other stacks though, I have done it a few times where I end up w secret using code in the client while prototyping but it’s just a single line of text at the top of a file to make it ser
487.
▲
by
jitl
1y ago
I used the older online notebooks for a bit and really loved the immediacy but I’m always hurting for TypeScript syntax support. The is this a thing w 2.0? Something I’ll need to add later with Vite and only available locally? It was a bunm
488.
▲
by
jitl
1y ago
Where should secrets come from then? Burn them into the deployable artifact??? Place them on the host filesystem in perpetuity???
489.
▲
by
jitl
1y ago
> just so a secret (of any kind) is never required on the client This is how web clients usually work though not NextJS special at all. You have a HTTP only cookie for authentication and proxy requests through your backend to authorize c
490.
▲
by
jitl
1y ago
This is a pressing concern for anyone trying to move large amounts of text data in and out of WASM. The batching makes good sense, I should try this for SQLite result sets!
491.
▲
by
jitl
1y ago
We don’t report your habits to any data broker. This information use used purely for local UI.
492.
▲
by
jitl
1y ago
If you ask Notion to record will record if you don’t ask to record, we won’t record
493.
▲
by
jitl
1y ago
Yep, completely agree.
494.
▲
by
jitl
1y ago
let me look EDIT: no, there's no transmission of logs or analytics events besides a check to see if the feature is enabled. We only transmit some data if you ask Notion to record.
495.
▲
by
jitl
1y ago
Notion doesn't like making things opt-in. A feature that's opt-in will get like 1% of the use of a feature that's opt-out. A happier middle ground would be to enable by default and show a "I don't like this, pls tur
496.
▲
by
jitl
1y ago
To elaborate: The Notion desktop app will observe if there is a process running on your computer that is actively using your microphone, such as Zoom. Notion does not and cannot listen to the audio coming from your microphone ambiently or s
497.
▲
by
jitl
1y ago
Yeah, I think I'm conflating our fear of >5000 connections for our Postgres workload (read-write that is quite write heavy) with our SQLite workload, which is 99.9% read. The way our SQLite workload works is that we have a pool of h
498.
▲
by
jitl
1y ago
Postgres has really not solved problems that come with being a networked server and will collapse under concurrent connections far before you start to feel it with SQLite. 5000 concurrent connections will already start to deadlock your Post
499.
▲
by
jitl
1y ago
Postgres will shit itself without a connection pooling proxy server like PGBouncer if you try even like 5000 concurrent connections because Postgres spawned a UNIX process per inbound connection. There’s much more overhead per connection in
500.
▲
by
jitl
1y ago
It depends hugely on how you decide to manage the connection objects. If you have a single thread / single core server that only even opens a single connection, then connection open overhead is never a problem even under infinite load.
501.
▲
by
jitl
1y ago
Yes: SQLite needs to inspect the schema when it opens a new connection object and does some O(number of conns) lookups in global state during this process. It’s best to avoid re-doing this work.
502.
▲
by
jitl
1y ago
It’s pretty explicitly targeting cloud cluster training in the PR description.
503.
▲
by
jitl
1y ago
Rust exists
504.
▲
by
jitl
1y ago
If you want to use rust, and it fits your use case, then use rust. Same as with any language choice if it’s the right thing for you then go ahead. I have a few million lines of existing TypeScript so will keep using JS runtimes for the fore
505.
▲
by
jitl
1y ago
esbuild is very stable and mature at this point, Rolldown is still rapidly evolving.
506.
▲
by
jitl
1y ago
The go imports use a Google-owned proxy for resolution which has a vulnerability facility. All golang package installs use the Google-owned proxy unless you set GOPROXY=direct when running go commands. https://arc.net/l/
507.
▲
by
jitl
1y ago
Back in the day, Sun Solaris and HP-UX were not end-of-life, and FreeBSD had more equal industry footing with Linux. Now Linux is the clear winner in server OS UNIX by a wide margin. Also, Ryan Dhal worked at Joyent, a Illumos/Solaris
508.
▲
by
jitl
1y ago
Less segfault, improved security / capability model
509.
▲
by
jitl
1y ago
Well the project goal seems to be extreme minimalism and stdlib only, and the choice of human readable data stores and manually editing the user list suggests a goal is to only need `vim` and `sha256sum` for administration
510.
▲
by
jitl
1y ago
Minimalism. It’s tiny and its data can be completely administered with `vim` and `sha256sum` Given the setup I’d guess it makes sense for little household scale apps w/ a user list in the low tens of people.
More ›