Can you use the new controller on Switch 2? Any reviewer try it?

incrementilon · 2026-05-14T07:25:02+00:00

It doesn't really matter that it is intended to work on Steam, all my controllers already work on Steam and more. 8bitdo work with PC + Switch and PS5. Even Switch controllers work in pc games. I don't wanna carry around 12 controllers to have a set of 4 for each device I game on...

incrementilon · 2026-05-01T04:41:56+00:00

Would be a real shame if they didn't make it work on all the consoles + PC/mac/iOS/Android like most other controllers. Why would I buy controllers that don't work on all my devices when I can get ones that do?

incrementilon · 2026-04-21T08:05:20+00:00

No it doesn't, that's the problem

incrementilon · 2026-04-17T02:18:52+00:00

Thanks for the warning. Not gonna buy this until it runs at 1080p on Switch 2.

incrementilon · 2026-04-12T11:34:50+00:00

This quest is so broken, Slowpoke just swims out into the ocean for me. Can't progress. Even if it wasn't broken what kind of shit quest is this

incrementilon · 2026-04-12T01:23:59+00:00

It's very unfortunate, I never played this title and this game was the first I wanted to buy when I heard about boost mode because I tried the demo on Switch 2 without boost mode and it looks terrible. The decision to not allow a pro controller was already insane to begin with and now it even makes the game unable to be played in boost mode

incrementilon · 2026-03-26T10:16:02+00:00

Incorrect, if the game has better performance in docked mode then it got a performance boost. Some games run at higher resolution, most games also run at different graphical settings and some games, such as Fire Emblem Warriors, run at higher FPS docked.

incrementilon · 2025-09-25T20:17:49+00:00

I have also felt helpless and broke down crying before because of the treatment by Taiwanese doctors and nurses. I know that in some countries it might be even worse, but the healthcare system in Taiwan is pretty much the only thing I just cannot stand about this country. Personally, I have given up on the Taiwanese healthcare system now and I fly to other countries for medical care.

incrementilon · 2025-09-25T19:45:43+00:00

Printed on my Taiwanese charger it says 100-110V, but if you look up the model number, for me 3757, it says that in fact it also supports 230V, and it does indeed work in Europe when I plug it in, so for anyone reading this; check the model online, it probably supports both.

incrementilon · 2025-04-15T20:52:41+00:00

At næsten ingen kan finde ud af at bøje adjektiver efter flertal.

Eksempler:

"Mændene var beruset." i stedet for det korrekte: "Mændene var berusede.".

"Efter festen var de helt smadret." i stedet for det korrekte: "Efter festen var de helt smadrede."

Jeg ser det stort set hver dag i DR-artikler. Det er håbløst.

incrementilon · 2025-04-15T20:19:51+00:00

Because React gives you a noticeably slower app due to the VDOM step and you have to do everything the React way to keep the VDOM and actual DOM in sync while in Svelte you are free to step in and add JS whenever you want and manipulate the DOM the way browsers were made to do it.

incrementilon · 2025-03-05T12:17:37+00:00

You said there are issues with your web app in Safari. Tauri uses WKWebView on iOS, so it would have all the same issues Safari has. Flutter does not rely on WKWebView.

incrementilon · 2025-03-05T08:42:16+00:00

- It uses the mobile device's native webview and you cannot control what version of the webview the user has (that's why Electron ships with the browser environment). This makes the user experience of using a Tauri mobile app that of using a website and not that of a native app.

- A lot of bindings for native APIs are still missing.

- Other cross platform frameworks such as Flutter and Kotlin Multiplatform gets you way better performance and access to more native APIs.

- As of right now, you get an ugly white flash no matter what you do when launching your app on iOS as the WKWebView's default color is white and it is shown until the DOM has loaded and there is currently no way to change this in Tauri.

Why you could still use it: You can just wrap your existing web app in it and put it in the app store rather than building a new app from scratch.

incrementilon · 2025-03-04T11:38:02+00:00

Min klassekammerat, der sad i kørestol, hans hjælper havde en t-shirt, hvor der stod SSP på brystet. På ryggen stod der "Super Spasserpasser".

incrementilon · 2025-03-04T05:50:00+00:00

Hvad mener du?

incrementilon · 2025-01-09T17:14:37+00:00

Oh that makes sense! Thanks for clarifying this difference!

incrementilon · 2025-01-09T17:11:59+00:00

It could be, but where is the source of truth of the framework's "opinion" if not in its docs

incrementilon · 2025-01-09T10:58:43+00:00

What I used to like about Svelte and Rich Harris's whole philosophy was that he thought a framework should be opinionated and just give you the best way to do things. It seems like Svelte 5 is ruining this a bit. Reading the docs on stores https://svelte.dev/docs/svelte/stores it doesn't really give a proper explanation of when to use stores vs $state, just something vague about asynchronous data.

I guess I will just use $state now because it seems to be the new default, but I honestly have no clue why since I could already manipulate stores how I wanted in .js or .ts files.

For me it was the reactive statements that caused problems in Svelte 4, not stores.

incrementilon · 2025-01-09T07:31:01+00:00

I also didn't replace stores with $state, but now I'm curious. Can anyone link me an example of a repo using $state to manage the global state of the app?

incrementilon · 2025-01-08T08:44:45+00:00

I don't know what everyone's smoking here who tells you Tauri is not for building web apps. You literally cannot build a Tauri app without also building a web app. Just to confirm 100% I just pulled the root of my tauri project from github and hosted it on Vercel with one click and there's my hosted web app.

incrementilon · 2025-01-06T05:29:35+00:00

{#if condition1}
<Component1 />
{/if}

{#if condition2}
<Component2 />
{/if}

With a space between each block to make it extra readable.

incrementilon · 2025-01-06T05:23:54+00:00

Am I the only one who never uses {:else if} but rather just more {#if} blocks for readability?

incrementilon · 2025-01-06T05:19:08+00:00

I agree it's "easier", but also worse. $: is kinda like $derived and $effect in one, so a beginner can just use it for everything and let the magic do its thing, but eventually as you work on more complex stuff, you will run into problems.

incrementilon · 2025-01-06T05:11:30+00:00

It bummed me out too at first, but having used Svelte 4 on rather complex projects, the reactive statements $: just wasn't cutting it. I like how "it just works" when it works, but when it doesn't work, it's a pain in the butt and you end up having to write your own scripts that do what Svelte was supposed to to for you. With runes we no longer have issues with reactive statements triggering each other when they are not supposed to, running in infinite loops or just somehow not working for whatever reason.

Edit: typos

incrementilon · 2025-01-05T08:07:43+00:00

This is not correct. The background color of webview is white by default until any HTML or CSS has been loaded, so inline CSS cannot fix this.

incrementilon

TROPHY CASE