It's not for ignorance, all other such cases in history were unsustainable. There must be some special element that makes it more enchanting that is known only to those privy. Even 'escapies' can't explain the phenomenon, how can any outsider?

Internal viewpoints of Russia of fully opaque, I don't understand how you can shut up a nation this big, I don't believe that there's a nation this politically active with so little insurgency. Whatever is being done there, it's scary effective

Most other news arenas don't have this many interested parties and individuals so motivated to shift the narrative. Even reports on the Chinese/Vietnamese border disputes contain less noise and misdirection. It's crazy

What makes the french special?

But yes, Israel is reciprocatingly hostile towards Hezbollah. The population is generally very happy for Syria and Syrians. The government is terrified citing instability and religious motivation, and their action is criticized internally as an overreaction

I can tell you from intimate knowledge that most sources host propaganda and lies about Israel as well, both positive and negative. It is extremely hard to find reliable info on Israel as all parties engage in misinformation.

This makes more sense, which sources can be reliable? I do mean reliable, I'm not looking for propaganda from either side. As an outsider I'm far too vulnerable to misinformation like that, I want to form my own opinions

I heard that Hezbollah has assisted the rebels, why would an Iranian proxy help? Why would the rebels accept Iranian help? I'm asking honestly, this is quite confusing

Cut my index.js bundle by 95% today, feels good to ship just 7kb js, feels ~fast~

I still don't understand what it means to build 'a' firehose... You can use `Stream` `PubSub` `Mailbox` to stream messages, each with regards to a different source and use case.
effect-cluster is not required for transaction semantics, it's for durable distributed flows. Context is sufficient

The `Stream` abstraction is a low level building block over the `Channel` primitive. The central idea is to expose an interface for building effectful stream processing pipelines. I can empathize with the complexity of streaming, but don't think it's fair to call `Stream` opaque or under-specified

you're thinking eagerly about streams, declaring them does not execute them. `Stream` mere describes a steam, it is not the thing itself. It's is lazy. You must execute it to start a stream. So it's more accurate to say you're creating another `Stream` from a `Stream`.

no, they are 2 totally different and unrelated streams, they happen to be a composition over the same stream, but not the same execution. Run a stream 300 times, you will get 300 different unrelated streams

correct

basically, you just use the the built in DI system and it's pretty straightforward. Just not so short to fit in 300 chars lol

you are being dead serious, I know you are, because that's exactly what I do

what do you mean firehose?
db-transaction semantics can be found in the `.withTransaction` method in `SqlClient` as part of the `@effect/sql` and it's implementations

almost, partitioning a stream allows for one side to consume elements faster than another by placing a buffer, simply filtering would drop the filtered values outright. unless the filtered streams are broadcasts of a single stream, that can mean losing values

almost, partitioning a stream allows for one side to consume elements faster than another by placing a buffer, simply filtering would drop the filtered values outright. unless the filtered streams are broadcasts of a single stream, that can mean losing values

what it means to retry a stream depends on the source of the stream. But it is important to distinguish between retying a steam and *replaying* a stream. Retrying a stream just means to open a stream again after it emitted an error

bsky.app/profile/datn...

also take a look at how `Schema.NonEmptyTrimmedStringOption` is implemented (just go-to-source in your ide)

just use `Schema.optional(Schema.NonEmptyString)`, you can also brand it and trim it
```ts
Schema.NonEmptryTrimmedString.pipe(
Schema.brand("Foo"),
Schema.optional,
)
```
Etc etc, no need to overcomplicate

Yes, it's `.from` property.

I am not sure what you mean by 'generic', all schema constructors are generic. requiredToOptional take 2 schemas, `from` and `to`, and an object with 2 methods to go back and forth between them.

`Schema.propertySignature` explicitly wraps a schema into a properySignature schema. This let's you use propertySignature transformations on it, for example `Schema.fromKey` to map a different key from the source to the one you use

What do you mean?

yeah, because spoilers: he is not from this century, he is also not actually a frog. You should play Chrono Trigger again, it's really good.

I didn't

I didn't say gritty. Viva Piñata is whimsical, vibrant, magical, filled with fun time and silly stories with wacky characters. it's also not infantile and *internally* realistic. You're conflating grittiness with realism

nonsense, Chrono Trigger was internally realistic and coherent. What a poor example. You're infantilizing fantasy by claiming that it's fantastic nature means it's innately unrealist or arbitrary