orsetto

joined 1 year ago
[–] orsetto@lemmy.dbzer0.com 2 points 1 week ago

Yup, no doubts there.

Anyway, OP, if I were you I'd buy that laptop (not for gaming tho, or at least not if you're looking for something more than "good enough")

[–] orsetto@lemmy.dbzer0.com 6 points 1 week ago (3 children)

I'm not really sure, but wasn't userbenchmark biased in favor of nvidia gpu?

In any case, I agree that an rx5500 is on the weaker side, so don't expect much, but it shouldn't be a lot worse than an rtx3050 (i'm not an expert tho)

 

If you have typed an <ESC> by mistake, you can get rid of it with a C-g.

quoting the emacs tutorial. made me giggle

[–] orsetto@lemmy.dbzer0.com 3 points 2 months ago

I used jerboa at first and it was really great, although a bit buggy (haven't used it in a while tho)

I'm now using a different frontend my instance provides (Photon, at p.lemmy.dbzer0.com) and it is really great on mobile. I added it to my home from the browser and it just feels like an app

[–] orsetto@lemmy.dbzer0.com 6 points 2 months ago (1 children)

Ads try to sell you something, there is no "call to action". Here, there is nothing to sell, so by definition it's not an ad.

They are just asking you if you'd like to help them in providing you the product you're already using.

[–] orsetto@lemmy.dbzer0.com 28 points 2 months ago (13 children)

Not an ad. No one is trying to sell you anything.

(If you get the notification) you're already using their product.

[–] orsetto@lemmy.dbzer0.com 3 points 5 months ago (1 children)

Honestly i wouldn't mind. Users on .world that don't want a butt load of defederations will probably (and hopefully) move to another instance, whilst the rest of lemmy will be free from all the liberals uncapable of discriminating between communists and tankies

[–] orsetto@lemmy.dbzer0.com 29 points 9 months ago

That's what a fed in your position would say.

[–] orsetto@lemmy.dbzer0.com 4 points 9 months ago (2 children)

The anguish of being stuck in the present

[–] orsetto@lemmy.dbzer0.com 1 points 9 months ago

Getting used to it is going to be a hell of a ride, but this is a wonderful thing.

Also using other pc is going to be even harder lol

[–] orsetto@lemmy.dbzer0.com 3 points 9 months ago (2 children)

Same. Forward slash always annoys me. It's in the middle of the keyboard, so you have to either 1. make a very uncomfortable move with your right hand, or 2. make an uncomfortable move with your right hand, or 3. use both your hands, which sucks.

Luckily I'm using linux, so I have tilde and backtick (`) as AltGr+' and AltGr+ì, which are pretty easy to type.

[–] orsetto@lemmy.dbzer0.com 3 points 9 months ago

I'm on mobile rn, it loads on mull (firefox fork) but not on vivaldi

[–] orsetto@lemmy.dbzer0.com 3 points 9 months ago (1 children)

Best thing you can do is learn a very strong and complex password to use for your proton account, that's what I did.

It takes a bit of time but eventually you'll learn to type it in fast.

 

Hi. I'm working on a project that compiles Rust code to WASM, and uses WASI in Node.js to execute it. After some development, I encountered a segmentation fault happening in the wasi.start() function. Considering that I'm kinda new to Node I was only able to understand that it was happening after the call to the exported WASM method returned.

This happened almost two months ago, and while I thought about reporting this to the node devs (WASI's also experimental), I was going to move soon and a lot has gone on.

Yesterday I tried to reproduce the bug on my laptop (that is not my usual development environment, which I don't have access to right now) but I wasn't able to.

I had to start fresh and install all the necessary tools from zero, so my theory is that there was something wrong in the previous environment. I'm also on Gentoo now, while I was running Arch previously.

Unfortunately I don't have the means to check on other environments. I tried to reproduce the old environment, installing the same versions of node and rust, with no luck. I also tested this with the latest versions and everything works fine.

This situation is upsetting. I don't know what's changed that caused the problem to "disappear", so i feel uncomfortable considering this solved. What would be the best approach in this situation?

EDIT: I also just tested it on Debian live, and I still wasn't able to reproduce the segfault

 
view more: next ›