2Pacalypse-

> Looks pretty though.

Does it though? Somehow Nolan made the mediterranean climate and Aegean sea look like washed out coast of Scotland or something. What's with the Hollywood's attack on color lately?

Pretty cool to have this in Rust, might be useful if/when I decide to move some functionality from TS -> Rust.

In the meantime, I have this impelemented in TypeScript in case anyone else will find it useful: https://github.com/ShieldBattery/node-interval-tree

Oh that's cool.

I actually had to implement this myself for a project, literally few days ago.

I had almost 0 knowledge of how audio files work or how the Web Audio API works. The implementation is very barebones, not very flexible, and has no error handling. But hey, if someone will find it useful regardless, here is how I did it: https://gist.github.com/2Pacalypse-/241c37adfff127bd5c66f3e2...

One less talked about thing when discussing StarCraft, that might be more pertinent to HN audience, is that this game was almost endlessly hackable. And I mean that in the truest sense of that word. Many a careers were launched by playing around with OllyDbg and learning to reverse engineer code all so you could create an awesome plugin [0] for the community.

Which brings me to my next point, which is that the community aspect of StarCraft is a huge part of why it remained popular for so long. As previously mentioned, there were hackers and programmers developing awesome tools that helped the scene, but also there were map makers which were essential in keeping the game balanced. One little known fact about StarCraft is that the last balance patch released by Blizzard was in 2001, at the early beginnings of the pro scene. After that, the game was kept fresh and balanced by community map makers.

Combine that with people who created websites where you could follow news about Korean pro scene (TeamLiquid has its roots here), talk with other people about StarCraft, and other people who organized tournaments and did everything else; and you get a formula which almost ensures the longetivity of the game. I wouldn't be surprised if there are people playing and following this game in 20 years time. I know I'll be one of them.

[0] - https://github.com/TheEngineeringBay/Awesome-Broodwar-Resour...

You might be interested in: https://github.com/ShieldBattery/ShieldBattery

It's a project that few of us started almost a decade ago to ensure the longevity of this game. We don't try to emulate Battle.net at all, but instead we take only the gameplay itself and reimplement everything else ourselves.

It's a work in progress, so please let us know what you'd like to see in there that's currently missing if you do check it out.

Any codebase that I had complete control over.

No, but more seriously, I've found that familiarity with the codebase is more important than having it be perfectly engineered. Once you're really familiar with the codebase, you know where dragons be, and you can make changes more easily. And God (PM) forbid, if you ever find yourself with some extra free time you might even reduce the size of dragons over time.

This brings me to my final point. Any codebase that I really enjoyed working with was the one that was constantly evolving. I don't mean rewriting everything from scratch every few months, but as long as I have permission (and time) to refactor the things that have been bothering me for months as patterns emerge, I'm a happy bee.

Isn't this only true if there is no physical infinity? I know it's-turtles-all-the-way-down is impossible for our brains to comprehend, but causality breaks down when infinities are involved. Another thing is that if space-and-time itself was born at some point (as they say), then talking about "before" and causality doesn't make any sense either.

But yeah, to your point, thinking that there was never "nothing", and that there always was "something" is equally mindblowing.

That is closer, but it's also not exactly correct. Now that I think about it, I don't think the English language has any sound where the letter "c" is used as it's pronounced in Croatian language. For example, the word "points" has the "ts" sound which is phonetically closest to the letter "c", but the the letter "c" is much sharper and shorter.

This is the statement posted by the perpetrator over the weekend: https://i.imgur.com/kHVasZz.png

1 Reason Why Current Music Doesn't Suck:

- I like it

More seriously, I've been listening a lot to the mainstream pop songs on the radio during my car commute, and I don't know which carefully crafted formulas and laboratories those songs come from, but they're in sync with what my brain perceives as "good music" quite incredibly.

I genuinely enjoy listening to them.

Based on the fact that this language shares the same name as me, I think it's one of the most beautiful languages that ever existed.

Jokes aside, this does look pretty neat.

Not only they can sue you, but they can make your life a living hell if you choose to fight them back. See one of the most famous examples: http://nissan.com/

While not that unexpected, I'm curious to see if this will start a trend that other game publishers might follow. I'm mainly curious about when Blizzard will deem the cost-benefit analysis to swing in favor of shutting down their old battle.net service which hosts games like StarCraft 1, Diablo 2, and WarCraft 3.

For StarCraft 1 specifically (and its Remastered version), a few us have been building a custom server/launcher[0] which should at least ensure that the game/community doesn't completely die out. However, we still rely on Blizzard's online services to verify the in-game purchases, like HD graphics (the game will automatically stop rendering the HD graphics if you didn't log into Blizzard's services in the last 30 days).

It remains to be seen how this will be handled by Blizzard if (when?) the time comes.

[0] - https://github.com/ShieldBattery/ShieldBattery

This is pretty cool if I do say so myself.

What does the picnic data show?

From my perspective as a software engineer there have been none.

At this point, doing everyone on GitHub itself is a very viable strategy to me, but I know that will never fly with people who obsess over story points and time estimates.

Yeah, I hated this too. I've been using the 7+ Taskbar Tweaker program[0] to change this behaviour and I honestly couldn't imagine using Windows without it at this point.

[0] - https://rammichael.com/7-taskbar-tweaker

I learned this on QI! - https://www.youtube.com/watch?v=nOcmEpp5Kmg

Fun fact: this is Chris Hadfield's son, who even makes a cameo in the video!

But Evan definitely stands on his own as a great video maker, definitely do check out some of his other videos.

Real Science channel on youtube did an episode on horseshoe crabs recently that is worth watching: https://www.youtube.com/watch?v=oXVnuG3zO_0

> Their big issue today is scaling.

Brian from Real Engineering did a video on this subject recently (referencing the Tesla's battery day presentation): https://www.youtube.com/watch?v=1Xwxe0wU4b8

What a delightful article. Just enough humour interspersed to make it enjoyable to read without going on long tangents to make it annoying. And as someone who has very limited knowledge of this stuff, I feel like I've actually learned something!

The video[0] at the end of the article was also very beautiful and concise. I wish more scientific writing was done in this way.

[0] - https://youtu.be/U_xWDWKq1CM

Well, as far as my understanding of hooks go, and please do correct me if I'm wrong, hooks are not just about giving functional component an option to use state and lifecycle methods. They are also a much more powerful and flexible replacement of mixins and offer an (arguably better) alternative to use certain design patterns, like render props.

I did assume that hooks were not supported in classes because it would be too complex to support that use-case, but the linked article specifically has an "Absorb the Complexity" principle, so it seemed a bit weird to me. Also, I understand the decision to try to motivate the community to use function components more, but is this the trend that we can expect to continue seeing in React? Certain APIs being phased out until they finally become deprecated. I know it has happened a few times already in React, but not on the level of something like a class API.