Dark Arc @ Dark_Arc @social.packetloss.gg

Hiker, software engineer (primarily C++, Java, and Python), Minecraft modde

---

Read more

Posts

40

Comments

2,490

Joined

2 yr. ago

Moderating

---

I blame (in no small part) Hollywood and movies like Jurassic Park for pushing stereotypes about the field being dominated by creepy, obese, and gross "computer nerds."

Outside of a few niches like computer science this is increasingly true in the US as well AFAIK.

But 99.9% of code I write is safe rust - which most people just call rust.

That's true for your application maybe, but they go on to say how one should consider whether or not their problem is going to fit well within the rules of the rust borrow checker and that needs to be talked about more (vs just assuming Rust is the safest option).

The second time you write any project it will be easier and faster as you learn a lot form the first time you write something. If zig is always the rewrite it will come off better. Almost all rewrites are better or faster, even if you are moving to a slower language - the language makes a difference to performance and ease of writing. But far more does how you write things and the data structures/algorithms you use.

I'm going to agree to disagree with you there. I'd throw this in the category of persistent myth. Yes, ideally, you learn from your first experience and make everything better, but the reality is you often just end up with different mistakes.

Rewrites aren't often done outside of hobbyish projects because they're very expensive, stop new feature development, and you really can end up with something that's worse than what you started with (this is especially true if you've switched languages or frameworks).

Overall they seem to want to write as much unsafe as they can and are writing rust like it is C. This is not a good idea and why zig will be better suited.

They do explain with citations why it makes more sense (i.e. you end up with something more performance) to write their VM outside of the restrictions of the borrow checker.

But you can write a VM without large amounts of unsafe if you want to and it can be performant.

I think the claim is a bit of a stretch off the cuff. Ideally to retort this some rustacian would implement a mark and sweep VM in Rust with maximal use of the borrow checker.

Edit: Looking at their code, it's not all just one big unsafe block either. But it is something that they frequently had to drop down to, to implement this particular garbage collection strategy.

I think one of the computers in my basement is an ASRock board, and it's the flimsiest board I've ever had. Like the USB ports are really flexible.

Interesting; I've associated them with just making cheap boards. Is that changing?

Hmm... There's been a lot of quality of life patches (key binds, esc to close interfaces, clicking outside of interfaces closes them, smarter quantities on the withdraw screen, the option to have left click do a "default action" rather than opening the window, middle click drag, etc). He was pushing out changes every day for like two weeks, then weekly patches.

I haven't really seen anything I'd call a bug (it's actually one of the most stable games I've ever played).

It's definitely a true early access game (and they've said as much; they're open to a lot of potential changes and have been quite receptive to feedback with strong consensus), so I'd definitely check back from time to time if you like it in concept. They're talking about adding action queuing and reworking the combat to feel "better" in the near term. Player trading and PvP duels should come soon after as well along with a bunch of other stuff.

The game is designed to be friendly to touch screens and they do plan to have a mobile client eventually (similar to RuneScape). However, they have said they will not add any micro transactions or other predatory stuff ... and I believe them; the Gowers have been quite principled about that over the years.

Yeah? What wasn't clicking for you? I love it

I prefer Threema over Signal, but I do not think the US government recommending an app means that they have it backdoored. The US government needs to protect its own communications as well and while the left hand may be thinking encryption is bad for law enforcement the right have is thinking encryption is good for national security.

So... I don't think there's some larger conspiracy, just the normal government dissonance.

Threema

Me with a 7900 XTX playing brighter shores 🥲

The specs in the comic are just crazy. The top of the line option has expanded a lot too. In the past Nvidia wouldn't have bothered making a 4090 because the common belief was nobody would pay that much for a GPU... But seemingly enough people are willing to do it that it's worth doing now.

AMD also revived CPUs in desktop PCs from extreme stagnation and raised the bar for the high end on that side as well by a lot.

So it's a mix of inflation and the ceiling just being raised as to what the average consumer is offered.

Graphical realism is an easier metric than good writing or fun.

All MBAs, in all industries, need to be done away with.

I'll add this to the list of things that were working just fine that we're about to break along with using a passport to board a plane.

Some power systems do actually put a fuse in the extension cord... I think it's the UK that does this. Basically every power system other than the US uses different (safer) plug designs that solve the arcing problem.

In practice daisy chaining rarely causes a serious problem and it makes things more expensive so it never really became a thing that was legislated or common within the US. Similar to how the plug designs themselves rarely cause a problem so it hasn't made sense to actually change them.

There are two things going on here.

The first is that yes, more connections causes more opportunities for the plugs to slip. So you can get short circuits or even arcing that can start a fire.

The second is that the wire in the cord has a certain rating on it. Many of those cords do not use 12 (20 amp) or 14 (15 amp) gauge wire; so, they're not rated for the full capacity of the wire in the wall. The breakers are sized to protect the wires in the wall, they don't know anything about the things plugged into them. So what can happen is you plug too much into the extension cord (particularly if it's a power strip) and the load on the extension cord is not enough to trip the breaker (because the walls are fine) but it's enough to overload the extension cord wire. In other words, the extension cord can start getting so hot it melts and possibly arcs up as the insulation fails.

You can have a fire from overloading a single power strip in just the same way. However, the more you chain together, the more likely you are to overload the power strip.

Ideally, you just think about what you're doing... But historically the easy answer is just to tell people not to chain things.

In short it's not about the distance, it's about the insulation and quality of the wire itself along with the number of connections.

I'm in like the opposite camp... But I've never been able to get past the initial learning curve of the game. Something has never clicked with this one for me

Looks like AMD has basically given up on the high end and is focusing more on the mid-range and iGPUs; arguably areas with much more market potential.

They've been saying they were doing as much throughout the year. They want to claw back market share and focus on power consumption and performance per dollar.

So... Having no public API means people just develop libraries to interact with your private API.

Furthermore, beautiful soup can work on any page... It's just a matter of how easily.

CSRF doesn't do what I think you think it does. It only works with a cooperating client (i.e. it's to protect a user in their own web browser). If it's a bot you'd just scrape the token and move on.

Fluctuations in user actions can also be simulated (you can have a bot architecture that delays work to be done to be similar to what a normal user might do/say/post) ... and rate limiting can be overcome by just using more accounts, stolen IP addresses, etc

You can do a lot, but it's always going to be a bit of a war. Things you're suggesting definitely help (a lot of them echo strategies used by RuneScape to prevent/reduce bots), but ... I think saying it's an architecture problem is a bit disingenuous; some of those suggestions also hurt users.

The most useful thing I've done with it so far is ask it specific game information like, "hey, I'm in x level and I see a chest. I can't see a way to get it right now, is it something I can come back and get later? Or do I have to figure it out now?". And it can answer that.

Yeah, except it can also get things very wrong. I tested it against my RuneScape knowledge. RuneScape is niche enough to not have them "fixing up" stuff specifically for it to make it look good and big enough that there has been a lot written for the LLM to go off of.

Suffice to say its advice was plausible sounding but inefficient if not outright grammatically correct nonsense. I would've been better served in every case by looking up player made guides.

Saves me from having to look up an ad riddled guide, but that's not a killer feature. Integration with aps could be huge, where it can actually do whatever task for you, or automate something tedious, but that's still not super common. I'd rather personally and directly control anything vaguely important.

Yeah it's kind of that last bit there.

I honestly don't know what they're going to do with AI stuff but I feel it's going to be a huge bust. The fundamentals of the technology are just completely unproven. To me it seems like a bunch of people invested in a palm reading machine and then (because they have a lot of money) tried to convince themselves and everyone else that the palm reading machine really is going to change the would (and they didn't just get scammed).