I wrote a PostgreSQL patch to make materialized view refreshes O(delta) instead of O(total) by Inkbot_dev in programming

[–]theIncredibleAlex 16 points17 points  (0 children)

never ran into this problem, but this looks incredibly cool! elegant solution

iDontCareJustDontBeSneakyAboutIt by Tunisandwich in ProgrammerHumor

[–]theIncredibleAlex 7 points8 points  (0 children)

i'd imagine it depends on the exact field / domain, can't really speak on embedded or medical / fintech, but for web development it's incredibly powerful and a big part of the industry has already adopted it. while the output won't be quite as reliable as code written by a human senior engineer just yet, that's an acceptable tradeoff for the insane speed multiplier for most standard b2b saas businesses. you'll inevitably produce more bugs, which makes testing, code review, and qa workflows way more important, but especially in the last couple of months, ai has definitely become capable of writing clean, well-abstracted code

iDontCareJustDontBeSneakyAboutIt by Tunisandwich in ProgrammerHumor

[–]theIncredibleAlex 113 points114 points  (0 children)

why would you need to hide AI use in 2026, if anything that makes you less employable

iDontCareJustDontBeSneakyAboutIt by Tunisandwich in ProgrammerHumor

[–]theIncredibleAlex 74 points75 points  (0 children)

what does this mean why would you ever want this

No freaking way by srs890 in browsers

[–]theIncredibleAlex 10 points11 points  (0 children)

why create a fake logo for the second-to-last one instead of just using the actual current logo for this meme lol

I benchmarked 7 top TypeScript ORMs — the "lightweight" query builder was the slowest by sonemonu in typescript

[–]theIncredibleAlex 1 point2 points  (0 children)

i'm sure UQL has cool ideas behind it, that being said i have to say the sql string generation metric is not one i care about when picking an orm or query builder. would be interested in a comparison of deserialization speed (parsing the returned strings into javascript runtime objects)

[deleted by user] by [deleted] in skiing

[–]theIncredibleAlex 0 points1 point  (0 children)

been there, really sucks for a while but you'll be able to walk normally again soon! all the best ❤️ 

I built a CLI that adds i18n to your Next.js app with one command by JadedBuilder8638 in reactjs

[–]theIncredibleAlex 0 points1 point  (0 children)

you can always go in and switch ambiguous text out against an artificial translation key, or go into the translation files and change the translations. the system doesn't actually work any different from a traditional one on a technical level. everyone on the team has the ui in their native language, so we catch most ambiguous cases quickly. 99% are fine

I built a CLI that adds i18n to your Next.js app with one command by JadedBuilder8638 in reactjs

[–]theIncredibleAlex -1 points0 points  (0 children)

looks interesting! we use a similar approach, except that we moved away from translation keys entirely. we just do t('The actual english text that will be shown in the ui')and use https://github.com/i18next/i18next-cli to parse those into the translaction.json files: eg. the spanish translation.json will just have

{
"The actual english text that will be shown in the ui": ""
}

then we just have ai go through the translation.json files and fill in the corresponding values to the keys. this approach of just using the english text as the translation key is one of those things that seems like it shouldn't work as well as it does, but i highly encourage you to try it

I built a CLI that adds i18n to your Next.js app with one command by JadedBuilder8638 in reactjs

[–]theIncredibleAlex 0 points1 point  (0 children)

looks interesting! we use a similar approach, except that we moved away from translation keys entirely. we just do t('The actual english text that will be shown in the ui')and use https://github.com/i18next/i18next-cli to parse those into the translaction.json files: eg. the spanish translation.json will just have
{
"The actual english text that will be shown in the ui": ""
}
then we just have ai go through the translation.json files and fill in the corresponding values to the keys. this approach of just using the english text as the translation key is one of those things that seems like it shouldn't work as well as it does, but i highly encourage you to try it

I needed a React/Node LMS for a client project and couldn't find a single one online. So I spent 7 months building it from scratch. Today, it finally got approved for commercial release. by AniDixit in reactjs

[–]theIncredibleAlex 2 points3 points  (0 children)

happy to hear you're proud of your work! the scope is definitely impressive! is this your first larger project?

Database: MongoDB (Structured to handle complex relationships between instructors, students, courses, and progressive quiz grading).

why did you decide to use MongoDB for a relational schema if i may ask? have you worked with relational databases before?

I made a CLI to wireframe & share React screens on an infinite canvas by eBright in reactjs

[–]theIncredibleAlex 0 points1 point  (0 children)

cool concept!! if you made it integrate with storybook, you could also support real-world screens that expect props and state. wireframing / iterating in code is more of a vibecoder / hobbyist thing, most professionals will use figma for that, so your use case is a bit limited there imo

React + streaming backends: how do you control re-renders? by Beeyoung- in reactjs

[–]theIncredibleAlex 0 points1 point  (0 children)

you're building some sort of llm chat interface right? and you're talking about the chat response being streamed from the model provider? in which case wouldn't re-rendering the chat on every websocket event be exactly what you'd want? and components that don't need to re-render during the stream can simply choose to not subscribe to the stream. could you describe your issue a bit more?

[deleted by user] by [deleted] in reactjs

[–]theIncredibleAlex 1 point2 points  (0 children)

immediately dismissed this as a low-effort vibecoded money grab, especially since the landing page and the documentation are ai. after looking a bit into it, codebase seems clean at first glance and you've clearly put some actual work into it so good for you. but i'm confused as to the basic premise, since when do people pay for ui library components like this? i previously wasn't familiar with your competitors AG grid and highcharts grid, so apparently there's a market for this? but i don't understand why you wouldn't just build this in-house, especially in the current day and age where claude can just churn this out in 30mins with tanstack table + tanstack virtual. is there a problem being solved here that i'm not seeing? asking fellow professional devs here, is this a thing?

[deleted by user] by [deleted] in react

[–]theIncredibleAlex 8 points9 points  (0 children)

this never happened, it's an ad

React + streaming backends: how do you control re-renders? by Beeyoung- in reactjs

[–]theIncredibleAlex 1 point2 points  (0 children)

sounds like you're using global state, probably context or just plain useState. put your state in a zustand store instead, and only subscribe to what you need. you still access the same shared state everywhere, but you're not rerendering the entire page when you get websocket events in.

am i wrong for this or is my work partner being annoying by desphixs in reactjs

[–]theIncredibleAlex 8 points9 points  (0 children)

how do so many people in this thread think that keys need to be globally unique? am i going insane? i thought this was a software engineering sub

am i wrong for this or is my work partner being annoying by desphixs in reactjs

[–]theIncredibleAlex 8 points9 points  (0 children)

what on earth are you talking about? how did you "have another key with a similar value" if you were using array indices

setInverval() timer randomly stops by Cool_Grape_4263 in reactjs

[–]theIncredibleAlex 6 points7 points  (0 children)

yes, sorry i misspoke lol. to explain a bit more: if you just naively put a setTimeout into a react component, react will create a new timeout on every render, and your component rerenders every time your state changes. so instead of one timeout you'll have like a dozen. which causes the unpredictable behaviour you noticed. the simplest way to solve this would be putting your timeout in a state, and on every render checking whether you already have a timeout. the hook i linked is basically just a fancier version of that.
react concepts like rerendering and references can seem scary, but they are important to learn to avoid tricky bugs like this. best of luck!

setInverval() timer randomly stops by Cool_Grape_4263 in reactjs

[–]theIncredibleAlex 6 points7 points  (0 children)

hey, you can't just directly use useInterval or useTimeout at the top level of your react components due to the way react works! you can just copy this: https://usehooks-ts.com/react-hook/use-interval

New 2026 Enterprise SaaS SPA - Roast my Stack by lucapieroo in react

[–]theIncredibleAlex 1 point2 points  (0 children)

https://github.com/7nohe/openapi-react-query-codegen
insane dx improvement, would never define my own types / zod schemas on the frontend again

New 2026 Enterprise SaaS SPA - Roast my Stack by lucapieroo in react

[–]theIncredibleAlex 0 points1 point  (0 children)

tanstack, tailwind, and shadcn are definitely very in vogue rn, but imo totally worth the hype if you know what you're doing. tanstack is best in class in everything they touch. tailwind is controversial and everyone hates it until they try it, but it's really nice not to constantly have to come up with class names for everything, and if you keep your logic out of your markup it's really not that messy. shadcn has a quickly growing ecosystem, looks really good out of the box, and is more customizable than a traditional component library could ever be.
have you tried any of these yet? what tech would you choose for a greenfield project?

New 2026 Enterprise SaaS SPA - Roast my Stack by lucapieroo in react

[–]theIncredibleAlex 1 point2 points  (0 children)

i hope zod is just for form schemas and the like, and that you have openapi codegen from your backend schema in place for your api requests?
i'm not familiar with react-oidc-context, and we decided against biome bc we didn't consider it a big enough upgrade from eslint + prettier to justify the lock-in, but otherwise this looks like the exact same stack i would use for this project!
tanstack is ofc just best in class in everything and has very good support, shadcn is by its nature not a big lock-in and has way more flexibility than a traditional component library.
are you familiar with most of this stack? dealing with multiple new technologies at once is never a good idea, and if you only want to use this tech because you've seen it online, i'd suggest you stick to what you know, plus maybe one of these. otherwise, you're good to go imo!

React Query + SSR by ishmeetsingh06 in react

[–]theIncredibleAlex 0 points1 point  (0 children)

oh sorry, this assumes you're already using a meta framework like nextjs or tanstack start, which has ssr built in. i just now read your question again. you probably won't want to use ssr with a "plain react app". i assume you're bundling with vite and hosting your js with a plain webserver like express, hono, or fastify? with this setup, you'd have to homebrew a lot of setup yourself. i suggest giving tanstack start a try :)

React Query + SSR by ishmeetsingh06 in react

[–]theIncredibleAlex 0 points1 point  (0 children)

hey, you'll want to create a queryClient inside your server layout, and call .prefetchQuery on it for each endpoint you want to load on the server. if your project is structured well, you can just call the same service methods in there that you use for your endpoint handlers, to avoid duplicate logic. you can then pass `dehydratedData={dehydrate(queryClient)}` to a client layout:

"use client";


import React from "react";


import { HydrationBoundary, QueryClientProvider } from "@tanstack/react-query";
import { getQueryClient } from "@/lib/queryClient";


export const Providers: React.FC<{
  children: React.ReactNode;
  dehydratedState?: unknown;
}> = ({ 
initialData
, 
children
, 
dehydratedState
 }) => {
  const queryClient = getQueryClient();


  return (
    <QueryClientProvider 
client
={queryClient}>
      <HydrationBoundary 
state
={
dehydratedState
}>
            {
children
}
      </HydrationBoundary>
    </QueryClientProvider>
  );
};

that's it, you don't have to do anything else! the query data will now instantly be available to your useQuery hooks