marcx

@dead_baseball Same way I'm also posing a question where the answer is obviously red, at what point would you switch to blue

@marcStevenson01 This is not an argument of red versus blue in the original question. A lot of people are reading it like that. This is a different question where the first answer is obviously blue and posits at what point would you switch to red.

Let's say red is up by 1 vote. There's only two people left in the world to vote, you and someone else, and you both know red is up by 1 vote. Which one do you press? Let's say red is up by 2 votes. 3 people left to vote. Which one do you press? (cont)

@ggs21725470 @dead_baseball Exactly the point(I'm team red btw), knowing the number of votes will influence your choice, in the original there's no way to tell if enough people are also going to press blue if you do. In an ideal world we could all go with blue trusting others will do same

@marcStevenson01 @dead_baseball you worded it wrong. if blue is down by X and X-1 left, blue already lost so everyone is voting red

@dead_baseball This only works because you know the total number of votes for each side, which definitely changes how you choose your vote. Same arguments could be made for the red side, if blue is down by X votes and X-1 people left to vote, what would make you change your vote to blue

Let's say red is up by X votes. X+1 people left to vote. What number would X have to be for you to change your vote from blue to red?

@ToniSmalloni @Gengar11teen @owleyedwisdom Or blue only dies based on how blue votes

@Gengar11teen @owleyedwisdom Every single rephrase and metaphor continuing to not include the part where Blue only dies based on how Red votes.

Red button pressers not understanding that the question has everyone already on the tracks

I don't get blue button pushers, you're willing to let's some random strangers decide your fate just so you can feel like a hero for saving people or what

No way youube has this

Dune Kwesi Arthur - Babylon Interlude Movie Edit by me

@0xSero Ok.

Giving away 5 Opencode Go subs Winners selected randomly from comments in 24 hours.

Even worse for monthly manga

@camsoft2000 @dillon_mulroy The more you depend on ai agents to code, the more you'll have to rely on them when things get out of hand

I’m getting to the point with one of the projects I work on where the complexity of AI slop is becoming a real issue. While I can still happily prompt the agent to add x feature and it will do so and it will likely work perfectly, the code is just getting too complex and fragmented. Agents love to copy and paste and keeping patterns DRY is a real challenge. The agent will start diverging all those copy and pastes until you’ve got loads of similar but slightly different blocks of logic. Again it all still works and solves the problem I’m after. But I just can’t get any kind of consistency anymore, the code is a mess and I just don’t have a handle on it. I want a clean unified architecture but agents just code with tunnel vision. The project is now too big and complex for an agent to fully reason with and too big and complex for me to reason with. The only real solution is a complete rewrite. Maybe this is the way things will go. Code will just become disposable. I don’t really want to care about the code and to be honest I don’t but I do care about consistency and maintainability and the AI slop is hurting those very things I do care about. I know some will say “I’m holding it wrong”, use x,y,z skill, tool whatever and already use tools and anti slop skills, plans, docs, etc but the outcome is the same. Vibe coding something into existence is truly magical. But turning it into a mature product with months of iterations is painful. I can’t even hand code this thing because I don’t understand the code anymore and I’m too lazy to try and code myself because I’m addicted to AI. So what’s the solution, either start again and accept that’s just the way we have to roll, or just carry on fighting the slop and accept each new feature will take longer to implement than the last. I’m tired. I’m addicted.

Unfortunately doesn't fix the issue of looking the codes up, a nicer api will be something like fast api's status module which combines both the staus code and the human readable version of the code

-

I have been thinking about this a lot. I think for a great many of engineers, the ones who did it because they loved it only to discover that money was in fact at the end of the rainbow found both the journey and the destination satisfying. In fact, I think I can argue with authority that the destination was only satisfying as the journey was difficult. The hard-fought evenings spent toiling away on an idea and codebase that slowly gives way to your vision was an incredible experience. The group of people that fell into this category of hard-fought journey and destination we will call them tinkerers. One thing tinkerers have always hated is the already known problems. The journey is clear as day. The obstacles minor inconveniences. Its purely a matter of typing the solution into the terminal. This is also why I think so many of this group goes out and does open source, or starts companies. Work largely falls into this category with few exceptions. From this reason is why I largely find UI work soul sucking. I know the solution, its a matter of just looking up the details and putting it into my editor. yawn. CSS, flex box this, grid that, put the tailwind classes in the bag. To me, the LLM software world is with little to no journey and discovery. Its more of simply taking my high level idea and just formulating it into testable, atomic chunks that can be verified. I have traded my favorite part, discovery and raw creation, with itemized list of TODOs and patience and "No Mistakes." To this, every morning from 6 to 9 I simply just hand code every thin. even UI things. It is because I want journey and discovery and raw creation. Maybe one day comes and its just so futile that I stop this. But for now, I still see such great value in this. I see such better thought through products. Because slowing down and truly thinking through everything. The architecture, the design, everything is an expression of discovery and creation. And I love it. I am sure there will come a day, maybe even in the next 6 months where I change my mind. For now, I pursue the love of the game intentionally. I do also believe that there exists people who get the same joy I got from building with tears and sweat by prompting LLMs. I am positive of it. I just don't understand how. But people love UI work. I also don't understand that.

one day, you'll realize that no one was really watching, and you could have done whatever you wanted. i just hope you don't figure it out too late.

@IonKorol @sebastienlorber So did they not clone the framework? Whether it was built on top of vite or not, they still cloned next js.

@sebastienlorber The tone matters. I don't want to take away from what they accomplished. But they didn't build the framework from scratch or anything. They reimplemented the framework layer, but stood on the shoulders of Vite. This gives me "Claude built a C compiler" vibes.

Projects like Next.js can be cloned by AI in a week now So... sharing your test suite can become a risk for the sustainability of your project I also suspect more open-source projects with commercial goals will adopt closed-source test suites in the future, as explained here

@KaraBharat Just use an object literal

JavaScript Map: Simple, cleaner, and powerful lookup pattern! #JavaScript

@ryanflorence @trueadm @necolas Isn't event.stopPropagation/stopImmediatePropagation rather more fitting for this functionality?

@trueadm @necolas yep <button on={[...on, press(handler)]} /> and then automatically handles event.preventDefault of the same types so later handlers aren't called, no more screwing around with composeEvents(props) messes, just built in

I actually really like Remix 3’s event pattern - in fact, it was literally what we explored with React Flare like 5 years ago whilst on the React team with @necolas. If you can build event subsystems that compose as self contained logic with their state then it simplifies things a lot. We didn’t ship React Flare because of many reasons - not related to the credits of the idea. I still think there’s a valid place for them though. Personally I didn’t find any of the other Remix 3’s experiments that impressive. They’ve all been done before in some capacity and found to have pitfalls. I admit though that every pattern or idea has pitfalls, but that’s my vibe. A good example is the DOM diffing on Frame, how does that work with dynamic components and lists? The whole getting the developer to do update() isn’t new either, Bobril and Ivi did that 5+ years ago. I congratulate new ideas and shared reasoning though. I noticed `context.get/set’ API in there - just like Ripple, which was validating. One question @ryanflorence, how do you spread events through composite components in this pattern? Do you expect people to pluck “on” and re-spread it?

Ever dreamt of having a job where you deliver mail to the residents of a tiny planet? Us too. messenger.abeto.co #webgl #threejs

@KaraBharat No need for useMemo here, the computation is not that expensive

A quick and neat trick that keeps your code clean ✨