teg4n_

Needing bespoke svelte-specific tooling for _everything_ is pretty annoying when it comes to developer experience IMO. It is just overly custom when you could use something like solid and have similar performance but easy tooling integration due to just being typescript and tsx syntax. Like you can’t use typescript 7 right now in svelte, oxlint / oxfmt doesn’t fully support svelte either among other things like storybook’s mcp server not supporting svelte.

I mean it does cost you API rates, you just get a certain amount of credit by having a subscription.

The LLM actually points out the problem tho

Rome tools is now Biome and Biome is really good. The company didn't work out but the tool itself is better than ever.

it sounds like you might have wasted your team's time previously and now they don't trust the code you put up with a PR. Maybe you can do something to improve your relationship with them?

As a sidenote, I highly doubt they are cooked longterm. Using AI is not exactly skilled labor. If they want or need I'm sure they could learn patterns/workflows in like an afternoon. As things go on it will only get easier to use.

The iPod came out way before Zune.

That's not remotely true.

How? If the attribute is not trusted doesn’t that mean the dom is already compromised?

Yes, it’s fair.

Yes, people that never participated are more impactful.

Its place is in shit like recommendation algorithms and giving rewards and incentives to customers, not store operations. When will they learn :\

This isn’t really true with React Native, Hermes as a JS engine is just drastically slower than JIT-enabled web view . Sure the “native” parts will theoretically be faster but your app code will be a lot slower. Just test how long a rerender takes in react native on a device than react on a browser for the same device.

And cross your fingers it didn’t make them up?

Militaries don’t normally enlist 42 year olds unfortunately.

What 4 year old gets dopamine from watching people have sex? absolutely bonkers