> Weird to add them to the list when they don't build a browser any more

It seems like their browser engine is still being supported for use in "Universal Windows Platform" apps, or at least that's what Wikipedia says.

https://en.wikipedia.org/wiki/EdgeHTML

sure ok, you can still use it in UWP webviews (but you can also use the chromium version). but that seems like a really insignificant application compared to the rest of the browsers being listed.

> imagine the confusion of unsuspecting users searching how to use sudo in the future.

Linux users can experience this now by using sed on macOS

People can experience confusion on any operating system by using sed :)

To be fair, you will probably be confused by using sed in general

Or by using a bash builtin that duplicates a normal command.

> - you make a living developing software for that phone

I fall under this. I'll be upgrading from an 11 Pro this time around mainly because I've let my battery go bad.

We can do most things from the simulator and when we need bluetooth or CoreLocation we can always run the app as a Mac app and use the computers chips.

The job title is a nice excuse to get the latest and greatest but it's not strictly necessary.

Why not replace the battery?

I've also dropped it a fair amount of times without a case so it's in rough shape. I'd be lying if I said the USB-C port and Ti shell weren't contributing factors to me upgrading.

> I'm not sure why you're saying Swift is locked in to Apple platforms, it's definitely cross-platform

I think the key word in OPs comment is "effectively".

The tools for building cross platform Swift exist and work in various levels but they aren't at the point where you would want to choose Swift over existing cross platform tools.

That caveat does not match the definition of “effectively” to me.

`java -XstartOnFirstThread -jar setris-desktop-1.0-SNAPSHOT-jar-with-dependencies.jar`

I had to add the start on first thread flag to prevent errors and start a launch. I do get stuck after `Starting UI Subsystem` gets logged but I havent put any real effort into trying to debug that yet.

I get this when run with homebrew's openjdk (which is JDK 20, I think):

  mikaeleiman@iMac ~/D/Setris-1.2_LINUX> java -XstartOnFirstThread -jar setris-desktop-1.0-SNAPSHOT-jar-with-dependencies.jar
  [LWJGL] [ThreadLocalUtil] Unsupported JNI version detected, this may result in a crash. Please inform LWJGL developers.
  [30.05.23][11:52:12] Loading Assets
  [30.05.23][11:52:12] Done.
  [30.05.23][11:52:12] Starting UI Subsystem
  [30.05.23][11:52:12] Done.
  [30.05.23][11:52:12]   0 FPS |    260MB RAM |    8 Threads | Render: 13ms
  mikaeleiman@iMac ~/D/Setris-1.2_LINUX> 

A window is opened, looks like the title screen with the text "press A". But nothing happens when I press keys, A or others.

Maybe related to the LWJGL warning?

I know little of how Java works, and especially how to override libs, but I did try downloading lwjgl's latest release and put all its jars in the classpath:

  CLASSPATH=(string join ':' (find . | grep jar | grep lwjgl)) java  -XstartOnFirstThread -Xmx4G -jar setris-desktop-1.0-SNAPSHOT-jar-with-dependencies.jar

(fish instead of bash; the "string join" part takes all the jar paths and joins them on a single line with colon separators)

Same output and behavior, though.

Also tried with an older JDK (version 17), but that fails to even open a window.

> How feasible are tubeless setups on long tours?

Very in my opinion, but I'm coming from a bike packers perspective.

Start the route tubeless and run it until it fails. When that happens throw a spare tube (that you should be carrying anyways) in it. If that goes flat, patch it.

Converting back to tubes is easy: take the value stem out -> put in tube. Yes, it's messier but it's not like you're showering regularly anyways.

> Being able to locally resupply with a compatible sealant is the main impediment

I would think that tubeless setup + plugs with spare tubes + a patch kit would get you far enough for this to not be a major issue. Carrying a small bottle of sealant would help. Worst case, you run tubes the rest of the trip.

Note: These are just my thoughts as a (formerly) sponsored bike packer.

Denali has the highest prominence with 20,157′. Mauna Kea's prominence is only 13,803′

> What does this mean? How would it link to their main account in anyway, regardless of this request?

Git adds some author information to each commit [1]. You can set those values project by project, and you can also set them globally.

To set a name and email to default to on all repos, you'd do this:

`git config --global user.name "Topsoil"` `git config --global user.email "topsoil@example.com"`

To set different committer info for a repo, you'd run the same commands without the `--global` flag while in the root directory of the project.

When this person got re-interested in their project, they decided to squash all the commits into one new commit, but forgot to change their name and email on the repo and as a result exposed their real identity when they published the code on GitHub.

I had to look up what f-list was, and it seems to be some kind of furry role-playing community? (i didn't do any research other than briefly looking at the first page of google) so i understand why this person DCMA'd themself.

[1] https://git-scm.com/docs/git-commit#_commit_information

I recently learned, that you're able to switch the git user dynamically based on the folder the repository resides in, by using the includeif directive in your gitconfig. [1]

This is very useful, if you have separate accounts, for example a business and a personal account.

[1] https://gist.github.com/Icaruk/f024a18093dc28ec1588cfb90efc3...

I also recently learned this... just now. Thanks for sharing.

No. This attack is specific to iMessage, since iMessage can access the springboard (the singleton class, not Springboad.app), while apps downloaded from the App Store cannot.

It's not exactly specific to the image preview code, but rather the code that handles the notification when receiving an iMessage.

The attack mentioned in the Wired article[1] relies on iMessage asking the sandboxless Springboard[2][3] to deserialize a maliciously crafted field, included in the incoming iMessage, to escape the sandbox. This specific vulnerability doesn't appear to apply to other apps.

[1] https://googleprojectzero.blogspot.com/2019/08/the-fully-rem... [2] https://en.wikipedia.org/wiki/SpringBoard [3] https://iphonedev.wiki/index.php/SpringBoard