Has anyone seen DukeZhou?

Not lately

me niether

@TheMattbat999 according to his profile: Last seen Jan 18 at 21:10

Here I come with some rant again. I currently dont enjoy my job whatsoever and I'm currently consider quitting and do some selfexploration and projects I feel like doing

There is also the option of working for money and having fun and exploration in hobby projects.

or the not full-yolo route and work parttime

It's a worse option, but having fun and exploration during work would be too good to be true.

well problem is these also involve programming and on top of my workhours the amounts i code really adf up heavily

to a point where i neither enjoy work or the projects i usually enjoy doing

What exactly is the issue?

a mix of not enjoy long work projects in combination with me not having enough time/energy on hobby projects

I mean why don't you enjoy it? I'm having a hard time believing you just got tired of programming.

I got pretty annoyed having to do certifiable documentation in 5 times redundant word documents that are impossible to keep synchronized with unknown requirements.

But that is something that is fixable.

Especially when you are ready to quit your job you may have a go at saying "Boss, our current processes suck. We could be much more productive if we did it like this and that". If he fires you for that you didn't really lose anything. And chances are things actually improve.

Problem is that there are many things that we can do to improve the situation, which we are well aware of, but we lack the capacity to do so.

You could try to find the worst issues for you and the company and say that the company can no longer afford not to fix them.

I don't know, hard to tell without knowing anything.

Also you run into the problem that if you complain too loudly you are made responsible for fixing them, which might be outside your expertise.

I might just be a little to overworked and I'm putting to much thoughts into my job when I just could work my 8 hours or so

hey guys, i got told that i always should try to use the stack instead of the heap in c++. now im doing a SDL tutorial, and so many things are used with pointers(heap), like SDL_Window*, SDL_Surface*, etc. im just confused now :)

Hey it's finally snowing!!

hah, since months! (where i live) :)

@Chris there is no difference between allocating on the stack/heap

stack memory is the memory that is accessible via the stack register by the cpu

The speed of its allocation/deallocation is fast because it is strictly a last-in/first-out design. It is simply moving and decrement/increment operations.

ok, but why is the heap used for SDL_Window*, SDL_Surface* ? makes no sense to me

i never know when i should use pointers and when not -_-

Heap memory is a bunch of memory that gets allocated when using malloc, calloc, new [...]. it almost always must be manually freed, though you should reallly use a smart pointer class or similar to avoid needing to remember to do so

i really have to read much more stuff about this topic, then it may gets clear to me. thx

@Chris Pointers are just a way of getting an indirect reference to a variable: instead of holding the value of a variable, they tell you its address in memory

but isn't it resource wasting to use a pointer? because the pointer variable needs some memory too, right? (but probably that less that it has no negative effect at all?)

memory of int i + ptr_i > memory of int i

i guess

Normal variables store the value whereas pointers store the address of the variable, in hexadecimal notation

I remember reading somewhere that the size of a pointer is usually 2 bytes (on 16 bit compilers)

So no, pointers are not resource wasteful ;)

@Chris Use simple stack-allocated objects until you have a reason not to. In practice you can almost always get away with stack-allocated objects or making it someone else's problem by using std::vector.

Unless you use terrible libraries such as Qt where writing good code is essentially impossible.

I never really understood why libs like Qt exist

Qt was created before C++ was standardized and had a standard library. It then evolved in a different direction than C++ which is why it is so incompatible.

I just find it confusing af

ah

There are efforts being made to make Qt more compatible with C++. Maybe some day with Qt6 it can become a library instead of a framework.

Verdigris is a pretty decent start.

Maybe once they give up pre-C++11 compatibility they can move away from raw owning pointers.

I can't even find which C++ versions they officially support.

it literally hasn't been snowing like this for 7/8 years

it's pretty cool :D

:O

Awesome

It just suddenly started snowing last night in London, even

London is not zoned for snow, snow is not meant to happen here

throw new notsupportedexception();

@nwp out of curiosity, how are you differentiating 'framework' from 'library'?

@GabrieleVierti Yeah global warming FTW!!! (not.)

A framework is essentially an intrusive library that changes the language. A library simply offers functionality without changing the language.

back when I was uni, they were used a synonyms. Presently, the first web hit says the difference is inversion of control. Mileage vary on some terms, that's mainly why I'm asking for context here.

Qt makes it so you can no longer use templates, typedefs or put classes into source files for example. C++ does not normally have those restrictions.

Ah, I didn't know that it had those side effects. I'm not sure if I'd pick those terms myself, but that level of behavior does warrant some manner of "here be dragons" notice.

It is somewhat exaggerated. You can still use those features, just not on classes that use Q_OBJECT.

Still, I would consider that to be a design flaw.

Oh, and pointers. You can't simply use std::unique_ptr<Ui::MainWindow> ui; because that would be too easy. Got to keep using Ui::MainWindow *ui; with new and delete like a caveman because otherwise Qt Designer breaks.

Verdigris fixes some of those issues.

I learned (an admittedly ancient) C++ that favored new & delete over the likes of malloc, so the latter point is probably lost on my sensibilities :)

malloc is pretty useless in C++. It only gives you memory and does not create objects.

C++ is pretty useless.

hahah just kidding

no really, C++ is great, it's just hard to work with. :)

The new cool is to just use values. Or std::vector if you need a list. And std::make_unique if you absolutely must. But never ever new or malloc.

It's not useless, it's just a very different model of programming. There was life before objects.

C++ does not support that model. If you access memory without first putting an object there it's undefined behavior.

When it came out std::vector had a rep for leaking memory.

It no longer does that.

Did C++ upgrade int etc into objects?

:)

@Pikalek yes

Actually I don't know about "upgrade". I think they have always been objects. Even in C.

But C does not have the concept of "object lifetime". You just access stuff and if it exist it's fine. C++ says an object springs to life in the constructor and is destroyed in the destructor, and if you access it outside of those you get screwed.

They are 'types', but I don't think they were objects. You could not do stuff like `int x = 13.add(17); for instance'

You could create an object in the space that malloc gives you, but that is just really cumbersome to do and there are more convenient tools to use.

Again, at the compiler level, I'm not so sure that's accurate.

Funny side-effect: You cannot use memory mapped files without undefined behavior in C++.

They are trying to fix that though.

Yes, I agree there are now probably less cumbersome ways to do some of these things. But that's not the same as saying they don't exist.

They totally exist. malloc is part of the C++ standard and is extremely unlikely to get deprecated.

You can even use malloc properly. It is somewhat helpful when implementing std::vector.

The only fully objectified languages I know of are Small Talk & its descendants.

It depends on what you consider an object. In C++ essentially everything that is made out of bytes is an object, which is probably not the smalltalk definition.

@doppelgreener go away snow! :D

@Kay completely appropriate because when it snows more than a little here, london just stops working

ahahahaha

Isn't it always cold in London?

because if it is, it's never gonna stop snowing :D

London's got its own biome separate from the rest of the UK, and it's been unseasonably warm here

so just like my fridge, londom developed an own ecosystem

@nwp I meant classes in the sense that you can do class-like OOP things with it. For example, can inherit from long?

You cannot.

@Kay honestly it's probably because of the pollution levels

if you're outside london you can see a dome of smog hovering over the central parts of the city pretty much

if the trend continues, in a hundred years London will resemble the city in The Fifth Element, including with the lower levels being uninhabitable due to lethal pollution levels

thats what I though. Personally i find no appeal in london

playing keyforge after work with colleague💪

@Kay noice!! have fun

@nwp Ah, ok, things maybe haven't changed super radically then. Admittedly, discussing programming languages at this level can get weird - sometimes object means 'instance of a class', sometimes it's a term that means 'managed collection of 1s & 0s'

after that, streaming some game dev.

gonna be good.

@doppelgreener yeah ive heard some good things about keyforge, though i find the random deck very weird

@Kay I need the name of the channel :)

howdy folks

hello!

getting further on my level editor prototype for my haunted house game concept

I'm doing all the prototyping on Github as a public project, too

github.com/nickiannone/hauntedhousegame

did y'all here github opened up free private repositories recently?

Yeah I heard; I'm specifically doing some of the prototyping here in a public repo because I want to use my code as an example project for now

I'm gonna switch it to a private repo when I rewrite the core logic into Unity

yep that sounds fair :)

We can now all hide our source code from everyone except Microsoft. Long live open source!

I might just have the scenario levels and assets be private, and let the core of the game be open-source, even after switching to Unity

I'll have to play around with asset loading in Unity to try and pull that off

on a totally different note, I'm super salty about some political discourse on Facebook from earlier today, which I won't get into detail about

I'm gonna camp out in here for a while to cool my head

what's everyone else working on?

playtest of the new Killer in DbD

the unannounced next one

also documenting new features for dbd

did you know some people disconnect the moment they know the Killer is the Clown?

@doppelgreener I did

Nice! I didn't know you were on the DbD team

one pitfall of making a horror game is that some of your stuff will actually scare/upset people.

and it's pretty freaking awesome :D

been since august

diggin it

as designer, not prog

great game actually, and I'm not just shilling

@Almo oh dear

next up: spider killer

I really enjoy it

hahah :D

I remember a buddy of mine playing a similar survival horror game, but I can't remember the name of it

It was something where different regions of the map get blocked off at different times, and the survivors have to close portals and stuff while dead players revive and become part of the opposing team

Is that the same game or am I getting stuff mixed up?

that's definitely not dead by daylight

at least not any part of it i've seen

i2.wp.com/www.gaminghistoria.com/wp-content/uploads/2018/08/…

The Entity is vaguely spider-like when it appears

yeah that's not dbd

It was kind of an old-timey zombie survival game

@GabrieleVierti twitch.tv/rhast0r

Just me doing my little weird things :p

@Almo that's true

dead by daylight is fairly new, and you are four survivors summoned to a creepy place where you have to get generators up and running while being pursued by a killer. the whole realm is controlled by The Entity who has put everyone here.

if the survivors get generators running they can escape.

but once a survivor's dead they're gone.

dbd released 2016.

so "fairly new" describes it, depending on how old you are :D

someone who's 16 might think it was ancient. :D

@Kay I'll tune in when you go live :D

@Kay I dropped a follow

Also, would there be an audience for game programming streams?

if so, come check me out at twitch.tv/shotgunninja sometime :P

@Almo wow, i had no idea, i'd only heard about it very recently

:D

@ShotgunNinja well, you definitely get people like me in the audience

That's an old-school computer graphics term

It stands for "bit block transfer", which was shortened in some API to "bitblt" which became "blit" in the vernacular

It just means to draw a region of pixels to a surface

cool thank you @ShotgunNinja

^

As far as I can tell, the term "blitting" for bit-block transferring was popularized in the computer graphics industry, though.

@GabrieleVierti @ShotgunNinja WOOP WOOP cracked the the 3/4 * 100 mark

?

followers that is

streaming while having mic muted, I well played myself

oh no, the worst discovery

But congrats!!!

@doppelgreener hehe. Keyforge is really nice btw

@Kay :D

I never played keyforge.. is it a yugi-oh type of game?

nope, way off ahahah

I'm reading how it works in the "mamma mia pasta pizza" language

for me its artifact + dominion + i dont know

:D