wengo314

if one could boostrap tcc with it, then it might be a viable tool.

jemalloc saved my icinga2 installation that kept exploding in memory usage, when i (and agents from sub-zones) was hammering its api

when i preloaded jemalloc , memory remained at significantly lower levels, and - more importantly - it was stable.

there seems to be no single correct solution to memory allocation, depending on the workload

you know, i don't think saying "got it right" is correct here.

Because if you are presenting an option of walking to a car wash as a valid choice, it suggests you just want to get there, and not wash your car.

Just like walking/driving to an airport doesn't necessarily mean you're going there to catch a flight (although it's a common reason). might as well be picking someone up. or working there.

i hope that whoever caused all those bugs doesn't move later into developing Azure.

(part of me actually wishes it would happen, ngl).

seems like a common occurence in the region, although the virus is highly contagious and very deadly.

i wish we instead dropped js for something vastly more sane.

maybe instead of HL3 they will deliver linux on the desktop for the masses.

because that's the foreseeable trajectory at this point

what a trip down memory lane.

for some extra nostalgia, check out "one finger death punch 2" game (and its prequel). i bet it's sort of an homage to those animations.

reject outright. ask to split it into reasonable chain of changesets.

this looks like maintenance nightmare going forward, but i could be wrong.

If you are stuck on specific pg version for a while, maybe it's worth it.

vibe coding could not have come at a worse moment.

true, i saw a thread recently on reddit where guy hand-tuned compilation flags and did pgo profiling for a video encoder app that he uses on video encode farm.

In his case, even a gain of ~20% was significant. It calculated into extra bandwidth to encode a few thousand more video files per year.

FWIW i had it with icinga2. so now they actually preload jemalloc in the service file to mitigate the issue, this may very well be what you're talking about

in case someone is interested: https://github.com/Icinga/icinga2/issues/8737

(basically using jemalloc was the big fix)

https://icinga.com/docs/icinga-2/latest/doc/15-troubleshooti...

"Make one Ubuntu package 90% faster by rebuilding it and switching the memory allocator"

i wish i could slap people in the face over standard tcp/ip for clickbait. it was ONE package and some gains were not realized by recompilation.

i have to give it to him, i have preloaded jemalloc to one program to swap malloc implementation and results have been very pleasant. not in terms of performance (did not measure) but in stabilizing said application's memory usage. it actually fixed a problem that appeared to be a memory leak, but probably wasn't fault of the app itself (likely memory fragmentation with standard malloc)

* "if they want Adobe to be successful".

i wonder how this all win play out in the end.

i think the problem started when quantity became more important over quality.

you could totally compete on quality merit, but nowadays the volume of output (and frequency) is what is prioritized.

in case you don't know, some Gameboy games required to have Nintendo logo in the game data as part of copy protection. allegedly that was legal protection against bootlegs.

https://www.copetti.org/writings/consoles/game-boy/#anti-pir...

Playstation2 used something similar. ( https://github.com/mlafeldt/ps2logo )

I suppose it gave companies in question additional legal leverage - they could not distribute copies of games without violating the trademark laws.

imho it's embarrassing that this got merged in the first place.

it's not a major flaw, and no exploit. but it seems as if nobody paid due attention to actual changes.

this explot is basically "death by a 1000 papercuts", now that i think about it.

i just thought it was "this" shortened to DOS standards.

web2.0 was about user generated content.

i would say this is the so-far elusive web3.0

The cassette tape in an Etak Navigator was read at about 200cm (80″) per second!

i struggle to imagine how did the tape handle it.

the problem was the nouveau would do this before when firmware was easy to intercept from the driver (and could be extracted easily). the newer driver uses different methods of firmware upload and it's a real chore to do so now.

so nouveau gave up on it. they also expected nvidia to drop some firmware.

now that newer cards have GSP.bin firmware, which can be interfaced with easily - things are different. i would wager a guess that it's similar to atombios from amd. you just call a function in GSP and it knows what registers to poke with the right values to achieve what you need.

he's doing another pump and dump

sony pulled Otheros feature from ps3, and people still use Sony consoles.

i tried chatgpt to produce some ansible playbooks for postgresql_privs module - that module uses or used to use rather convoluted logic and i could never exactly wrap my head around that one ( and i had a rather non-trivial use case for it, so maybe that contributed to my struggles).

the produced playbooks passed the syntax check, that much i can admit. it went downhill from there, producing files with completely invalid keywords.

don't quote me on that but i read somewhere that microsoft has a strict policy of NIH in their codebase - everything gets reimplemented from scratch unless it's completely unfeasible.

The only problem might be the software patents that their code leverages.

ok, what are those youtube stories? honestly, i don't think i saw one.

that is because HR exists to protect the company, not the employee.

it would be a big media storm if that aforementioned reverse thing happened.

i think it's a brave assumption that gold will forever be as valuable as now.