curtisblaine

This reminds me of https://github.com/electric-sql/d2ts. Not sure they're comparable, but they seem to be aiming at the same problem.

Question: aren't you allowed to photograph or film anyone you want in public? Or the target being underage somehow removes this right? I always thought you can film whoever you want, but you can't publish what you filmed in some cases.

the cultural values that a detached elite wish to impose on their offspring for life have been transposed into law, policy, and regulation, and from there, into the personal lives of young people

Isn't this what happens in Islamic countries all the time though?

"Tightening" and "wiring" something. You're not in the construction industry, you're writing unit tests for a cookie modal.

Logseq is a mystery to me. They used to have a web version that they discontinued to "concentrate on the product", and that's where they lost me. I assume they "concentrated" on the app and the desktop version, presumably to get some revenue from their sync service, which is understandable, but it could have been executed better. Fast forward a couple of years and I see they're incomprehensibly pivoting to split the product in two. If it's strategy, I can't understand it.

Nobody says that React is great (also) because it's industry standard. If you pick up a React codebase you instantly understand how a component renders, where its state is, what its effects are, which components render that component etc. If it's React with a decent linter configuration, it's even easier. With a custom framework, on the other hand, you're at the mercy of who invented it. You have to find where state is, you have to trace where the state is "teleported" via broadcast, you have to understand where side effects are invoked etc. If the custom framework is as good as React, I'd still choose React just because it's a de factor standard.

I see benchmarks for cold start, why there are no benchmarks for runtime performance Vs Node, Deno and Bun? (and quickjs et al.)?

Many definitions of tool explicitly exclude body organs to draw a line between innate mechanisms that are inestricably linked to the body and objects used to extend one's innate physical or mental influence on the environment. The eye is not a tool, according to these definitions, but eyeglasses are.

What is a good tool that's invisible? I'm genuinely curious. All tools I've used are either simple and heavily limited (so, not "invisible" because hard things are hard) or powerful but heavily specialized (so, not "invisible" because the learning curve is very evident). I feel the trade off is inescapable.

And some are more tied to the globalist and progressive-for-the-sake-of-progress views of their current founder. Why not let users pick their poison?

If A = −1: Read one keypress from the human operator and place a number representing it into slot[B]. (If no key is pressed, place 0.)

If B = −1: Display slot[A] as one character of text to the human operator.

This is not well specified imho:

1) What if both A and B are -1? I can't do any of the two, or I would read / write an invalid slot (since slots indexes are >= 0)

2) What does "Read a keypress" mean? Should I wait for the operator to press a key? In that case, how can no key be pressed? Timeout? Or should I just check if a key is already pressed when the instruction is executed?

Do you mean traders set up buy or sell orders and they get matched when market opens? That's... Just how markets work normally?

No. I want either:

1. The copyright infringement of big corpos fully justifying my copyright infringement in the face of law

2. The copyright infringement of big corpos being prosecuted in the same exact way as my copyright infringement would.

There is really no middle ground.

The only scary thought is that all these important operations don't have a plan B if prosemirror, a software they don't write, don't own and presumably don't pay, goes away.

Maybe I'm stating the obvious, but nobody has any moral obligation to be inclusive in content they share on their personal blog, for free, and nobody should reasonably expect it.

How do you bundle web workers that import dependencies? iirc the issue in esbuild for that is still open and users are manually building their workers as separate entry points, which is very fragile.

@afavour if you need precompilation in CI can't you simply use... tsc?

Don't we have `tsx` and `nodemon` (or the native Node reloader) for that? What are the DX gaps you see on the server side out of on-the-fly transpilation and reload on watch?

I'm always curious of the use case when someone proposes Node code bundling. What's the advantage? Obfuscation in SEA?

Normally "improvements" penalize group A to favour group B; if group A is the majority, they will outvote the "improvement" in any democratic process.

What are the open source, easily hostable forum platforms available in 2026? I remember I looked at the oss web-based self hosted chat platforms not long ago and I found they were all either abandoned or had crippling limitations if you didn't pay for the closed version. I wonder if that's the same for forums.

As a brand new user, I see a lot of posts obscured by moderation. What I'm saying is that bsky is not only block lists: there's moderation applied without opting in to it, right off the bat. I created a new user just to try it, I went to the Babylon Bee's bsky account and all its posts are covered by a banner right out of the box.

As a brand new user, I see a banner covering the posts. I didn't opt in to any list or moderation settings. Yet, some posts are hidden from my sight and I have to explicitly opt in to see them.

That's not true though. If many people or the mods flag a post, other people cannot see it without clicking - it's covered by a banner. I have a new user on bsky, I never touched any configuration knob and by default I can't see certain posts. Someone decided for me.

If I were truly able to decide what I see I would see every single post as a new user. Then I would have the optuon to opt in to lists, banning / hiding other users etc.

Instead, I'm forcefully opted-in to not seeing what someone else decided I shouldn't see from the start, and I must find the way to opt out.

@phillipcarter: of course it's users (and mods) doing that, but in the end, if you open bsky today you see a single, huge, left-biased social media. If you look at Mastodon, you see at a lot left-leaning trans-and-furry-friendly instances, true, but you also see a bunch of right wing instances plus Gab. What happens with bsky today (single instance, echo chambered) is simply something I don't expect from a "distributed" social network. Why is that?

My question was in good faith tbh; I see other protocols (Mastodon, nostr) not being really commercially relevant but being much more politically diverse than bsky. I was wondering why is that - is something inherent to the protocol (e.g. I heard that it's extremely hard to set up your "alternative bsky" if you don't have resources, unlike Mastodon instances, so you're not really incentivized to just do it and see how it goes) or is it just bad luck?

"Censored" I mean "flagged", sure. In practice, they're all hidden from the casual user. But really, I'm interested on why ATProto was touted as revolutionary while in practice it powers a standalone heavily politically biased social network where moderators are extremely active flagging everything that's on the right. In that respect, Mastodon is more "revolutionary" - you handle your instance, you provide your moderation, you optionally integrate with other instances. Mastodon itself is used, in practice, to moderate a highly diverse ecosystem of social networks, from the gay-friendly ones to Gab. Nostr, although it's not so widely used, is even more tailored against sectarism by default.

From what I see, Bsky is a single instance of one of the most politically aligned social media in existence; in practice, you can achieve that with any proprietary implementation, you don't need ATProto. I honestly thought that the protocol was engineered to prevent an echo chamber, but in reality it powers an enormous standalone echo chamber that is not moving anywhere, so I was wondering what's the difference.

#2 is very much used in high performance web apps, whenever you can't afford the overhead of message passing. I agree it's a specialized tool and normally you don't need it, but it's a misrepresentation to say "it's an obscure feature that almost nobody uses". If you do webGL, for example, you almost invariably end up using shared array buffers.

You bypass GC by allocating pools of array buffers at the cost of low-level memory management.

Worth noting that javascript has had workers, shared memory and atomics for years and that you can use them today. Look at this guy writing a lockless allocator: https://greenvitriol.com/posts/lockless-allocator

The only difference in this PR is that it makes threads light (workers are fat because they carry a whole v8 instance with them) and it makes shared memory default with light threads (now you need to pass a shared array buffer first).

Javascript is probably not your first language, I get it, but it has had "the siren song of a mutex" for years now. What really surprises me and I can't explain is why you went and took time to express such strong opinions on something that you obviously don't even know or use that well.