belgesel

If you try to translate "gelato" to English literally, you can say it means "frozen". While "dondurma" also can be translated as "frozen" to the English. I don't know why Americans called it "ice-cream".

When I see the term "ice-cream", I think of cold white creamy thing on a cone that you can buy from fast food chains. That is different from what we call "dondurma" here in Turkey. That is much softer and more creamy than "dondurma".

Turkish people probably saw the dessert from Europeans. At least that's what Nisanyan says.

https://www.nisanyansozluk.com/kelime/dondurma

IIRC the main reason to use FreeBSD instead of Linux was BSD being a lot simpler and have a lot more room to optimize their specific use case.

Can you elaborate on that, couldn't find the proposal, I want to learn more about it.

I was expecting some form of benchmark to see if claims about better performance is true.

even echo has it $ echo -e "hel\x70"

Just out of curiosity, how much time you have before taking the shot? (seconds or minutes)

I believe it is their new rule. But it shows up only if you are using twitter for a while as logged out. Clear data from browser and it goes away, but will eventually show up again.

Isn't that the other way around? I thought clang was trying to support all gcc extensions to be able to build Linux kernel.

I would rather see both of these compilers to stay competitive to push themselves higher.

For those who don't know, this is a follow-up story of A Teenager's Guide to Avoiding Actual Work which got the attention on HN lately.

https://news.ycombinator.com/item?id=27206552

I do use 1000^n, but I agree that most people tend to use 1024^n. 1000^n kind of makes more sense since "kilo, mega" etc. are the actual SI prefixes for multiples of 1000s. I don't know who or what caused this chaos but 1000^n is definitely more human friendly.

You are right. In 5G, data packets goes through less tunneling than it was before. Although there is less tunneling, 1ms latency for "end to end" or from user device to the Internet doesn't sound realistic. I have no real life measurements but if I would have to guess, it should be around 5~10 ms.

I didn't want to whine about the changes. But why did they move "Restore Previous Session" button into History in the menu. That was by far the most used button in the menu for me. Now I have to click 2 buttons.

Suppose I have the following struct and functions.

  struct my_struct{int a; char private[10];}
  void * get_struct_field_nonconst(struct my_struct *ptr)
  { return &(ptr->private[0]); }

With these elements you are only allowed to give non-const pointers to read or write inside private field. In order to truly apply this to const pointers (no casting etc.) you will need another get_struct_field() function but defined as this.

  const void * get_struct_field_const(const struct my_struct *ptr)
  { return &(ptr->private[0]); }

This will work but it is ugly. Here _Generic keyword allows you to write these functions but use them with a common name. Such as get_struct_field(). And that would be something like this:

  #define get_struct_field(ptr) \
  _Generic((ptr), \
  const struct my_struct * : get_struct_field_const, \
   struct my_struct * : get_struct_field_nonconst) \
  (ptr)

Hope this would help!

Presenter doesn't give any information about it. But I think it is not a type defined in C standard and presenter's own implementation.

Although I disagree with some part of the presenter's ideas. I learned struct initializers and _Generic keyword from the presentation. So that is a great win for me. Now I can write safer code with the const and non-const pointer types.

Suppose that I want to return a pointer to a field inside of a struct. Either I had to write const and non-const versions of the same function and use them which brings unreadable code. Or I would have to define argument as const and return non-const pointer which defeats the purpose of const in the first place.

This keyword allows me to use same function name with const and non-const pointers.

The guy has an article discussing 5G Telco business.

5G: The outsourced elephant in the room - https://berthub.eu/articles/posts/5g-elephant-in-the-room/

And also HN Discussion - https://news.ycombinator.com/item?id=26843068

I think people need another 100 years to forget about it. It's just a toy in the hands of politicians. And now they choose to use it against Turkey. Some day this whole thing will be forgotten.

Nobody living today are responsible or should be responsible for it.

I want to know what will this recognition does to your own country both in short and long term. Will Turkey pay a fee for the genocide or will they have to just give up from Ağrı?

This subject was always used against Turkey in political confrontations for years. Turkey has been better and stronger ally to USA. This recognition is nothing but a political warning against Erdoğan and his latest actions against USA and also this will make Armenian residents in USA happy.

IMHO nothing will change for us (Turkish and Armenian folks living in Turkey), don’t know about Armenians living in Armenia.

So why are you happy?

I believe before Discord got the high ground there was a program called Curse. I wonder if it is still functional.

Well, most of them includes heavy macros that is designed to be optimized by the compiler. So calling a macro from another language with different syntax does not sound easy.

Rust is catching many developer communities' (kernels, game engines, browsers etc.) attention lately. I have never used it but considering to use it in the future.

But I am wondering how will they make it work with underlying Linux mechanisms. One of the first challenge that comes to my mind is RCU or any other memory reclamation functions. Will they not use these memory mechanisms at all or call them from Rust source code?

A question to parallel programming experts. Can we assume that a task that is well seperated to perform on single core is always better than multi-core?

I meant using multiple instances working on single core vs. single instance with multi threads.

this is nice. Just like bash, emacs has so many features hidden under it's hood.

Anybody with intention to work on older systems can work with older releases of Autotools, while newer releases can focus on much more needed features.

I believe it is still true. OpenSSL uses dirty stack bytes for randomness and it causes valgrind to warn for invalid access.

I think authors also taught about that and wrote the paper for newbies. Almost every new researcher is reading from top to bottom.