friendzis

In a country that has legalized (not even decriminalized!) marihuana, a still present full-ban on moonshine paints an interesting picture on legislative process

> Like what does it gain the person doing it

Time / quantity.

Pre-LLMs you needed a whole "marketing" agency to astroturf on a meaningful scale. Post-LLMs a single person can run multiple astroturfing campaigns in parallel.

> they're going for sweet liquors and premix cans of fizz.

Not surprising, sweetness literally mutes palate sensitivity. Genzers are the most sugar addicted generation, from a very young age. It would not surprise me to see research in some future that this massive early life sugar exposure comes with muted development of taste.

This post is a testament that mobile AI experience on Android is much better and yet iphones are not really losing market share to that.

> Apple's incompetence in AI / Assistant etc stuff has to be studied.

Why should Apple focus on technical excellence when the company and their products are touted for literally gimmicks? In the end this is what brings the money and profits through the door, can't blame a company for providing what the market craves.

I LOVE the irony that is the top response, Michelin level gourmet

> Because if there are no material consequences for wrongdoings, they probably would not care. And there are very few kinds of actually material consequences for big companies. One of them being a really hefty fine.

In mono/oligo-poly situations there's no really such a thing as "a really hefty fine". Either the cost will be happily trickled to the very public that are being wronged or the fine is effectively unsurvivably hefty, which noone would levy against a too-big-to-fail entity.

Look at the recent fine for Meta for example. Settling a case against one of the core monopolic drivers for a couple percentage points of early revenue is peanuts. I can't believe the exec suite[-s] are thinking anything else than "which anti-consumer behavior can we buy indulgence for?", they would be stupid not to at these discounted rates.

I'm half joking here, but at this point it feels like the only reasonable way to instill some fear against building Torment Nexus and cyberpunk dystopia would be personal criminal liability of the boards and exec suites that is impossible to settle.

Your argument relies on two assumptions:

1. That a new player would offer enterprise level product, instead of consumer grade. IMO it's very likely that if such a scenario unfolded, the market would be segmented into enterprise/consumer not only at the product level, but at the supplier level too. At least initially.

2. That AI compute demand is essentially unlimited AND silicon production capacity is and will remain bottleneck in datacenter buildouts. IMO we are much closer to the point where physical infrastructure becomes the apparent bottleneck than it would seem, IF political climate allows. Datacenter buildout is THE talking point in Ohio elections and if the dems win, datacenters will become THE talking point in the whole USofA. In just a couple of months the landscape they are operating in could become very different.

While this 1/2 typology is incomplete, diabetic ketoacidosis is a phenomenon generally relevant to type 1 family of conditions.

Normally (even with pure type 2!) glucose-ketone levels move in opposition: to put it simply ketone production is activated by low insulin, which is activated by low glucose. Ketone bodies are then consumed instead of glucose or excreted and generally homeostasis ensures that ketone levels do not approach anywhere close to ketoacidosis levels.

In cases where insulin production is broken (Type I diabetes, monogenic diabetes, mody) despite exogenous carbs raising blood glucose levels ketone body production is still active, however in most cases glucose is the preferred energy source, which leads to broken homeostasis of ketones, ketones accumulating and resulting diabetic ketoacidosis.

Type II family is characterized by high insulin. Some call it insufficient insulin, some call it insulin resistance, but the result is that insulin remains high and ketone production low. Regardless if the person is nominally healthy or has insulin resistance, the only way to trigger ketone production is to get insulin low for extended period, which is caused by lack of exogenous glucose. So either ketogenic diet or full-blown fasting.

Advanced and prolonged Type II diabetes (even if treated with insulin) can cause insulin production to drop along with insulin resistance, so the patient could develop Type I-like symptoms and risks, including DKA.

> There is little indication that in 2028 situation will be any better unless something drastic happens like AI crash.

China.

This market situation is a perfect storm for chinese manufacturers to step up. They don't have to chase latest-and-greatest, price-performance is one of the strongest demand drivers in consumer segment. They need a viable alternative, offer it at a reasonable price - which is much easier to achieve under current heavily inflated conditions - and that would quickly entrench them as a household brand.

Remember, it's not that there's no chinese lithography tech at all, it's just not advanced enough to yield mass production silicon at commercially viable prices. It might be the case that at current market conditions this caveat does not hold and all they need to do is ship. Even if the current prices mean they do it at break-even it would still be an enormously massive win.

Again, they don't have to compete at the flagship level from the get go, they need something commercially viable. There are tons of Chinese companies in the west and probably even more western on the outside chinese white-label goods. Chinese government has enough weight to push domestic silicon on those companies to create domestic silicon industry that can make the unit economies work.

All in all, there is a very likely scenario where this current AI boom and the resulting crunch on silicon supply creates a competitive silicon industry in China. If you think something in the realm of "I would not buy chinese silicon even if it was cheaper" it does not matter. Look at smartphone market share outside of USA, Japan and West Europe: in majority of the world Apple+Samsung barely touches 50%. What this "rest of the world" lacks in individual purchasing power it more than makes up for in numbers.

> I think Western people still call this situation “outsourcing” when in reality what is happening is that China is better at manufacturing than everyone else, and they’re starting to be better than everyone else at design and engineering, too.

The media to this day portrays China as if it was 80s. Yes, at that time it was an open-air manufacturing plant. You can run rudimentary floor operations with high school educated workers, but you still need trained engineers and managers to run the operations. Exporting engineers quickly became impractical, which led to local engineers getting trained. At some point the training became the bottleneck so local educators were trained. And so on.

Over the years, China has built the entire industrial pipeline: all the way from education and vocational training, to scientific research, to local engineering houses. Remember, the people who built Shenzen are now retired. Or to put it into perspective, China is currently at roughly similar age of industrial boom as post-WWII USA was in... the late 90s - early 00s.

"The West" had a head start with regards to IP and China is indeed fighting an uphill battle there, but they have a huge domestic market to grow the companies out. The proud "Designed in X, made in China" things are being replaced with white-label "made in China", where "designed in China" is implied.

Do you have a robot vacuum? It's probably Roborock / Dreame / Ecovacs, not even some western branding.

> But what kept me away from Rust for a long time is this talking point of rejecting incorrect code which is so obviously wrong it made proponents of Rust sound very cultish to me.

In discussions regarding testing and static vs dynamic languages, I like to emphasize the point that with static languages you get some "tests" for free: the compiler enforcing the contract will "test" that you are not passing in string for integer. With e.g. Python if you want to be defensive and on the correctness side, you need to implement poor-man's type restrictions and tests for the unit so it behaves sensibly with call-site being incorrect.

Does it sound cultish to you to insist on static type checks when e.g. writing Python? There's quite tangible value in that.

> Rust cannot prevent incorrect code, nor is this possible (halting problem).

Yes, nothing will prevent analyst/PO from misunderstanding business requirements, nothing will prevent dev from misunderstanding the technical requirements. Or not thinking things through. Errors on this front will always turnaround.

Correctness in this context refers to programmer's and compiler's understanding of code being aligned. Correct code does what it is supposed to do. Rust takes type safety and elevates it to a next level, ensuring reads, writes and object lifetimes are correct.

The overarching argument in this article seems to be sort of chicken and an egg.

> 4. No experienced developers

Well, with C you need experienced devs that are also EXPERIENCED IN C. You can write C that compiles but is all kinds of incorrect, usually subtly. Any new language that works with the dev on writing correct code or outright refuses to compile with incorrect code (hinting at Rust here) cracks this egg a bit.

> If you want to target some obscure platform, then likely it's assuming you're using C.

Some (most?) obscure platforms offer a fork of GCC, yes. With LLVM frontend becomes less and less relevant. This particular chicken and an egg is being broken with or without a successor to C.

> Any C alternative will be expected to be on par with C in performance. The problem is that C have practically no checks, so any safety checks put into the competing language will have a runtime cost, which often is unacceptable. This leads to a strategy of only having checks in "safe" mode. Where the "fast" mode is just as "unsafe" as C.

This argument is circular. There are indeed some scenarios where you do absolutely need "macro system for assembly" to do some weird shit, but typically that is a relatively small part of the whole project. Unsafe modes help tackle this small need. The argument reads like needing C-ish language for some little parts of your project requires to use C-ish language for the whole project.

> 3. Programmer productivity

This whole argument is weirdly focused. In my experience, a huge chunk of effort is spent on rework. Any language that improves turnaround rate improves productivity on feature level. The argument again assumes that devs manage to produce correct code without turnarounds (which is rare in practice even with highly experienced devs) and therefore any new language would increase turnarounds. Safety and productivity features are usually designed to increase quality without expertise-floor.

A nitpick. While this definitely does not apply to the problem described, some changes are indeed mostly alignment, not implementation.