big perf change coming tomorrow morning that on paper should make a pretty big difference but it's unfortunately impossible to test impact of this shit locally so. we'll see!!!!!!!!!
- he/they villainx
- flickr.com/photos/kukkurovaca
 |  |  |
objectively too many tv/anime/manga screencaps
photography, especially infrared
- no nazis, no terfs, no yimbies
Alt: The Cohost Daily Tag
cohost.org/TagOfTheDayPhotoblog
www.nickshere.com/Landing Page
kukkurovaca.com/Obsidian Vault / Psuedoblog
plaintextadventure.com/Combined RSS Feed
kukkurovaca.com/rss.xmlYou must log in to comment.
in reply to @jkap's post:
Completely seriously: working on websites seems so much harder than working on operating systems/standard libraries.
I used to work in web hosting and can confirm. Folks could never believe how many different ways users can break a website. XD
I could never understand anything about servers, they never really made sense to me, I'm kind of glad I went for working on local daemons/frameworks
I used to do embedded systems work and I can confirm. I miss systems programming so fucking much.
sorry didn't mean to imply otherwise. just thinking about how that's a common thing with perf stuff in particular
nah totally get what you mean. i'm just glad we've got our visibility where it is since before we were guessing at fuckin everything
I can think of one other prominent example of someone learning this in real-time as I type.
When I was working on my senior thesis project in web development, I fixed a typo two hours before we presented. When I asked the person who was responsible for launching the website and keeping it running if we could make a tiny change like this, he said "No. Absolutely not."
I understand what you mean here haha
I hope it goes well for everyone that worked on it! Good luck!