Homebrew Web browsers for (New)3DS?

[Drvulcanlord]

Dose anyone know of any usable homebrew web Browsers for the (New)3DS I have tried to find some but the only one I could locate was kuppa cruiser and it always crashed. If you know of any please let me know.

Thanks

 

[StringIsNullOrEmpty]

There is a thread right here where someone tried to implement one:
https://gbatemp.net/threads/wip-jermus-3ds-web-browser.611921/

TLDR:
It can't be done. The (N)3DS is simply too under-powered to load modern websites.

 

[KleinesSinchen]

TLDR:
It can't be done. The (N)3DS is simply too under-powered to load modern websites.

Have to disagree on this. Depending on what is the goal, a 3DS – especially the new type consoles – would be able to handle it. Probably slow, but basic browsing (possibly in mobile mode if a site supports one) should be in range. Adblocking, script blocking and prevention of automatic inclusion for third-party content should be part of such a hypothetical browser to not exhaust all resources in the first second.

In my opinion the problem preventing serious attempts by talented/knowledgeable developers to port a browser engine to 3DS is the "Use your phone! Don't you have a phone?"-attitude. As if the existence of more suitable devices for a task would be a good reason for not trying anything on older stuff.
While we are at it: A powerful PC and a smartphone from the top class could replace pretty much every old thing via emulation.

 

[SylverReZ]

No point on using your 3DS for surfing the web, where you can use a mobile phone or PC, plus they get updates more often.

 

[Coderman64]

Old-ish thread, I know...but I just finished my port of NetSurf to the 3DS. Hopefully, it helps!

 

[WindMageVaati]

Have to disagree on this. Depending on what is the goal, a 3DS – especially the new type consoles – would be able to handle it. Probably slow, but basic browsing (possibly in mobile mode if a site supports one) should be in range. Adblocking, script blocking and prevention of automatic inclusion for third-party content should be part of such a hypothetical browser to not exhaust all resources in the first second.

In my opinion the problem preventing serious attempts by talented/knowledgeable developers to port a browser engine to 3DS is the "Use your phone! Don't you have a phone?"-attitude. As if the existence of more suitable devices for a task would be a good reason for not trying anything on older stuff.
While we are at it: A powerful PC and a smartphone from the top class could replace pretty much every old thing via emulation.

I have no phone