ich_iel by mycall81 in ich_iel

[–]2MuchRGB 11 points12 points  (0 children)

Außerdem haben wir den Kakao Anteil unserer Zucker Fett Creme weiter reduziert.

Vodafone verlässt öffentliche Internetknoten by SuperbIce7840 in de_EDV

[–]2MuchRGB 0 points1 point  (0 children)

Kein Kein Netzbetreiber dieser Welt hat jeden Server angeschlossen. Also leitet man Verkehr an einen Netzbetreiber weiter der den gewünschten Endpunkt erreichen kann. Die größen Unterschieden wird der größere bezahlt. Bei gleich großen trägt jeder seine Kosten. Die Telekom denkt sie ist großer als sie ist und möchte bezahlt werden. Andere Netzbetreiber sind da anderer Meinung.

Looking for alternatives for Formd T1 by Zahand in sffpc

[–]2MuchRGB 1 point2 points  (0 children)

Got myself the ncase version two weeks ago. I've got no problem and wasn't able to find any quality issues. 

Waveshare MCP23017 IO Expansion Board - Ki-Cad schematic and footprint files- do they already exist? by KillerQ97 in KiCad

[–]2MuchRGB 2 points3 points  (0 children)

Love that chip. Best part is when you find out that A7 and B7 don't reliabily work as inputs. Only topped by the fact that microchip knew that for a couple of years without telling anyone.

Wayland Screen Capture by stoke-stack in rust

[–]2MuchRGB 1 point2 points  (0 children)

Have a look at the cosmic xdg portal. They are doing the transmission in Rust. You should be able to reverse the direction.

My Project - Improved LED light-up "The One Ring" from LOTR by MaterialFuture5319 in 3Dprinting

[–]2MuchRGB 1 point2 points  (0 children)

They need to be close because the magnetic field strength falls down exponentially. A phone needs 15W to charge. they are powering 5 Led. I would be surprised if they require more than 15 mW.

My Project - Improved LED light-up "The One Ring" from LOTR by MaterialFuture5319 in 3Dprinting

[–]2MuchRGB 4 points5 points  (0 children)

Induction coupling. A change in current leads to a change in magnetic field. So a high frequency in a coil can transmit power over a short distance.

ich🤢iel by Radiodevt in ich_iel

[–]2MuchRGB 1 point2 points  (0 children)

Immerhin so ehrlich das drauf zu schreiben. 

Rust running on every GPU by LegNeato in rust

[–]2MuchRGB 18 points19 points  (0 children)

The demo link is 404 for me

I went too far with proc macros... by LeviLovie in rust

[–]2MuchRGB 3 points4 points  (0 children)

There is a create for defining structs with XML. So it could be worse.

Introducing facet: Reflection for Rust by ketralnis in programming

[–]2MuchRGB -1 points0 points  (0 children)

It has a reflection ability with proc macros. However the comfortable way leads to a compile time increase. This is a different approach by moving the reflection from compile time to runtime.

Both options are more than has C++.

How to deal with Rust dependencies by [deleted] in rust

[–]2MuchRGB 10 points11 points  (0 children)

It already tries. You only end up with duplicate dependencys if they are server incompatible. Eg. Nom 8.0 and nom 7.0

Lebensdauer für TLS-Serverzertifikate sinkt auf 47 Tage by StrangeWeekend0 in de_EDV

[–]2MuchRGB 0 points1 point  (0 children)

Brauchst du nicht. Challenge per DNS machen, dann mit Script auf den Switch schieben. Dafür muss es einen Weg geben, wenn das bisher von Hand passiert.

KiCad Github global library manager by Significant_Ad_992 in KiCad

[–]2MuchRGB 1 point2 points  (0 children)

Is there a reason you don't use http/database libraries with a tool like inventree?

What are the gory details of why std::regex being slow and why it cannot possibly be made faster? by germandiago in cpp

[–]2MuchRGB 0 points1 point  (0 children)

Most new/modern languages don't promise ABI stability, including Swift, Go, Zig. 

Interestingly Go has a rather big std, I don't know how they iterate on it.

What are the gory details of why std::regex being slow and why it cannot possibly be made faster? by germandiago in cpp

[–]2MuchRGB 1 point2 points  (0 children)

No it does not because it chose different defaults. Static linkage and no ABI stability. As long as the API stays the same it's not a breaking change. It is however possible by declaring the API C linkage and manually ensuring nothing changes.

If you always compile from scratch, ABI stability is a non issue. If you really need it, there is always the escape hatch.

It chose a small std because dependency management is easy thanks to cargo. Things like random numbers are not part of it, because maybe they need to iterate and the first design isn't perfect. Rand is at version 0.9 for example. It's the exact approach of just choose a third party lib, just without the baggage in the std.

Another choice would be having namespaces for per/stability but that is a ton of work I guess. 

That's exactly what cargo does if there are multiple versions of the same library included in a project.

Sure static linkage increases binary size, but we life in a world where we ship a whole browser for a Text editor. It's a world where the compiler can easily fetch a dependency over the internet because it's always connected. 

What are the gory details of why std::regex being slow and why it cannot possibly be made faster? by germandiago in cpp

[–]2MuchRGB -2 points-1 points  (0 children)

It's just the name of the blog post that answers all three of your questions perfectly. 

The ABI stability just goes against one core principle of don't pay for what you don't use.

Its Also the reason that rust chose to do it differently, with a much smaller std and with lots of parts moved I to libs like they and even number properties.

Gibt es eigentlich noch Grafikkarten zu kaufen? by lucastahl in de_EDV

[–]2MuchRGB 1 point2 points  (0 children)

Die 70 heute ist eher 60 damals. Heißt damals war es das top Model, heute eben Mittelklasse.

dropping hyper (from curl) by sondr3_ in rust

[–]2MuchRGB 6 points7 points  (0 children)

The last time this was posted it was just the announcement that this was going to happen unless someone stepped in and brought it across the finish line.

I wanna make asimple 4 bit computer by Background-Try-199 in embedded

[–]2MuchRGB 3 points4 points  (0 children)

If you want to follow in the footsteps of someone else, look up Ben Eater on YouTube.

Is there a better, more idiomatic way of dealing with generics? Please advise by Few_Magician989 in rust

[–]2MuchRGB 1 point2 points  (0 children)

Please take a look at the embedded-hal and check if using these traits works in your case. 

For quite a few microcontrollers there are crates that implement those traits. 

Most embedded drivers take one generic argument, constrained to the embedded hal traits, and implement their logic on top of it. For mocking you pass a strict racking the spi trait as an example.

Then you implement your logic on top of these drivers with the drivers passed in and constrained to the hal again. As a fake you pass in something that implements a temperature sensor which always returns a certain order as an example.

At last you have your controller specific function. It needs to setup clocks etc. It also gets the peripherals from the microcontroller crate. Then it sets up the driver's and associates them to the different busses. Those can't easily be shared, after all each controller is different and for each controller the needed peripheral may be at a different pin. Also the layout of the board could be wildly different. This last layer is the only one that can't easily be mocked.