369
submitted 2 days ago by [email protected] to c/[email protected]
top 50 comments
sorted by: hot top new old
[-] [email protected] 5 points 19 hours ago

I’ll give it a pass as parody, but you really should include the source material.

xkcd 303

[-] [email protected] 1 points 19 hours ago

Yes. Sorry. I expected everyone to know this, but in hindsight this is of course a bad assumption.

[-] [email protected] 65 points 2 days ago

10 years ago this meme said "compiling" shows how much docker has made things more "efficient"

[-] [email protected] 16 points 2 days ago

We've created this hell for ourselves

[-] [email protected] 11 points 1 day ago

For me, Docker has been amazing. It’s probably my single most favorite tool in my tool belt. It has made my life so much easier over the years. It’s far from hell for me! 🐳

[-] [email protected] 2 points 19 hours ago

Same. Now, it is complete shit on Windows, though supposedly it is better on W11, and that is a no go. However, on Mac, it is a dream. On Linux it is a dream. Pgadmin, postgres, mqtt, redis, all the arrs, qbittorrent, jellyfin, and whatever else I want to try and throw away if I don't like it.

[-] [email protected] 6 points 1 day ago

As a self-hoster, I love docker. It's been an amazing deployment tool.

[-] [email protected] 15 points 2 days ago

Tbh, all of web development has become this... efficient. I remember the days where I could create a website in PHP and have it done in a couple of hours (per page), and now the only way I can do that would be using AI and going full on "vibe coding" mode.

[-] [email protected] 5 points 2 days ago
[-] [email protected] 13 points 1 day ago

Yeah, but why would I use it when much worse options exist

[-] [email protected] 2 points 1 day ago

Maybe it's time to go back to the good ol' days

[-] [email protected] 4 points 1 day ago

Nah, the good ol' days were when websites provided value to their users. The only competitively sustainable business model is the reverse: where users provide value to the website owners.

[-] [email protected] 1 points 1 day ago

What do you mean? You can just make some react/typescript template and fastapi server thing, or any of dozens of equivalents, extremely quickly. I'm by no means an expert on web stuff as I develop software for controlling machines, but we used the above for some internal services in my last job and I could get a clean and functional site running in a day with no prior experience. I get that for public facing stuff you'll have some higher requirements but I couldn't imagine those wouldn't apply just because you're coding in PHP...

[-] [email protected] 10 points 1 day ago

a clean and functional site

But the specs no longer call for a clean, functional site. Today's "professional" web development specs call for user tracking, customized content per user per platform per locality the page is being served to. Then there's the backend dashboard services showing the overlords user behavior patterns and how they change based on tweaks made to their ui, I wouldn't be surprised if the algorithms auto-tune presentation to optimize behavior.

[-] [email protected] 3 points 1 day ago

It's all the extra requirements, all the extra engineering that needs to be added that is IMO ruining web applications. Sure, they have huge benefits, but I hate when the application is simple but the backend is so overly engineered that it takes a week to completely build a fully fleshed out application. You have to organize your components, add styled-components.js, make sure it's compatible with mui.js, create test cases for each component, setup a DB and integrate it to hold all copy as well as any input from the customer, make sure that it's accessible (this part I admit that it's important), make sure your test cases always pass, setup routing tables, add analytics, add pixel campaign api, squash git conflicts, integrate some other weirdo apis that marketing and leadership pulled from some obscure service no one has ever heard off, debug some weird edge case error caused by a node dependency 3 levels down, present the finished website to leadership only to be destroyed and now you have to redo 75% of the site with leadership changes... rinse and repeat.

It's a good thing I fucking love my job 🙃

[-] [email protected] 4 points 1 day ago

You know what you didn't mention? Security. Privacy. Authenticity.

[-] [email protected] 2 points 1 day ago

Ok yeah I totally get how that would be a burden... But I wouldn't like to attempt doing all that stuff in PHP ;)

[-] [email protected] 21 points 2 days ago
[-] [email protected] 8 points 2 days ago
[-] [email protected] 1 points 1 day ago

Restoring 1226 nuGet packages...

[-] [email protected] 7 points 2 days ago

Someone doesn’t know how to leverage Docker BuildKit

[-] [email protected] 3 points 1 day ago

Is there more to it than using multistage builds when appropriate?

[-] [email protected] 2 points 1 day ago

Oh yeah there is a lot you can implement to really get the most out of your architecture via docker and minimize your build times.

One is using BuildKit with BuildX and Docker Build Cache.

BuildX is the one I highly recommend getting familiar with as it’s essentially an extension of BuildKit.

I’m a solutions architect so I was literally building with these tools 15 minutes ago lol. Send any other questions my way if you have any!

[-] [email protected] 3 points 1 day ago

Ah thanks, I do have another question actually! So aside from speeding up builds by parallelizing different stages, so that

FROM alpine AS two
RUN sleep 5 && touch /a
FROM alpine AS one
RUN sleep 5 && touch /b
FROM alpine AS three
COPY --from=two /a /a
COPY --from=one /b /b

takes 5 iso 10 seconds, are there any other ways buildkit speeds up builds?

[-] [email protected] 3 points 1 day ago

Yeah! So the first thing that BuildKit provides that greatly improves build time is that it will detect and run the two stages (one, two) in parallel so the wall-clock time for your example is 5s (excluding any overhead). Without BuildKit, these would be built serially resulting in a wall-clock time of 10s (excluding any overhead).

Additionally, BuildKit uses a content-based cache rather than a step-by-step key cache used by classical Docker. This content-based cache is intelligently reused across different builds and even re-ordered instructions. If you were to build then rebuild your example, the sleep steps would be skipped entirely as those steps are fully completed and unchanged in the content-based cache from the previous build. It will detect changes and re-build accordingly.

Lastly, (albiet not a BuildKit feature directly) is to leverage inline build caching for things such as dependencies so they are persisted to your filesystem and mounted during build time such that you don't have to fetch them constantly. This isn't really necessary if leveraging BuildKit fully since the content-based cache will also handle the dependencies and only pull if changed. i.e:

RUN --mount=type=cache,target=/root/.cache \
    your-build-command
[-] [email protected] 1 points 1 day ago

Not really, no.

[-] [email protected] 7 points 2 days ago

I'm waiting for the LLM to reply

[-] [email protected] 4 points 2 days ago

I was going to watch a tuto on how to be more efficient but YouTube is still buffering

[-] [email protected] 2 points 1 day ago

Delayed because of your ad-blocker :p

[-] [email protected] 2 points 1 day ago

I swear it's gonna load any second now and I'll be able to do something productive!

Still better than ads, though 😄

load more comments
view more: next ›
this post was submitted on 18 Jun 2025
369 points (96.9% liked)

Programmer Humor

36598 readers
299 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS