Live data from Hacker News

One game, by one man, on six platforms: The good, the bad and the ugly

ruoyusun.com

131–140 of 156 posts

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#131
post #4

> Linux accounts for less than 1% of the total players I think some types of games (think factory building, zachtronics style puzzle games, ...) might have a bigger percentage, though that's only a feeling I have, I don't have numbers myself, I just see such games more often have a Linux release on Steam that seems appreciated.

The article is about a factory building game, isn't it?

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#134

Earlier quoted context omitted.

Flutter is actually pretty close to this right now. I'm building an app that targets Windows, Mac, iOS and Android and so far it's working really well on all of them with more than 90% code reuse. If Google doesn't give up on it I think it's going to be a much better stack for cross platform applications than the browser is.

Flutter has a multitude of problems, at Google's inability to support anything long-term is probably the smallest. Flutter apps don't look or work like native apps, and the only people who will put up with that are people who have to do so because their enterprise mandates it. Flutter apps have horrible battery performance. Flutter apps are always at least six months behind what is possible with native toolkits and S…

This doesn't match my experience at all. It's leagues ahead of react native in memory usage, disk space, responsiveness etc.

Users are used to apps that don't look much like the out of the box platform toolkit by now. Even apple isn't very consistent about this anymore.

Native is better if course if you have the luxury of writing your app twice or three times but not many of us do.

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#135

Earlier quoted context omitted.

Flutter is actually pretty close to this right now. I'm building an app that targets Windows, Mac, iOS and Android and so far it's working really well on all of them with more than 90% code reuse. If Google doesn't give up on it I think it's going to be a much better stack for cross platform applications than the browser is.

> If Google doesn't give up on it I think it's going to be a much better stack for cross platform applications than the browser is. When I read this, I don't know if you're saying it's not ready yet or something. Is it close but not there yet? Do you experience bugs?

No so far I've had a great experience with it. But keeping up with new improvements and changes to the underlying platforms is going to require ongoing investment. Hopefully google continues to think it's worth it.

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#136
post #97

Earlier quoted context omitted.

The Java Applet was this. Flash also was this. Now the browser is just a bloated pile of crap.

As opposed to Java applets?

Java is the best thing we have gotten since C in 1970.

That was 30 years ago. Since then everyone has been copying Java:

C#, WASM, Go, Rust... nothing even scratches the surface.

And it never was insecure, it was removed by the same people that leverages consume only devices and root certificates.

That said I'm actually a proponent of bringing back the MIDlet, J2ME was the best software platform ever created.

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#137
post #131
post #4

> Linux accounts for less than 1% of the total players I think some types of games (think factory building, zachtronics style puzzle games, ...) might have a bigger percentage, though that's only a feeling I have, I don't have numbers myself, I just see such games more often have a Linux release on Steam that seems appreciated.

The article is about a factory building game, isn't it?

[deleted]

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#138
post #136

Earlier quoted context omitted.

As opposed to Java applets?

Java is the best thing we have gotten since C in 1970. That was 30 years ago. Since then everyone has been copying Java: C#, WASM, Go, Rust... nothing even scratches the surface. And it never was insecure, it was removed by the same people that leverages consume only devices and root certificates. That said I'm actually a proponent of bringing back the MIDlet, J2ME was the best software platform ever created.

You misunderstand me. I think Java's great. Java applets were quite bloated. moreso than Electron. You can still make Java Applets if you want, but people have moved on.

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#139
post #124

Earlier quoted context omitted.

Web browsers are remarkably backwards compatible. 20 year old websites continue to work fine. The things you linked are only advised against for new code: > These features are likely stable because removing them will cause backward compatibility issues and break legacy websites. (JavaScript has the design goal of "don't break the web".) Still, they are not cross-platform portable and may not be supported by all analy…

20 year old browsers don’t work at all, though. You can’t browse any of the top 100 sites, and you won’t be able to download an old release of firefox with your old version of internet explorer, because SSL.

[deleted]

Re: One game, by one man, on six platforms: The good, the bad and the ugly

#140
post #45

Earlier quoted context omitted.

Browsers are absurdly well-optimized for performance. If you know how to tap it, you can make screaming-fast apps of various kinds, with top-notch graphics, font rendering, accessibility support, audio, video, etc. They also have really solid networking capabilities, as long as you don't need raw TCP or UDP. In particular, HTTP/2, HTTP/3, WebSockets, and WebRTC allow for a lot of advanced things. By now, you also hav…

I love how people use hyperbole such as "screaming fast" and yet a native application that's not even all that optimized will tend to run absolute circles around these "screaming fast" solutions. How are we supposed to describe these native apps? What's faster than screaming fast? ear shatteringly quick?

> I love how people use hyperbole such as "screaming fast" and yet a native application that's not even all that optimized will tend to run absolute circles around these "screaming fast" solutions.

And you of course have nontrivial examples to prove that? Or as always source: trust me, bro?

Post reply on HN