Zagitta

I hope EU comes down HARD on them for trying to pull this shit

Torrenting is on the rise again since the golden era of streaming where Netflix gave you access to everything has ended.

https://www.cnet.com/tech/services-and-software/digital-cont...

Have you not heard of remote-id?

It's a legal requirement for drones above 250g to broadcast not only their position but also the position of the operator and their identification number.

I think you missed the point of Jon's talk, it was in large to highlight some deficiencies that currently exist in the language but are actively being worked on.

As he mentioned the current situation with return position impl trait + 'a was surprising even to some of the core rustc developers so it's not like they intended for it to be like that.

You can't expect open source developers to be omniscient and know you want to use a specific feature if you don't communicate that to them. Would you rather have them add telemetry?

RAM was rarely about what you can do today but rather how long your device will last.

Soldered on RAM and expensive upgrades are defacto planned obsolescence.

The cat is already out of the bag.

There's no meaningful way to limit access to any of this when it's purely software based and the hardware required to run it are commodities.

It's nothing like chemical weapons were the reagents can be controlled as they're hard to come by or synthesise in a amateur lab.

So your argument is that it's better for your device to prevent you from using it out of the box rather than games which you fairly easily can opt out of by just not installing them?

"Programming in Rust is like being in an emotionally abusive relationship. Rust screams at you all day, every day, often about things that you would have considered perfectly normal in another life. Eventually, you get used to the tantrums. They become routine. You learn to walk the tightrope to avoid triggering the compiler’s temper. And just like in real life, those behavior changes stick with you forever."

This is a pretty negative and unfortunate take on rust that I cannot recognize after having spent the past 2 years professionally writing backend rust. I did write c++ before that so it's likely that it takes some experience with the pain of an unhelpful (and in some cases downright hostile) to fully understand and appreciate the so called "yelling" rust does.

From my perspective every lifetime complaint the compiler has is a deeply appreciated hint that not only saves you countless hours of debugging down the line but also makes me feel confident/safe in the code which you never could achieve in a c++ codebase without making defensive copies everywhere.

Being able to lend/borrow data without fear truely is rust's greatest strength and something people coming from GC languages have a hard time appreciating.

Imagine if car repairs worked the same. Oh you damaged the front bumper on the curb? Sorry we're gonna have to do a full engine replacement as the chassis might have flexed and cracked the engine block despite it running perfectly fine.

It's frankly ridiculous what people consider acceptable behavior from apple.

Apple lost that "shouldn't have to" when they decided to parent society by using theft as an excuse to serialize parts and prevent third party repairs.

Except if the environmental cost wasn't externalized it would be unfeasible to not do component level repair at scale.

Another aspect to this is that it board repairs could be made significantly easier if companies bothered designing boards with proper test points and expected values documented in a diagnostics manual. Just take a look at how old school oscilloscopes and other test equipment was designed with not only full schematics but well defined diagnosis procedures.

Take a look at this and you'll see it actually just randomly blows up :^) https://kristerw.blogspot.com/2017/09/why-undefined-behavior...

Google has basically thrown the towel in the ring when it comes to C++ considering they're building a replacement like Carbon and also using rust in and more places so they're likely pivoting to those two instead

It's not that hard to write "we keep none of your personal data" as your privacy policy, if you want to track me on a personal blog you better get your legal story straight...

Sane defaults tend to evolve over time with the hardware architectures so it's probably not a very good idea to encode these into the API.

A lot of what you request can be achieved by using Vulkan wrappers that simplifies these things without making the driver API more magic/implicit and regress back to the dx9/openGL style API's that mantle/vulkan/dx12 was made in opposition of.

Rust is rapidly picking up steam in the embedded sphere :-)

Unfortunately it's an industry with a lot of stubborn old people so I don't see any major changes happening until they've retired but I'm willing to bet that async is going to revolutionize embedded development. Being able to await interrupts and doing efficient cooperative scheduling while writing straight forward code is a massive QoL improvement which is what embassy is enabling: https://embassy.dev/

Perhaps they're mocked and avoided in your sphere but there's certainly plenty of consumer products using them. Both sonoff and Tuya produce enormous amounts of products with them.

What exactly is your problem with them? The chips are fairly capable and the newest ones have transitioned to RiscV in case you're unaware. Sure I wouldn't use them for anything serious realtime but that rarely requires wifi/ble anyway so not sure why you'd pick an ESP to begin with for that :)

As others have noted this sounds like a contention issue that you should fix by not allocating in your hot path if at all possible. The easiest fix would probably be to try to switch out your global allocator for something like https://github.com/gnzlbg/jemallocator and see if that doesn't give you a nice performance boost.

As technically interesting this is, it's certainly going to be surefire way to kill your compile time :-)

How many code bases have you actually worked on? I can tell you it's very common in constructor initializer-lists to the point that both the mozilla and webkit styles of clang-format does it.

I don't understand your argument, can a western salary better absorb these taxes? Sure but how does imposing CO2 tax "protect their lifestyles"? The tax is based on how much CO2 you produce so rich people who consume more also end up paying more. Furthermore the tax aligns incentives to actually decrease CO2 production by finding greener alternatives. Last but not least pointing fingers at each other for past transgressions does very little to actually help the do or die situation that climate change is rapidly turning into.

Lower supply means higher prices which increases the attractiveness of renewable energy?

One could say they miss-calculated :^)

Is there a term for that? I was thinking "hostile obsolescence" or "active obsolescence".

<rant> In my opinion Arduino and "pro" does not belong in the same sentence.

I work as an embedded software engineer who's tasked with ripping all the terrible arduino code out of a fairly large codebase where I work and the arduino core libraries are the lowest quality code I've ever had the displeasure of working with.

It's full of awful decisions everywhere in the arduino core libraries such as defining min and max macros when they're writing C++ code which in turn results in STL includes blowing up if you attempt to use something simple and safe as std::array.

I could go on for days about all the terrible decisions that reeks to high heavens of always taking the path of least resistance... </rant>

The Cura slicer from Ultimaker has a setting to enable that kind ironing on top surfaces although just with the regular nozzle but it works surprisingly well!

It says "IO Voltages: Both 3.3 V or 5 V supported" under the features tab.

You can't, you're the product not the user unfortunately.

Do you have an appropiate charger? I was researching usb-c charging for my XPS 13 (9350) and apparently the charging standard allows for different voltages so it's not all 5V as you'd expect from good old usb and therefore requires a specific charger capable of delivering the right voltage (19V in my case from what I could gather).