Johannes Ewald
@johannesewald.de
I've been using Vim for about 2 years now, mostly because I can't figure out how to exit it. Co-founder of @peerigon. Previously working on @webpack.
Oh ok, that’s a political reference, I didn’t get that. Nevermind 😃
April 1, 2025 at 10:56 PM
Oh ok, that’s a political reference, I didn’t get that. Nevermind 😃
I have a vague idea, but I always forget what is what 🥲
April 1, 2025 at 10:54 PM
I have a vague idea, but I always forget what is what 🥲
I thought esbuild produces a single file but maybe there‘s an option
March 19, 2025 at 7:38 PM
I thought esbuild produces a single file but maybe there‘s an option
What tool does Node use under the hood?
March 19, 2025 at 7:37 PM
What tool does Node use under the hood?
Is it? Did you check every digit? 😃
March 14, 2025 at 12:21 PM
Is it? Did you check every digit? 😃
Yes, it was meant to be abstract, not about TypeScript.
March 14, 2025 at 12:02 AM
Yes, it was meant to be abstract, not about TypeScript.
Is this something experienced Rust developers would solve easily or is it something that is just really hard in Rust?
(I‘ve encountered this in my pet project and I gave up 😅)
(I‘ve encountered this in my pet project and I gave up 😅)
March 13, 2025 at 6:07 PM
Is this something experienced Rust developers would solve easily or is it something that is just really hard in Rust?
(I‘ve encountered this in my pet project and I gave up 😅)
(I‘ve encountered this in my pet project and I gave up 😅)
That’s so cool to see it in a real-world project 😃
February 25, 2025 at 6:37 PM
That’s so cool to see it in a real-world project 😃
Thank you! 🙏 So it‘s not useless 😌
February 23, 2025 at 6:05 PM
Thank you! 🙏 So it‘s not useless 😌
To be fair: I don’t maintain it anymore because I don’t use it. I gave edi9999 maintainer rights but they‘re doing a great job as far as I can tell :)
February 23, 2025 at 5:57 PM
To be fair: I don’t maintain it anymore because I don’t use it. I gave edi9999 maintainer rights but they‘re doing a great job as far as I can tell :)
As far as I remember I needed a safe way to evaluate expressions without using eval(). I was using Angular.js in a different project back then so I decided to extract "the good parts" ;)
So nice to hear that it’s still of great use for you 😌. What‘s the topic of your talk?
So nice to hear that it’s still of great use for you 😌. What‘s the topic of your talk?
Angular.je
February 23, 2025 at 5:57 PM
As far as I remember I needed a safe way to evaluate expressions without using eval(). I was using Angular.js in a different project back then so I decided to extract "the good parts" ;)
So nice to hear that it’s still of great use for you 😌. What‘s the topic of your talk?
So nice to hear that it’s still of great use for you 😌. What‘s the topic of your talk?
Hat mich auch erwischt 😅🥵
February 21, 2025 at 3:12 PM
Hat mich auch erwischt 😅🥵
Not sure what you mean. I don’t see any error in my playground…
February 21, 2025 at 6:31 AM
Not sure what you mean. I don’t see any error in my playground…
This summarizes my experiences with AI coding assistants so far. After my initial reservations, I started to appreciate them for quick feedback or easy refactorings.
They’re impressive for the first 50% of the task, but I often hit the point where I think it would be faster now to do it by hand.
They’re impressive for the first 50% of the task, but I often hit the point where I think it would be faster now to do it by hand.
February 12, 2025 at 8:28 PM
This summarizes my experiences with AI coding assistants so far. After my initial reservations, I started to appreciate them for quick feedback or easy refactorings.
They’re impressive for the first 50% of the task, but I often hit the point where I think it would be faster now to do it by hand.
They’re impressive for the first 50% of the task, but I often hit the point where I think it would be faster now to do it by hand.
I don’t know but I wish they’d use Array<Type> as the canonical form :)
February 10, 2025 at 9:15 PM
I don’t know but I wish they’d use Array<Type> as the canonical form :)
I hate that AIs are still bad at refactoring code. There‘s so much refactoring that‘s too sophisticated for string replace but too dumb for humans 😃
February 8, 2025 at 11:08 AM
I hate that AIs are still bad at refactoring code. There‘s so much refactoring that‘s too sophisticated for string replace but too dumb for humans 😃
That‘s what I did :) I decide against rules that complain about code that works and isn’t flawed in some other way.
I asked @mattpocock.com the other day and he also turned it off
I asked @mattpocock.com the other day and he also turned it off
February 8, 2025 at 10:36 AM
That‘s what I did :) I decide against rules that complain about code that works and isn’t flawed in some other way.
I asked @mattpocock.com the other day and he also turned it off
I asked @mattpocock.com the other day and he also turned it off
Regarding skipLibCheck: I agree with your sentiment but I often find myself turning it on it big projects. It’s mostly necessary because of conflicting types in node_modules (e.g. Cypress bringing their own type definitions for Mocha, etc.).
February 7, 2025 at 10:35 PM
Regarding skipLibCheck: I agree with your sentiment but I often find myself turning it on it big projects. It’s mostly necessary because of conflicting types in node_modules (e.g. Cypress bringing their own type definitions for Mocha, etc.).
Regarding exactOptionalPropertyTypes: it sounded very promising, but it complained about lot of code that was just ok. Most of the time people don’t distinguish between non-existing properties and undefined and it’s kind of ok.
February 7, 2025 at 10:35 PM
Regarding exactOptionalPropertyTypes: it sounded very promising, but it complained about lot of code that was just ok. Most of the time people don’t distinguish between non-existing properties and undefined and it’s kind of ok.
Regarding noUncheckedIndexedAccess: I‘d turn it on. I don’t think it‘s about holes, but rather indices out of bounds. I saw several instances where it caught actual bugs in sloppy code.
February 7, 2025 at 10:35 PM
Regarding noUncheckedIndexedAccess: I‘d turn it on. I don’t think it‘s about holes, but rather indices out of bounds. I saw several instances where it caught actual bugs in sloppy code.