Tim Cook, as CEO of a public company, is incentivized to deliver shareholder value.

Entering this market with a good product does just that.

Beyond that, this is an entry point for people to use Apple products. It can be bridge to get this consumer to buy more premium hardware and software later on.

If anything I perceive a bit more mistakes when I have to do things in TS (and in a way simpler domain, in a way smaller project).

Heavily using Claude Code to build my own kanban and a Cloudflare native headless CMS meant to feed Astro websites.

With so many mechanisms for creating users and posting en masse, I find it really hard to believe the contents of any comment or post I read that goes past a paragraph or two. And of course I am still skeptical even if it is less than 2 paragraphs of text.

I find the contents of that specific post hard to believe. Specially since the user hasn't participated in the conversation at all.

I like this place a lot and it saddens me we are just going to see more of this.

Not sure what you guys were trying exactly and what tools you had at your disposal.

However, I am glad this happened. New Linux Ambassadors will step up and this issue will be buried into the alternative social media communities such as Mastodon, never to be heard of again.

I disagree that Framework will lose a meaningful amount of business over this.

1. https://world.hey.com/dhh/as-i-remember-london-e7d38e64

Now we can argue how good or bad the nodejs (or any alternative JS implementation) is. At the end of the day the objective is most likely to rock the boat enough to be acquired and have a payday. With enough discipline you can get far before the footguns show up.

To me it is bending the original tool (JS, async driven, weak typing) to fit a purpose it was not made for (hard typing, synchronous) in detriment of what it is that makes the tool good in the first place (IO performance).

My understanding is that Zod performs synchronous operations to validate the schemas. Something about "using the tool correctly" resonates here. Maybe don’t validate very large and nested schemas frequently and things like that.

But I can’t help but think it is adding another layer of potential footguns that you have to be mindful about. Maybe the benefits outshine the risks in disciplined teams that understand both the tool and the runtime. However I can’t help but think about the less disciplined teams abusing Zod and then wondering why things are slow.

Are you making the assumption he, as an EM that codes, has the coding skills of an intern?

I have recently came back to the topic of software engineering always "having" to keep up.

At the end of the day what keeps me going is the creative opportunity (specifically trimming out the block and carving out a statue) and the fact that this is the closest I will ever be to be a wizard.

With the setup you described I just felt I had to write more, even if it was in the same language.

NextJS/React covers a massive talent pool, so you will inevitably get less experienced candidates going through your pipeline until a good one shows up.

You might not spend as much time if you were tapping into the markets of say Clojure or Elixir, maybe even Go. Not telling you to change your stack, just highlighting the differences in talent pool size and quality.

Be transparent with the compensation from the get go. If you are trying to tap LATAM markets, good devs are reaching (close to, but still a bit far) US salaries, so offering 70-80k for a Senior role won’t guarantee a Senior dev.

If you are experienced, Rails/Laravel but I'd loop Clojure in too.