"Let me guess, you 'need' more?" edition.>Free beginner resources to get started with HTML, CSS and JShttps://developer.mozilla.org/en-US/docs/Learn - MDN is your best friend for fundamentalshttps://web.dev/learn/ - Guides by Google, you can also learn concepts like Accessibility, Responsive Design etchttps://eloquentjavascript.net/Eloquent_JavaScript.pdf - A modern introduction to JavaScripthttps://javascript.info/ - Quite a good JS tutorialhttps://flukeout.github.io/ - Learn CSS selectors in no timehttps://flexboxfroggy.com/ and https://cssgridgarden.com/ - Learn flex and grid in CSS>Resources for backend languageshttps://nodejs.org/en/learn/getting-started/introduction-to-nodejs - An intro to Node.jshttps://www.phptutorial.net - A PHP tutorialhttps://dev.java/learn/ - A Java tutorialhttps://rentry.org/htbby - Links for Python and Gohttps://quii.gitbook.io/learn-go-with-tests - Learn Go with Tests>Resources for miscellaneous areashttps://github.com/bradtraversy/design-resources-for-developers - List of design resourceshttps://www.digitalocean.com/community/tutorials - Usually the best guides for everything server related>Need help? Create an example and post the linkhttps://jsfiddle.net - if you need help with HTML/CSS/JShttps://3v4l.org - if you need help with PHP/HackLanghttps://codesandbox.io - if you need help with React/Angular/Vue/wdg/ may or may not welcome app development discussion. You can post and see what the response is.Some app technologies of course have overlap with web dev, like React Native, Electron, and Flutter.We have our own website: https://wdg-one.github.ioSubmit your project progress updates using this format in your posts, the scraper will pick it up::: my-project-title ::dev:: anontools:: PHP, MySQL, etc.link:: https://my.website.comrepo:: https://github.com/user/repoprogress:: Lorem ipsum dolor sit ametPrevious: >>107431816
Yesterday my pipeline to deploy on staging env fail no stop, i debugged for half an hour then i scroll my rss feed to discover that cloudflare did it again It was a noice Friday
>>107457129maybe you guys might know, who's knocking on the doors of [aws, azure, cloudflare], somebody is certainly knocking
is google being a faggot again? their youtube iframe api is shitting the bed
>>107457208Hacking groups maybe. Or Cloudflare just fucked up. I read this article back in October, after AWS had an outage, which argued that tech lay offs are coming back to bite big tech in the ass. They laid off experienced workers when actually those experienced workers kept everything running:>where have the senior AWS engineers who've been to this dance before gone? And the answer increasingly is that they've left the building — taking decades of hard-won institutional knowledge about how AWS's systems work at scale right along with them.https://www.theregister.com/2025/10/20/aws_outage_amazon_brain_drain_corey_quinn/
>>107458281I don't buy it, 3 big ones down in like 3 weeks distance max, fishy
>>107458339It could be hacking groups maybe. Like the hacking group which infiltrated American telecommunications companies:>The list of telecommunications victims in the Salt Typhoon cyberattack continues to grow>AT&T, Verizon, and Lumen Technologies previously confirmed to The Register that their networks had been compromised by Beijing in what the US government has called a "significant cyber espionage campaign" against American operators.https://www.theregister.com/2025/01/06/charter_consolidated_windstream_salt_typhoon/Yes I read that website quite often for tech news.
>>107458475this looks more like it, but off course, who knows
You HAVE worked on your current personal project today, right /wdg/? I've worked on mine.
>>107459483nah bruh, my personal project is getting certs and increasing my salary, if they want me to work on my personal project they have to pay me for it and set work time for it during my shift
so React...you never have other endpoints other than index / "/"? You just change what component you're rendering on App?That is pretty odd.
>>107459740No it doesn't have to be like that. You can have client-side routing with React. React Router implements this and there are probably other solutions. Look at Twitter for example, I think the whole thing is a big React app, and it routes different URLs to different React components.
>>107459740The whole app is a JS application, that lives inside the root, yesBut if you use a router, you component (like react-router-dom) you can change the URL when you change between views, so a certain view is tied to a URL path.Of course, if your entry point in the app is not the root, you will hit an error. For instance:https://foo.com/boobs/will give you an error, since there is no index.html there. That is why in many frameworks you will find something like a "_redirects" file inside the "public" folder, with content like this:/* /index.html 200That will tell the application to redirect any URL path to the root, that is where the application is served, while keeping the URL path, to know which view to load.
/* /index.html 200
>>107461884I have been writing an Express/React website recently. I have a few Express route handlers, and I fetch those routes from the React app. But then I also defined a catch-all Express route handler to handle all paths I haven't specified. All that route handler does is send index.html to the client. So if someone goes to foo.com/bar, or foo.com/baz, or whatever, they'll always get index.html, then my React app does client-side routing.
>>107462316React is frontend. Express is backend.Also, React in the backend is a travesty.
>react/nextjs reputation getting utterly btfo by the 10.0 cvelove to see it
>>107463212quick rundown?
>>107463417RCE in react server components/server actions, CDNs have been spending the last few days patching every WAF bypass that keeps coming uphttps://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182people are waking up and realizing nextjs and server components are dogshit
>can't access global context variables inside for loopi think i fell for the SSR templates meme
>>107465410>SSRmeme pushed by nextjs, iaas, and paas resellers to charge you more for higher load. Send json and let the client render it lol
>>107466222As far as I know, one of the main selling points of Next.js and similar is that it makes it possible for search engines to index the content of your website and help with SEO and such.How does one go about achieving that with a normal React frontend setup?
>>107466349As far as I know (I'm not an expert), search engines will ALSO load your average SPA, execute the json, render the html, and then parse that.The difference is that if your js is too HUGE, the crawler will eventually peace out and give up because it's taking a few milliseconds too long for its jewish overlords.SSR just makes it so that the crawler gets its content instantly so it can spend more time looking at the page.That's my naive understanding of it at least
>>107466349>Have to invent solution to a problem that would not exist if another solution to a problem that does not actually exist was not in useNo user ever asked for SPA, SSR or whatever. And now web devs are deploying stateless "serverless" server imitations in order to render stuff on the server using client technology. It's just cgi.pm, but more complicated with two levels of indirection for no good reason.
>>107466391>execute the jsonexecute the js*
>>107466394>No user ever asked for SPAActually I'm asking for it. SPAs are great.
>SSR on first request>CSR for subsequent requests>good for SEO and avoids SPA waterfallstake the tanstack pill
In my personal project, I've been playing around with the new View Transitions.They seem pretty fun and I can see them being useful for UX, if the developer knows what they're doing.They basically work like this:On one page, you give any element a unique ID like "elem-123".Then on the page you want to navigate to, you give a different element the same ID "elem-123".Then when the user navigates from one page to the other page, the browser automatically transitions the old element to the new element (by default it translates it, transforms it and blends it, but it can be customized).More info here https://developer.chrome.com/docs/web-platform/view-transitions
>>107464196>people are waking up and realizing nextjs and server components are dogshitgood shit
>>107462330Yeah I'm using React on the front-end and Express on the back-end. I have an Express route, after my other Express routes, which catches every path (not otherwise caught by another route handler). This catch-all route just sends index.html to the client. Then my React app uses client-side routing for whatever path the user has navigated to.
>>107466483Looks cool. Would be good for a PWA I want to make. I like the idea of PWAs because it means I won't have to pay A*ple or G*ogle to list a native app in their app stores.
>>107468823>Would be good for a PWA I want to makeYeah it's definitely great for mobile app feeling. I just implemented a card slide view transition for these tabs and it really feels like a native mobile app
>>107468960That's so cool, do you preload all the data?
>>107466349You can always read the user-agent, and if it's a crawler render a minimal template with no styling whatsoever
>>107469626Yep, it's an Angular SPA. If you open the /scenes page or any of its subpages, there's a scene service that fetches the list of scenes as JSON once. The sub-pages that it transitions to inject the same service, so they use the same data without re-fetching.You can still use view transitions without having the "target data" immediately available, it just loads in during the animation then so you might see a flicker of the content appearing for the first time as it slides into view
>>107469725Neat. I tried Angular briefly last year but it just doesn't resonate with me like React does
Jesus christ
>>107472725I'm guessing you haven't bumped the dependencies in a while
>>107473069Trying to debug something in https://github.com/xanderfrangos/twinkle-tray
>>107473206Those niggas should bump their dependencies
>>107468192>I have an Express route, after my other Express route>catch-all route>send index.html to frontend
>>107474768Yeah. So if someone navigates to example.com/whatever-the-fuck, they'll get index.html, which loads the React front-end. The React app then does client-side routing.
>>107474790so... what was said from the beginning. cool thx
>>107460449>>107461884I see. I hadn't seen many examples where they did interesting things like this. I'll look into it more.
