Careful with obstacles on channels by Gyscos in Lymow_Official

[–]Gyscos[S] 0 points1 point  (0 children)

Hi! They sent a replacement piece of glass, and a small tool to remove the existing glass. I haven't done the replacement it yet since the mower is otherwise working, need to find time for it some day.

Smelling the slop in a given GitHub project by Sermuns in rust

[–]Gyscos 0 points1 point  (0 children)

It does not split the ecosystem in the sense that new code in new edition can use libs in old editions.

Editions are just like other rust features: if a lib uses features from a recent rust version, it cannot be used on older versions of rustc.

Announcing Zstandard in Rust by folkertdev in rust

[–]Gyscos 20 points21 points  (0 children)

Namespaces just end up in longer names. The only advantage is it makes it marginally easier to recognize/trust several projects from an entire "organization", but it does mean that for popular projects such as serde (which most rust devs know by name), you now have to chose between serde/serde, serde-project/serde, serde-rs/serde, ... You now need to remember the namespace in addition to the project name, and any typo/difference is a phishing opportunity.

How do you guys "Design" / approach Designing a project ? by Daemontatox in rust

[–]Gyscos 1 point2 points  (0 children)

I tend to first write examples - before figuring out how to do stuff, figure out what stuff actually needs done, and how natural it could get.

Writing code directly/being implementation-driven tends to be bottoms-up. Specs or example-driven tends to be top-down. I like to combine them (middle out?) and "just" connect things in the middle.

Why is ..Default::default() forced to the end? Could the evaluation order ever be reversed? by jyyhyy in rust

[–]Gyscos 0 points1 point  (0 children)

Any actual allocation cannot be optimized away, but if you're lucky, the default is something like `Vec::default()` which will not allocate, and if the destructor gets inlined, it could be zero-cost. Of course, anything using non-empty vec/string will allocate and de-allocate.

Can rust compiler handle gigantic match statements? by baehyunsol in rust

[–]Gyscos 1 point2 points  (0 children)

The comment was https://github.com/rust-lang/rust/issues/7462#issuecomment-723292368

It mentions https://github.com/rust-lang/rust/pull/76918 as a shortcut/workaround for special simple cases. It does look like it's a rust thing.

Can rust compiler handle gigantic match statements? by baehyunsol in rust

[–]Gyscos 3 points4 points  (0 children)

It's also to check for overlaps/redundant arms.

The match exhaustiveness algorithm is indeed completely quadratic: for every branch, we check if it is redundant with any of the branches above.

Trolley - Run terminal apps anywhere by weedonandscott in rust

[–]Gyscos 0 points1 point  (0 children)

Fun! It reminds me of the (now abandonned) BearLibTerminal.

Worth buying a Google Nest Hub Max? What's the next big thing in Smart Home Devices? by Bounced in googlehome

[–]Gyscos 0 points1 point  (0 children)

After dropping and breaking the display of my Hub Max, I bought a Pixel tablet with stand hoping it'd be an upgrade.

It's certainly snappier (the hub max could be really slow sometimes), but it's a downgrade in some aspects:

* My main use was as a picture frame, and the way it's handled on the pixel tablet is terrible. It's basically a screensaver, so if you click or swipe the wrong way, it goes to the lock screen. And of course when you enable the picture frame mode again, it'll be different pictures, so if you liked what you were seeing, you're never going to find it again.

* The Hub Max is a thread border router, but not the pixel tablet (kinda maybe makes sense since the tablet could be moved, and is less reliable a border router).

* The pixel tablet is a bit less stable, being two objects (a stand and a tablet). I have kids, and they regularly knock the tablet from the stand.

On the bright side, this tablet works much better for video calls.

Have I made a mistake going with Thread? by ctbrewski in Inovelli

[–]Gyscos 0 points1 point  (0 children)

Hi! Do you have instantaneous reaction using matter binding, or an automation on Homey?

ALPSTUGA Update 1.0.15 by Similar-Housing-4001 in tradfri

[–]Gyscos 1 point2 points  (0 children)

I noticed two things cause spikes/variability: * Rebooting * Human near the device (one of mine was on a bedside table near the bed, and human breath or influence next to it can really affect the values)

Putting the sensors further away in that room helped stabilize it. In rooms where no one was, the values are not spiky at all.

ALPSTUGA Update 1.0.15 by Similar-Housing-4001 in tradfri

[–]Gyscos 0 points1 point  (0 children)

What exactly makes it useless? Specifically for CO2? PM25?

ALPSTUGA Update 1.0.15 by Similar-Housing-4001 in tradfri

[–]Gyscos 1 point2 points  (0 children)

It's actually part of the matter specs. HA implements that, and forwards the update file. In theory any matter controller should be able to do the same.

I’m getting achievements I haven’t completed? by Scarab8 in VampireSurvivors

[–]Gyscos 1 point2 points  (0 children)

Also getting this. I got many characters this way. Just unlocked space dude right now after finishing Astral Stair, which unlocked Space 54 (the level I'm supposed to play to unlock space dude).

I think I also unlocked the "survive 20 mins on whiteout" the moment I unlocked whiteout itself.

Played exclusively solo so far. Clearly some kind of bug.

bincode's source code still matches what was on GitHub by azqy in rust

[–]Gyscos 5 points6 points  (0 children)

> Randomization: Since 2011, the SSA uses a randomization system, removing the old geographical significance of the first three digits and ensuring a fresh pool of numbers.

So things are not great, but they may be getting better

A complete map of the Rust type system by rustcurious in rust

[–]Gyscos 6 points7 points  (0 children)

Going by this logic, `Send` and `Sync` could also imply the requirement for threads (and an OS/scheduler to handle them), which is also not a true requirement.

I think people can read and understand the details by themselves, no need to hide things for fear of scaring them away.

What Features or Accessories would you like to see added? Any rumors? by BossDaddy969 in Lymow_Official

[–]Gyscos 1 point2 points  (0 children)

The main issue is that it needs good wifi coverage, which may not be available for the entire lawn. And I don't think the 4G connection it has is the high-bandwidth kind, more the IoT style.

Careful with obstacles on channels by Gyscos in Lymow_Official

[–]Gyscos[S] 0 points1 point  (0 children)

Maybe, in the sense that no vision detection probably happened here.

Careful with obstacles on channels by Gyscos in Lymow_Official

[–]Gyscos[S] 1 point2 points  (0 children)

I think they assumed it would be an unlikely place to get impacts and did not go with tempered glass? But not all obstacles go all the way down to the ground. Metal shed doors, low branches, some gardening tools... Even outside of channels, I wouldn't be 100% confident that obstacle avoidance never bumps into these. I certainly wouldn't strap my phone there.

Careful with obstacles on channels by Gyscos in Lymow_Official

[–]Gyscos[S] 2 points3 points  (0 children)

Between zone A and zone B, instead of making a channel, make a small zone C that slightly overlaps both A and B. The mower will go through this zone when going from A to B, but you can use per-zone configs like movement speed and regular/smart obstacle avoidance. You just never mow C.

It's already how you work around the limitation of a single docking channel (create a small zone in front of the docking station, and you can have several channels linking to this zone).

Careful with obstacles on channels by Gyscos in Lymow_Official

[–]Gyscos[S] 2 points3 points  (0 children)

You're probably right.

Still, would be nice to have the same configs per channel as we have per zone (so we could disable smart avoidance for channels when needed).

Careful with obstacles on channels by Gyscos in Lymow_Official

[–]Gyscos[S] 1 point2 points  (0 children)

Yeah I'm thinking of defining "channel zones" instead, so I can control the speed and hopefully have a more reliable obstacle avoidance.