aigoochamna

Using an SPA to reduce server load, when you could generate this content and use edge caches and have zero server load?

I'm more upset with the new design choices than the architecture choice. The old site was ugly in a retro-cool way. The new site is just ugly.

Thousands will thrive. Startups have always been a Ponzi scheme.

The winners are the ones that grab funding now, achieve growth and sell quick to hand the bags to someone else.

Sounds honest to me. A site designed to help students cheat is being replaced by an AI that is more than willing to help you cheat. Seems like it would legit hurt their business.

Thanks for the X-Clacks-Overhead header and reference. I just went down a whole rabbit hole researching it.

Go

Feels like I read this announcement yesterday. Time flies!

A thinkpad x220?

> It's 2023, how do you choose between MySQL and Postgres?

Easy, you pick Postgres. There's no reason to ever use MySQL.

How big is that file... I have 2TB files compressed down to ~300GB and gunzip'ing them takes ~2-3 hours. Granted, that's still a long ass time, but not 2-3 days.

If anything, I wonder what kind of hard drive John has. If you're reading them off a network drive backed by tape drums it's probably going to take a while ;P

I have rewritten my blog a few times...

From a static HTML/CSS site to Ruby on Rails. From Rails to a pure Go MVC with my own templating format. From the custom Go server to static HTML/CSS on Github pages; to finally a Next.js with server side rendering and using markdown with frontmatter.

I think the point of blogging is to do crazy things you can't get away with at work :)

I wouldn't say bundling started with babel... but was predated by browserify and other bundlers... oh the days of gulp/grunt and browserify...

http://phrack.org/issues/7/3.html ?

I used to use a custom build script to do deploys (scp a binary onto a monolith server, execute a script; systemd restart www.service, etc). Worked fine for years. It would continue working fine, too.

I moved to Vercel and adopted a fairly serverless approach and leverage edge functions and edge caching where ever possible. It has been wonderful and I don't see myself ever going back to doing things myself. Sure, I could spin up some AWS services and figure it all out myself, but the freedom Vercel has given me has been worth the added cost. As a solo founder it has been amazing.

No more worrying about security, access control, updates, or anything other than my own product and features. I don't care how it works. I don't want to know. I just want to continue improving my product.

Exactly why I clicked on it. Hopefully has more responses than mine did!

Red bull and cocaine.

I somewhat get where htmx is coming from. It's not bad per-say.. I actually like the general idea behind it (it's sorta like Turbolinks, but a bit more optimal using fragments instead of the entire page, though Turbolinks requires zero additional work on the markup side and works with JavaScript disabled out of the box).

With that being said, I imagine it would become unmaintainable very quickly. The problems htmx is solving are better solved with other solutions in my opinion, but I do think there's something that can be learned or leveraged with the way htmx goes about the solution.

Sounds to me like Google is butt hurt they got out played with their own research.

Why not offer a bare bones subscription, like $2.50 per-month and charge by usage volume every month?

LiveOverflow has a simple explainer and demonstration of this in two videos:

https://www.youtube.com/watch?v=Sv5OLj2nVAQ

People have been using AI and machine learning since the beginning of the web. Googles very search has been using ML for years.

I argue we have already been using these technologies, they merely got better and more available.

What I did was talk to the designers I worked with. I got to know their tools. I even did some 1:1 sessions with them after work learning design basics. I taught them some coding, they taught me design.

Right... there are a lot of contradictions in their comment. You want to focus on your product, by managing your own server(s)? You don't want to over engineer early on but you're running a load balancer and n-servers? Why not a single server? Or, offload the management entirely to someone else and focus on your product.

Vendor lock in? Next can be self hosted, deployed on AWS/Amplify/Lambda, your own hardware, etc. I wouldn't say it's as locked in as some other solutions out there.

You can't "protect" yourself. The only protection you can build is by building a moat of some kind-- like building your business on data or some core knowledge only you know about, something that isn't easily replicated by anyone else.

That being said, there's a very high chance your product doesn't fall into the category above. You likely have no defense against the threats you perceive.

I would urge you to focus on building a better product faster than the big players. Do things they can't do (like good customer service, make it personable, things that can't scale, etc).

I started learning React a few days ago (for Next.js). It's not Native, but it's similar I guess. What has been working for me?

Read the React docs (do the tic tac toe project work, go through all of their fundamental/learning docs). Then build some small things.

Metaversarial Networks

Is anyone else bothered by tossing chemicals all over your dishes? I imagine this wouldn't work or be feasible with a more health conscious detergent.

Meditations by Marcus Aurelius

Hmmm but Windows is shit.

Infinite Jest, written in 90s and predicted Netflix and others.