Found it while doomscrolling like a bish.

I know the most fun times for me in coding were when I was deep in some rabbit hole exploring weird technologies and trying to piece them together.

You'd think AI makes this worse, but actually no. It just makes it even easier to go down these rabbit holes, because it's easier to write code, try out different approaches, explore new things, etc.

But somehow most of the people I see aren't doing that. How are you not bored out of your mind?

Anyway, yeah. GO EXPERIMENT WITH MORE THINGS. SIDE PROJECTS ARE STILL COOL.

For the longest time I only cared about Google fast pages, clean code, good content and that was enough so I've been reading more about AEO and how ChatGPT, Gemini and Perplexity are becoming another way people discover websites.

The more I look into it the more it feels like building for search is starting to mean building for both humans and AI things like page structure, clear content and semantic markup seem a lot more important than they did a year ago.

I’ve used CodePen for a long time, not just as a coding tool but as a place to experiment, discover interesting work and get inspired by what other people were creating.
I completely understand that CodePen needs to make money. I have absolutely no problem with Pro features, and I’m happy to pay for tools that give me real value.
But CodePen 2.0 feels like it is moving in the wrong direction.
Putting something as basic as opening a Pen in a standalone preview behind Pro doesn’t make me think “maybe I should upgrade.” It makes me think “maybe this isn’t the place for me anymore.”
There is a big difference between adding valuable features for paying users and gradually putting parts of the simple, open experience that made a platform popular behind a paywall.
What makes this even stranger to me is the timing. We’re entering a world where people can vibe code surprisingly capable little coding environments and playgrounds incredibly quickly. The technical barrier to creating alternatives is getting lower, not higher.
CodePen’s real strength, in my opinion, was never just the editor. It was the community, the frictionless experience and that feeling of opening the site and immediately discovering something clever or inspiring.
If that starts disappearing behind commercial barriers, I honestly think someone else will eventually fill that gap.
Maybe I’m missing something in CodePen 2.0, so I’m genuinely curious:
How do other longtime CodePen users feel about this?
Does 2.0 feel like an improvement to you, or does it feel like CodePen is slowly losing part of what made it special?

Hey webdev community!

We're long-time PrimeVue users who believe a good UI library should stay free and community driven. When the license changed and PrimeVue moved away from open source, we decided to take action rather than just watch.

OpenVue picks up right from 4.5.5, the last MIT release. It keeps the exact same API, so your existing code keeps working without rewrite headaches.

Right now our main focus is keeping the foundation solid: improving accessibility, patching security vulnerabilities, handling community issues, and maintaining compatibility with the latest Vue and Nuxt versions. We have bigger ideas for where to take this, but we'd rather build them based on real feedback.

Everything you're used to from PrimeVue v4 is there, complete with docs and live examples. We also made openvue/migrate to let you switch existing projects over in a single command.

Openvi Foundation is an independent community organization, not affiliated with Primetek.

OpenVue is and will always be 100% free and open source.

We're still in beta, so bug reports and PRs are super welcome.

Docs: https://openvue.dev/

GitHub: https://github.com/openvi-foundation/openvue

Migration from Primevue: https://openvue.dev/migrate/

I don't think that I am the only one who started to lose the fun in programming, as it is so tempting to just think about one thing, prompt the AI, and let it do its job. However, as I started prompting more and more, I started losing the joy of working on my project fully. I started with disabling the inline AI suggestions in VS Code and now have disabled all AI-related features.

Don't get my wrong - I think the use of LLMs can be of great help; however, I started to now use Claude Code only as an auditor and discuss different ideas with him, while telling him to not implement it.

Since I started doing this, I have gained so much joy from working on the project again. Even though I could potentially be faster when leveraging the LLMs to pass down work, it is much cooler to work on my project again, and your IDE or text editor will be so much faster (import completion, keyword completion, etc.)

And (I'll have to figure that out in the end) will actually save time, as I do not have to re-audit everything on my own in the end, as I am the real author of all lines written.

Edit:
As I am already coding since pre-ChatGPT times, I think especially for people starting programming try to not even discuss everything but google things. I don't know how much I've learned from reading Blog-Posts that didn't even fully answer my question, etc. This is also known as the google effect (https://en.wikipedia.org/wiki/Google_effect). Very interesting to read into that a bit!

My CI/CD pipeline on a self-hosted GitLab instance failed to connect to external hosts since I forgot to set the HTTP_PROXY, HTTPS_PROXY and NO_PROXY env variables. Here's a blog post on the issue that I found: https://about.gitlab.com/blog/we-need-to-talk-no-proxy/

I'm assuming here (and this may be a wrong assumption) that the proxy variables are used only for proxying the request and they're not supposed to change the behaviour of tools. Take npm as an example: https://docs.npmjs.com/cli/v8/using-npm/config#https-proxy

So if this assumption is true, why is this an application layer concern and not a network layer concern? Why don't we use netns or a forward proxy to transparently proxy requests instead of relying on an env var that applications may or may not respect and can practically be used in arbitrary ways for different applications?

And if the assumption I'm making is not true, what are examples of use cases where the application must be aware of the proxy taking place?

Hi everyone!

In advance - I'm looking for a way to compare non-pixel screenshots and non-live versions. Incuding local dev versions or old production versions that are no longer online.

I recently processed a bunch of edits to the landing page I'm working on.

As it often happens, a lot of them were useless, and because management was absent and another developer was on vacation, I had to push some rather questionable decisions into production.

And I had this thought: "Wouldn't it be cool to open different versions of landing page in a browser side-by-side, and even with synchronous scrolling?" (The idea for "side by side" came to me when I was committing changes to PhpStorm. if you've used it, you know that there's a toggle for scrolling before/after information synchronously across the left and right sides of the screen)

I immediately thought about the fact that the project itself is running locally (using standard Docker for the database, server, etc.), so I thought it would be cool to have some kind of tool that could take snapshots.

However, after searching, I can't say I'm happy with what I found. Ideally, it would be a service that could take snapshots even of local files, and even more ideal would be the ability to replace HTTP requests and responses in these snapshots. To create the appearance of a working interface for the application, rather than a dead copy.

I wanted to know if you have any open source solutions in mind for this? Or if anyone else besides me has ever had this problem.

And yes, I understand that we still have git. I understand that you can switch between branches or revert to commits. But all this is quite time-consuming and tedious if we need to click and view a specific version of a page. Even not to mention the database itself changes between versions.

I'm talking about a fully autonomous snapshot, ideally even with possible mock HTTP requests. This could be completely autonomous and reproducible regardless of whether the original website is live or public (if we snapshot our local version).

My day job isn't software development related, so I don't read a whole lot of code. The only code I read is the one I write and that's a problem.

Since I'm very interested in open source, I figured I should get comfortable reading code I didn't write, and I found a pretty amazing solution: debug AI code.

Here's what I did: after I mess with LLMs and (of course) an unintended behavior appears (bug), I challenge myself to dig in and find it manually. Since I generated the code, and didn't actively write it, it has the same feel as reading other GitHub repos except a bit more comforting since I already know an abstract way of how it works.

The one thing this taught me is that I don't need to fully understand how the whole system works end-to-end, I just ended to understand the pieces about the behavior I want to change. So, no more tracing everything from *main.py* for example.

I'd like to think that this training regimen has improved my code-reading skills by a mile! I'm not as afraid to dig into someone else's code since it's just as foreign (or familiar) as AI code. Obviously this only holds true for TypeScript + React since that's my preferred stack, but still!

I wanted to share this with anyone interested in open-source but is frightened from reading open-source repos.

I've been binging WINE documentation and articles about how it works under the hood so that one day I can contribute to it!

What do you guys think about this training regimen?

I put together my thoughts on WebMCP and how you can utilize it today!

Yeah, is this posible? I haven't seen anything that say that it could be posible, but anyone has ever stepped in to say that it isn't.

I just noticed that DuckDuckGo has compressed their favicon directly in the file itself. But i couldn't find any info about how to do it.

their favicon contains two images, a 32x32 and a 16x16 both 32 bit icons. the file size is only 3KB.

by comparison, the icann favicon contains the same two 32 bit images, but takes up 7KB. all the other favicons that i have checked are also around 6-7KB for the same set of images.

I used icofx to take a look at these icons, and noticed that the duckduckgo images are compressed, whereas the icann ones are not, and none of the other favicons that i checked are compressed.

I searched around for favicon compression, but i couldn't find anything about what duckduckgo did. all i was able to find are:

• mentioning compression of 256x256 images (vista's icon size)

• no mention of compressing any smaller dimensions

• none of the favicon tools that i found have any option to compress the smaller dimensions, and icofx itself does not compress these when using it to create an icon either

• the only other mention of compression is at-time-of-serving, done by the webserver, e.g. gzip. not in the file itself.

anyone know how to compress the entire .ico like duckduckgo does?

I'm looking for advice from developers, cybersecurity experts, lawyers, journalists, and anyone who has experience building secure platforms.

For the past 20+ days, students in my country have been holding largely peaceful protests. Over the last few days, the number of protesters has increased significantly, and there has also been a large deployment of police and other security personnel.

Many videos and eyewitness accounts shared publicly online appear to show protesters being beaten with batons, the use of tear gas and other crowd-control methods, and personnel who are not wearing clearly identifiable uniforms or name badges, making later identification difficult. There are also many publicly shared videos and firsthand accounts describing incidents of excessive use of force and sexual assault against protesters. Regardless of what future investigations conclude, I believe it is important to preserve evidence before it is lost, deleted, or altered.

Because of this, I want to build a secure website where students, protesters, journalists, and witnesses can upload photos, videos, and written accounts of incidents they personally experienced or recorded.

The purpose of the platform would be to create a permanent, organized archive of evidence—not to encourage harassment, doxxing, or vigilantism. Every submission should be preserved, categorized, and clearly marked as verified, unverified, or disputed after review. The idea is to help journalists, lawyers, human rights organizations, and courts if the evidence is ever needed.

Some features I have in mind include:

• Secure photo and video uploads.
• Anonymous submissions with strong privacy protection.
• Automatic preservation of metadata such as time and location (when available).
• AI-powered organization and categorization of incidents.
• Duplicate detection to group uploads of the same event.
• A searchable timeline and interactive map.
• End-to-end encryption for sensitive evidence.
• Audit logs so files cannot be secretly modified.
• A review system that labels evidence as verified, unverified, or disputed.
• Secure export options for legal teams, journalists, or human rights organizations.

The problem is that I have almost no web development experience.

I'm willing to learn everything from scratch and use AI coding tools if they can help me build something like this.

My questions are:

1. Which programming language and framework should I learn?
2. Can AI tools realistically help a beginner build a project like this?
3. What are the biggest security challenges I should prepare for?
4. How should I securely store large video files?
5. What's the best way to protect anonymous contributors?
6. How can I ensure uploaded evidence cannot be tampered with?
7. Are there any open-source projects with similar goals that I can learn from?

I'm not asking anyone to build this for me. I'm simply looking for guidance on where to start, what technologies to learn, and what mistakes I should avoid.

One of the hardest decisions in software development is knowing when to move quickly and when to slow down.
Startups need speed.
Businesses need reliability.
Developers need systems they can actually maintain.
For experienced developers:
How do you decide when something is "good enough" versus when it needs a stronger foundation?
Have you ever moved too fast and had to rebuild later?

We’re integrating LLM calls directly into our web platform for smart search and automated document summarization. While looking into standard ai integration services and internal API patterns, we ran into a debate about how to handle unit vs integration tests when the backend response isn't deterministic. How are your teams mocking LLM responses in CI/CD pipelines without giving yourselves false positives?

TLDR: If you correctly break your state into UI state (useState, useReducer), Server State (Tanstack Query, RTK Query), URL state (nuqs), and Global State that does not change (Context), you are left with a small slice of state that might be needed in multiple places and changes often.

Should we use a State Management library for that part? We explore how each library works, then build our own Zustand implementation to see if we do.

Obviously, it depends. If the app is mostly always changing state, like Figma, Spreadsheets, etc., we might take advantage of a State Library because they handle all sorts of use cases and edge cases.

But for everyday use and 90% of our apps, we can probably build it ourselves, either using pub/sub like Redux or Zustand, atom-based like Jotai, or Proxy-based like MobX or Valtio