u/cbarrick

Your options are essentially either:

• Bundle your data into the binary with include_bytes! or similar.

• Ship your files to your users along with your binary. You would usually use something like the xdg crate to lookup the paths to the files. XDG is Linux/BSD specific, so you'd need something similar for macOS, Windows, and Android.

If you're not shipping this to external users, just commit to a specific path and do regular file I/O. If you just cargo run your project, you can use relative paths.

Do you have specific examples?

Is there a reason why we can't move that logic into ld or is it mostly just legacy tech debt?

This brings up a question I've always had.

Why exactly do we use cc instead of ld for linking? What is the C compiler providing on top of the raw linker command?

Anthropic is also claiming to have concurrently disproven ETH.

https://hexagonmath.org/2610.00577v1

Anthropic is also claiming to have concurrently disproven ETH.

https://hexagonmath.org/2610.00577v1

It was made illegal to process transactions like this during the Obama administration, as one of the reforms to bring us out of the 2008 financial crisis.

Don't get me wrong, X11 was cool tech.

But also I believe that it is largely responsible for Linux falling behind in the desktop/workstation market.

The client/server model was never a good fit. Having a locally running app connect to a daemon/server on the remote machine was always a way better separation of concerns than doing the split in the GUI layer.

For cases where you truly need a remote desktop environment, RDP etc. was the better model. Sounds like this new Wayland protocol is heading in that direction.

This is nightmare level if your map leaves large gaps between pumps due to terrain.

You can mitigate this a bit by ensuring that there is water storage next to each pump.

In general, I put storages in supply mode next to each building that produces a resource. It reduces the amount of time workers spend outside of their workplace.

Very pretty diagrams.

But I gave up after swiping one million times to make it through the explanation of abstract interpretation. It doesn't need to be that fine grained.

Never even made it to the actual new research...

UGA has about 8,500 beds.

The other 40,000 students need to live somewhere.

Googlers internally crowd source their pay data, with a high participation rate. In my experience, levels.fyi under reports compared to that.

So you're not wrong that new hire offers can skew the data compared to promos, but it is still low in my experience, at least for Google.

Big +1. This is the canonical source for tracking updates.

Folks can add more at https://github.com/galadran/we-have-a-problem.com.

IIUC, levels.fyi aggregates reports from multiple years, so it under reports current average comp packages.

Stripping citizenship based on minor visa violations opens a whole can of worms that is better left closed.

Tons of folks have minor visa infractions on their path to citizenship. For example, the TN visa is not an immigration-intent visa. So it feels like if we strip Elon of citizenship due to minor infractions of his student visa, then we have to strip citizenship from everyone who got here on a TN visa, which includes a bunch of Mexican-American citizens.

As much as I hate Elon, I don't want to give the radical right more legal avenues to deport citizens.

Stripping citizenship must require a very high bar to clear. Like treason-level crimes.

They are P-384 keys, so they only need to be 384 bits long.

But yes, it's the same general idea. They should have 384 random bits, but they actually only have 8 random bits.

So the eight private keys are:

4, 56, 66, 115, 155, 156, 230, and 237

LMFAO

But this is just like any other SSH agent: once decrypted the key is stored in memory.

IIUC, in the OP, the key is stored on the secure enclave and is never put in memory.

So it is secure against malware that can read your memory or that compromise your SSH agent. (Though if that happens, you probably have bigger fish to fry.)

The best way to represent this is with a colored dot in the center of the district (or in the population center of the district).

Filling the entire district makes it seem like the party that is popular in rural areas has outsized influence.

Neighborhoods near universities need density.

Single family zoning near campus is ridiculous.

I haven't checked enrollment numbers since I was a student, but I wouldn't be surprised if UGA is pushing 50k students. Those kids need a place to live near campus.

It's also wild to assume all students are trust fund babies or are somehow wealthier than the families in Athens. Studying at UGA is a path out of poverty for many students.

The TL;DR is that new standards are more about the number of people that can be supported on a single access point and less about improvements to the experience to any individual user.

So there is no motivation for users to upgrade. We'll just slowly get bumped up to newer standards.

Isn't this one of the classic pieces of software engineering advice? "Don't roll your own datetime" is up there with "don't roll your own crypto."

I would expect mature datetime libraries to correctly handle UTC. That like their one job.

Yes!

The entire idea behind UTC is to be an integer number of seconds correction between TAI and actual mean solar time.

If you don't want leap seconds, just use an already defined standard that doesn't have leap seconds.

Need to transition from UTC to TAI? Use Google-style leap second smearing (though over a longer period since you have to smear a larger number of seconds).

There is no reason to change UTC. All.of the code that deals with UTC already knows how to deal with leap seconds. We gain nothing.

Converting between these different timestamp standards is just a simple table lookup. What do we gain by making this change?

No idea why you're being down voted.

With a bottle full of bub.

You can read the source, verify for yourself that it is safe.

Even if you don't individually read it, others can and can make noise if something is evil.

No one can tell what the binary is doing before running it.

ETA: Also, OP can silently change the binary to a malicious one at any time. So even if it is safe now, we can't know that it will always be safe. With source changes, we can see the commit log.

Nothing stops the repo owner from uploading a malicious binary to the release. Why should we trust OP?

I'm not giving sudo access to a random binary on the internet.

OP should provide installation from source.