What's your moat? From my personal experience, it's very easy to get openai to summarise text like this so it seems any email company could implement a similar feature pretty quickly.

Email is one out of the many channels pitchers and investors are communicating through today. While there is some summarizing involved in the process that's not the product. Pitchportal learns what the investor is interested in din and not.

Could an email company create an alternative to pitchportal, sure they could but they wouldn't create a solution for every single motive for communication. They wouldn't create a competitor to Instagram because people are sending photos via email.

What gives pitchportal a moat is that for every minute an investor is using pitchportal, it is getting way better at predicting intrest. Down the line if there's a competitor, they wouldn't have the data that we have collected.

I would suggest you stick with it. Docker compose is very powerful once you get the hang of it and it can be used to deploy straight to AWS etc.

But no, you're not a bad person if you give up. Remember that each time you restart a container it goes back to it's original state. Apt update should be done during the image build.

There's unlikely to be a self-driving image dataset bigger than Google reCAPTCHA's. Maybe scale is the key to operating more safely.

My email address has been used by someone in America to sign up for an online fashion brand. I get emails of their receipts every time they buy new clothes.

More recently, they signed up to some tanning salon and I got a receipt for a Brazilian wax!

Proven

Webpack is much slower because it's written in JS. Vite uses esbuild to compile, which is written in Go. That's probably why you saw the speed up.

Vite uses esbuild under the hood. It can also create bundles with all your deps, which is essential when you don't want an npm i step involved during deployment (lambdas/containers).

To be clear, it is esbuild that bundles not vite.

esbuild index.js --bundle --outfile=build.cjs --format=cjs --platform=node

You can use pkg then to make this bundle executable.

pkg build.cjs

This is not vite. :-)

Fair point. But vite makes this easier than esbuild. I get a bundle that's immediately executable with node

Vite uses esbuild only during development, in the build it uses rollup.

Yes, I've noticed that. So to debug problems I need to know both rollup and esbuild, and how exactly Vite configs boil down to configs for these two.

Has this happened to you? I expected this to happen to me, but I’ve never noticed a disparity.

I've run into problems with Vite when I was using it for electron, and I could not figure out how to fix it. I needed to create a new project from scratch. Vite seems in general to be fast moving, and software depending on it breaks easily.

Why though?

> "I won’t bore you with the story of how WP Engine broke thousands of customer sites yesterday in their haphazard attempt to block our attempts to inform the wider WordPress community regarding their disabling and locking down a WordPress core feature in order to extract profit.

> What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.

If you read the full (pretty short) statement, it comes of as something written at the end of a bad day with a lot of petty and vindictive emotion behind it all. Regardless of the actual issues, which I know no more of than the statement on the website.

https://wordpress.org/news/2024/09/wp-engine-banned/

Copilot is useful for auto completing glob or writing a simple regex. Anything more complicated and it will often make mistakes. Finding mistakes in 20 lines of AI generated code is slower than writing it yourself.

Mesmerising