SimeonC
@simeon-c.bsky.social
Christian, Husband, Father, Coder, Photographer, Drummer.
Working at tablecheck.com
Working at tablecheck.com
Technically this works, but it’s way too difficult in practice unless you’re only using a single property.
October 3, 2025 at 11:36 PM
Technically this works, but it’s way too difficult in practice unless you’re only using a single property.
If it’s internal access to the class then what others say is all I’ve found. If you’re more interested in external access then a generic or sub class can work.
class A<TFoo = string | undefined > {
foo: TFoo = undefined;
setFoo(v: string): A<string> {
this.v = v;
returns this as never;
}
class A<TFoo = string | undefined > {
foo: TFoo = undefined;
setFoo(v: string): A<string> {
this.v = v;
returns this as never;
}
October 3, 2025 at 11:35 PM
If it’s internal access to the class then what others say is all I’ve found. If you’re more interested in external access then a generic or sub class can work.
class A<TFoo = string | undefined > {
foo: TFoo = undefined;
setFoo(v: string): A<string> {
this.v = v;
returns this as never;
}
class A<TFoo = string | undefined > {
foo: TFoo = undefined;
setFoo(v: string): A<string> {
this.v = v;
returns this as never;
}
I’m mostly just giving up. I too loved those too features, along with boosts (and I actually like the auto tab close feature 🥲). No other browser seems to come close unfortunately.
I’m currently using a very strange combination of Arc and Dia - here’s to hoping Atlassian can revive it.
I’m currently using a very strange combination of Arc and Dia - here’s to hoping Atlassian can revive it.
September 16, 2025 at 10:06 PM
I’m mostly just giving up. I too loved those too features, along with boosts (and I actually like the auto tab close feature 🥲). No other browser seems to come close unfortunately.
I’m currently using a very strange combination of Arc and Dia - here’s to hoping Atlassian can revive it.
I’m currently using a very strange combination of Arc and Dia - here’s to hoping Atlassian can revive it.
I think the 1 - 2 upgrade was so hard it just scared everyone off trying to upgrade again!
Our clients are also really sensitive to performance degradation in the UI which is really difficult to test (lots of perf optimisation done in) so just potentially a lot of effort that’s hard to justify.
Our clients are also really sensitive to performance degradation in the UI which is really difficult to test (lots of perf optimisation done in) so just potentially a lot of effort that’s hard to justify.
August 24, 2025 at 6:40 AM
I think the 1 - 2 upgrade was so hard it just scared everyone off trying to upgrade again!
Our clients are also really sensitive to performance degradation in the UI which is really difficult to test (lots of perf optimisation done in) so just potentially a lot of effort that’s hard to justify.
Our clients are also really sensitive to performance degradation in the UI which is really difficult to test (lots of perf optimisation done in) so just potentially a lot of effort that’s hard to justify.
Thanks for the explanation! Makes sense
August 23, 2025 at 12:16 PM
Thanks for the explanation! Makes sense
😆 we haven’t managed to upgrade off of ember 2 yet so that’s a pretty hard sell internally!
August 23, 2025 at 12:16 PM
😆 we haven’t managed to upgrade off of ember 2 yet so that’s a pretty hard sell internally!
The API for this just feels very out of place against other “standard” libraries (well, what passes for standard in react is uncomfortably close to flavour of the month) like tanstack query.
My company has 1 ember and many react projects and have want to change to react only, so very keen on this!
My company has 1 ember and many react projects and have want to change to react only, so very keen on this!
August 23, 2025 at 11:22 AM
The API for this just feels very out of place against other “standard” libraries (well, what passes for standard in react is uncomfortably close to flavour of the month) like tanstack query.
My company has 1 ember and many react projects and have want to change to react only, so very keen on this!
My company has 1 ember and many react projects and have want to change to react only, so very keen on this!
🤔 is this the same reason to MobX needing a higher order function wrapping each component so it can track the used variables needed for reactivity? Each of those “state callback props” are there to help with the reactivity tracking - is that right?
August 23, 2025 at 11:17 AM
🤔 is this the same reason to MobX needing a higher order function wrapping each component so it can track the used variables needed for reactivity? Each of those “state callback props” are there to help with the reactivity tracking - is that right?
Nice! The `Request` component seems a bit odd to me, just from comparison to all the other react kind I use - any reason it’s not as a useRequest hook?
August 22, 2025 at 11:07 AM
Nice! The `Request` component seems a bit odd to me, just from comparison to all the other react kind I use - any reason it’s not as a useRequest hook?
Still have to support older safari versions, one day, one day… 😭 (though I really should prepare for that day and find some excuse to try them out 😆)
August 19, 2025 at 10:12 PM
Still have to support older safari versions, one day, one day… 😭 (though I really should prepare for that day and find some excuse to try them out 😆)
I’m using asdf, mostly cause I have to switch more than just node versions
August 11, 2025 at 11:25 PM
I’m using asdf, mostly cause I have to switch more than just node versions
Wow, that’s amazing work!! This might actually be enough to give me confidence to get beyond just trying out biome/oxlint or similar and still keep that confidence from the typed eslint rules.
July 10, 2025 at 9:32 PM
Wow, that’s amazing work!! This might actually be enough to give me confidence to get beyond just trying out biome/oxlint or similar and still keep that confidence from the typed eslint rules.
My Pro Tip: git worktree for each feature branch. Means I can have one cursor window for each features branch too (poor man’s background agents)
July 4, 2025 at 11:27 AM
My Pro Tip: git worktree for each feature branch. Means I can have one cursor window for each features branch too (poor man’s background agents)
Nice, last time I tried this I got a few of the open issues you’ve been working on. Looking forward to having another go
June 17, 2025 at 11:49 AM
Nice, last time I tried this I got a few of the open issues you’ve been working on. Looking forward to having another go
Thanks for the insight.
April 15, 2025 at 11:05 AM
Thanks for the insight.
How different is it from danger.systems/js/ ?
Danger JS
Apply cultural rules during your CI process.
danger.systems
April 10, 2025 at 10:19 PM
How different is it from danger.systems/js/ ?
Yea, that was the point my boss was making. AI is disrupting coding in the same way the printing press disrupted making books. I’m coming to terms with this being the “Industrial Revolution” for coding.
March 15, 2025 at 1:09 AM
Yea, that was the point my boss was making. AI is disrupting coding in the same way the printing press disrupted making books. I’m coming to terms with this being the “Industrial Revolution” for coding.
Personally I’m a “very pretty handwriting” kind of coder so it’s a struggle for me to accept my skills are now becoming obsolete.
The analogy helped me come to terms with the change
The analogy helped me come to terms with the change
March 14, 2025 at 11:14 PM
Personally I’m a “very pretty handwriting” kind of coder so it’s a struggle for me to accept my skills are now becoming obsolete.
The analogy helped me come to terms with the change
The analogy helped me come to terms with the change
This would have been my answer before I helped my Japanese wife with her English as second language learning materials!
February 16, 2025 at 12:59 AM
This would have been my answer before I helped my Japanese wife with her English as second language learning materials!
Yea, I think they’re looking for C as that’s the one that says the car is physically being planned to be fixed. B is the classic “could” doesn’t necessarily mean they will do it. A is what we “normally say” but that doesn’t actually mean the car will be fixed same as B 😅
February 16, 2025 at 12:57 AM
Yea, I think they’re looking for C as that’s the one that says the car is physically being planned to be fixed. B is the classic “could” doesn’t necessarily mean they will do it. A is what we “normally say” but that doesn’t actually mean the car will be fixed same as B 😅
Don’t worry, after about two months your Vite setup becomes just as duct taped as webpack ever was. My goal with upgrading was modern simplicity standard - my vite config is a monster now 😅
February 12, 2025 at 10:40 PM
Don’t worry, after about two months your Vite setup becomes just as duct taped as webpack ever was. My goal with upgrading was modern simplicity standard - my vite config is a monster now 😅