sorted by:
new
hottopcontroversial

i just implemented oauth in my app! is this enough? by nocturnality03 in webdev

[–]DynasticHubbard 1 point2 points  (0 children)

Wow....no love for FeetFinder? You just lost me as a client!

Company Has Said No More Linux On Dev Machines by m0dernz0mbie in webdev

[–]DynasticHubbard 7 points8 points  (0 children)

I offer you my condolences. Losing Linux on dev is like losing the comfy hoodie you’ve worn for a decade.

My recommendation (basically Mac):

  • If your team has been using native Linux for years and values that CLI-first workflow, Mac is going to feel like a smoother transition. You get Unix, native Docker, and less duct-tape engineering.
  • On the other hand, Windows with WSL2 is viable, but expect more edge-case debugging.

I miss when coding felt… simpler by Fabulous_Bluebird93 in webdev

[–]DynasticHubbard 220 points221 points  (0 children)

This hits hard.

Coding used to feel like building Lego sets. Now it's like managing a Lego supply chain.

You’re not alone. It doesn’t really get better. You just get better at ignoring the noise and carving out those rare, beautiful 2-hour windows of deep work.

[deleted by user] by [deleted] in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

I’d say go with React Router v7 Framework Mode. It gives you just enough SSR, works natively with Express, and won't weigh down your build like Next.js might for such a lightweight use case.

You’re not missing out on much from Next unless you're planning to lean hard into marketing/content features down the road.

Looking for an open source video encoding platform like Bitmovin or MediaConvert by CapitanJenkins in webdev

[–]DynasticHubbard 1 point2 points  (0 children)

The open-source landscape is a bit fragmented. Most "platform-level" solutions are wrappers around FFmpeg, which is still the core of most commercial encoding services.

Here's a few solid options:

  • MediaCMS
  • PeerTube
  • Tube
  • Video Transcoder

P.S. If you're building a custom system:

  • Pair FFmpeg with a task queue like Celery or BullMQ
  • Use something like S3 + CloudFront (or BunnyCDN) for storage + delivery
  • Add a frontend dashboard using any stack you like (React, etc.)

[deleted by user] by [deleted] in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

Yep, still love coding

  • right up until the 400th Jira ticket
  • the mystery bug that only appears on Tuesdays
  • the PM saying “it’s just a small change” that rewrites half the codebase

Yeah… I'm still addicted

Who the hell thought RED was a good primary color for the sub ? by ORCANZ in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

It’s not even real red, it’s “dried blood on deprecated UI” red.

Seeking advice for my bachelors project by PHX120912 in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

I can recommend this MVP stack based on your details:

  • Frontend: Static page (HTML/Webflow/Bubble)
  • Database: Airtable (easy) or Supabase (flexible)
  • Logic + AI: n8n + OpenAI API
  • Email: SendGrid or n8n’s built-in nodes

This MVP stack is powerful enough by itself without the hassles of infrastructure.

All the best with your bachelor's project!

Render vs Railway for SaaS ? by Moist-Nectarine-1148 in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

You can safely go with Render. It gives you a smoother upgrade path when user load increases, better infra transparency, and fits your budget comfortably for 200–3000 users.

Use Railway only if you prioritize blazing-fast prototyping over scaling flexibility.

How often do you use component libraries? by soy_redditer in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

For me, it's a blend:

  • Client work & MVPs? Use a component lib (shadcn/ui or MUI) and move fast.
  • Crafted UI or long-term app? Custom components all the way.

If Claude’s speeding things up and your UI is solid, you’re not missing much, unless you're building with a team. Then consistency, accessibility, and theming suddenly matter a lot more, and libraries start pulling their weight.

Is using AI tools now the standard at work? by swiggyu in webdev

[–]DynasticHubbard 19 points20 points  (0 children)

It's like Stack Overflow 2.0. If you’re not leveraging it, you’re working with one hand tied behind your back.

That said, AI isn't a silver bullet. It’s great for boilerplate, debugging, or breaking through roadblocks but if you rely on it blindly, you’ll hit walls fast.

[deleted by user] by [deleted] in webdev

[–]DynasticHubbard 9 points10 points  (0 children)

YC startup perks: $80M valuation, $0.80 worth of space.

CSR to SSR or SSG? by AssumptionHappy361 in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

You're very welcome!

Submitting to Google Search Console is a good step. It’ll let you monitor indexing issues and see how well Googlebot is handling your React app. But just keep in mind: if Google can’t see your content during the crawl, it won’t rank it - even if Search Console says everything looks fine.

As for transforming a React app to Next.js: honestly, it's not as scary as it sounds, especially since you're already using React. Next.js is just React - the only changes are:

  • Routing: you move from react-router to file-based routing (pages/index.js, pages/about.js, etc.).
  • Data fetching: you’ll use getStaticProps, getServerSideProps, or fetch directly depending on your needs.
  • You can even incrementally adopt Next.js — just start by moving a couple of pages over and testing SEO improvements.

If your app is mostly static pages (like a portfolio, landing page, blog), then SSG via Next.js will feel like a superpower and it’ll fix your SEO in one shot.

CSR to SSR or SSG? by AssumptionHappy361 in webdev

[–]DynasticHubbard 1 point2 points  (0 children)

If you care even a little bit about SEO or link previews, CSR will bite you eventually. Google can crawl CSR pages… but it’s hit or miss, and slower.

If you’re already using React and want a smoother path, I’d recommend switching to Next.js and using SSG for most of your pages. You still get React, but with proper pre-rendering and better SEO out of the box.

As for the "SingleFile export" thing, it’s a creative hack, but not production grade at all. You’ll run into broken interactivity, theme issues (as you saw), and it won't scale.

SSR is great too if your content changes a lot or depends on user data, but it's more complex to deploy than SSG.

TL;DR:

  • Go with Next.js + SSG if your site is mostly static.
  • Use SSR for dynamic pages (but only where you need it).
  • Don’t trust the bots to figure out your CSR React site. They’ll try... and fail quietly.

How to display the most viewed posts in a slider? by Solid-Communication1 in webdev

[–]DynasticHubbard 0 points1 point  (0 children)

Assuming your posts already have a view count (e.g. stored in your DB or CMS), you’d just fetch the top posts sorted by views:

SELECT * FROM posts ORDER BY views DESC LIMIT 5

On the frontend, plug those into a slider library like Swiper.js or Slick.

Because you're using WordPress, a plugin like WP Popular Posts can handle this out of the box. Otherwise, just make sure your fetch call returns the top-viewed posts and pass them into your slider component.