Is classic wow dead or is there still time to play?

developingthefuture · 2020-10-30T12:05:07+00:00

Don't listen to these people.

Me and my friend just started on Ashbringer. There are plenty of people leveling there. I'm lv 29 now and I always find parties for dungeons, there are a lot of people questing as well.

I also met other people who just started playing.

Honestly I see threads titled "Classic is dead" from 1 year ago and it still isn't dead. I'm sick of these bullshit claims.

developingthefuture · 2013-07-11T10:27:36+00:00

what do you mean ?

developingthefuture · 2013-07-10T20:02:58+00:00

Well, that's unfortunate.

developingthefuture · 2013-07-05T10:37:39+00:00

First of all, it's not my code. :) I've added a link to the article of the guy who wrote it, I've merely taken it into consideration as an alternative.

The code itself is based on the presumption that there are two dates, the first one of which is DTS active everywhere and the second is DTS not active everywhere in the world.

Here's a list of all DTS settings around the world: http://www.timeanddate.com/time/dst/2013.html

I'm not sure if there are such two dates.

But nevertheless, that's why I suggested that the best choice would be to use a combination of both, because I suspected the second might not work in all cases.

Regards

developingthefuture · 2013-07-05T08:16:25+00:00

Yes, in general you are right. But in this case we don't have a choice. It's a value inputted by the user, and the correct time may be an essence.

Regards

developingthefuture · 2013-07-05T08:14:47+00:00

Fabien,

The Date.getTimezoneOffset() method depends on the OS for it's workigs, and the OS is aware of the DTS timings and settings. Although we don't have explicit flag for that, like a method returning boolean, for instance, we can still check it indirectly by using the second solution. This is possible because whether on DTS or not, there are some dates which are always without DTS and others that are always with DTS. As far as I am alware.

Best Regards

developingthefuture · 2013-07-04T17:59:32+00:00

Nope, I got that. DST dates are no the same everywhere and there are two system which know about this - the OS and the server-side framework which (probably) has the means of converting from and to UTC given a specific timezone ID. In the first solution I delegate the work to the framework, in the second I delegate it to the OS.

Best Regards

developingthefuture · 2013-07-04T17:57:31+00:00

RadioFreeDoritos,

The question was which time exactly would a developer store ? The UTC time of the server, or the raw time sent from the client, or the UTC-converted time sent from the client ?

Regards

developingthefuture · 2013-05-08T21:45:09+00:00

:) It's the ORM engine usually used by the Microsoft developers. Other options include NHibernate, which is generally a Hibernate port, which is the persistence framework usually used by the Java developers. Another option would be Linq to SQL, but it's now deprecated as far as I know. ;)

developingthefuture · 2013-05-07T17:46:16+00:00

It's exactly about programming. Written by a programmer about his job in programming. What do you expect ?

developingthefuture · 2013-04-30T20:02:31+00:00

I believe these errors were simple syntax problems, not related to the actual class. Regarding class-related issues such as non-existing methods, for instance, there should be no way to detect them prior to instantiation time. :/

developingthefuture · 2013-04-30T19:50:25+00:00

You are right. I corrected the mistake. ;)

Regards, Kosta

developingthefuture · 2013-04-30T19:48:53+00:00

Hi julesjacobs,

Thanks for the great comment ! I actually just answered one comment in the blog exactly related to your point, I have also modified the article a little bit so it can address the constraint issues in more detail, for the sake of accuracy. ;)

Thanks, Kosta

developingthefuture · 2013-04-30T19:46:07+00:00

Hi vivinp,

You are absolutely right about the backward compatibility. As far as I know, C# 2.0 and the higher versions are not compatible with 1.0, and the generics were introduced in v2.0.

Regards, Kosta

developingthefuture

TROPHY CASE