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.
Our experiences clearly differ then. And for others as well since it's a common complain.
Countless time I have seen other people complain as well. There are articles about it even. Can't find the YouTube link now but recently a gamedev abandoned Rust due to compilation speed alone because iteration speed was paramount to their creative process.
Handwaving isn't going to make it any better. And thinking Go/TS compilation speed are comparable to Rust is, a handwave and a half to say the least.
Cargo check and friends are subpar for AI because they actually need to run the thing and unit tests for efficient agentic loops.
A single loop might recompile and rerun the application/unit tests enough times that slow compilers like Rust and Scala become detrimental.
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.
It’s a joke on the original anecdote’s timeless formula of double-filtered appeal to patriarchal authority (the father relaying the wisdom of the boss to the son).
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.
It’s still super popular, more so than Cyberpunk and did all the stuff Cyberpunk shipped with, better, a long time before it. It does help that Rockstar have been basically working on making that kind of game for decades whereas CDPR haven’t.
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).
I tried to do that in the article. But the thing is that when you're writing a little piece of code React makes it dead easy to make hover in your code. There a lot of little things like that.
You start out with good intentions, but after 4 years of different people certain parts of codebase start looking really weird even with code review. You just can't catch every little detail.
And this is why tools should make it easier to do good thing (good as in what you'd want to see in the end).
> after 4 years of different people certain parts of codebase start looking really weird
That's pretty much how software development works though. It's what happens when people with varying skill levels, schools of thought, preferences and approaches to problem solving all work in the same code base. Heck, it'll probably happen even if it's your own pet project: four years is a long time in something as fast-moving as web development, especially when you factor in things like market-driven priorities (E.G. adding new features vs. fixing old "good enough" crap kicking about).
I honestly doubt there's a single software project in history that doesn't have shady corners after a couple of years, no matter how excellent their frameworks, conventions and developers are and how draconian their review process is.
That is true, but the effect various "quirks" have on result are very very different.
I did not decide to switch from React with a light heart, it was a long and painful decision. But it seems to me that React's path of least resistance leads to a slow bundle, and you're going to fight an uphill battle.
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.
I navigate from time to time to Korean website, very few occasion they actually uses Chinese characters, except:
1. Some countries names. 中(China)/美(US)/日(Japan)/北(North Korea)
2. Blue House (think of it as Korean's White House, representing the headquarters of the administration), sometimes referred as 青(Blue).
3. The president's surname, sometimes referred as 文(Moon)
Except for those very limited cases, I don't think Korean people are actually using Hanja anymore, it almost feel like some sort of emoji for then, that they probably can't read it, just comprehend the meaning.
As to Korean names, yes I think they still have a Chinese name registered somewhere, but no longer required and not shown on their government ID card.
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.
