Hacker News new | past | comments | ask | show | jobs | submit | Nullabillity's comments login


Little Boy certainly had "profound impacts on cost savings, productivity, and quality of life" in Hiroshima.

Impact isn't inherently positive.


> I’ve even seen people say that em dashes are indicative, I guess those people neither care about good writing nor know that em dashes are as easy as option + shift + hyphen on a Mac.

They are virtually indistinguishable from regular dashes (unless you're specifically looking for them), and contribute nothing of significant value to the text itself. They were only ever a marker of "this is either professionally edited, or written by a pedant".


> Blaming uber for having those drivers seems like a stretch.

It seems perfectly predictable that a loophole you actively exploit will be closed off. Don't build your business model around loopholes, or be prepared to face the consequences.


Yesn't.

Rust is perfectly happy to emit/use dynamic links.[0] It's just that the primary C use case (distributing and updating the main app and its libraries separately) ends up being unsafe since Rust's ABI is unstable (so compiler versions, libraries, etc must match exactly).

Avoiding static relinking during development is pretty much the use where it does work. In fact, Bevy recommends this as part of its setup guide![1]

Practice paints a slightly less rosy picture, though; since the feature is exercised quite rarely, not all libraries work well with it in practice.[2]

[0]: https://doc.rust-lang.org/reference/linkage.html#r-link.dyli...

[1]: https://bevyengine.org/learn/quick-start/getting-started/set...

[2]: For example, https://github.com/linebender/bevy_vello/issues/84


> something productive

So... not this.


It sounds like you're confusing the Wii's backwards compatibility with the PS3's. The Wii didn't have a separate "GameCube chip", its core was effectively an overclocked GC.

https://youtu.be/meZA9KHkFuY?si=5xrsSjNxKLxLnd6J

He explains it quite well. Sorry it’s German but I guess the information about the chips and reasons Nintendo choose them should be all over the net.


Merge main into your branch, then merge --no-ff your branch into main. No need to rebase or squash anything.

> Merge main into your branch

The same problem GP was trying to avoid is created here, the merge conflict resolution being on the merge commit.


On top of this, integration is an "interesting" step on its own! When trying to diagnose an issue it can be super valuable to be able to understand whether it was broken from the start or broken by the merge. Rebasing throws all of that valuable information away!

Even better, `git merge --no-ff` your PRs and use `git log --first-parent` for the simplified "as-if-it-was-squashed" history.

Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: