izabera

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

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 :)

tested it on this https://github.com/izabera/cube.bash/tree/timep

i ran `source /path/to/timep.bash; timep ./cube.bash "R U R' U' R' F R2 U' R' U' R U R' F'"`

without profiling https://i.imgur.com/JE93ony.png

with profiling there's a bunch of errors but overall it's ~300x slower https://i.imgur.com/qif7Qp3.png so i'm sceptical on all the efficiency claims

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

what's the problem with that? we have erotic texts dating back thousands of years, basically as old as the act of writing itself https://en.wikipedia.org/wiki/Istanbul_2461

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.

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?

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?

did something along those lines a while ago https://github.com/izabera/j trying to keep an interface similar to jq

thanks, i fixed it. it was only happening on bash 3.2 and i don't use a mac so i didn't see it. https://github.com/izabera/bitwise-challenge-2048/commit/73f...

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.

oh boy do i have the paper for you https://proceedings.neurips.cc/paper_files/paper/2014/file/f...

what does "huge democratization of work" even mean? what world do you people live in? the current global unemployment rate on my planet is around 5% so that seems pretty democratised already?

the third point is applicable to a number of tools and systems, but who would claim that using git doubles your security surface?

every time this comes up, the thread immediately gets 300 comments suggesting that everyone pays whatever amount to keep the bots at bay

twitter sells blue checks for $8/mo and it's full of bots

I am now focusing on checking your proposition. I am now fully immersed in understanding your suggestion. I am now diving deep into whether Gemini 2.5 pro also does this. I am now focusing on checking the prerequisites.

i don't understand what market there is for such a product. deepl costs $8.74 for 1 million characters, this costs $1.99 for 5000 (in the basic tiers, and the other tiers scale from there). who's willing to pay ~45x more for slightly better formatting?