Yes. Entirely different software. Different programming language and tech stack. Also different system requirements and feature set.
Not sure about the developer spirit. PieFed development has traditionally been moving crazy fast and it gets like several new features every month. I think that’s a matter of focus. It comes with consequences, though. But I think overall the project is doing a good job with trying to be compatible to other software. Prioritizing important stuff and doing the right thing. Sometimes some things get done, rather than be 100% perfect. But past experience tells me things often get fixed or changed around once necessary. Not sure if that’s a wise decision here. The JSON exchanged between the servers is probably extra work if changed around later.
I’d legit rather the software develop and occasionally spaff it up and break the server for a few hours every once in a while rather than the non-moving 5 year plans of Lemmy development.
Also, usually piefed.social is the only instance that gets hit with this as, being the flagship server - it takes the brunt of more ‘experimental’ features. Most other servers don’t upgrade to the latest iteration until they’re sure it’s not going to break them.
break the server for a few hours every once in a while
That’s not what botching the protocol does. It opens the way to mess up the posts that shouldn’t be messed up, until the devs get around to fixing it in the protocol and implement the fix on the server and all the clients change their implementation. By that time data on the posts can be irretrievably borked unless someone sits down and retroactively reassigns which answer is the the ‘selected’ one, which again might need an addition to the protocol because it isn’t a central database, except the dev also can’t actually unilaterally decide which is the ‘selected’ answer because the user might’ve changed the selected answer themselves.
Does this sound like ‘breaking the server for a few hours’?
This smells of fresh college-grad coding with people who can’t foresee how their programming decisions affect the software’s workings in the future.
I have a bit over twenty years with some of them spent at a site that had a million users daily. Seeing as we’re measuring dicks here.
We’re not building a space shuttle, here. Lighten up.
Come on man. It should be a mantra for web devs to never ever lose or bungle users’ data. You know, the thing that gives the web its entire worth, one person sharing with others their personal experience in overcoming the daily grind and tedium: them asking “how do you deal with this shit?” and others replying “well if you contort just so to keep your back from giving out, and press these buttons, you can in fact live to the end of the day”. This should persist on the web for years to come and for everyone to discover. But somehow you think that if you save five minutes on ruminating through your decisions, that’s worth a whole lot and everyone should cheer on you for implementing that change despite the fact that I could overwrite that reply with “you greedy schmuck need to shut up and do your miserable job because you suck”, and this is entirely okay with you.
That’s not what is going on, no. You called my work “fresh college-grad coding” and I described my experience to assure you that it is not. I made no intimations about the length of your dick, qualifications or credibility.
Yes. Entirely different software. Different programming language and tech stack. Also different system requirements and feature set.
Not sure about the developer spirit. PieFed development has traditionally been moving crazy fast and it gets like several new features every month. I think that’s a matter of focus. It comes with consequences, though. But I think overall the project is doing a good job with trying to be compatible to other software. Prioritizing important stuff and doing the right thing. Sometimes some things get done, rather than be 100% perfect. But past experience tells me things often get fixed or changed around once necessary. Not sure if that’s a wise decision here. The JSON exchanged between the servers is probably extra work if changed around later.
I’d legit rather the software develop and occasionally spaff it up and break the server for a few hours every once in a while rather than the non-moving 5 year plans of Lemmy development.
Also, usually piefed.social is the only instance that gets hit with this as, being the flagship server - it takes the brunt of more ‘experimental’ features. Most other servers don’t upgrade to the latest iteration until they’re sure it’s not going to break them.
That’s not what botching the protocol does. It opens the way to mess up the posts that shouldn’t be messed up, until the devs get around to fixing it in the protocol and implement the fix on the server and all the clients change their implementation. By that time data on the posts can be irretrievably borked unless someone sits down and retroactively reassigns which answer is the the ‘selected’ one, which again might need an addition to the protocol because it isn’t a central database, except the dev also can’t actually unilaterally decide which is the ‘selected’ answer because the user might’ve changed the selected answer themselves.
Does this sound like ‘breaking the server for a few hours’?
This smells of fresh college-grad coding with people who can’t foresee how their programming decisions affect the software’s workings in the future.
Haha
I have 25 years of experience at this and am well aware of the tradeoffs I’m making.
We’re not building a space shuttle, here. Lighten up.
I have a bit over twenty years with some of them spent at a site that had a million users daily. Seeing as we’re measuring dicks here.
Come on man. It should be a mantra for web devs to never ever lose or bungle users’ data. You know, the thing that gives the web its entire worth, one person sharing with others their personal experience in overcoming the daily grind and tedium: them asking “how do you deal with this shit?” and others replying “well if you contort just so to keep your back from giving out, and press these buttons, you can in fact live to the end of the day”. This should persist on the web for years to come and for everyone to discover. But somehow you think that if you save five minutes on ruminating through your decisions, that’s worth a whole lot and everyone should cheer on you for implementing that change despite the fact that I could overwrite that reply with “you greedy schmuck need to shut up and do your miserable job because you suck”, and this is entirely okay with you.
That’s not what is going on, no. You called my work “fresh college-grad coding” and I described my experience to assure you that it is not. I made no intimations about the length of your dick, qualifications or credibility.
Good day, sir.
Oh, so your response to the quality of your work is to cite your age. Wow, what an amazing retort.