In before "what browser are you using", this is Google Chrome.

And... it made software less secure

Slop slop slop slop slop.

I wish AI were anything else than slot machines. Sometimes you win! But mostly you're just busy pulling thay lever over and over again, hoping for the output you want.

Probably gonna cancel this subscription soon.

The audio generative AI simply does not function as advertised. You're offered the possibility of adding a new instrument track, and you can choose an instrument, but the generated audio turns out to (basically always) be a song, not an instrument track. An interesting one! But not what I asked. 😅

I start realizing from the UI that this product is probably for the most part vibe coded. Stuff like: multiple "collapse sidebar buttons" differently styled and conflicting with each other. Which immediately made me lose some respect for the product.

But worse...

That was very sophisticated and good, but most of the work was in cycle/dom, which I wouldn't build. I would just use React, much like how cycle/react currently is written. I'd also drop the functional programming because embracing the React ecosystem means those child components are anyway not pure

staltz.com/use-react-in...

JSX can burn in hell as far as I'm concerned

Frameworks are opinionated ways of building apps, so I would make those opinions clear and support only one way of working with Cycle.js.

No "flexibility", but a lot of interoperability (via React with its ecosystem).

Good thoughts, and I respect you. But this thread is a good counterexample of what I'd like to build. As soon as a good open source tool comes out, people start asking for support for alternative building blocks (RxJS, xstream, Preact), which quickly dilutes the whole thing.

Because it's the new HTML. No point in competing with it. Too many good React component libraries out there that must be utilized

Muuuuito velho

"AI coding" / "vibe coding" is ridiculous and I hope the industry eventually sees it. The amount of nonsense code being produced is worrisome

GitHub Copilot in my IDE is still important for me. I use it for autocompleting 1 or 2 lines of code, not much more than that. Just helps me type less and preserve my muscles

Sigh how do I edit posts, I meant "this couldn't be more true" not "further from"

Anyway, I still believe in diagramming to aid in documenting and understanding code. Mermaid is a gem for that.

If there is one programming skill that has paid off in my career is debugging thoroughly, investigating, troubleshooting, and loving the problem, not jumping to solutions.

(Tangential, but Cycle.js couldn't have fulfilled that dream because its charts turned out to be dynamic AND nested, which no one can follow. A chart must be static for the whole duration of the program, for it to be useful as a reading and teaching tool)