574 karma · joined December 5, 2017
You're rewarded for participation with fake nonsense points, same as all the forums of yore.
The maker communities, music subs, and local/city subs I'm in do not have any of these problems.
I suspect there's no actual difference, the author just liked the sort of people who were willing to deal with the traditional "crappy forum" interface for the sake of connecting around some niche hobby, and it provided enough friction to promote adherence to the community's culture.
There are just more people on the internet now. The problem always boils down to some version of Eternal September.
https://github.com/BrenoFariasdaSilva/Authy-iOS-MiTM is going to be my project for the afternoon.
The takeaway should be that watermarks aren't very reliable and you should keep your guard up anyway.
Is this normal humans kicking the tires on a new model, or a few whales doing serious benchmarks?
One connects with Thunderbolt only. The other connects with Display Port for video and USB-C for the rest of the built-in dock.
It's OK most of the time with the nipple switch. My one piece of advice is *avoid HDMI*. I learned after getting this monitor that the HDMI protocol is a petulant unstable little shit that does not tolerate renegotiation well. Get yourself a USB-C to DisplayPort cable.
You're suggesting that a language with concurrency is simpler/easier than a language that does not have concurrency.
https://blog.andymasley.com/p/data-centers-heat-exhaust-is-n...
> The one remaining question: why the clean step change?
In the middle of this piece, he runs into a critical flaw in his reasoning and just shrugs it off.
What's your plan?
I think it's just important context to keep in mind that these sorts of takes are very typical to top https://bearblog.dev/discover/ in the same way that certain types of posts are designed to rank well here. I considered migrating my blog there earlier this year and ended up deciding that, while I loved the product, the community was not healthy.
[1] https://forkingmad.blog/ai-summary-blog-post/
[2] https://blog.spu.io/you-dont-want-to-make-things-you-want-to...
[3] https://blog.happyfellow.dev/simulacrum-of-knowledge-work/
Performance is poor and there are a million other reasons to beat up on GH. This is not one of them.
AI is the future, so we need cursors of the future that simulate the frustrating lag and imprecision of LLMS. Dots chase other little dots around and do inscrutable little animations.
Actual answer: You need javascript to see their dumb custom cursor.
I have tasks that used to take ~3-5min with Sonnet 4.6. With OpenRouter Kimi, the same task takes 10+ min. It's also just obviously slower in opencode sessions. The results are good, and I love the lower cost, but the speed can be frustrating.
Any specific examples?