Johannes Ewald
@Jhnnns
Followers
2K
Following
14K
Media
126
Statuses
6K
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. Member of the @webpack core team.
Augsburg, Deutschland
Joined January 2012
I haven’t tweeted anything for quite some time because I don’t like it here anymore. A couple of days ago I created an account at 🦋 and I have to say it’s way better 😀. You should switch as well. Feels like Twitter a couple of years ago.
1
0
0
Funny enough I came to the same conclusion :).Please follow this advice:.
I thought of writing about good errors, but the concept fits in a tweet. Look:. [<WHO>] Failed at <WHAT>: <WHY>. Please, please follow this. Thank you.
0
0
2
RT @EposVox: Wow, .io domains are going away. That's huge news.
every.to
How geopolitics can alter digital infrastructure
0
185
0
I‘d stick to CSS-in-JS. For me, it always had this separation into runtime vs. compile time flavors. There were plenty of compile time variants for quite some time (e.g. linaria, which I preferred over styled-components or emotion).
We’ve trying to come up with a new term for “compile time css-in-js” as that is awkward to say every time. Any ideas?. - Here’s a horrible idea to get us started:.JSStN (aka “Justin”) for JavaScript Styling Notation?.- CSS as JS?.
1
0
2
RT @rough__sea: I wrote this open letter because I believe the "JavaScript" trademark has been abandoned by @Oracle as defined in US tradem….
0
241
0
RT @philwalton: 📢 New post: The State of ES5 on the Web. For years, we defaulted to transpiling to ES5 in order to support IE. But is that….
philipwalton.com
Should web developers and JavaScript library authors still transpile their code to ES5? This post looks at what the data suggests based on what popular libraries, tools, and websites are doing
0
48
0
This works ridiculously well 😅.
I went overboard with the idea of using CSS as a HTTP server. Introducing ✨ Cascaded Server Sauce ✨. Thread 🧵
0
0
2
This 👇. Although I prefer short files, shorter is not always better :). When in doubt, keep code together in bigger files.
🗂 Splitting your code into multiple files doesn’t always mean better organization. Sometimes, it can actually make finding things more complicated. There's a lot of cognitive overhead in "what goes in this file" or "where do I put this code" that seems unnecessary.
0
0
3
RT @evenstensberg: We’re establishing a governance model for @webpack ! . Do you have any feedback about how the project should run? Do you….
0
1
0
RT @devongovett: JS needs a "standard" way of implementing conditional compilation that works across all tools. process.env is still the be….
0
10
0
Do I know anyone from the v8 team who is able to explain why `bigObject` is kept in memory? The inner queryFn doesn‘t reference it, hence it should be safe to discard (as long as no eval() and friends is used).
Problem: React Query keeps a reference to everything that was in scope when the queryFn is created. This may lead to a memory leak. Solution: Create a custom hook for each useQuery call (typically worth it anyway to support reuse and consistency). More:
0
0
0
RT @karlhorky: We recently migrated to ESLint v9 with Flat Config (somewhat painful migration). some things that we found out that may be h….
0
30
0
That’s an interesting idea for a JS bundler. My concern with this approach is that I don’t know how good the cache-hit ratio is in a real world scenario. Especially on mobile, browsers tend to purge caches more often (afaik).
I wrote a new type of JS bundler that can reduce download size and loading time:.
1
0
1
JSR looks really nice. Maybe that’s the new fresh start the JS ecosystem needs.
JSR - the JavaScript Registry - is now available in public beta. 🛠️ TypeScript first, ESM only.🌐 Works across runtimes (Node, Deno, Bun, workerd and more) and alongside npm/yarn/pnpm.🤗 Free and open source. Read about it on the Deno blog:
0
0
0