> Replaces the standard Go runtime with one designed for the Dreamcast's constraints: memory 16MB RAM, CPU single-core SH-4, no operating system.

24 total megabytes, with an M, of memory between system and video (another 8 there), single core 200mhz CPU, graphics chip runs at 100mhz. Shenmue runs on it.

Glares at Teams.

▲

pjmlp 6 hours ago | parent | next [-]

I really don't get how Teams gets developed, not even the worst offshoring projects I have been part of, have reached so low in quality.

▲

giancarlostoro 7 hours ago | parent | prev | next [-]

It baffles me that Microsoft can build an entire OS, and build and rebuild GUI stacks, and they couldn't build the Teams UI using C#???

	▲	lexoj 28 minutes ago \| parent \| next [-]
		They needed true cross-platform consistence, so it had to be equally terrible everywhere.
	▲	federiconafria 6 hours ago \| parent \| prev \| next [-]
		Microsoft applications always look and behave as if they were ported to windows...
	▲	mfro 7 hours ago \| parent \| prev [-]
		If they built Teams with a C# UI framework, it'd have to be rebuilt 4 times by now.

▲

bttf 4 hours ago | parent | prev | next [-]

Would happily take work chat, video conferencing in network-enabled Shenmue over Teams, Slack any day

▲

perching_aix 8 hours ago | parent | prev | next [-]

Could implement a custom Teams client on top of that. My biggest concern would be TLS and media decoding, but could just proxy the traffic and roll a text only client.

I mucked about with Microsoft Graph a bit before, didn't seem too bad.

▲

gethly 7 hours ago | parent | prev [-]

> CPU single-core

This does not fare well for Go though.

	▲	Thaxll 22 minutes ago \| parent \| next [-]
		Most Go code on Kubernetes runs on a single core.
	▲	jerf 6 hours ago \| parent \| prev \| next [-]
		It runs fine. It is perhaps a bit pricey for a 200MHz system, I'd certainly focus on having only a few of them and doing most of my work by looping over some sort of user-defined tasklet (or, in other words, "standard game architecture"), but it's not like Go requires multiple CPUs to work at all.
	▲	awesome_dude an hour ago \| parent \| prev \| next [-]
		Wouldn't it suit Go over some other architecture, because of goroutines being in userspace, the single CPU is effectively multithreaded when using Go
	▲	c2xlZXB5Cg1 7 hours ago \| parent \| prev \| next [-]
		Paging Mythbusters
	▲	lagniappe 6 hours ago \| parent \| prev [-]
		Huh?