HNHacker News
TopNewBestAskShowJobs

gdxhyrd

233 karma · joined November 6, 2019

submissionscomments
gdxhyrd··on WoW streamer hires YouTubers who leeched off his stream to run official channel
> If you go to Twitch and scroll down in Fornite you will see hundreds of people with less than 100 viewers which also confirms that the game means almost nothing.

Not at all. There are so many small Fortnite streamers because they want to become big like the popular ones and they know it is extremely hard to grow a stream out of the top 10-20 most watched games.

You can easily prove this: pick any popular but-not-so-much game and you will find way, way less streamers. To the point some have only 5-10 people streaming it, while having many tens of thousands of concurrent players. And yet only a total 100-1000 viewers combined are watching at a given time.

gdxhyrd··on Win32 on macOS
> isn’t communication less hidden if anything?

Not everyone uses IRC (but it has archives). Email (and its archives) are a thing, too.

Given you can read all the development of the Linux kernel since almost the beginning (and they don't use chat IIRC), I don't think you are correct.

> There’s a reason large open source projects moved to these (React, Rust, etc).

No, there is no reason. They are newer projects with younger people and they just picked something more modern, based on a web browser.

If there was truly a reason, the kernel and other projects would have moved, too.

You can argue, of course, the pros and cons of each alternative.

gdxhyrd··on The Outer Worlds: Fixing the “game thinks my companion is dead” bug
Those defensive measures you describe are the kind of hacks that introduce more and more complexity.

Defensive programming is not fixing bugs with more features, quite the opposite: it is failing hard when a condition does not hold.

gdxhyrd··on Dota 2 with Large Scale Deep Reinforcement Learning [pdf]
If you want the bot to avoid winning by micro, you add delays, cooldowns on interactions, imperfection on clicking, misclicks, etc. on the level of a human pro.

In any case, simplifying the game is usually done to make training far cheaper.

gdxhyrd··on Learning from OpenBSD can make computers marginally less horrible
What a load of BS. The 32-bit ABI is independent of the 64-bit one. Nobody is asking Apple to backport new changes or APIs to 32-bit because nobody cares about new apps in 32-bit. We do care about not breaking the existing ones, though.

The rest of your arguments about storage size, update time, "optimization" etc. are not just irrelevant, but also solved more than a decade ago without penalties in other operating systems.

The funniest thing is the last one about 2010 devs. Go ahead, go back in time to 2010 and tell everybody to make their hundreds of millions of LOC and third party dependencies (many without source) and duplicate their testing cost just so that Apple cannot be blamed to drop 32-bit support ten years later.

Let me tell you the reality: Apple is a hardware company, not software. Apple cares about selling iPhones, not enterprise long-term support or non-casual gaming. On the other hand, Linux and Microsoft and other companies care about users and customers and they are paid for that because they are a software shop. That's the difference.

gdxhyrd··on Learning from OpenBSD can make computers marginally less horrible
> You are moving the goalposts.

No, I am not moving goalposts. OpenGL has been useless for all intents and purposes in macOS for years already. The deprecation is the least of concerns.

> 1) OpenGL is a terrible fit for modern GPUs so I don't agree that it "worked well"

A terrible fit? What are you even talking about? It is as featureful as the latest D3D11 which is the API most games are based on. What is useless is the OpenGL version and drivers that Apple ships.

Please don't spread FUD. There are no security nor technical reason nor significant cost on maintaining a proper OpenGL.

gdxhyrd··on Intel’s Manufacturing Roadmap from 2019 to 2029
It does not matter. Those that know use it as the ID for a process and it is fine. Those that don't, don't really need to know.

There is much, much worse marketing out there to tackle first.

gdxhyrd··on Learning from OpenBSD can make computers marginally less horrible
See the sibling reply.
gdxhyrd··on Learning from OpenBSD can make computers marginally less horrible
OpenGL support has been abandoned by Apple years ago, not to mention being broken.

The fact that it is now officially deprecated is just a warning from Apple to remove it soon without bad PR.

gdxhyrd··on Learning from OpenBSD can make computers marginally less horrible
I am not upset because Metal replaced OpenGL. I actually like Metal's design.

What I am upset about is the removal of a standard that worked well. Just don't allow OpenGL apps in the Store and that would be enough.

Even worse, removal of 32-bit support in macOS. Now that's a extraordinarily bad move that confirms Apple does not care about enterprise nor gaming.

gdxhyrd··on Lots of bugs in 32-bit x86 Linux entry code
Worthwhile? We had PAE for a long time, sure, but I think it was fairly obvious when the Athlon 64 appeared that 4GB was not going to cut it, given some people already had 1GB at home...
gdxhyrd··on Lots of bugs in 32-bit x86 Linux entry code
Sure, but the ones that pay the bills are servers and companies which don't care one bit about i386.
gdxhyrd··on Intel’s Manufacturing Roadmap from 2019 to 2029
It is common knowledge even among consumers that pick PC parts.
gdxhyrd··on Speeding Up the Rust Compiler
In libraries, yes. In applications, no. A lot of errors are fatal.
gdxhyrd··on Threads can infect each other with their low priority
The PI the article describes does not need an exhausted queue, just merely used.
gdxhyrd··on Threads can infect each other with their low priority
I would say your assumption is wrong. A lot of people have a CS background, but there are many others that don't.
gdxhyrd··on O(n^2), again, now in Windows Management Instrumentation
Quadratic, not exponential! :)
gdxhyrd··on 0.30000000000000004
All major C/C++ compilers implement IEEE754. If you are telling the compiler to disregard it, that is on you.
gdxhyrd··on React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS
I am amazed at the fact that even going the slow path gets laggy with a mere 900 elements...

What are they doing?!

gdxhyrd··on React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS
I really, really hope nobody writes games in React.

It is such a bad fit for games and it is very disrespectful of the environment and your users' battery.

gdxhyrd··on React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS
No game engine does that and they don't face an "impossible" amount of data. A game designer may choose to spread work over several frames, but that is done on purpose by the developer.

And frustum culling has nothing to do with this nor it reduces any amount of updates.

gdxhyrd··on When your data doesn’t fit in memory: the basic techniques
What you are missing is that " algorithm A is O(n)" is a meaningless statement unless you define under which operations.
gdxhyrd··on Steam for Linux client adds support for Linux namespaces
This is the right answer. With Proton, Steam has a very good start for their Cloud Gaming offering.
gdxhyrd··on Haskell and Rust
Rust is designed to replace C++.

That "ugly syntax" is the de facto standard in the industry. No one, comparatively, would use Rust if it went the Haskell/ML way.

gdxhyrd··on How Swift Achieved Dynamic Linking Where Rust Couldn't
We are not just talking about arch/system ABIs but language/library ABIs.

In any case, 14 years is definitely a very short time for arch/system ABI support, specially compared to Linux or Windows which will basically never kill x86 ABI support.

Apple has just killed thousands of apps and games that people are using.

gdxhyrd··on How Swift Achieved Dynamic Linking Where Rust Couldn't
20 MB is a ridiculous amount compared to anything else going on in your phone, including sending a few high res shots. Many apps and iOS updates are an order of magnitude bigger, and they are not even games.

If size was such a huge concern, Apple would have provided it a long time ago in Swift.

gdxhyrd··on How Swift Achieved Dynamic Linking Where Rust Couldn't
I answered to that in the last paragraph. I don't see the appeal in 2019, in particular in the Apple ecosystem where backwards compatibility is not respected that much.
gdxhyrd··on How Swift Achieved Dynamic Linking Where Rust Couldn't
Yes, but the guarantees Swift provides are not a requirement for that.
gdxhyrd··on How Swift Achieved Dynamic Linking Where Rust Couldn't
In the linked blog post they mention size explicitly:

> ABI stability for Apple OSes means that apps deploying to upcoming releases of those OSes will no longer need to embed the Swift standard library and “overlay” libraries within the app bundle, shrinking their download size; the Swift runtime and standard library will be shipped with the OS, like the Objective-C runtime.

For new UI backends you don't need a different interface, you provide the new UI under the old interface. If your new elements have new behavior you will need to update your app anyway.

gdxhyrd··on How Swift Achieved Dynamic Linking Where Rust Couldn't
The technicalities behind Swift's work on ABI stability are very interesting but I remain unconvinced developers care about ABI stability nowadays; outside security updates and the very basic layers (syscalls, WinAPI...).

In the past, ABI stability was way more important for many companies because there were many more closed source dependencies, way less access to online updates, way less emphasis on CI/CD, etc.

The argument for size by avoiding several std runtimes is strange in 2019, specially considering Apple's policy of deprecating things and forcing devs to update apps constantly.

← PreviousPage 4 of 5Next →