izabera
izabera on Hacker News
this argument does not make a ton of sense to me. would it be better if they were charging by the byte? that's fixed and you can measure/control how many bytes you send, but you still have little control over how many bytes you receive, or whether those bytes are useful in the first place.
likewise, suppose you buy a 1gb plan from a mobile isp, then you find a youtube tutorial that you're interested in. the nugget of information you need is 23 minutes in, but you have no way of knowing that upfront, it may not even be there. you can exert some control over how many bytes you send in the headers of the get requests to youtube, but you have little control over how youtube compresses the video you requested. also you download 2 30s ads and a sponsored segment before finding what you were looking for. unfortunately you're now out of data on your plan. do you blame your isp for their shady sales practices? is it youtube's fault? what did you pay for?
that's one confusing title in $currentyear...
they're generally pretty but they should really hide the cursor, it looks offputting in basically all cases
the secret is to keep things ˢᵐᵒˡ
> Unlike other apps or cookbooks, we’ll teach you the hows and whys of cooking.
this is literally like every other app or cookbook
"is shared_ptr thread safe?" is a classic question asked thousands of times. the answer by the way is "it's as thread safe as a regular pointer"
atomics aren't free even without contention. the slogan of the language is "you don't pay for what you don't use", and it's really not great that there's no non atomic refcount in the standard. the fact that it is default atomic has also lead people to assume guarantees that it doesn't provide, which was trivially predictable when the standard first introduced it.
maybe some car pool services for the most frequent routes could run at regular intervals. there could even be some predefined stops to efficiently batch many people getting on and off the car pool at once
i'm struggling to imagine many negative effects on society caused by the specific papers in this list
random example, may or may not come from a real situation that just happened:
- other team opens jira ticket requesting a new type of encabulator
- random guy who doesn't know anything of how the current encabulator system works picks up the ticket for whatever reason
- 10 minutes later opens a 2000 line vibe coded pr with the new encabulator type and plenty of unit tests
- assigns ticket to the person who designed the current encabulator system for review
- encabulator system designer finds out about this ticket for the first time this way
- "wait wtf what is this? why are we doing any of this? the current system is completely generic and it takes arbitrary parameters?"
- waste an hour talking to the guy and to the team that requested this
- explain they could just use the parameters, close pr and ticket
it's so incredibly productive
deepseek is from china and all their papers have been very well received
thanks for taking the time to make it work on my code :)
Posted by
izabera on Saturday August 16, 2025 @09:35AM
from the media.ccc.de dept.
not trying to be a hater but how is 100mb/s high performance in 2025? that's as performant as a 20 years old hdd
I post a lot of silly personal code on GitHub and the vast majority of issues/pull requests I receive are completely inane and generally not remotely helpful. Things ranging from "I've added a subtle shadow effect to the title in the readme" (thought it was someone's first pr just to get started but that wasn't even the case) to "I've added support for $obscure_system_youve_never_heard_of" (well meaning but the code is now 4x longer and a maze of ifdefs so maybe you should just keep it in your branch?) to "I tried this on my extremely outdated system that's old enough to vote and it threw an error" (yes it very much will throw an error, none of this can work there and I cannot help you).
But a few people have reported certain fundamental problems with my approaches or have otherwise put in a significant amount of work to debug and fix issues, and they've been extremely helpful and I can only hope I'll get more of them in the future.
Posted by
izabera on Saturday August 02, 2025 @01:59PM
from the youtube.com dept.
ffmpeg is not too different from a microbenchmark, the whole program is basically just: while (read(buf)) write(transform(buf))
what a "real life application workload" looks like is entirely dependent on your use case, but fio is very widely used in the storage industry
it's a good first approximation to test the cartesian product of
- sequential/random
- reads/writes
- in arbitrary sizes
- with arbitrarily many workers
- with many different backends to perform such i/o including io_uring
and its reporting is solid and thorough
implementing the same for your specific workload is often not trivial at all
> Today we’re releasing an API that gives you and your agents full-stack backends. Each backend comes with a database, a sync engine, auth tools, file storage, and presence.
this is a hosted lamp stack, we had it 20 years ago. is cpanel is not fashionable anymore?
Posted by
izabera on Saturday July 05, 2025 @08:53AM
from the github.com dept.
this looks convenient to use from c++, but the example code it generates is rather suboptimal (see
https://godbolt.org/z/3rWceeYoW in which no normal compiler would set up and tear down a stack frame for that) so i'm guessing there isn't any support for optimisations? what's the advantage of this over just compiling + calling dlopen/LoadLibrary on the result?
thank you i was so proud of it lmao
they do place themselves as an alternative to make, but imho they're entirely different and not at all comparable. make is centered around creating artefacts and not rebuilding what is already built. just is a command runner.
this is literally never an issue because every editor automatically uses tabs for makefiles
30 lines are always going to be easier to read/write/debug than 3000 lines, so it'll probably remain easier (for both humans and machines) to write correct code in languages that make it possible to express ideas concisely and elegantly.