dit was boffen

memory safety... do it. skip the next conference and add memory safety

1:49:52 The graph supposedly shows that the "normal" O(n) algorithm stays close to "fast" which is O(log n). This is not how log n looks in log-log scale.I think there is a mistake there.

A czy slajdy z linkami będą dostępne?

00:00 - introduction 03:32 - outline of the talk 03:55 - modern hardware; memory access and cache 11:20 - how reading from cache works 13:50 - cache implications 14:40 - Data Oriented Design 17:02 - AoS vs SoA 26:09 - data oriented transforms 27:08 - code coupling 27:54 - data coupling; threads 33:50 - entity control system 45:00 - summary 46:01 - Q&A

How to handle the case that an Actor process is killed (as is common in k8s)? Are the entries in the actor's message queue then lost, or are they persisted and resent to another actor? Could we achieve idempotent behavior when sending the same message (with an unique message id) to the same actor twice or to different actors in parallel? What about time-out constrains for messages?

I dropped out of CS at uni and I don't know how to make my own programming language :(

5 principles: 1) 1 idea per slide 2) SIZE matters 3) Six lines (body) 4) Value = solution/data that audience finds valuable 5) Contrast

3.10

"Clearly you can't do this". Ah. yes. I erm um, no I can't see it

A very good presentation here.

Hi, I sent an email 7 days ago to you guys titled "Large group of students". Just trying to get in contact.

Very small correction that WGS84 is not a "geoid" but is an "oblate ellipsoid". The geoid is an equipotential surface of the earth's gravity potential that best fits the oceans at rest.

There are a lot of Unity projects that don't use Unity DOTS, but use 3rd party ECS solutions. Russian ECS community is pretty big, 2:47 shows it, people build production games around Unity + ECS quite often.

Me { ListenToSpeech() => hopeInTheWorld++; ListenToQuestionsAfterSpeech() => hopeInTheWorld--; }

Interesting topic, but the presentation is very hard to watch.

Dr. Przemysław Szecówka; is my lecturer from uni. he is the best teacher I've ever seen in my entire studentship career :).

Never say If the language gets made just make it . Time waits for no one believe in your light spirit that brought you the idea . That just normally means it should be a scraped or finished product for the future . Its up to the one who has visionary dream its just a future rift follow the stream . One love ! ✌

Very enjoyable talk!

Very entertaining and educational. Pity so few have watched.

"... thanks, by the way it's David C-R-ockford"

Announces a new programming language. Proceeds to describe message passing and databus / data mesh architecture. Useless talk.

What kind of arrogant douchebag thinks they're so much better than everyone around them that they won't answer a question like the guy asked when introducing him??

Thank you

I'm having a hard time seeing this as a language instead of a design pattern.

Nothing new, check out Scala/Akka-Actors ... and its not paperwork and works already ... does this mean the future is already here ;-)

Sounds a lot like Erlang?

Could you talk about that neo language and also perhaps do some crash course on neo so we could probably see the difference

JS is a corrupted Scheme.

I love this guy, read many chpters of his book

Thoughts on the bevy engine built with rust? That game engine inspired my search for more videos on this topic and I was surprised to see no mention of it.

Type hints and type checkers exist 🤦‍♂️

Yeah you should defenetly use strict typing or basically add the types to variable names instead of making the code less efficient

Whenever you try to make things invulnerable to all complications, you are trying to make the world foolproof ... but the world will just create a more powerful fool.

Design Patterns is/are primarily about providing features not available in your programming language. In the 1950s, subroutines were a design pattern. Nowadays, it's a machine language opcode. 2) - Getters and Setters are actually a mortal sin. You might GET your bank balance, but you never ET it ... you deposit or withdraw from your bank acount.

Great talk, very comprehensive and complete explanation of this, not so easy, topic

I still haven't seen one code sample where coroutines are better than callbacks. By better I mean more readable, easier to maintain, etc...

I don't get it, they boo people who come up with an actual algorithm for reversing a string and instead they glorify using the premade std::reverse function without even mentioning about its complexity ?

Wonderful lecture - thanks! I've been around since assembly language around the 1970's. . But isn't a try / catch structure at he end of the day not just a GOTO? You just adjust he stack pointer ?

Very interesting programing course. Excuse me please realizes different syntaxs

Hi, it the video from Michał Redford kowalczyk online? Thanks

10:46 _Static_assert is also a keyword since C11

To work around the problem with 'optional<void>' (which is isomoprhic to 'bool' btw), you could use regular void, i.e. std::monostate if you don't want to implement your 'Void/void_t' class

Great talk, I always love your talks that go very far afield to make points about software development. Only note - when given the choice of writing a function that takes a path to a file or a file object, choose the third option - just return the data instead. I am happy to call open and write myself, if it means I don't have to call io.TextIO to get the output as a string :D

suggestions for the following snippet that mixs type(signed/unsigned) in expression ``` signed char *ptr; if (ptr[0] == 0xff) // bad, compare char to integer ``` use the following ways, ``` char *ptr; if (ptr[0] == '\xff') // '\xff' is a char int_least8_t *ptr; if (ptr[0] == -1) // -1 is signed integer uint_least8_t *ptr if (ptr[0] == 0xff) ``` in cpp17, ``` byte *ptr; if (ptr[0] = byte{0xff}) ```

Brawo Kamil! ;)

Unsigned by default is dumb. At least in C++. It sounds great on paper, but in practice, its horrible Signed by default sounds bad on paper, but is best in practice.

when talking a new lang I'd expect memory management, null values, variable initialization, etc. He discovered microservices

So, the next programming language is "Misty"? I I doubt it.

Hearing Conor give a full talk about Python is almost like hearing him speak Polish