I think you could have left it at differing experiences and not gone further saying I'm handwaving anything. That doesn't seem productive.
I'm not saying that Rust compilation time is comparable to Go/TS, I'm saying the blanket claim that Rust iteration speed will be a bottleneck requires context.
I definitely agree with you that it is a complaint that is often repeated online, but that doesn't make it universally true. In my experience it's a claim that is often echoed without proper context.
Particularly in the case of AI Rust recompliation times in my experience have not been the dominant cost, but are instead overshadowed by inference time, the agent working through different approaches, etc.
In my experience developing different types of applications in Rust, the claims of a "slow compiler" are overstated. Sub second iteration times are definitely a thing in Rust as well, unless you're adding a new dependency for the first time or building fresh.
My working space thermometer was also measuring 26C last week and I was very uncomfortable. Tolerance for warm and cold temperatures is different for everyone.
The One Dark (Atom's default dark theme) and Solarized come to mind as widely used themes although I'm not sure they have as much of a branding as the two you named.
Austria was never part of Germany. It was part of the Holy Roman Empire and after that the German Confederation, with the latter being dissolved in 1866. The first actual united German state was founded in 1871 as the German Empire, without Austria (Kleindeutsche Lösung).
Hangul is the script you are thinking of, which was invented and introduced in the 15th century by King Sejong.
However, there are many Chinese loan words in Korean language, especially on an academic level. You can even find Chinese characters in Korea today, usually in newspapers, on street or restaurant signs. For example, the Korean word for "president" is 대통령 (Taet'ongnyeong), but in newspapers it may be written as 大統領, which are the matching Chinese characters.
Also, most Korean parents choose Chinese characters to write for their children's names, which read (more or less, as Korean does not have tones) the same as the Korean characters.
As opposed to the two you mentioned, WhatsApp has e2e by default. Kakaotalk and Telegram force you to use "secret chats" for that which are device to device only and cannot be shared among different devices with the same account.
> There's a difference, in almost every piece of software, between closing the last window and quitting. In a browser, just pressing the "close" button would lose all your tabs, whereas "quit" will preserve them. That makes no sense to someone coming from Linux or Windows;
MacOS distinguishes between closing an application's window and closing the whole application. Therefore, closing the last window will not automatically close the application as well. Consequently, in a browser pressing the close button results in all tabs getting closed, with the browser still running.
Quit however closes the whole browser and, hence, preserves the tabs. This is the action triggered by pressing the close button on Windows and Linux.
I can understand that this is counterintuitive coming from Linux or Windows. But it is a design-choice coherently implemented throughout MacOS.
Definitely fast and elegant. I like it very much! I thought at first, that it didn't show comment threads with indents, I almost missed the "X replies" label. I like it the way it is, however.
Just two things:
1. In the "Lists"-tab, it says "synched". I'm not a native speaker, but I guess that should be "synced"?
2. Maybe I just missed it, but: Is there any way to submit a comment from within the app?
> Worlds largest ICT companies by revenue, category and year founded:
> [...]
> 2. [2] Samsung (1969)
I know, I'm nitpicking here, but I guess you are thinking of Samsung Electronics here, which is just a part of the Samsung Group. Samsung was founded in 1938.
Sounds to me, like you are finding excuses to defend a bad design decision. If my mouse dies on me, then I expect to be able to plug it in and then continue to use it, with a minimal interruption of my workflow. Which, how you presented it, is not possible. I shouldn't be forced to bend my workflow around my devices, but my devices should bend to my workflow.
Yes, this is not always possible, but in this case it is just an unnecessary inconvenience. And if I decide, that I want to have the "crappy experience" of using my mouse while it's on a charging cable, then I should be able to make that decision.
This is not "refining experience", it is just bad design.
I'm not saying that Rust compilation time is comparable to Go/TS, I'm saying the blanket claim that Rust iteration speed will be a bottleneck requires context.
I definitely agree with you that it is a complaint that is often repeated online, but that doesn't make it universally true. In my experience it's a claim that is often echoed without proper context.
Particularly in the case of AI Rust recompliation times in my experience have not been the dominant cost, but are instead overshadowed by inference time, the agent working through different approaches, etc.