US companies outsourcing all of their manufacturing to countries with cheaper labor and laxer environmental & labor laws led to this. What did those titans of industry think would happen down the road? "I'll be retired." Corporations have way too much power in the US, and that has considerably weakened it.
They definitely play both sides to spread chaos. That's been extremely effective for them in reducing American power and influence. Getting their messaging out there is also a goal.
To be strict with taste and tradition, yes. However taste and texture can be approached with other ingredients to recreate the egg composition : after all cooking (and especially baking) is a chemist soup.
- protein: tofu, gluten, plants protein extract, lentils, chickpeas, beans, chia seeds, mixed squash seeds...
- lipid: various vegetable oils
- sulphurous aroma: Kala namak salt, also very popular for vegan scrambled eggs
Depending on the selection, other ingredients might be adjusted. EG: lentils contains carbohydrate to if you use them for protein, use less floor and no corn starch.
The tool OP developed is precisely perfect for this king of calcul. However sometimes alternatives aren't based on the exact micro and macro reproduction but on the final result: banana is great for vegan pancakes but lacks protein. It's probably it's starch and fibers that help getting the texture right.
>It doesn’t matter that the language you use is memory-safe, if you didn’t design for correctness or have no process that will eventually lead you to fixing all bugs.
It's also worth noting that they linked a post about how memory safety is literally a matter of life and death, so it seems like their point is that memory safety is one class of bug, and a compiler guarantee about it doesn't equate to a guarantee of correct, bugless, unexploitable code.
Like, the linked author brought up that Khashoggi's wife's phone was hacked. Maybe that was due to a memory bug or some other kind of bug. Maybe the next journalist who gets hacked is a victim of a memory bug or some other kind of bug. But that linked post didn't take a holistic view of correctness, but went straight to, "Rust is safe. Rust saves lives." There's a logical error there that's being pointed out.
If you really want to save lives, you need to eliminate exploits. Not just do a victory lap because your compiler ostensibly eliminates one class of them. The compiler doesn't catch all bugs. The compiler isn't the only tool for catching bugs.
That's my reading of it, anyway. I think he has a point, and the Rust people do as well. I think it's wrong to portray him as bitter.
That is correct, this blog post is about understanding the priority of various subgoals and the ultimate goal (creating useful software). Memory-safety is important but overfitting on that subgoal, as I believe the memory-safety blog post is doing, won't make you create better software.
If Rust helps you get all the way to correctness, then great, but that blog post was insane.
> The compiler doesn't catch all bugs. The compiler isn't the only tool for catching bugs.
I acknowledged that in my prior comment. This person is letting perfect be the enemy of good, and I guarantee you that they aren't running their binaries through Valgrind and Ghidra to check the runtime safety after it's built.
Exploits like Heartbleed get shipped because people abdicate their responsibility to write safe software. Shackling developers to dynamic analysis tools is not any better of a solution than using a memory-safe language to start. Rust is shaving a calf to avoid the whole yak.
Almost all of my tinkering is “download this thing, cache it (because it’s huge), run a program or a series of programs on it, and package the output up somewhere.” When I’m writing the thing that does the work I’m not tinkering any more..
I've been places, from embedded bare metal to ML AI, and that "embedded bare metal" end is the one place I don't use Python directly in. Embedded bare metal is just ruled by C forever.
Bit of a shame, because C is kind of bad at its job, but nothing else has the "compatible with everything" badge of honor.
The tooling around embedded devices though? Python.
When I want to tinker it’s usually because I want to make something faster than anyone else has done. Does that help illustrate why some might prefer to tinker in Zig, and why your definition of tinker seems a little narrow?
Most of the time "make something faster than anyone else has done" is just not worth doing? Good enough is good enough. Unless it's some super hot path and it's the speed that's the main goal, nothing else. Which is rarely the case.
If you only ever think of tinkering for the purpose of execution speed ninjutsu, isn't it your definition of tinkering that's far too narrow?
No, I’m saying that it’s how I like to tinker. Others have their own ways of tinkering that are just as valid!
I personally think the optimization challenge is fun. I like digging in to low level stuff, reviewing the assembly dumps and processor pipeline architectures. I fail or give up most of the time, but I enjoy learning in the process.
I’m just trying to show how Zig fits my tinkering well, since you said you can’t see how Zig would ever be a good fit for tinkering. I’m not saying it’s a good fit for all forms of tinkering.
>an iPhone could not afford to let every installed application maintain its own background poll against a remote server. The proposal...a single persistent TLS connection from each device to Apple, over which any registered third party could deliver alerts.
I thought apps were sending notifications locally in the device. Like, if a messaging app receives a message, there's a network call for that. Then if the messaging app wants to tell the user they received a message, it can just hit a local API for that, right?
Is the pattern actually that the app makes another network call to the notification service to register the notification, which makes another network call to the device to deliver it?
yeah this is what author hints at with "Push as a battery problem". Apps are limited by default in what they can do in the background due to this, so most apps are in a suspended state not making network calls when you are not using them. To avoid the app having to keep running this stuff is delegated to OS which tells the app, "hey I have a push for you wake up and handle it!" You can send pushes locally but because of the background limitation it is not practical for unpredictable events like messages coming in.
Not sure i understand. Sure it doesn’t require it but Apple doesn’t trust you to handle it because you’ll probably drain the battery or spam the user or whatever, that is Apple MO, putting themselves in the middle so they can control the experience.
The single persistent connection is just to receive pushes, there is still some daemon controlled by apple in charged of dispatching to correct app.
Seems like you're claiming Ukraine's 2014 "Revolution of Dignity" and subsequent democratic elections were something the USA did. That's a controversial claim, and one that ignores the recorded actions and sentiments of the Ukrainian people. It's also unrealistic and gives the US too much credit.
The US does have their hands in pies across the globe, but that was a large scale uprising of Ukrainian people. No outside force can make something like that happen if the people aren't already aligned.
The simpler explanation is the Ukrainian people wanted to be closer to the EU, and didn't like Yanukovych's authoritarian tendencies. I wouldn't be surprised if some propaganda blamed it on the US, but it doesn't make sense. If the US wanted to do regime change and the public wasn't behind it, it would look very different. There are unfortunately many examples.
Epub would also be a great target.
reply