Jul 20 2014, 4:29 am
|
|
ZomgPonies
 |
W-W-W-Weekly bump.
|
I'll be watching this since it looks like the issue will be affecting Baystation 12 soon.
| |
Too many procs, too little uses, congrats to SS13 for efficient programming, I guess?
(Inb4 bashing, I have an SS13 server, so I know how much shit is in the code.) | |
Agreed
| |
Just to let you know, I haven't forgotten about this but the webclient stuff has taken top priority recently, especially as I'll be out next week. This is still on my docket.
| |
Eh, I'd say leave it as it is for now and let the developers take care of reducing the amount of procs they have in their code.
Really, it's not BYOND that is to blame.. | |
Laser - If devs promised they removed the proc limit, yet it's still there, then yes it's something for them to check.
Lummox - Thanks for the update, it's appreciated. | |
ZomgPonies wrote:
Laser - If devs promised they removed the proc limit, yet it's still there, then yes it's something for them to check. Sure, it is, but on the other end, it may just be better for us SS13 devs to start reducing the large list of unused or unneeded procs that are still around in the code. A cleanup would if anything do the entire game a better service than a bad one. | |
Good luck cleaning it up. I think it'd be faster to remake SS13 than to clean up what it currently is.
| |
That's how I'm currently keeping development going, trimming out the fat. But this is just removing dead debug procs, or stuff Paradise doesn't/will never use. It's a bandaid at best.
| |
Zecronious wrote:
Good luck cleaning it up. I think it'd be faster to remake SS13 than to clean up what it currently is. There's the spirit.. And look at what happened to the remakes, they failed. One by one. You could probably have fixed a bunch of those procs by the time you wrote that, though. Just saying. | |
If you knew where they were. There are thousands of procedures, and it's difficult to look through them all and see which ones are unneeded and which ones aren't.
| |
Decius Reln wrote:
If you knew where they were. There are thousands of procedures, and it's difficult to look through them all and see which ones are unneeded and which ones aren't. I know of a few out of the top of my head, which is quite a surprise given the time.. Yes, it would take time. Yes, it is a boring task. And yes, nobody wants to do it. But at some point, this'll only come back to break other things, or cause worse/weird issues eventually. There's a load of programmers out there that work on SS13 at the moment, I'm sure some could do something. | |
There is no argument that it would be good to do things. I'd do things myself. I'd recommend creating a piratepad and posting it on your server's forums requesting people to come and add in entries for what needs to have things removed-- Just the file names and maybe a short description. Something to start from. Collaboratively working like that, we could likely get more done and such.
Most of the codebase between Paradise, Bay, and /tg/ is the same anyway. Edit: And I confess that it was more of.. I, admittedly, was annoyed by what seemed like a sarcastic and negative manner from you. I recognize that a lot of it is honesty. The code is brutally bad in a lot of places, but acknowledging it and being negative about it are different things. My best request is that we try to focus on productive things, rather than negative things. I don't even mean asking you to give examples (through the piratepad) as a challenge to discredit you. I mean it seriously, so that I can look at it myself and see where and what I can do to help trim off fat and help. | |
Incidentally, are any of those branches open source still, or did the copyleft licensing we put on SS13 go the way of the dinosaur?
| |
TGStation is on Git, as are all the branches of that (paradise, bs12, etc).
Goonstation is still closed-source, afaik. | |
I suppose if they don't distribute, they don't violate the LGPL license. Similarly I guess Exadv1 is free to re-license accordingly for them.
Got links to said git repositories? | |
https://github.com/tgstation/-tg-station
https://github.com/Baystation12/Baystation12 https://github.com/d3athrow/vgstation13 https://github.com/ZomgPonies/Paradise These are the four big public ones. vg and tg are action oriented, Baystation is RP oriented, Paradise -tries- to stay in the middle. | |
I don't, offhand, have a copy of r4407 itself. I think the initial commit of /tg/station is either exactly it or close enough.
Fork of r4407: https://github.com/tgstation/-tg-station Forks of /tg/station: https://github.com/NTStation/NTstation13 https://github.com/Baystation12/Baystation12 - Old enough that lots of stuff is different. Forks of Baystation: https://github.com/ZomgPonies/Paradise https://github.com/d3athrow/vgstation13 Bay and all the Bay forks have hit the icon_states per dmi limit, and /tg/station is rapidly approaching it. Bay hit the 32 bit instruction limit first before it was raised. It makes sense to me that Bay or a fork would hit another limit first. | |
rev4407: http://puu.sh/74cEu
Doesn't compile with BYOND >= 500. | |
