codeptualize

Supabase + Next.js is what I'm using.

To cover your list:

- Auth: Supabase has auth, with oauth support for many services. Also prebuild UI for login forms etc. It's really easy to set up

- Live updates: Supabase has a realtime api to send messages, or subscribe to db changes

- Database: Supabase is basically a Postgres database with a bunch of stuff on top, it generates a REST/GraphQL api from your schema, meaning you don't have to make endpoints.

It's incredibly productive as it covers all the basics. It's open source so you are not locked in, and they have a free plan that will get you quite far.

For the frontend Next.js is my preference, but you could opt for other frameworks if you are more familiar with them. Next.js on Vercel is really easy to set up with preview builds, automatic deployments etc.

It seems that Microsoft is the big winner in this story, well played.

Personally I have no shortage of ideas, only lack of time and resources to execute on them. This is true for most founders I know (can't say if that's representative).

I also don't think ideas are very valuable. Great founders can make amazing companies from seemingly average, boring or even bad ideas. On the flip side, bad execution can easily ruin incredible ideas.

Could you maybe elaborate on what you mean by "startup ideas"? As frequently you start with a problem that you try to solve, often based on your experience and skills. Could you maybe provide some examples? That would make it much easier to respond meaningful.

Sure, that might be true on paper, but if you have the ability to turn off the money faucet you have a lot of leverage regardless of what the documents say. No espionage drama needed haha.

If you then imagine being dependent on that investor not only because your service runs on their infra but also your biggest enterprise customers use your service through their infra, you are even more incentivised to listen to them..

A real power struggle! How exciting. It goes to show that no matter the structure, when it comes down to it the investors always have the last say.

Haha if you think about it like that, it seems like he managed to ingrain some of his methods into the culture..

haha that would be next level, and indeed entertainment for weeks to come

This is Elon level recklessness.. is he involved in any way?

I agree, the way they did this just shows incompetence and recklessness.

Even if they are making the right call, you can't really trust them after ruining the reputation and trust of the company like this.

This is ridiculous haha.

Another great example that even huge multi billion dollar companies are lead by people. What a mess.

However this plays out, this is a big wake up call for everyone who is currently dependent on OpenAI. More changes will be needed to restore trust. It's going to be messy for a while. For a company that has executed pretty much perfectly until now it's so surprising how they just ruined their reputation like this.

Obviously the comparison is not one to one, different time, different traffic, different event, and number of upvotes is not the main measure of importance.

That said, this is pretty big. OpenAI is a wildly successful company and as CEO Sam Altman is one of the big players in that.

Not only was he fired, but he was fired unexpectedly and very publicly, this rarely happens. Usually companies try to prevent the media storm that is happening right now by quietly moving people to less important roles and or they “want to spent more time with family” or “are looking for another challenge”.

So it’s not just the firing of the ceo of one of, if not the most, successful startups of this time, it’s completely unexpected, and the wording suggests something really big has happened or will be happening, or the board is making reckless decisions, which would be newsworthy on its own.

Not having all the information makes people wonder what’s going on adding to the attention as we all speculate on what’s going on and how it is going to change things.

Another factor in this is that a lot of startups and companies rely on OpenAI making it directly relevant to a lot of people, especially those on this website.

I wonder what you want to get out of this, and what damage his clone is causing you and your project?

I've had my website cloned before and I totally get the feeling and absurdity of the situation, but realistically there is not a lot you can do without it (negatively) impacting you as well.

I think it's good to message this person, as they probably should include your license, maybe indeed make people aware, but at some point it might be better to let it rest and focus your energy towards your project.

Especially if it's not really a threat to your project (and it doesn't look like it is as your project seems like it's doing quite well, congrats!) you could wonder if the best course of action is to just not give it any attention at all.

This is exactly as I expected it would end. We'll see this happen again, and again, and again.

Some politician gets the genius idea to have backdoors in encryption, initial support, then reality sets in and the plans are abandoned.

There is just no sensible way to implement this, therefore it's not going to happen.

This iteration did go a bit further than usual.

How are you going to do the updates without FE logic? Refresh the page constantly?

The client being able to fetch just updates is a lot more efficient. If you open a web socket the server can even push.

You make a great point why we use client side solutions.

Could be! If it has a bunch of interactivity it will probably make your life a lot easier.

Idk if you know js/ts and React, so there might be some learning involved. (You could also check other fe frameworks if React is not your jam, some folks swear by Vue or Svelte.)

About knowing what’s going, I get that. For me I’ve wasted so much time setting up projects with webpack and all the the other stuff that I have a pretty good idea, but also I’m just thankful that I can just focus on my project haha.

This article had as a “good” example a div with an onclick, I think he fixed it, but it shows a lot..

Frameworks also have linters that will help a lot, it’s on you to use them

It looks like the latter, and loaded blocking as well.. I get it, convenient, but that's not really great for the argument.

https://html-first.com/stylesheets/tailwind-full.css 68kb of blocking unused css.

In total ~100kb of blocking scripts and styles. Most frameworks would optimize this for you out of the box..

Could be, but also just page transitions, think a blog, documentation site, often you keep the navigation and just replace the content. If you are curious, it's quite easy to try. The results are really snappy, it's really nice.

But, I'm not trying to convince you. If you are happy with Pelican and it works for you, great.

All I'm pointing out is that we use these things because they do actually solve problems, often make things faster not slower, and allow me to make better websites and apps for my users. From simple websites, to complex applications.

And it's totally fine if it works you, I'm not saying one is better, I'm saying both are valid choices and if you statically export from a framework, it's not that different from what you describe.

> Frameworks force the dev into specific ways of doing things

Not really. Take Next.js, you can also use markdown (or more dynamic flavors of markdown like MDX/markdoc), you can use a headless cms, it doesn't really matter..

If you don't like Next.js you can pick a different solution, there are many! If Pelican is your jam, by all means, it's a great tool.

> I'm curious what you guys need on your sites that require so much JS.

In my day to day I work more on web apps, but lets stick to "simple" websites. Example: Using Next.js again, out of the box it does instant navigation by preloading new content on hover, and not doing full refreshes when they aren't needed. Great for the user, less bandwidth used, much faster sites. That's just one example.

If you statically export you won't even notice, and when navigating it will actually be a lot faster when only the content is replaced..

Have you checked this is the reason? not slow network? and not ads/analytics and blocking assets? That's not exclusive to frameworks btw, and probably less likely as most optimize these things for you.

The website that is linked originally has a bunch of blocking assets.. lighthouse score is not amazing either.

Just like the original article, you might want to test your assumptions a bit more.

This looks really helpful! As someone learning Rust these are a lot of the things I wonder about but can be quite hard to find good information on.

So pelican and hugo are not frameworks? How is a static site generator any different from statically exporting next.js/nuxt.js or similar?

I've used all the things mentioned, and I quite like the ergonomics of frameworks for static websites. Added benefit is that I can make static sites dynamic if necessary.

And to be clear, these static exports are incredibly fast and performant.

> you could roll your own SSG in a weekend

Sure, I could do that, or I could build my app/website in that weekend..

> "Not that complex"

Even if you have a fully static website you generally have a navigation bar and footer that needs to be on multiple pages.

Things don't need to get very complex to benefit from frameworks and tooling.

> We use static-tailwind, a version with no build step, in development.

So you do use a build step for production? Or are you shipping a bunch of unused styles?

Another good example is jQuery, the last release was 2 months ago, and there is plenty of activity on GH.

This is a very good point. I would also look in different directions for inclusivity.

We now have Framer, Webflow and all the others, you don't have to write any code to make amazing websites.

I think this is a great example of all the small details we take for granted in the tools we use, and we would miss without realising when following these tips.

When there are so many projects that run on React, and so many companies rely on React, it's inevitable that it will be supported for a long time to come, even if it would go out of fashion.

And speaking from experience maintaining React apps is quite nice. React has great backwards compatibility, and where it doesn't there are usually codemods available. Dependencies can be tricky, but that's not exclusive to React.

Also don't forget React evolves, backed by multiple #huge companies, and still innovating.

Not at all. There are a lot of frameworks that support static exports and/or pre-rendering. Often those produce incredibly fast results, in many cases faster than hand rolled solutions.

If you use a CMS you have already a templating situation and dynamic content, using a framework, or jamstack like situation is not that different, depending on the specifics it might produce faster results.

This. Even for basic websites you benefit from some form of templating/components for example to get the nav & footer on each page.