theThree

I don't know if I'm the only one experiencing this: It's too hard to find the download link from their website.

I developed a JS pg client that use pipeline mode by default: https://github.com/stanNthe5/pgline

I'm using Bun, but I avoid using any Bun.* function, because I don't want to bind my typescript project to a runtime.

It's still not ready for use. I don't care Enum. But you can not import local files without extensions. You can not define class properties in constructor.

It still have issues. Example: `import foo from "./Foo"` doesn't work. You have to `import foo from "./Foo.ts"`

Something like this?

async function runTasks(tasks: Job[]) { for (let task of tasks) { try { await task() } catch (e) { } } }

Async/await is the only thing prevent me from using Rust.

Good to see there is already a preview version (@typescript/native-preview). Can tsc/ts-node use it now?

The fastest PostgreSQL Node driver written in TypeScript: https://github.com/stanNthe5/pgline

Will do that. Thank you.

You can still control it by adding "//no-await". In fact, the "//no-await" makes me feel more clear.

From my own testing. In high-concurrency scenarios, their performance is roughly the same, and Node uses less memory. When it comes to string concatenation, Go has to do a lot of extra work (no "+",Estimating string length, Preallocate memory ) just to catch up with the speed of Node (simply using "+").

Maybe at some point. Their vsCode extension has 1M downloads, while Bun has 155k.

In web backend, Node.js is not slower than Go.

    function f1(a:number, b:number, c:number, d:number) {
        [a, b] = [b, a]
        [c, d] = [d, c]
        console.log(a, b, c, d)
    }

For the above codes Typescript gives error message: Type 'number[]' is not assignable to type 'number'.

>That means you have 1 GiB in the pool.

This only happen when every request last 1 second.

Chinese are unable to visit ChatGPT.

Can anyone explain to me what is "TypeScript types“?

The appeal of Go is goroutine.

> a, b := 20, 30 // accepted. why ??

I guess it is a dept of error handling. Otherwise you have to write "foo,err1 := Foo();bar,err2 := Bar(),.."

Context is useful in many cases. In go I have to pass ctx from func to func. In nodejs I can easily create&use context by using AsyncLocalStorage (benefit of single-thread).

OK,just now I tested the new version and it is still slow.

Use "npx create-expo-app@latest --template default@beta" to install new version. Start with production mode, using android device, it takes about 300ms to render 2000 Views. The same test on React web is still much faster.

Only the "recommended" section.

I did a performance test last year, rendering thousands of views, and Flutter's rendering speed was 5 times faster than React Native. I wonder if this version will be improved after the update. Interestingly, I used React on the web to render the same number of views, and its speed was much faster than React Native.

When will `worker` API be ready for production?