Hi, I'm Alex Kates 👋 I'm a product engineer currently working at Croissant as a Founding Engineer. I'm addicted to writing about building, and building things worth writing about. Some extracurriculars include AWS Community Builder Instructor at MIT xPRO Bootcamp Volunteer at Tech for Campaigns
Nothing here yet.
That's exactly what I have, and it's worked pretty well. If I was buying one today though, I'd double the memory. I found it can start to crawl when I have both emulators, a Next.js app, and a couple other apps like slack, dbeaver, linear, etc all running.
Neil Douglas I respectfully disagree. This isn't a religious take, but a practical guide for choosing between JavaScript and TypeScript in 2023. It's a persuasive article, not just personal preference. While "use the tool that makes you happy" sounds good, it's not practical in a professional setting with real financial stakes. Why not write an article sharing your own perspective?
Thanks for your comment, Neil. I feel like I presented a fair argument for why someone should use TypeScript in 2023. Do you have an argument for why someone should pick JavaScript instead? I only used the word "need" once in the summary, and I may edit that out because I don't want to be dogmatic about it. This has just been my experience.
