> You write a `TrafficLight` struct. You use an `enum` for state. You might use a Mutex. The compiler ensures you don’t access the memory of a deleted light. But does it ensure NS and EW aren’t green simultaneously? No. That’s a logic error, not a memory error. Rust saves you from a segfault, but it happily compiles a crash.
But Rust's type system still lets you build a system that covers that logic error. Don't do the naive thing (two lights as enums with states of Red or Green which permits four states, one of which is invalid). Create a four state enum: RG, GR, RR->GR, RR->RG (the third and fourth look superficially the same but indicate which light will become green in the next state transition). You could also do three states (RG, GR, RR) but then you need to track additional state to know which light was green and which will become green, which is neatly encapsulated in the four state machine. There, logic error removed from the program and within Rust's type system.
If you don't want both lights to be red at the same time, then you just do it with two states: RG, GR. Now it's impossible to get into the state where both lights are green because that state doesn't exist and you don't need a guard to prevent it, it literally cannot happen in the code.
That was deliberately just a simple example to give people an impression how the "code" looks which the LLM generates. There is no doubt that you can implement a traffic light with a "traditional" programming approach. The question is rather, why an LLM should produce something which was mostly invented to overcome human weakness, instead of using the much higher potential of this technology. As a programming language author myself I'm interested in the role of programming languages in the age of LLMs; the article represents my conclusions so far.
I picked out that example because it weakened your article. It comes across as a claim that Rust can't help with logic errors, which is false (whether your intent or not that's how it reads). Using bad examples that are easily countered weakens your overall thesis.
Your thesis is interesting, and something I've applied in work (formal methods, or informal-formal methods without the full rigor, to code). But you spend a large amount of the article bashing Rust and its community instead of building up an interesting discussion. I mean, your conclusion section is literally titled "Conclusion: The End of the Cult". Your intent is clear there, to bash a community and language. That's not productive.
As a senior engineer, I am quite alienated by the hype and the completely exaggerated promises that are being made to people. It is precisely such exaggerations that inevitably lead to equally exaggerated counter-movements (such as today's anti-OOP, for example). As long as the community is unable to view technologies objectively, a lot of money and time will be wasted on false expectations. If we don't take a clear stand against this, nothing will improve. I have presented my argument. It consists of more than just a keyword.
If it were shadowbanned we wouldn't be able to comment on it. People have flagged it, it triggered the flamewar detector, or both. That's why it got downranked.
If you think the topic of his death has been "shadowbanned" (for some non-standard definition of shadowbanned), check the front page. There's another discussion there about it.
> This topic is not on the front page for me, yet it was on the front page for you.
I'd suggest checking again. It's around #12 right now. I suspect you didn't actually look and just wanted to make something up to complain about. Which is a strange thing to do, but there are stranger things people do on this site.
kisama has no submissions listed. They have a comment which is [dead], and probably dead for that link. But there are two possibilities:
1. The link itself caused the comment to be auto-killed. This can happen when you link to particular sources (I've demonstrated it in the past with, IIRC, a UT subdomain that had ended up in the spam list somehow, mods corrected it).
2. The fact that a new account with low karma submitted a link caused it to be killed. This is very common, they get caught up in the spam filter (which doesn't always look at the link content, but at the account behavior). New account, one of their first comments includes a link, often spam.
Email the mods, link is at the bottom of almost every page on HN, if there's nothing wrong with the link (and it looks like there isn't) then they'll restore the comment and account (if it ended up getting shadowbanned).
In the US or elsewhere? I've known a lot of people who attended college at 16, and through friends with teenage children know even more these days. They attended (or are attending) schools in a variety of states.
To qualify for general admission to a college, you must have a high school diploma, its equivalent, or be 18 years of age or older.
Unclear whether that is statewide or just a requirement of this state institution. I suspect many of the ones that do have this age requirement also have the diploma exception.
By what you quoted, VA does not require you to be an adult to attend college, if you graduate high school early (or somehow satisfy the diploma requirement early) you can attend college there (assuming you get admitted and meet whatever other requirements they have like SAT scores and such). That's not an example of a state barring minors from attending college.
Probably fair. I think there is a lot of in terms of initially starting school, skipping grades, etc. that it is practically difficult (probably more than it used to be)-and probably a lot of competitive schools that will just go NEXT on the application. More or less obviously, private schools have a lot more flexibility.
I was going to say something similar. Competitions between people does nothing for me (neither motivates nor demotivates), but accountability groups help me a lot to be more consistent or push a bit harder. But I've found that some of my friends really get turned off by the accountability groups, they feel like they're falling behind and end up giving up. Which is disappointing, the accountability groups aren't meant as competitions but encouragement. If you've got someone like me (I can lose weight quickly once I start exercising just a bit more than whatever my baseline is going into it) but your weight is harder to shed, if you see it as a comparison/competition then it can become very discouraging.
Phrasing in things like that matters a lot, how you talk about it and what you talk about.
https://www.eia.gov/energyexplained/use-of-energy/electricit... - This shows a breakdown. HVAC is not the most [edit: as in majority, it has the largest share though], but it is a significant amount. Also my household is apparently well below average (though still higher than you) for the US and our region in the US.
But Rust's type system still lets you build a system that covers that logic error. Don't do the naive thing (two lights as enums with states of Red or Green which permits four states, one of which is invalid). Create a four state enum: RG, GR, RR->GR, RR->RG (the third and fourth look superficially the same but indicate which light will become green in the next state transition). You could also do three states (RG, GR, RR) but then you need to track additional state to know which light was green and which will become green, which is neatly encapsulated in the four state machine. There, logic error removed from the program and within Rust's type system.
If you don't want both lights to be red at the same time, then you just do it with two states: RG, GR. Now it's impossible to get into the state where both lights are green because that state doesn't exist and you don't need a guard to prevent it, it literally cannot happen in the code.
reply