Given that Google has said they'll be delaying source code release for Android to every X months intervals (iirc), how is GrapheneOS planning to handle security updates? Will they just be Google's binary blobs?
Isn't that about feature releases? My understanding was that security patches are separate from this
edit: looked up the announcement https://www.androidauthority.com/google-android-development-... but it doesn't even mention the word security. I don't know enough about the manufacturer side of things to say whether this means there's also no security updates while they work on new features
The controversy isn't about defending one's country, it's about you and the parent comment author assuming what this is all about without reading the article.
The core of the issue about autonomous use of AI in mass surveillance of Americans and autonomous use of AI in automated weapons that make kill decisions. Anthropic is perfectly fine with working with the War Department and "defending one's nation".
But they are not okay with their AI being used to make a mockery of the 4th amendment and making automated kill/no-kill decisions about actual human lives.
Pardon my ignorance, but doesn't a byte-by-byte output recreation of the C++ code in Rust defeat the whole purpose of using Rust? For one, would it be idiomatic Rust anymore? Also, if there's a (non-memory related) vulnerability in the C++ code, would it be possible for that to be introduced in Rust too?
The impression I get from the article is not that the compiled code of each implementation produces the same object code, but that when the implementations are run with the same inputs, they produce exactly the same output — that is, the same JS VM bytecode.
If they had developed a technique to get a modern C++ compiler and rustc to generate exactly the same output for any program (even a trivial one) I think that would be huge news and I would love to see all the linker hacking that would involve.
I've looked at the code from the PR. It seems to use safe types and standard idioms like pattern matching, so at least at first glance it looks like Rust.
It could have been worse. C++ code naively converted line-by-line to Rust typically results in weird and unsafe Rust, but in this case it seems they've only been strict about the results being the same, not the structure of the implementation.
Rewrites have a very high risk of introducing regressions. Trying to fix bugs while rewriting will only make things harder, because instead of simply comparing outputs exactly, you'll have to judge which output is the right one. If you let the behavior significantly diverge during the rewrite, you'll just have two differently buggy codebases and no reference to follow.
It's much easier to make a bug-for-bug compatible copy, and fix bugs later.
Once you get a byte-by-byte duplicate, you can start refactoring into idiomatic Rust. Convert pointers to references, rip out unsafe blocks, and let Clippy go ham.
1) Is it possible to start off with plain Postgres and add pgdog without scheduled downtime down the road when scaling via sharding becomes necessary?
2) How are schema updates handled when using physical multi-tenancy? Does pgdog just loop over all the databases that it knows about and issues the update schema command to each?
1. Yup, we support online resharding, so you don't need to deploy this until you have to.
2. That's right, we broadcast the DDL to all shards in the configuration. If two-phase commit [1] is enabled, you have a strong guarantee that this operation will be atomic. The broadcast is done in parallel, so this is fast.
I'm currently using Ghostty with Zellij, and there has been a constant tension w.r.t whether I should use a zellij feature or a Ghostty one (i.e, tabs/panes/etc) when they provide the same thing.
I've come to the conclusion to rely more on Zellij because I can SSH into my desktop from my laptop remotely to continue my dev session exactly where I left off.
So, these days I don't even use "native" terminal tabs anymore.
How are situations like lack of liquidity to pay the taxes handled?
i.e, As an employee you get stock options, which you exercise when you leave the startup. Then long before the company has a liquidity event the FMV shoots up because the business is doing well. How do you as a wage worker pay the taxes on your paper riches without a way to sell your shares?
I know several people that got cleaned out in IPOs partially due to how taxes work on no-liquidity (lockout) periods. If you IPO'd at $10 ($3 goes to the tax man), and when you can finally sell it 6mo later and stock is only worth about $3, the IRS makes more money than you.
Checkout what happened at Uber [0].
My cousin at Aurora borrowed money for his tax bill on IPO. I don't know the final numbers, but I hope he at least broke even.
Isn't this already a problem in many situations? If you exercise your options when you quit, pay only a very small strike price, but acquire private shares with a much larger fair market value, in the US at least you'd owe the IRS a lot of money but have no liquidity to pay it. Though this new tax would make that a yearly problem instead of just a problem when you exercise. (and mean that early exercise doesn't let you avoid it)
I think in that case, you, the hypothetical wage worker, got hoodwinked pretty effectively by the beancounters when they were able to get away with compensating you in contracts that are apparently worthless to you.
Do you think about the things you say, or is it just reflex?
Everyone working for a startup knows it may be 5 years to a liquidity event. We're all big boys, we work on uncertainty and expectation. If the government changes the rules halfway through, it's pretty brain-damaged to blame the beancounters for hoodwinking the employees, and not using their magic oracular powers to predict how the laws would change under their feet.
Do you not factor in the risk of government tax policy changing when you make large financial decisions? I certainly do (for instance, when I choose between traditional and Roth contributions for my 401k, or when I was purchasing a new car a few years back), and it doesn't strike me as a particularly difficult thing to do; I think I may have even done so the last time I was hired for a job which offered options (although that was quite a while ago and my memory is hazy).
More to the point, however, I think if 2 years is insufficient notice to get your tax situation in order w/r/t employee stock options, either your finances are enough of a mess, or you're frankly just so stupid, that you would not be helped much more with 5 years, or even 10 years, of advance notice. And at that point, you (the poster, not the hypothetical hapless employee) are just arguing that the government should never change its tax policy, which is just absurd.
> I don't see the U.S rushing to adopt either renewables or nuclear. We're just increasing our fossil fuel burning (natural gas)
This is wrong. Natural gas is falling from 42% of U.S. electricity generation in '23 and '24 to 40% in '25E and '26E [1]. Renewables, meanwhile, keep marching from 23% ('24) to 24% ('25E) and 26% ('26E). (Nuclear falls from 19% ('24) to 18% ('25E and '26E).
That's capacity, not generation. Getting through the accounting tricks that make renewables seem viable is a challenge. 1 watt of nuclear capacity is worth 1.5 watts of FF and 9 watts of renewables. That's because the amount of power from each type of plant is very different due to downtimes of generation. Nuclear runs all the time and refuels for a couple of days every 18 months (depending on the reactor). FF plants run most of the time by require 10x more maintenance downtime. Renewables only make power about 10% of the time. That's how they skew the numbers to make renewables seem viable when they produce a shockingly low amount of actual power. Oh, and if you use renewables for baseload you have to keep a spinning reserve which means they actually increase (not decrease) the amount of CO2 emitted per watt generated.
Irrelevant. The question is what we're investing in. "The U.S" is "rushing to adopt...renewables."
> FF plants run most of the time
"CCGT capacity factor rose from 40% in 2008 to 57% in 2022" [1]. "In the western United States," meanwhile "the capacity value of PV plants can be in the range of 50% to 80%" [2].
> That's how they skew the numbers to make renewables seem viable when they produce a shockingly low amount of actual power
You should tell the folks overwhelming choosing to build and finance renewable power plants! They clearly missed this key point, they’ll surely be grateful you let them know that their renewable investments don’t make sense, and they should have picked nuclear due to it being cheaper overall
reply