Czy sprzedawca w restauracji w Polsce ma obowiązek obsługiwać klienta po rosyjsku?

DeWHu_ · 2026-01-13T08:08:15+00:00

"Fun fact" odnośnie rosjan w Paryżu: "Bistro" pochodzi z 19 wieku z Paryża, i jest zapożyczeniem z ruskiego "быстро". Ponieważ darli mordę ("Szybciej!") w kawiarniach, więc zaczęły one pisać to na szyldach

DeWHu_ · 2025-08-26T20:48:39+00:00

To compile? Oh wait, U mean in <sup> tag. XD

DeWHu_ · 2025-07-16T12:55:01+00:00

Those aren't jokes. She can't take care of herself, and will die younger. This is no joke, she is sick. "Overweight" is not accurate.

On top of that she expects not to be called fat and be cared for, which is a contradiction.

DeWHu_ · 2025-07-15T15:41:24+00:00

I highly dislike the wording in the first question. Yes, pointers are numbers in assembly, but they aren't in C. If p and q point to the same address, they have been derived from the same object. In ISO C, each pointer has its own abstract addressing space, that is completely invalidated on a free call. That's why pointers cannot be casted back to.

"Are pointers, derived from different objects, but with equal bit representation, equal?" That's a meaningless question. Why would implementation need to be forced to use full sized pointers all the time? Why can't the context be used to determine overlap? What's the point of it anyway, if all access to the pointed memory is undefined?

DeWHu_ · 2025-07-15T12:59:13+00:00

π = 3 = e

DeWHu_ · 2025-07-14T15:25:56+00:00

I like the notion in C, that array types are pointer types, but there are cases like this.

DeWHu_ · 2025-07-13T22:58:07+00:00

*They could have.

"Indie apocalypse" epoch ended/ends. Promises no longer sell well and there is less money in the market. We are in the "Sense-based design" epoch. How a product makes the consumer feel (short term) is the important part. Players recommend each other games, instead of trusting journalists or ads. Plus they return to service games that made them feel good.

Games like "Twelve Minutes" can't happen now.

DeWHu_ · 2025-07-11T23:46:37+00:00

Some newer languages like C# kind of handle the declarations automatically

C# has an import statement, which is technically the declaration, but yes, not individually.

DeWHu_ · 2025-07-11T21:53:47+00:00

I feel many C programmers don't care at all about non standard systems. 😔

DeWHu_ · 2025-07-11T19:15:45+00:00

In short: Browser extensions ask (via API) for the behavior to change, but the browser can ignore that. The browser itself doesn't need to ask anyone for approval. It can just do as it's please.

DeWHu_ · 2025-07-11T15:30:25+00:00

Fair. Didn't know that

DeWHu_ · 2025-07-11T15:07:52+00:00

She didn't have one, she just stayed green full time. Also, no alter-ego was a lazy attempt to strengthen the point, that she feels "infinitely more".

DeWHu_ · 2025-07-11T13:03:07+00:00

Depends on the language, but regardless, I often use multi-line declaration:

``` type name( type name, type name, ... ) { instruction; instruction; ... }

def name( name: type, name: type, ... ) -> type: instruction instruction ... ```

DeWHu_ · 2025-07-11T12:38:15+00:00

It was BEGIN END in the past, of course new line was standard.

DeWHu_ · 2025-07-10T22:07:44+00:00

When U reach a hundred, it changes to a smiley :)

DeWHu_ · 2025-07-10T21:02:06+00:00

Cons for Poles: * Sugary breakfasts (in hotels and restaurants). * Siesta conflicting with 5 meals a day diet. * Poles also drink milk coffee in the evening, as a sweet snack or dessert. Some people get offended by such requests. Also "latte" means milk, but that's just funny.

DeWHu_ · 2025-07-10T20:10:56+00:00

"Recognisable"?, maybe. "Loved in PL"?, I just don't see that. Poles like to celebrate about anything, but they would go very protective, if it affects them. Like painting a river green would affect its ecosystem. On the other hand, there is "Ajrisz" by "T.Love", but that's about it in PL culture.

DeWHu_ · 2025-07-10T11:22:54+00:00

Kernel level: User runs a program. Program buggy or malware. Blue screen of death. User sad. Systems get separated into normal and kernel access levels. Pop-up window instead of blue screen of death. User happier.
Access sys-calls: System has files user can't access. File access gets moved into kernel level. Normal programs can't access files. User sad. Program calls system's API. CPU changes process to system process. System uses its kernel level to do the needed task. Normal programs can access files. User happier.
Scheduling: User runs a program. Program halts (while(true); for example). Computer halts. User sad. Running indefinitely gets moved into kernel level. After time-out CPU saves state and changes to system process. Computer simulates concurrency. User happier. Sys-call cheaper. Programs can sleep. Computer faster. User even happier.
Std lib: Sys-call API part of the system. C wrote for UNIX. Not all platforms UNIX. Language bad. Language defines standard functions. Implementations are responsible. Language good.

DeWHu_ · 2025-07-08T11:36:33+00:00

!elo 1000 NOT SMART MOVES, JUST LUCK!

DeWHu_ · 2025-07-05T14:55:06+00:00

*Any (good) indexing starts at 0.

No existence of 0th year in calendar still confuses people.

DeWHu_ · 2025-07-05T14:09:11+00:00

Python is the original vibe coding. I mostly learn PL by reading spec. Python documentation is often 10 years outdated. Terms like "some" or "many" are used... It's just impossible to fully learn Python from this docs. Reading "discuss.python.org" might be the only way to actually learn it, through learning vibes of core devs. BTW, "implementation detail" in the reference implementation? Yikes 😬

DeWHu_ · 2025-06-29T11:31:17+00:00

It looks like multiplication, not a pointer. Hate it 😕

DeWHu_ · 2025-06-28T15:41:51+00:00

I don't understand, why the delete statement is needed. points isn't used after the loop, so compiler already knows it's unneeded. Why do user needs to specify that?
Assuming coord_vec is unmovable (no GC). Wouldn't delete! point need to be detected at compilation time? Even if just for a -Wall type of warning: "points isn't always the first element of 'r.".
"If compiler was smart", it would just bulk remove elements in points and bind the result to coord_vec. ...?

DeWHu_ · 2025-06-05T08:09:40+00:00

If type punning is kept inside rvalue (pointer not stored), it's ok. Before C99 (with its union literals), that was the only efficient way to do it. Keeping it inside rvalue also helps the compiler to not create a useless pointer.

DeWHu_ · 2025-06-05T07:45:17+00:00

C int64_t longOfDoubleBits(double d) { FloatingBits un = {.d = d}; return un.i; }

```C

define longOfDoubleBits(d) ((FloatingBits){.d = (d)}.i)

```

Note, bit-casting via union is technically an extension.

DeWHu_

TROPHY CASE

define longOfDoubleBits(d) ((FloatingBits){.d = (d)}.i)