codelo-time.bsky.social
@codelo-time.bsky.social
Just wait until NaN is not NaN.
November 15, 2025 at 11:57 AM
Fight me
November 9, 2025 at 2:34 AM
I'm sorry to hear that 😞
Maybe one day you'll get over it 😜
June 19, 2025 at 11:10 AM
The error says 'Args is not an irritable' because Args is only any[] by default. Otherwise it is unknown.
January 24, 2025 at 11:42 PM
And here's some bad examples

```ts
const badExample1: MyObjFn<{ type: number }> = obj => undefined;
const badExample2: MyObjFn<{ type: Record<string, any> }> = obj => undefined;
```
January 24, 2025 at 11:39 PM
Here's some good examples

```ts
const goodExample1: MyObjFn<{ type: 'any literal value' }> = obj => undefined;

const someObj = { type: 'known type' }
type KnownTypeObj = typeof someObj;
const goodExample2: MyObjFn<KnownTypeObj> = obj => undefined;
```
January 24, 2025 at 11:38 PM
So, using extends in a generic lets you refine what the minimum matching type can be.

Take this example

```ts
type MyObject = { type: string }

type MyObjFn <T extends MyObject> = (obj: T) => void;
```

You are saying, T must be an object with the property `type` who's value must be a `string`
January 24, 2025 at 11:38 PM
I had a friend ask if it has something to do with the spread operator.

Sorry bud.

Firstly, that's a rest operator. Secondly, yes, the error is in the function arguments, but it's not a syntax error, it's a type error.
January 23, 2025 at 2:06 AM
Solid explanation. I think of it as more of a filter, like 'this type should extend something, if yes then narrow it down to a type, but if not then it's definitely this other type'
January 21, 2025 at 4:02 AM
Like, what even is infer?
January 21, 2025 at 3:36 AM
Just goes to show how much devs do not understand typescript
January 21, 2025 at 3:35 AM
Depends on your definition of decent. I would say I'm decent. People I've worked with would say 'god tier'. But i know god tier and I'm only decent.
January 20, 2025 at 10:04 PM
Ooft. Yea BASIC in any form is not great to use. But if someone was like "damn, that BASIC lang looks bussin asf, no cap" I'd slap them, then help them find a project to learn it. Let them find out why it's shit so they know what to avoid next time.
January 20, 2025 at 9:49 PM
Idk mang. Feels like saying anything is cut and dry when it comes to learning is reductive for how people learn. Maybe explain the differences of the languages and see what excites them?
An excited learner goes deeper, in my experience 🤷
January 20, 2025 at 9:41 PM
I've not tried bun, but i imagine it has it's own way of doing things that depend on either npm packages or bun's apis. Either way i bet it's not simple or cover enough situations, or we'd all be using it.
December 29, 2024 at 8:13 AM
December 29, 2024 at 8:09 AM
The only useful future ecma standard i see is type annotations. Where we can just ignore ts compiling and still get types/functional code. But i assume this will ignore some type annotations because of compatibility with ecmaScript.
December 29, 2024 at 8:08 AM
Webpack requires a phD. Vite breaks linters and ignores type errors. Deno droped support for bundling. Esbuild dropped modern build options.
December 29, 2024 at 8:04 AM
I find the tools very annoying as well. TSC does everything but bundle. Webpack does bundles but you need loaders for TS. Future es api support requires ditching ts for babel. All of these are inconsistent with the es module standard. And there's no simple, do everything bundler/compiler.
December 29, 2024 at 8:01 AM
First time, every time 🤙
a close up of a woman 's face with a hat on her head .
ALT: a close up of a woman 's face with a hat on her head .
media.tenor.com
December 13, 2024 at 10:02 AM
Uhhhhh... The first one?
a cartoon of a blue cat wearing a yellow shirt with cool cats written on it
ALT: a cartoon of a blue cat wearing a yellow shirt with cool cats written on it
media.tenor.com
December 13, 2024 at 9:58 AM
Seconded. Also, make `cosnt` keyword valid es6.
December 13, 2024 at 9:47 AM