Accumulate all the component nutrients. And average this over a day.
Now when I search for lotus seeds, I want to see how much nutrition they have relative to this diet. You could argue that RDA essentially serves a similar purpose and that might not be too far off but what I'm interested in knowing is how much diversity a food item is adding for me.
“This research does not suggest that any individual cited in this report deliberately concealed their commercial affiliations from journalists. Rather, it highlights a recurring failure by news organisations to disclose potentially relevant industry interests when presenting former senior military figures as independent expert commentators on defence, conflict, and national security issues.”
“Of course, holding private-sector roles after military service is both lawful and commonplace. This is not the point of this report. Rather, the concern highlighted here is about the UK’s media.”
“The findings presented here do not argue that the individuals identified are acting improperly, nor that their analyses lack merit, however we assert that the public has a right to full and relevant information when evaluating expert commentary, particularly where it involves lives, public expenditure, and international security.”
“It is important to note that this report does not allege wrongdoing on the part of the individuals identified, nor on the part of the publications presented within the pages of this report.”
Practically every third paragraph reiterates this.
They are anticipating a flood of complaints from various well-connected groups and individuals that it's an unfair hit piece. They want to be able to point to all the "Hey, we didn't say this ACTUALLY MATTERED" disclaimers they front-loaded it with.
Except they said that it actually matter. The reason they didn't said that all those people with a potential conflict of interest lied is that it's not necessarily true. After all the article didn't reveal some secret conspiracy, it higlited the use of not disclosing some public, easily accessible informations by some media outlets, which are the ones to blame
Source? The UK has been extremely vocal about defending Ukraine's sovereign rights and has spent a lot of money supplying it with defensive equipment.
Russia despises the UK. The UK does have a few right wing pro Russia people, just like the US does. Just like most of Europe does. It is the fringe view and not reflected in state policy.
You are of course correct. I completely forgot about him. Jeremy Corbyn could probably be lumped in as an elected official. There is a pretty virulent form of left wing in the UK who argue that Russia is good because it's imperialism is somehow justified (I think it boils down to anti-NATO sentiment.)
> obvious bias
The rise of a few right parties with sympathy to Russia was on my mind. Although that talk has seemed to have quieted with more national issues taking up breath.
If supply-chain security is a concern yarn is the worst js package manager you can pick. It comes far down their priority list, below "just make things work without need for user input". Whatever you thought you configured will simply be ignored many times and that's considered a feature.
Go look in that projects issue tracker and commit log for changes to relevant configuration and you will know what I mean.
I can tell you a bit about my own experience, as I've I used Rust for two years, but have now transitioned to Zig. I started working on a modular synthesis engine, and I realized that Javascript wouldn't give me the granular control I needed. So I decided to use Rust. This was my first foray into low level programming, so learning Rust first was great because I internalized their ownership rules. However, I started to realize that Rust was doing quite a bit of stuff behind my back, like freeing objects when dropped, or making allocations when I inserted an item. This is a big no-no for realtime programming, and Rust didn't help me understand what was happening. It was then that I read matklad's blog post on rust hard mode, https://matklad.github.io/2022/10/06/hard-mode-rust.html. I looked at some of his other blog posts too, and saw Zig. So Zig had been in the back of my mind for a while, when I decided to port a Tcl interpreter to Zig. I've been about 7 months in now making my own interpreter, and it's been a delightful language. Yes, I've had my share of memory leaks and double frees, but the debugging trace lets me capture a stack track at each reference count increment and decrement, so I'm able to hunt them down pretty well. I'm also hyper aware of memory layout and allocation failure, because allocation is fallible in Zig. The error union handling makes it pretty easy to propagate OOM though, so it's not hard to make code that's resilient to OOM. If I had tried to make this in Rust, I would have been fighting the standard library, ecosystem, and borrow checker constantly, because high level programming languages have non-trivial ownership semantics, and a lot of optimizations like epoch based variable caching just don't play nicely with references as trees.
Because it isn't memory safe. I honestly think it's beyond the point of "irresponsible" and well into "negligence" that we're still developing unsafe technologies - people are being harmed by this choice. It's one thing when you have to target specific platforms and maybe Rust wasn't an option or whatever, but the reasons to choose unsafe languages at this point are vanishingly small.
Zig is very cool, I love many aspects of it. I'll never touch it, I'll always advocate against it tbh. I'd probably advocate that software written in languages like Zig be flagged for FEDRAMP and other environments since devs seem to not care unless they're legally barred from making these sorts of choices.
I completely agree. Zig has a nicer DX no doubt - no fighting the borrow checker etc. But if you are are writing software for other people they don't care about how nice your developer experience is, they only want the software to work correctly - and how can you guarantee that the software you wrote does what you expect it to do if it's not memory safe?
It doesn’t fully guarantee that. But it guarantees you don’t have a huge class of bugs. And it makes concurrency a lot easier to reason about.
No system will likely ever guarantee that software does what you expect. That runs into the halting problem, and practically runs into a verbosity problem. But that doesn’t mean systems that give scoped guarantees aren’t amazing for building (and iterating on) reliable software.
I don't think Rust users are relevant here. It primarily comes down to personal preferences, and since Zig and Rust are so different, some will be drawn to Rust and others to Zig. If you really like a language and it suits your needs, be it Rust or any other, there's no need to look to switch. I think that the audience Zig is aimed at is low-level programmers who haven't taken a liking to Rust, which is the majority of them. Rust isn't very popular among experienced low-level programmers (certainly for a language that old), and I guess Zig is hoping to be more to their liking.
For example, I find Rust to be far too similar to C++, and it shares most of the problems I have with C++ only with much lower adoption. I'm not saying I'm ready to make the switch, but at least Zig offers a different approach that's intriguing to me.
Try it if you want full control over every memory and IO operation and "drop". If you hit "goto-definition", you eventually get to see the OS switch statements and syscalls. There's not much magic.
Do not try it if you are scared of memory management and memory leaks.
Not working within the bounds of lifetimes, and more ecosystem that doesn't live in the world of lifetimes, gives Zig some of the wonderful dev ergonomics of Rust while making it easier to prototype.
For small, short game dev, or even smaller embedded projects, this ends up being a wonderful way to live as often times you're trying to eke out performance in ways that would require breaking out of whatever type abstractions or using unsafe.
For long-lived systems, for systems that need to have lots of people with various skill levels work on them, for a mature ecosystem, for a language/standard library with stability... You probably don't want to pick Zig right now. Some of these points will change over time with Zig becoming more mature, some won't. Zig will always be super cool to build things in.
As far as most low-level programmers not liking Rust like some other commenters say, lol, lmao even.
I'm okay with smileys, but Unicode wasn't the right standard to deal with it. Unicode maybe wasn't the right standard to deal with anything.
At least nothing is wiggling. Of those Unicode points which are graphical, at least all of them can still be printed on paper and won't require a screen. I wonder how long that invariant lasts.
Google/Apple needed it to fill the moat for Japanese phone market - for Google it was because Japanese carriers were stripping emoji from outgoing emails, and for Apple it was because iPhone as a real phone and not an Internet-connected pocket PC with voice call had to support the SoftBank emoji set.
And yeah, :slack-style-emoji-notation: is superior. It was just a historical necessity for Google/Apple.
Personally I think the whole emoji thing is a triumph of Unicode. Being able to convey more subtext through emoji makes communication so much easier especially across language boundaries.
reply