There’s a massive cultural thing in the US about the iPhone being the preferred phone and if you don’t have one it must be because you’re too poor to afford one. Obviously this is a result of marketing and isn’t universal but it is a surprisingly widely held view.

Given that, showing up in a group chat as a lone blue bubble marks you out as the inferior group member (in some people’s eyes). It doesn’t matter so much 1:1 but if there are 10 people the odd one out stands out.

I’ve never had to do this sort of thing in a lab, but I now feel I know exactly what that feels like! You have my sympathy!

Isn’t dust what you get when things disintegrate?

It’s just psychologically nicer. It’s a bit like it being nicer to get on with work when my desk is tidy (not that I tidy it that often)

I do it, because it makes a massive difference to me how tidy my bedroom feels and how welcoming the bed looks at the end of the day. I just have a duvet though, so it’s 10 seconds of pulling on each corner until it’s reasonably even - not going for perfection!

deleted by creator

One more note on learning Rust: what Rust does is front-load the pain. If you write something in another low-level “direct control of memory” language you can often get something going much more easily than Rust because you don’t have to “fight the borrow checker” - it’ll just let you do what you want. In Rust, you need to learn how all the ownership stuff works and what types to use to keep the compiler happy.

But then as your project grows, or does a more unusual thing, or is just handed over to someone who didn’t know the original design idea, Rust begins to shine more and more. Your C/C++/whatever program might start randomly crashing because there’s a case where your pointer arithmetic doesn’t work, or it has a security hole because it’s possible to make a buffer overrun. But in Rust, the compiler has already made you prove that none of that is possible in your program.

So you pay a cost at the start (both at the start of learning, and at the start of getting your program going) but then over time Rust gives you a good return on that investment.

Context: I am an embedded software engineer. I write a lot of low level code that runs on microprocessors or in OS kernels, as well as networking applications and other things. I write a lot of C, I write some Rust, I write Elixir if I possibly can, I write a lot of Python (I hate C++ with a passion).

I don’t think you want Rust. Python is unbeatable on “idea to deployment” speed. Python’s downsides:

• Painful packaging/distribution if you want to get a load of people who don’t have Python installed to run your thing (e.g the GUI program we currently maintain for talking to our hardware)
• Performance under some circumstances. There are some things that are not quick in Python. They’re not always the things you expect because Python actually drops down to C modules for a lot of the number crunching that you might do. E.g. for ML you are basically using Python to plug a load of bits of fast C code together

Rust is good when you need at least one of:

• High speed
• Control over use of memory
• Low level systems programming (drivers etc.)
• Can’t cope with a Garbage Collector
• Compiling to a microcontroller

If you’re doing one of those and so have become expert in Rust, then it is actually excellent for a lot of other things. E.g. you might build your data processor in it, and then distribution is easy because it’s just a single binary.

One option you might look at is Go. You get a lot of performance, you get good parallelism if you need it, it’s designed to be easy to learn, and it also compiles programs to a single binary for easy distribution.

Similarly I lose immersion when I’m going into a corner and I struggle to see the car on my inside. That’s why I want to try VR.

I don’t play with a shifter, just paddles on the wheel (driving F4 in iracing), so I don’t think I’d have any trouble with where the controls are. Maybe the Apple Vision Pro will end up being the best racing headset though and solve your problem.

What can you possibly need more than 100TB of storage for?! Presumably some redundancy but still way more than I can imagine a personal need for.

Great article. Similar to “NASA’s booster size is the result of the size of a horse’s ass”: https://www.linkedin.com/pulse/4-feet-85-inches-space-shuttle-horses-ass-william-batch-batchelder

I think the UK has completely eliminated the US style stop sign. I haven’t seen one in years.

I’m lucky enough to be able to have a lot of choice where I work - in a software engineer and there are any number of places where I could work and be paid well. Given that I feel some responsibility to work somewhere ethical - not everyone else has the opportunity to decide.

Yes, but the public transport in Singapore is excellent. I wish more cities did it.

The general concept you’re describing is called Risk Compensation. It feels intuitively correct, but in whatever context it’s been studied in almost all cases it turns out that the safety feature is actually better overall. Some people might be a bit riskier knowing about the safety net, but not enough to counteract the safety improvement.

Also - in the UK - road deaths go down over time, while miles driven goes up. Driving is getting safer. Cars are part of that, but so is road nd signal design and driver training.

It’s a core capability, but it’s a lot of work due to all the different types of thing you can post.

An app that can read posts and write comments is still useful without submitting posts, but an app that can submit posts but not read them is pretty useless. So, when you’re making stuff you do reading posts first, then you do writing comments, then you do submitting posts. That makes sense, right?

Let’s say it takes a few weeks to do each, and you’ve got to the stage where you’ve done reading and comments, but not submitting. That’s useful already! You’re not done, but what you’ve got is still useful for people and people want it, so why not release it at that point? Then carry on working and release the remaining features after.

Releasing as early as you can is good for everyone - the developer starts getting income for the work they’re doing, they learn about bugs and issues earlier in the development process and we get to start using it sooner. For me Sync without submitting is still better than the other apps, so I want to use it.

Everything=all but there is a Lemmy oddity here.

Everything shows everything for all the communities subscribed to by anyone on your instance. So it might be different from one instance to another because the users have subscribed to different sets of communities.

It’s likely to be a small difference between two big instances (lots of users so most communities will have at least one subscriber), but if you self host an instance it’ll be pretty useless.

I think we need to separate the system from the product. With Reddit they’re the same, with a single owner. With Lemmy/ActivityPub, just like with email, there’s an underlying system that nobody owns. It’s an ecosystem of pieces created by lots of different people.

It is a good thing that people are building products on top of that. Some of them are FOSS and some of them not. As long as no-one gets too much control of the underlying system then that’s great! Users retain choice and can choose FOSS apps if they want, or they can choose something like Sync.

I agree it would be sad if the only apps were paid, but I think a mix is a sign of a healthy ecosystem.

Yup, same here Firefox Android.

Yeah, anything after the @ is the instance. Each instance hosts some of the communities (subreddits) and some of the users. Donate to the instance you’re signed up to as a first priority and then maybe any other that hosts a load of communities you care about or do a particularly good job at something.

But if you’re broke and can’t afford it, don’t worry! On the other hand those of us who DO have a little bit of disposable income should donate a little here and there to help bring about the internet we want to see.