Teeworlds - bridge

Hello people of #teeworlds, I'm here to bless you with technology from the future, libcurl. However it'd be best if we could get the engine jobs revamp along with it. Thus it is time I inquire once more about allowing a little more C++11 in our codebase

11:32

shared_ptr's are perfect for this and they can't be zero overhead without language support, ofc we can refcount on our own, but not reinventing the wheel and all

i agree that the engine jobs should get reworked, but what about just using the non-blocking libcurl api?

C++11 WOHOOOOOOO

12:17

!!!!

12:17

send code

https://github.com/fokkonaut/F-Client/commit/d14f4f07711678903cb172b79bb729db5523937d

Learath2: you want to add a libcurl dependency in Teeworlds?

refcounting doesn't sound like a huge deal to implement

minus: in the face of threads?

12:55

we need c++11 support for proper atomics though to implement them

12:56

@redix truly nonblocking libcurl isn't reliably available due to dns lookups

minus: Sure but why bother when it's already a language feature? I'm sure the people who implement the standard for compilers have a better testing suite and code review standards then us

open a c++11 proposal issue, stop starting an obsolete conversation again like last time

You really are a buzzkill

the arguments are the same, each time

13:04

and nothing seems to move forward

Maybe we should port teeworlds to x86 assembly, you know these newfangled languages are too much

even dune seemed to agree at some point that c++11 is fine. who else needs to be convinced?

13:05

oy?

oy

open an issue

@jxsl13 I don't think moving Teeworlds to C++11 is a good idea

13:06

I recognize it is a controversial topic with many valid arguments on both sides, but I don't remember saying that it is "fine"

13:07

I personally think it will do more harm than good

._. I'm not gonna look through the logs for that.

13:08

Dune needs to be convinced again, attacc!

13:08

(or open an issue)

iirc sharedptr is like 10 lines to implement. heinrich5991 seems to say there is some overhead without c++11 features though :)

correctly implementing shared_ptr is hard

13:16

it's a synchronization feature

13:16

Dune: was it just auto you were worried about?

13:17

what if I find a way to lint against auto so that people adding auto to the codebase get a failed build?

lambdas etc. c++11 seems to push people to introduce unnecessary levels of abstraction. I agree that it would be fine if we had strict code guidelines, and it is only in the absence thereof that I personally prefer c++03

13:19

it would be silly to have a bot just for my personal likings though ;)

lambdas make code faster, but we can lint against them, too

well-used lambdas are good yeah. kinda like gotos, yet we don't allow gotos

comparing lambdas to gotos is… every modern language has lambdas, but I don't think I know any that has gotos

13:21

this is a false comparison IMO

Which I think is equally unwise, but that's another discussion

I'm not hardcore against it though, if everyone else is for it, I'll just go with it :) I was only answering because jxsl13 seemed to implied I was for it

13:21

Learath2: I liked your goto, yeah

13:22

I like that Teeworlds uses abstractions very sparingly and I think it has deserved it a lot

13:22

served* (?)

served in what way? It's not terribly easy to read the teeworlds code, nor is teeworlds very performant

code simplicity and readability. You feel like the code is complex/hard to read?

13:33

(of course, I'm biased because I'm familiar with it)

I don't but I've been looking at it for 10 years, it's trivial to navigate around for me, a lot of people start out, implement a chat command or two, see the rest of the code with 0 documentation and bail

The lack of documentation is an issue but unrelated to the code, right?

The lack of documentation wouldn't be much of an issue if the code was really readable though

xD I feel the code complexity