Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don’t mean to be snarky, but when seeing “make our neat package registry easy to use we wrote our own custom IDE for you to develop in,” I can’t help but think this project has jumped the shark.

Does Pika really expect devs to be so drawn to their package registry that they want to write in Pika Code instead of their existing editor of choice? Is publishing packages in JavaScript really that hard?



If there was an extension for VSCode, maybe I'll consider using it.

But using your fork of it instead? Not a chance.


I just don't understand dumping my entire development environment to solve one of the easier parts of package development.


I think the whole point of Pika was to not require a complex local development environment for coding websites. Installing a bunch of stuff is probably the #1 or #2 main complaint about modern frontend and a huge roadblock for newbies.

By using their CDN you can already make pages and apps with just a text editor, without node, npm, webpack, etc.

I think it makes sense for them to try to improve the experience of package creation and publishing too.


Why would those hypothetical newbies need to publish packages? That’s not something you should care about before quite some time when you’re learning a language.

Or is the idea to have a registry full of tutorial packages?


I never said that newbies would or should be publishing packages.

Pika CDN and @pika/cli can potentially make newbies' lives easier, but it doesn't mean that every project under the Pika umbrella is aimed exclusively at newbies.


Fair enough.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: