IMO, this screams the need for both tort reforms and something like a nationalized representation system.
Perhaps something like a standard set of filings for a given case. Maybe automated rulings on less consequential motions. Maybe some sort of hard limits on the amount of billable hours a law-firm can work on a case. Anti-slapp laws for sure.
Like, for example, maybe we allow a total of 100 billable hours worked, with an additional 10 billable hours allowed per appeal. The goal there being that you force lawyers and lawfirms to actually focus on the most important aspects of a case and not waste everyone's time and money filling motions for stuff you are allowed to get, but ultimately has 1% impact on the case. Perhaps you could even carve out a "if both sides agree, then you can extend the billable hours". You could also have penalties for a side that doesn't respond. For example, if you depose them and they fail to follow the orders then they lose billable hours while you get them credited back.
The main goal here being avoiding both wasting a bunch of court time on a case but also stopping a rich person that can afford an army of lawyers from using that advantage to drive their opponent bankrupt with a sea of minor motions.
That $100k is also on the cheap side. If the other side has a lawyer and a lot of money to burn, they can easily hike that way up. Filing a billion motions that your lawyer has to respond to, deposing everyone you've ever met, going after every document you've ever looked at. The more money someone has, the easier it is to make you spend more money, even if you are right.
Right. My case was a very simple contract dispute with very little discovery and only a couple of people to depose, so I was lucky there. And the other side did have more money than me, but not so much that they could burn several hundred K on it without feeling it.
$50k is going to be on the cheap side for any case that ultimately involves the court. Anytime a case goes to trial, you can easily be looking at $1M+.
There's a reason companies keep lawyers on staff. It's a whole lot cheaper to give a lawyer an annual salary than it is to hire out a lawfirm as the standard rates for law-firms are insanely high. On the low end, $150/hour. On the high end, $400. With things like 15 minute minimums (so that one draft response ends up costing $100).
Take a deposition for 3 hours, with 2 lawyers, that'll be $2400.
It still biodegrades within the pit. In fact, that's actually a problem because it can generate fire starting temperatures! (Crazy I know) It's also a problem because a part of biodegrading is producing CO2 and CH4.
But I generally agree. The big issue here is we as a society have moved away from biodegradable packing and distribution. I get it, plastic prevents waste and mold. That's why we use it. It's also dirt cheap. It's a byproduct of oil refining (literally cheaper than water).
The ultimate solution to the plastic problem is making plastic more expensive, and the way to tackle that is by reducing oil consumption. Fortunately, that's sort of just naturally happening.
I'd be interested in knowing what the CO2 emissions were from these. You still need to feed the yeast, so you'll have the CO2 emissions involved in growing a crop associated with this. And if you look at the chart in the OP, you'll see that grain production is about half the CO2 emissions of milk. That's likely part of the milk CO2 production accounting.
In addition, you'll need more cleaning/sterilization/mixing. I'd guess that it's lower, but I wonder how much lower.
And then there's the other products that generally get thrown into the mix to make up for things like missing fats. For example, a vegan cheese based on bacteria will often include coconut oil, probably to get the same fat profile.
Whey is an interesting product in general because it's a waste product of cheese making.
Feed efficiency is critical when doing these calculations as cows inherently need energy to survive not just produce milk. As such even if you use the same crop two different sources of protein can have wildly different levels of CO2 emissions embedded in their creation. https://en.wikipedia.org/wiki/Feed_conversion_ratio
I think it is likely more efficient. That said, cows do have the advantage that the food they consume needs little to no processing in order to produce milk. The yeast needs pretty precise processing of the incoming mash both to make sure a wild yeast strain doesn't make it's way in, and to make sure the yeast ultimately produces the right proteins.
You can't just throw in grass clippings into a vat and get whey. You can throw grass clippings into a cow to get milk (though, TBF, I dislike grassy milk).
I agree it’s likely to be more labor intensive per lb of feedstock, but only 21% of calories in milk are protein and overall milk has ~10% of the initial energy. So you’re looking at ~2% of the energy from these crops ending up as milk protein.
That’s a lot of room for improvement which then means far less labor on growing crops.
Cows are pretty terrible because of methane from their burps (not farts; burps). People are working on that but it's still real. A 50% drop would be very significant
Ok, so a lot of this boils down to the fact that this sort of software really wants to be running on linux. For both windows and mac, the only way to (really) do that is creating a VM.
It seems to me that the main issue here is painful disconnects between the VM and the host system. The kernel in the VM wants to manage memory and disk usage and that management ultimately means the host needs to grant the guest OS large blocks of disk and memory.
Is anyone thinking about or working on narrowing that requirement? Like, I may want the 99% of what a VM does, but I really want my host system to ultimately manage both memory and disk. I'd love it if in the linux VM I had a bridge for file IO which interacted directly with the host file system and a bridge in the memory management system which ultimately called the host system's memory allocation API directly and disabled the kernels memory management system.
containers and cgroups are basically how linux does this. But that's a pretty big surface area that I doubt any non-linux system could adopt.
Given that Claude Code runs without issues on macOS, I'd guess that it's more about sandboxing shell sessions (i.e. not macOS applications or single processes, for which solutions exist).
Unfortunately, unlike Linux, macOS doesn't have a great out-of-the-box story there; even Apple's first-party OCI runtime is based on per-container Linux VMs.
The upgrade to the native installer gave me some issues, I had Claude fail to return any responses and continuously eat memory until my computer crashed! The only fix I could figure out is nuking my entire .claude dir, losing all my history etc with it
It’s a solved problem in the VM world too. Memory ballooning is a technique where a driver inside the VM kernel cooperates with the hypervisor to return memory back to the host by appearing to consume the memory from the VM. And disk access is even easier; just present a network filesystem to the VM.
The network file system to host is usually pretty slow no? That was my impression.
As for memory ballooning, the main issue with it is that it (generally) only gets triggered when the host runs out of memory.
For a host which is only running VMs, this is fine. But for the typical consumer host it becomes cumbersome as you still need to give the VM a giant memory block and hope that your VM of choice is good enough to free on time. It's also uncoordinated. When swapping needs to happen, if the VM was using the host for allocation the host could much more efficiently decide what needs to go into swap.
And if the host was in charge of both the memory and file system, then things like a system cache could be done more efficiently on top of all that.
> The network file system to host is usually pretty slow no? That was my impression.
NFS doesn't have to be slow. If you avoid traversing the TCP/IP stack, performance is fine. Linux guests can use vsock to communicate with the hypervisor directly, and macOS hosts can use the Virtualization framework to map a guest vsock to a host UNIX socket.
The web has a secure storage standard and OAuth + MFA is just as secure as anything your bank could cook up in an app. In fact, I'd be shocked if banks did a better job of security in their apps vs what browsers and standard auth flows provide.
Banks just like selling the idea that "if it's encrypted, it's secure". But trust me when I say this, bank security across the board absolutely sucks. The company I work with does financial data ingest and... yeah... There's more than a few institutions where we had to pull teeth to get them to send stuff through an encrypted transport (SFTP, for example, they want to just use FTP).
The original Google Nexus program showed that there is a market for more open phones and platforms.
I don't disagree with you that in order to sell, these devices need to be somewhat appealing to more than just devs. However, I will say that the dev market isn't as small as it once was. A decent phone with an open platform would be something a lot of devs would likely prioritize buying. It won't be the next Iphone, but it will be a pretty dedicated market segment.
Framework is a good example of that. A laptop business that stays afloat mostly because there is a desire for repairable long lasting products, even if it's a bit niche.
Given a lot of phone manufacturers are now trying bizarre edges to get ahead (like foldable... who wants that?) it seems like a good rarely taken route.
Agree with you on the foldables. God, no one wants that. That's why they have to pitch it as some luxury product the masses can't afford. I hate those creases too. No one can convince me those things are durable...no matter how many marketing videos they make.
> Agree with you on the foldables. God, no one wants that.
I think there are a lot of people who would love to have a smaller form-factor for when the phone is in their pocket, with a large screen for when it's being used. The current state-of-the-art might not be very good for foldable phones, but the demand is there, and that's what drives innovation.
Well...not to be disagreeable, I've had the Flip 4 and now, since it came out, a Flip 5. Both are excellent products. IF you keep a semi-fresh screen protector film on them, the screen will not break/crack in the flex/fold area. I didn't try them for luxury, I tried them because they fit comfortably in my pants pocket.
I guess I could see it. I'm guessing you tend to wear pants with shallow pockets correct? It is a problem my wife runs into that woman's pants have next to no pockets. She ends up needing to store her phone elsewhere as a result.
Yes, on the shallow pockets. Also, I had the habit of putting my non-folding phone down when sitting, and then leaving it behind.(!) I would sit it down because it wouldn't fit into my pocket and I didn't always carry a hip pack. Except for the stupid high prices of the "fold" phones, they would put me right back in the non pocket fitting situation. (Although the extra screen space would be sweet!)
Foldables are a growing market in Asia, where they are more widely available. They are quickly becoming a new status symbol, displacing Apple. Especially in China where the local phone manufacturers are now completely independent and free to experiment.
Apple somehow completely missed the plot (yet again) despite being having the largest tablet marketshare. Google, to their credit, is now pushing developers towards supporting dynamic screen dimensions.
I don't even use an Apple. I travel a lot within Asia, so, I'm aware of the foldables situation in Asia. But, again, only to prove my point - not everyone runs around with those. You usually see the wealthy and some rich kids carry them around.
It's pretty strange that the only subject you seem to have expertise in is e/os. Over a year and that's the only thing you've felt comfortable in discussing?
and so what? should I ask for permission to discuss something? it's crazy how omniscient people are aggressive on the internet. Is that your normal behaviour IRL??
Good stuff! This feels very human. How do you feel about Murena? I feel like like they're very much a "Next Gen" privacy tech company. I've also heard they're crowd-funding!?
I think this is behavior that should be encouraged online. Staying quiet and letting the experts talk to increase the signal to noise ratio is a GOOD thing. OP has hands on experience with something that is at least for now quite niche.
I used to only really speak about node.js topics because that was what I had real fighting experience with, at a scale beyond what most webdevs had ever seen. Those were also my most upvoted posts by far.
I get what you are saying, and if that's what the OP was doing I'd somewhat agree with you.
However, if you haven't already, I'd encourage you to read over their past comments. They all read almost identical to the start of this thread. Before this post they had something like 3 other comments on HN and they were all about how great /e/OS is. All of them have a blurb about the privacy focus of /e/OS. They all read like copy from marketing.
That is bizarre commenting behavior for a niche OS. And these weren't comments about using /e/OS, but rather comments speaking positively about using it.
Your posts on node.js, I assume, weren't all "Node.js is the greatest programming environment I've ever used. It's so smooth and fast." Instead, I'd wager your highly upvoted comments contained useful information about using node.js.
I'd also say, that there are people that work for various software tech companies who post here. The best comments I see almost always start with "Full disclosure, I work for X". Those are far better received.
Perhaps something like a standard set of filings for a given case. Maybe automated rulings on less consequential motions. Maybe some sort of hard limits on the amount of billable hours a law-firm can work on a case. Anti-slapp laws for sure.
Like, for example, maybe we allow a total of 100 billable hours worked, with an additional 10 billable hours allowed per appeal. The goal there being that you force lawyers and lawfirms to actually focus on the most important aspects of a case and not waste everyone's time and money filling motions for stuff you are allowed to get, but ultimately has 1% impact on the case. Perhaps you could even carve out a "if both sides agree, then you can extend the billable hours". You could also have penalties for a side that doesn't respond. For example, if you depose them and they fail to follow the orders then they lose billable hours while you get them credited back.
The main goal here being avoiding both wasting a bunch of court time on a case but also stopping a rich person that can afford an army of lawyers from using that advantage to drive their opponent bankrupt with a sea of minor motions.
reply