Open sourcing pouet.net ?
category: offtopic [glöplog]
Hey guys, I'll be short.
I spent some time on pouet again, e.g. this tiny pouet API, but also cleaning up the mess, and I think it could be cool to open the source of pouet, for many reasons.
I'll still be the one to merge pull requests for now to prevent shit happening. You know...
Who's in ?
I spent some time on pouet again, e.g. this tiny pouet API, but also cleaning up the mess, and I think it could be cool to open the source of pouet, for many reasons.
I'll still be the one to merge pull requests for now to prevent shit happening. You know...
Who's in ?
go ahead :D.
Analogue: I'm a little confused - how does this match up with the work Gargaj and others has been doing for years, both with cleaning up what can be cleaned up as well as working on Pouet 2.0? I'm confused because this seems to be an initiative that's directly going against their design decisions?
I never thought I would say this but:
What Gloom said
What Gloom said
Yay for open sourcing Pouet.
Super Yay for exposing an API.
Nay for throwing away all the efforts Gargaj et al. have done on Pouet 2.0
Super Yay for exposing an API.
Nay for throwing away all the efforts Gargaj et al. have done on Pouet 2.0
Why not finish Pouet 2.0 first and than open sourcing Pouet ? (just my 2 cents)
The idea of opensourcing Pouet is great, but the work on Pouet 2.0 goes on from 2008 (am I right?). If we still wait for Pouet 2.0, Pouet would risk not being opensourced ever.
So to open this code is the right choice, unless we have a precise deadline for Pouet 2.0.
yeah, this would be a good time for a status report on whatever is going on behind the scenes (hoho). a "web 2.0" version of pouet.net seems like a myth, but who knows - even demozoo is beginning to stir again :)
(that said, pouet.net works as it is).
(also, I'd much rather see demos than websites!)
(that said, pouet.net works as it is).
(also, I'd much rather see demos than websites!)
Let me clarify: I'm not against open sourcing Pouet (when the code is ready for it), and I'm absolutely NOT against an API surface for the Pouet DB (when the code for the API has been tested and verified, preferably through collective efforts), but the timing and scope of this particular move seems entirely random.
individuals do what they want, they are independent agents
What gloom said.
why would anyone want a pouet 2.0? if it is not broken, why fix it? why not just go back to watch the 1000+ photos of yourself drinking beer on slengpung and let analogue do what he wants to his site? Anyhow, Great to see that analogue is back!
"To fix something" is not the only reason to change something. Improving stuff is. I don't consider "fix me beautiful" a state-of-the-art feature, really.
i dont know about pouet2.0, but pouet3.0 will be hosted with sticks and stones
Exactly what Gloom said.
OTOH open sourcing Pouet 2 could be sweet as I have no doubt that this codebase is actually usable. But Gargaj and co. are better equipped to decide what to do there.
JuvenileShitHead or whatever is your real pseudo/name user #2100: I'm glad you ask why would anyone want Pouet 2. Well, from the impression I got when I had access to the FTP and DB of Pouet a few years back, the code base of Pouet 1 is so bad that it's near impossible to add features, fix bugs, add support for unicode on the onliner, bring small improvements in a consistent way. ...
Simple things like ensuring that the actual username of each user is displayed along with JuvenileShitHead is/was NOT possible to do in a single place in Pouet 1. The code base of Pouet is THAT bad.
OTOH open sourcing Pouet 2 could be sweet as I have no doubt that this codebase is actually usable. But Gargaj and co. are better equipped to decide what to do there.
JuvenileShitHead or whatever is your real pseudo/name user #2100: I'm glad you ask why would anyone want Pouet 2. Well, from the impression I got when I had access to the FTP and DB of Pouet a few years back, the code base of Pouet 1 is so bad that it's near impossible to add features, fix bugs, add support for unicode on the onliner, bring small improvements in a consistent way. ...
Simple things like ensuring that the actual username of each user is displayed along with JuvenileShitHead is/was NOT possible to do in a single place in Pouet 1. The code base of Pouet is THAT bad.
Don't feed the dubmood troll, he'll just think that he actually said something useful for once and didn't just replay old shite..
not having presented a pouet 2.0 after 5 years in the working, and then accusing analogues goodwill to be random and start crying is, very much random. dont you think?
POUET 2.0 :D
Is 5 years even enough? I've been away about that long and remember it being talked about.
Is 5 years even enough? I've been away about that long and remember it being talked about.
5 years in making > 13 years bitrot.
p01... I wish you never have to read that kind of feedback about something you wrote
I'm pretty sure there are many ways you can make your point without being disrespectful
I'm pretty sure there are many ways you can make your point without being disrespectful
Quote:
5 years in making > 13 years bitrot.
Yeah I'm sure Gargaj has been working really hard for 5 years on a website that shows a screenshot, download link, and user comments for some demos. I mean come on. :D
Oh and Gargaj I'm not busting your balls. You didn't have enough time or interest or whatever, it's cool... Especially since pouet1 has worked ok (even if people haven't been able write Japanese in the "onliner" or see multiple user names for one account).
Just because something isn't finished, polished and published doesn't mean it has no intrinsic value. Pouet 2.0 is accessible in a beta-state already, so I don't understand the urgency from Analogue to suddenly start slapping things together.
Oh, and Sak: shut the fuck up.
Oh, and Sak: shut the fuck up.
gloom: How about sticking to pathetic attempts at trying to impress people who aren't even interested, Mr. Outreach.
it's funny how this very same conversation pops up every now and then, like every 6 months or so :)
of course this is mr. "glass is half empty" speaking, but p01 is actually correct - from what i've seen of the codebase, it's irrepairably awful. plus i really don't think open sourcing it will solve anything, but i'm all up for being proved wrong.
pouet in general is sort of between a rock and a hard place - it's difficult to improve it gradually, and it's difficult to completely overhaul it in the sense that it wouldn't be pouet anymore, at least for some. i'm foreseeing an eventual replacement for pouet at some point, say, after demozoo finally launches and reaches maturity in a year or so.
and there's nothing disrespectful about saying the codebase sucks. i'm quite sure the stuff i or p01 did 13 years ago is pretty awful too.
of course this is mr. "glass is half empty" speaking, but p01 is actually correct - from what i've seen of the codebase, it's irrepairably awful. plus i really don't think open sourcing it will solve anything, but i'm all up for being proved wrong.
pouet in general is sort of between a rock and a hard place - it's difficult to improve it gradually, and it's difficult to completely overhaul it in the sense that it wouldn't be pouet anymore, at least for some. i'm foreseeing an eventual replacement for pouet at some point, say, after demozoo finally launches and reaches maturity in a year or so.
and there's nothing disrespectful about saying the codebase sucks. i'm quite sure the stuff i or p01 did 13 years ago is pretty awful too.
let me rephrase that: the reason why i don't think open sourcing the codebase will solve anything is that pouet needs someone (or some people) with three things: a) the vision, b) the skills, and c) the time. open sourcing in this case sounds like you've got someone who's hardly involved these days, accepting pull requests from people who are eager to contribute and to prove themselves but who don't know what the hell they're doing :)