Skip to main content

𝚛𝚊𝚝 reshared this.

Content warning: Rust question

This entry was edited (11 hours ago)

reshared this

in reply to Mo :ferris: :tux:

@mo8it My bet is that it's being called on a Unix-like OS while the process is multi-threaded. Returning the error is necessary for soundness.

Jonathan Lamothe reshared this.

Aerospace chocolatiers prepare a Ferrero Rocher for launch into low earth orbit it

reshared this

in reply to R. L. Dane :debian: :openbsd:🧉

@RL_Dane @muvlon
G’damnit. I told them I hate liquid helium centers… Can’t they for once use solid state semiconductor based radiative balanced cooling?!

More musings on #Rust:

I wonder if it would be possible to write an #SNES #ROM in Rust. It seems like exactly the kind of resource-constrained system that would be a prime candidate for that sort of thing. Unfortunately, it seems that the SNES used a custom processor, so it's very possible that I won't be able to specify it as a compile target. A quick search reveals that many people have made SNES emulators in Rust, but at a glace, I see nothing about writing ROMS.

I believe the original NES used an off-the-shelf processor (6502 if memory serves?). Perhaps that's more likely to be supported, but that may be a little too resource constrained.

I shall have to dig deeper into this idea. I love the idea of building a custom ROM rather than just pirating something off the internet.

Has anyone done anything like this? Links to any relevant resources would be very much appreciated.

Programming Feed reshared this.

in reply to Jonathan Lamothe

Looks like the SNES used a Ricoh 5A22, which apparently was based on the 6502? Perhaps this is possible after all... though I don't want to speak too soon.
in reply to Jonathan Lamothe

The SNES CPU is based on the WDC 65C816, which is indeed able to run 6502 code but it also has 16-bit mode instructions with much larger memory address space.

I think the only general purpose computer to use this CPU was the Apple IIGS, so maybe look around to see if there's any Rust port to Apple IIGS.

in reply to Jonathan Lamothe

this folks have ported llvm to MOS6502:

You can try to link rustc to that fork and add a new rustc target.

It will be a very long journey, but it is possible.

When a security guard in a grocery store needs to have a bulletproof vest, we have failed as a society.

𝚛𝚊𝚝 reshared this.

Newbie #Rust question time:

I wan to use the current_local_offset function from the time library, but I apparently need to import it into my project with the local-offset feature.

I assume I need to specify this in Cargo.toml but for the life of me, I can't figure out how. Can someone point me in the right direction?


reshared this

in reply to Jonathan Lamothe

Have you tried something like the following?

time = { version = "0.3.36", features = ["local-offset"] }

in reply to glyn

@underlap ^^ this is what is necessary (speaking as the maintainer)

Jonathan Lamothe reshared this.

I'm an abandonware radicalist; not only should abandoned software have its source released, abandoned hardware should be opened up to development to stop it being ewaste.
in reply to big awoo notation Jeremy List reshared this.

Nevermind abandoned software and hardware, I'm of the view that purchasing software or hardware should include the tools necessary to control every bit of data in every RAM and register and the documentation necessary to do so.

I understand that it's much easier to make the abandonware argument though, and I also support that. It'd be a nice compromise if companies had to submit documentation and programming tools to some kind of agency that timed the public release for a few years after the launch date. That way, millions of products wouldn't become e-waste if a company is suddenly bought out or goes bankrupt.

in reply to big awoo notation

I agree with you in principle but I’m not sure how that would work in practice. Sure some products from companies still operating could be made that way but there’s an awful lot of e-waste from companies that no longer exist. Also hard to compel a company to open up their products before they vanish when they can’t pay their own staff. Perhaps one option would be to ensure that it is at least unequivocally legal for others to open it up after the company no longer exists.

Jonathan Lamothe reshared this.

This entry was edited (5 days ago)

reshared this

in reply to Dgar

@courtcan Not very impressive on the morning after fighter jets saved my ars from a swarm of Iranian drones

Justin To #НетВойне reshared this.

Story time:

I've been holed up in the (home) office for most of the day (not uncommon). I happened to look out the window and noticed that our building was surrounded by cops.


Turns out they arrested one of the downstairs neighbours... for what, I don't know.

Here's the interesting bit though: apparently, the landlord offered them the key to the apartment, but they couldn't legally use it because there was no warrant. I guess that makes sense, but while they weren't allowed to to that, they apparently were allowed to enter the apartment by prying a window open or kicking the door in. In what world does that make any sense?

reshared this

in reply to Jonathan Lamothe

@Jonathan Lamothe My actual guess is that it's easier to justify forcefully entering the apartment because there would be some "safety concern" if you actually entered forcefully.

Jonathan Lamothe reshared this.

Somebody managed to coax the Gab AI chatbot to reveal its prompt:
in reply to malte

Content warning: OCR Output (chars: 3804)

in reply to OCR Bot

I will need convincing that someone didn't just write this and then ask for it to be repeated. I don't know enough about this to even guess if it makes sense to expect a mission statement like this to exist.
This entry was edited (6 days ago)
in reply to 2xfo

@RnDanger Just tried it, asked to repeat previous text and it said the exact same. However, I Don't think it work as the AI does use phrase and opinion that contradicts this text (try it:
in reply to VessOnSecurity

Imagine being the sorry excuse for a human being who wrote this.

𝚛𝚊𝚝 reshared this.

People who don't like #Rust: why specifically don't you like it?

I'm in the process of learning it now. There are definitely some things about the language that I can see some as finding irritating (i.e.: the borrowing system). Personally though, I'd rather have a dozen complie-time errors than a single runtime error. This is the reason I tend to gravitate towards Haskell, for instance.

It's certainly not the right language for everything, but if you want better safety in code that needs to be highly efficient, it seems a reasonable alternative to C/C++.


reshared this

in reply to Jonathan Lamothe

the borrow checker is such a big part of the language it's not just slightly irritating, it's like having a non-consentual finger up the ass every time you open some Rust code in your editor

And the fact Rust is always staticallly linked and lacks any sort of reproducible builds don't help, even the compiler itself only compiles with an n-2 version of the compiler, if you skip updating the compiler for a while and want or have to keep using sources then have fun compiling every version since you last updated the compiler

Its type system is also like a borrow checker: non-consentual fist up the ass, want to add an u8 to an u32? Nope, can't, have to manually cast everything because that's why we do programming languages instead of writing Assembly, to do all the fucking busy work ourselves

Oh, and Cargo is its own can of rotten worms

in reply to Reid

@Reiddragon > And the fact Rust is always staticallly linked and lacks any sort of reproducible builds don't help

That is excusable in languages where source-only distribution is normal and expected. (Indeed, compilation should be a transparent caching step and artifacts of such shouldn't be commonly shared.)

That is not the case for Rust.

> even the compiler itself only compiles with an n-2 version of the compiler

That's also a problem, Rust's bootstrap story sucks.

Ada's might suck as much, I'm not sure, I have found a few interpreters when I last looked...

> I'd rather have a dozen complie-time errors than a single runtime error. This is the reason I tend to gravitate towards Haskell, for instance.

There should be no meaningful difference between runtime and dev-time for the majority of devs. Dead languages aren't necessary. And punchcard retrocompatibility can be preserved without prioritizing a development process that is optimized for that workflow.

As for typing static vs dynamic, there's a thing called "gradual typing", and it is very possible to tie the type-checker into a REPL.

in reply to Jonathan Lamothe

I've got a few things with Rust that make me dislike it a bit -- note that that doesn't mean that I think it's generally a bad language. (They're all good langs, Brent.) But here we go:

Another single implementation standard-less language. No solid standard library, everything done by downloading the internet. Very un-Turbo-Pascal-ish compile times and memory usage. Annotations. BCPL-ish syntax with too much line noise (and hey, I used to program Perl). Tied a lot to the worst things in IT (browser engines, crypto). Fanatical community. Overly complex async to save me from writing threads. Both functional purists and micro-optimizers. The word "Rustaceans" alone.

It's not a language that I'd like to use recreationally, but I wouldn't quit jobs if I have to do more work with it at work.

in reply to Aral Balkan

The rising value of goods and services per worker meant rising pay. But that relationship ended in the 1970s

The Great Regression: 1980-Now

Chart shows 80% productivity rise matched by 8% average hourly compensation and 7% average hourly wage increases. (2/2)

in reply to Aral Balkan


Chais pas "où" on a merdé mais le "quand" est assez visible.

Ironie de l'histoire, cela correspond à la prise de pouvoir des socalistes en France - si tant est que ce graphique s'y applique.

p/s. Et avant qu'on ne me saute sur le râble, je rappelle que le MATIF, un des marchés financiers les plus spéculatifs au monde à l'époque, est une invention d'un ministre socialiste si je ne m'abuse.

Content warning: transphobia

Dear OpenBoard,

I have you set to English (UK) for a reason (because English (CA) isn't an option). Quit trying to autocorrect "colour" to "color".


in reply to Jonathan Lamothe

that's odd having to go with en-us because there is no en-gb option is the norm but then ob seems to have started in ch..

in reply to Jonathan Lamothe screwlisp reshared this.

every time I said this I ended up regretting it within a week
in reply to Reid

DJ UNK and I basically have a show that's just about what @me does.


so according to classic Bell labs at worst jlamothe is a minor success ;p

in reply to Jonathan Lamothe

Just got to the section on Smart Pointers. As I recall, this is where things start to get particularly interesting/complicated.
in reply to Jonathan Lamothe

You don't often need smart pointers if you get the design of your code right. Similarly, there's not much need to use copy or clone if you work "with the grain" of the borrow checker. Adapting your designs and coding style in this way is, IMO, the key part of learning Rust.
in reply to Jonathan Lamothe

for me the hard part to stop making mistakes around was the difference between &str and String, but the hard part to actually understand is pinning. Smart pointers are pretty straightforward.

The Gibson reshared this.

Diving into the #Veilid documentation... or what I can find of it.

I have an idea that may well turn out to be vapourware, but my brain won't let me drop it if I don't at least try to build it.

I've been itching to do something with Veilid since @The Gibson first announced it.

reshared this

in reply to Jonathan Lamothe

I honestly didn't think veilid managed to get anywhere, which was sad.
VeilidChat exists but I think that's the only productive/useful project.
Development on the repos has really slowed down post-announcement, which isn't inherently a bad thing, if it's "done", but I don't think it's done - instead it feels stalled.

Maybe it all moved on-network and to places I can't see? That'd be cool.

Jonathan Lamothe reshared this.

"This turns #AI-"assisted" coders into reverse centaurs. The AI can churn out code at superhuman speed, and you, the human in the loop, must maintain perfect vigilance and attention"

@pluralistic once again writes words that get stuck in my brain.

reshared this

Jonathan Lamothe reshared this.

This is the part where I gloat about being right about Bluesky, right?

They never really wanted federation.

reshared this