mashlol

I recently pre-ordered and got access to the original wc3 which they've since patched with updates.

I started working on a new custom map, which now has support for Lua and all kinds of new natives like UI natives that allow you to completely customize the UI.

Unfortunately, the debugging tools are abysmal. There is currently a player desync happening in multiplayer in my map (somehow different players disagree with their local emulation), but I am given absolutely zero information about it. No stack traces, there's no way to add breakpoints or logs, prints slow things down to a crawl and so aren't really reasonable to try to debug with either. I've done manual tests slowly by removing parts of code, but due to the random nature of the desync, it's really challenging to solve anything this way. Even if I remove some modules and can't get a desync anymore, doesn't mean it's fixed - it's possible I just never hit the specific circumstance that causes it.

Whenever errors occur during load, I just get an error dialog with an empty box. Whenever errors occur during runtime, it just stifles the error and continues without logging or warning or anything. Lua has `debug.traceback()` but it seems Blizzard has prevented calling it. It's like trying to code without a compiler, without stack traces and without a debugger. Very challenging.

I'm extremely excited for reforged, but I really hope there are better debugging tools added for Lua (perhaps for JASS as well, although I'm not as familiar with the need there). If anyone from Blizzard is reading this, I'd say that's my number one concern right now.

Right, but the only "profile data" they would need to add to the logs to know, would be a user ID. Not really any private info.

Yeah it's very surprising, it really does stifle competition and can only be a bad thing for consumers in the end.

The client could send the request to Apple though, and pass the URL through that way, instead of requesting the actual URL. There's a trade-off there though that Apple gets to see all the links being sent over iMessage.

> Nobody's mentioned Hexo yet

Hexo is #2 in the list in the article...?

> This site can’t be reached

> monitup.tk refused to connect.

> ERR_CONNECTION_REFUSED

Seems to be down?

I don't understand the problem with those modules. Just because you can do something one way, doesn't mean you shouldn't add an easier and better to understand way. The intention of `string.endsWith('Blah')` is easier to understand then `string.indexOf('Blah') === string.length - 4`. Java String has both `indexOf` and `startsWith`, do you think that is also problematic?

You can't really compare "web development" to "application development". I think it's more fair to compare a single web framework with a single native framework. The web ecosystem of frameworks is much larger, meaning there are far more options, much more to adapt to if changing projects. Switching from a well-written iOS codebase to a well-written Android codebase would be no different then switching to a well-written React codebase.

> I've been doing some web development on a fairly long-lived and large code-base

Perhaps it's just not a well written codebase. It's extremely easy to write bad code for web, where perhaps it's slightly harder to do for native development (although still very easily possible of course). It's also very possible to write good maintainable code for both as well.

> I'm not even talking about the fact that everything has to be stateless

It doesn't have to be stateless. Take a look at React.

> just the fact that it really feels like there's no consistent way to do anything

That's pretty much the same with application development. Perhaps not as much for Android/iOS themselves since there is basically only one option for each of those. Even within those there are many many ways of doing everything. It's up to everyone working on the codebase to keep things sane. That's no different with web development.

I really want a feature that would allow me to cast from my phone to my desktop. I have a big TV plugged into my desktop but I can't cast to it from my phone, I have to remote in and manually control the desktop, it's painful.

I don't think they are, there's often comments at the top that are posted x minutes ago where x < 10. I don't think posts that new could have that many votes. There's probably a weighting factor comparing votes to recency, maybe other factors too.

Could have also possibly been an emulator.

I'm curious why you hated the fact that it was in JavaScript? Was it because it ran in the browser? Because this one probably can, but it runs natively by default as far as I can tell.

I also got this message on a Nexus 5 running mobile Chrome, which as far as I understand it has nearly the same featureset as desktop chrome. Perhaps it's not actually doing feature checking, it's just guessing based off the user agent string. Or perhaps it would present horribly on mobile anyway.

> it was just a dress code, how will you treat me if I bring up a more serious issue?

They did bring up the dress code issue to their managers, and it was dismissed. Petitioning it is a level above that, and while I agree that firing them is a bit much, it doesn't mean they can't take feedback necessarily. It sounds like they would still be receptive if you bring up a more serious issue in the proper way (i.e. talking to your manager).

I disagree. Having interned 6 times at 5 different companies, the best ones by FAR are the ones where interns are treated exactly the same as full-time employees. The reality is that interns are not that far off from the new-grads, why would you treat them any differently? Interns should be treated exactly like a new hire, with the exception of the fact that they are temporary, so obviously you don't have to assign them to long term projects or anything like that.

I wasn't aware of any changes. What did they change?

Does this mean any vr headset will work with games from the Oculus store?

They ask you for code. Real, runnable code. The interviewer types it verbatim from what you wrote on the board...

I don't think they necessarily care if it compiles, or if you forgot whether it was Set.has() or Set.contains(), but for some reason they do not allow pseudocode.

A team can surrender if 4/5 teammates agree and at least 20 minutes have passed in the game. Players often believe the game is over before 20 minutes though, which causes these problems.

I'm on mobile, not using an ad blocker, and I still got this message... really Bloomberg...?

Also by performance being affected perhaps they are referring to the 5 extra secondtheys make you wait.

Isn't this kind of the opposite of that? You're jumping to a position further in the code, to a "variable" that hasn't been defined yet.

The PDF won't open for me on a Nexus 5, doesn't show thru githubs mobile site either.

Edit: It worked when I requested the desktop version of github though.

This has actually happened before at official League of Legends tournaments (that is, a fairly serious bug in a serious match). I believe their policy in the case of a serious bug is to re-do the match, but I am not 100% sure.

Yes you have to install an app (soon to come is email fallback if you don't have the app, and Chrome push notifications on Android, which don't require an app downloaded).

While I hadn't heard of it until you mentioned it, the main difference between this and Pushover seems to be that 1) Pushover seems to have more features and available platforms, and 2) Pushover costs money while this is free & opensource.

When you download the app, it registers with Parse, which generates a registration ID for your device. When you use the CLI, it goes to Parse with the key you received from the app and queries for your installation, sending the notification to that specific installation.

Ah good find with the Android bug, I forgot Android re-draws everything on rotates. As of 0.0.3 it is now possible to customize the text with -t.

Ah, this is interesting, didn't encounter this during testing. Working on a fix, thanks for reporting!

Yes they are the parse app keys, they are meant to be public.

Is this on npm? You should add it if it isn't!

This is very useful, thanks for hosting it. Awesome website too, and super easy to set up.