caspper69

I write Rust code. I don’t mind it. But the truth is, I use very little of the language.

I visit the Discord, and I see all the crazy overcomplicated shit these people are writing.

If I had to try and make heads or tails of some of that shit I’d go crazy.

I actually think some of it is actual trolling by Rust itself.

And yes, the people are toxic. It’s like they really believe C and C++ and everyone else did literally everything wrong. And some of their justifications are seriously weak sauce.

And remember, I like Rust. At least the parts I use. But it’s easily going to eclipse C++ in complexity if it continues the way it has been operating.

The breaking changes version to version. Zig tends to be quite liberal about moving forward, as should be expected at its version level. It simply outpaces the llms datasets.

I feel like this article means well, but assembly or machine level types are not the same. Sure, the assembler and cpu will execute the instruction with the given type, but the next instruction can use a different instruction with different types and no one will be any the wiser. So one operation’s uint64 is another operation’s int64.

The type data in assembly doesn’t live with the data itself, nor are types for data stored anywhere.

I get the point but I think it just misses the mark.

Step 1: download windows media tool

Step 2: create iso with said tool

Step 3: use rufus to make iso into bootable usb with the installation options you want

Step 4: reformat & install

Step 5: Drivers

Step 6: chrome and/or firefox

Step 7: o365

???

Profit

There’s a reason people say don’t meet your heroes.

No matter how elevated they are in your mind, they’re still just people. One pants leg at a time and all.

Ah yes, the lulz, the great American pastime.

Yes, duffel bags full.

But it doesn't take too many cash purchases that are not inline with your tax returns before somebody is going to start snooping around.

edit: although sometimes, a lot longer than one might expect.

Maybe not the actual quality, but if I put a $50k Rolex on the table and a $50 Timex, 98/100 people will choose the Rolex, right or wrong.

Wow. At least I know who downvoted me.

Maybe you should take a step back and realize that sofware developers themselves are not the primary purchasers of most software. The average joe or jane purchaser doesn't have some magical AI slop detector, especially if the UI is well done.

One of my favorite phrases is “the market can stay irrational longer than you can stay solvent.”

Even if all signs point to impending doom, at the end of the day if people are still buying, stocks will hold their value.

The difference, and I think we as an industry will have to reconcile this depending on how advanced llms get, is that you don’t see the quality in handmade code like you do in a high end watch or a luxury automobile or appliance. The veneer might be identical. It’s going to be tough to convince people that handmade software has added value or quality over slop. I still believe it does right now, but that might not always be true. And this is an industry that has pumped out a lot of sloppy code for decades, even before it was actual slop.

Yes, many people instinctively stay away from anything microsoft (except github, typescript and npm). But the stack is solid. I’m always reminded of Stack Overflow and how they built on asp.net and like 7 servers and it scaled very well for years.

Everyone has what they like and what they’re familiar with, and for better or worse, especially for startups it’s rarely .net. But I couldn’t imagine e.g. using js instead on the back end, but that’s just me.

They are aligning more closely with the Rust 2024 model for unsafety, which requires inner annotations at the point of unsafety in addition to notation of the function (unless it is the safe-unsafe boundary) plus it imposes a requirement for a SAFETY doc notation for describing the specific invariants the caller must enforce to uphold the safety guarantees. Not terribly onerous in my opinion. I maintain a few native library wrappers on nuget, so I will have to do some updates around IntPtr usage, but this doesn’t seem like it will be terribly painful in my case. Thankfully I don’t do much marshalling. Plus you get a nifty badge on nuget for making your library safe.

The blurb toward the end about Rent/return makes me a bit nervous though. They say they’re not going full borrow checker, but rent at least sounds an awful lot like borrow to me. Details were basically non-existent though.

I guess I wonder what the end game is here though. The more they make C# like Rust with a GC, the less incentive people have to use C# except maybe to support legacy work. I am still far more comfortable in C# than Rust, and I believe C# is superior for e.g. web, but over time this advantage could be lessened quite a bit as the Rust ecosystem continues to grow.

It's been over for years. Google scares companies into bidding against each other just to be seen. It's a complete farce & a racket. It's the pay to play web.