The challenge is that the level of complexity with rules interactions in MtG is absolutely enormous, especially if you want to allow the freeform format, which allows all sets and cards.
Let's not gate keep the word "creator". Writing new software is just as much "creating" as whistling a tune, writing a song, drawing a new piece of art, painting a miniature, carving a stone, or anything else. Something exists now that didn't exist before. It has been created.
You're agreeing with the comment you're replying to. The parent comment is saying the "playbook" doesn't say to give a date, and they've given one so absurdly soon that it's impossible to hit. The "get signups for a fake product" is out of the playbook, promising it 4 months from now when it doesn't exist at all is not out of the playbook.
What apps are you referencing that Meta/Facebook launched and failed to clone Snap/Houseparty/IRL? Their snap competitor is Instagram, and it's still doing very well. Instagram is _also_ their TikTok competitor, and Reels has done a solid job in that space as well.
All of your examples are unique, distinct separate product and problem spaces, whereas Threads is pretty aligned with Instagram as-is. A lot of the plumbing for Instagram is likely reusable for threads, and a lot of the same optimization techniques might apply just as well (or with minor tweaks). I don't think this is as much "launch something new" as it is "instagram with a mask on".
A negligent civil engineer that failed to verify construction details provided by GPT, which later led to a bridge collapse, would lose their license. A negligent doctor that failed to vet a treatment protocol to a patient that later caused them harm would lose their license. Negligence is a fair, reasonable, and valid reason for someone to be determined unqualified to practice their profession in the future.
The average comment is more in-depth because there's a long history of thoughtful moderation by people like dang. The community has learned what the bar is, and now holds itself to it (more or less). The social standards here didn't come for free, and if you were to take a random selection of the HN audience and get their Reddit profiles, I strongly suspect you'd see a notable difference in the quality of the content they post to the different platforms.
Any major changes to gut biome will definitely take more than two weeks. Anyone who has ever had to do an elimination diet will tell you that it can take 4 to 6 weeks for things to normalize when making dietary changes.
The benefit of buttons isn't in the response time, it's in the tactile feedback that makes it so you don't need 16ms response time. I heard it click, I felt it click, it clicked. If the thing I wanted to happen doesn't, it's because it's broken and not because I can't tell if I clicked the right spot on my iPad. Not having to take your eyes off the road in these cases is the benefit of buttons, and no improvement to response time in touch screens will fully solve that.
If the server code is too complex, at least give me an OpenAPI spec (or equivalent) that the server must adhere to, so I can spin something simple up on a Raspberry PI to solve the problem myself.
Just a friendly heads up, but Go Transit is also the name of the regional transit system in Southern Ontario, Canada (originally named GO Transit for Government of Ontario Transit, as it started as a part of the Ontario Ministry of Transportation). Calling it out because your app looks cool, but with the direct overlap in name and product focus, it could lead to a future trademark dispute if your app takes off.
This is funny, because often times as soon as you add benchmarks, the masses will scream that the benchmarks aren't useful because they don't test real world conditions (global network latency, wide ranges of queries with effectively random patterns, etc.). Benchmarks feel a bit like a "damned if you do, damned if you don't" situation. That said, I love me a good benchmark.
I'm always fascinated by Dwarf Fortress whenever I cross paths with it, particularly from a technical architecture point of view. How did they architect the history simulation? How do they efficiently update everything on each tick? What is the game loop like?
If anyone has any resources or links to articles, either definitive from the DW developer, or conjecture based on exploration and research, I'd love to learn more about how DF works.
While I think the assessment that modern medicine is more effective, and often stands on the shoulders of these types of historically used plants, not everyone has safe access to modern medicine (either because "modern" medical treatments aren't available where they're located, lack of finances to pay for it in egregiously overpriced areas, or general mistreatment by the medical community). Using alternatives, while not as refined or high quality, is better than nothing.
What OP was saying was a few tweaks could make a monospace variant, which would be a nice programming font. I don't think a monospace variant is available right now.
It might be a vain metric in the aggregate, but to an individual, the people who are passionate about their sport and have worked nearly their entire lives to become the best at it across the entire globe, it's an accomplishment that is nearly incomparable.
Note: You can see all the rules here: https://mtg.fandom.com/wiki/Comprehensive_Rules