CodePen 2.0
41–50 of 56 posts
Re: CodePen 2.0
#42Earlier quoted context omitted.
Not necessarily! Linux is incredibly complex. AWS is incredibly complex. Next is incredibly complex. GitHub is incredibly complex. We need simple tools and we need complex tools. It's the middle ground that's hard to navigate.
When we're lucky, that complexity is mostly locked behind abstraction and you only occasionally have to care. Of course those you usually discover at 3AM on a Saturday
Re: CodePen 2.0
#43(meaning I found it hard to read and focus)
Re: CodePen 2.0
#44But, lately. I often go to Gemini Canvas and just ask for some simple thing I want like "make a browser theme generator that lets me pick a base color and then the site picks graphic design principled colors for the rest of the theme's colors and lets me download a theme extension ready to use. Have a browser preview of how the theme will look in the page". < 5 minutes later I have such a thing. Sometimes I want to prompt for changes, other times I just want to tweak a few things by hand, hence, wanting it in codepen.
Re: CodePen 2.0
#45Re: CodePen 2.0
#46I've been a CodePen user since the very early days. Have always loved the platform. I hate to be negative, but I'm honestly not a fan of the 2.0 release. What I loved about CodePen was just being able to try out something really quick and simple. But the new interface makes me feel more like I'm building a website inside of a website.
If you want to go back to a simpler editing experience, https://plnkr.co/edit/?preview might just do the trick for you. Hasn't changed in literally years. Nowhere near the polish or flair you see from legends like Chris Coyier though.
Re: CodePen 2.0
#47I've been a CodePen user since the very early days. Have always loved the platform. I hate to be negative, but I'm honestly not a fan of the 2.0 release. What I loved about CodePen was just being able to try out something really quick and simple. But the new interface makes me feel more like I'm building a website inside of a website.
I suspect they're doing this because of AI. Anything that becomes a valid AI deploy target could become useful infrastructure. The rate of humans testing things in a CodePen will slowly fall off, similar to Stack Overflow. The rate of AI models deploying to CodePen 2.0 will pick up significantly. In some number of years, the amount of code written per month by machines will dwarf all code written by humans from 1957…
Re: CodePen 2.0
#48Earlier quoted context omitted.
That's the hard part about tools like this. They're too simple to be used for anything important, and as soon as the creator follows that path you end up in a situation where it's too simple for anything complex and too complex for anything simple. Amazing platforms like Glitch ran into this problem. (Some did pull it off! Like how Vercel built a kingdom out of `now`.)
The more complex the more fragile. The simpler the solution the more robust. This, I feel, is an overall truth to software development. And simpler solutions, as far as I know, are usually the more useful ones.
I think we can have complex things, but they can be simple (to use, to understand, to manage). But it is really hard to make a complex thing simple. The straightforward way is to make it complicated, and most items remain that way.
Re: CodePen 2.0
#49I've been a CodePen user since the very early days. Have always loved the platform. I hate to be negative, but I'm honestly not a fan of the 2.0 release. What I loved about CodePen was just being able to try out something really quick and simple. But the new interface makes me feel more like I'm building a website inside of a website.
Codepen was indeed nice for quick and simple experiments, but LLMs take away the need for that.
Re: CodePen 2.0
#50I've been a CodePen user since the very early days. Have always loved the platform. I hate to be negative, but I'm honestly not a fan of the 2.0 release. What I loved about CodePen was just being able to try out something really quick and simple. But the new interface makes me feel more like I'm building a website inside of a website.
(also, the sister site jsbenchit[1] has been one of the more reliable microbenchmarking tools among the various sites I've tried - most end up triggering deopts or introducing "noise" in a way that makes the output less reliable)