nercury

For anyone unfamiliar how rust helps, the idea is this: first, you can identify common usage patterns and build safe wrappers around raw system operations.

The wrappers have no additional cost when compiled: A nested structure of Wrapper<OtherWrapper<OverSomePointer>> has a size of the flattened contained data, all the type info will be stripped away.

This part is the hardest, but the reward is that you can then use these wrappers without thinking about lower-level details. Of course, it is possible to do that in other languages, but rust type system can encode more information in types. That means more checks at compile time and less cautionary instructions are needed in the code comments.

I always hear arguments that "Rust still does not prevent X!". That's not the point. Rust type system simply can prevent more if used as intended.

Thankfully ChatGPT can translate this into readable English.

A bit of fun whatabautism: I've tried unsubscribing from mailing list, it required to login. I've asked it to reset my password, it send me my old password over email as a reminder.

Have we forgot that we have attributed "thinking" to all the machines since the beginning?

They are simplifying the heuristics: if it's not on MS store, then it's a virus.

It's mostly fashion.

Your article says "there is no empirical reduction in bugs" and nothing else.

Don't "run" programs, don't let them "spawn" threads, don't allow CPU to "follow" instructions, don't "read" or "write" files, should I keep going? All these words used to mean humans doing things, we have been anthropomorphising the machines since the beginning. You are fighting a loosing battle here, better to just calm down and relax.

Perfect climate: not too hot, not too cold, no earthquakes, underground fresh water basically anywhere you dig. Fiber optics covering the entire country. Full 4G coverage, because no mountains. Soil perfect for growing food. Lots of country still covered in natural forests, when compared to other EU nations.

The problem is not corruption, the problem is this self-loathing victim mindset. I am also from there and I am sick of it. If you don't like it, go away somewhere where the are no problems and no corruption.

The argument for static types is that it makes type bugs impossible because the types are static. There is no emotional attachment other than rage when faced with "but but it does not eliminate ALL the bugs!!!!!!".

Do younger people have a lax definition of "innovative"?

With GC rust would have been just another slightly different language.

It's possible to unfollow everyone who posts outrage tweets, give it a try. It will become eerily quiet, and hopefully only occasional once-a-day quality tweet will remain.

Twitter has a useful feature: unfollow. Just follow what you want to read, and curate the content this way.

The other issue, getting more followers, is all about posting something worth following.

This is basically scaremongering at this point. The system that failed is well understood now, and the whole aircraft has been scrutinized.

But no, let's dump all these planes. Very ecological.

Let's do a complete redesign using a new parts. Because those won't have any problems.

/s

It's quite clear how this "magic" is possible. Weather you like it or not, the future is a "product on a chip". That includes everything: CPU, GPU, RAM, SSD, and assembly instructions for vendor-specific things like NSObject. This puts everything physically close together (efficient), eliminates all the protocol compatibility overhead (efficient), removes all the standards the company can't control (efficient). The downside, of course, that this will be the ultimate vendor lock-in, which is hard to compete with, and can't be serviced by anyone else. The upside is that the alternatives will always remain relevant.

No, trolleybuses: https://kauno.diena.lt/sites/default/files/styles/940x000/pu...

Helicopter?

Unfollow anyone who retweets outrage tweets, or posts low-effort content, follow people who post original, high effort content, and never go to the twitter's home page -- read only the latest tweets in chronological order. This will considerably reduce tweets that target emotional triggers or simply waste time.

No, the modules are fine

My suggestion for beginners would be to write modules inline and then use the IDE refactor command (IntelliJ plugin has that) to move them to another file. This is the best way to "get it".

Good job projecting your reasons to the world.

If you find yourself to be 10x engineer, you probably need a better team.

Does this mean that one of the reasons MCAS relied on a single sensor could be the already saturated CPU? Mindblowing.

It is worth learning C because there is a lot of code written in C.

Sadly this cron has fired the shell script author, and no one dares to touch it.

Small companies won't have resources to create their own content filters.

Guess who is going to sell content-filter-as-a-service?

I want to reflect on that this is still done without any garbage collector.

You have successfuly uncovered that Rust is a fundamentally different programming language, instead of a variation of the same. I feel that having learned Rust, any new language similar to Rust would have way lower learning curve. It is quite similar to the jump required from imperative to a funtional language. We may be missing a good name for a paradigm the Rust falls into.

It's futile battle though to achieve both performance and safety in C++: as an example, safety requires avoiding moves, using reference counting, while achieving performance means avoiding copies and passing occasional references around, among other things. That's why advertising C++ solution as fast does not work well with "but C++ can be safe too!".