lauchness

Sad Ash Ketchum | Senior Software Engineer

[lauchness @lauchness1]

It's pretty dope to work @Lazer_HQ

[Lazer @Lazer_HQ]

Lazer started so we could build and ship amazing products.

5 years, 350+ clients, 40+ YC companies, 20+ unicorns.

And we still love what we do.

https://t.co/dCQgsCmYJr

[Billy Strings @BillyStrings]

I’m gonna wake up and change my ways one of these days

[lauchness @lauchness1]

@Rich_Harris @cayt3r @jarredsumner This sounds like a great hit single

[lauchness @lauchness1]

Lookout @graphprotocol, https://t.co/cPAWgyFjnR is coming in hot 🔥

[lauchness @lauchness1]

@rohan10 @ryanflorence Fair enough, seems like we agree.

My verbiage wasn’t conveying my issue with Apple - they have control issues and the AppStore is a tool to enforce their control on products.

[lauchness @lauchness1]

@leeerob - using pages router, can I have code that is bundled for the *server only* if the code is used in `getServerSideProps`?

I've got some larger modules that I don't want to send in the client bundle, but they seem to get in there when used during SSR

[lauchness @lauchness1]

@ryanflorence How else would you fetch data? A loader function? A useFetcher hook? Don't be silly, clients are made for fetching, servers are made for delivering clients that fetch. /s

[lauchness @lauchness1]

@ceeoreo_ Invest in a decent guitar.

Learning is hard, learning on a poor instrument is nearly impossible.

Try and find a community to play with, even if it's just close friends. Playing with people helps you improve exponentially.

Best of luck!

[wilson.base.eth @WilsonCusack]

Trying to test cross-chain interactions can be annoying. Made this repo to help. Currently supports creating L1 -> L2 calls, using event logs, the way the Op-Node does.

PRs welcome :) https://t.co/krfXqdVjYB

[lauchness @lauchness1]

@sweetrobin9000 😂🤣

[lauchness @lauchness1]

@sunglassesface 🤣😅

[lauchness @lauchness1]

@GuilbertPaul Fair - I have a flair for the dramatic 😅

It wasn't a great experience though. Had to run the app as a containerized node.js app, which lost out on features that would have "just worked" in vercel.

And yes - the remix templates seem to work well.

[lauchness @lauchness1]

Out of the last 3 apps I've built for clients:

- Next.js App router - was a nightmare to deal with deploying outside vercel (for their completely unreasonable pricing)
- Next.js pages router - ran into issues due to Next overriding fetch
- Remix - incredible to build and deploy

[Kent C. Dodds 🏹 @kentcdodds]

I get asked about this a lot (especially since the launch of Epic Web), so I've written it down.

Here's why I won't use Next.js:

https://t.co/crVN7hOszL

[lauchness @lauchness1]

@vessjs The client had existing infra they switched to.

I have not used Open Next - may need to in the future if something like this comes up again.

[lauchness @lauchness1]

@dillonraphael @Railway Had to run it as a Node application, which lost out on a lot of the features that would have "just worked" on vercel. Builds/deploys ended up taking a looong time, which was not fun for hot-fixes.

Not impossible, just not great - which is sad, because Next was my go-to

[lauchness @lauchness1]

Can only say good things about working with @0xinsanity https://t.co/ofpqGSjqxZ

[lauchness @lauchness1]

@sweetrobin9000 🤦

[Tristan Guest @tristan_guest]

Messing around with HTML canvases.