You keep using this word "best". It doesn't mean what you think it means.
> UO was the most popular mmorpg until EQ came out. EQ was the most popular mmorpg until WoW came out. WoW has been the most popular mmorpg ever since.
FTFY.
Your logic is akin to McDonalds being the best simply because they are the most popular.
Completely disagree with your first statement. I played UO for 4 years (Lake Superior FTW). I lost many friends who quit due to rampant unwanted PK'ing.
By the time Trammel came out most of us stayed for a little while and then said "Fuck it." The game was already old to us "veterans". New content only delayed saying goodbye.
Yeah the 3D clients were a complete clusterfuck. They actually shipped more then one 3D client? wow.
UO Renaissance was like kicking a dead horse. The people who stayed weren't interested in trying new games -- they stayed because of the social aspect.
I don't know how bad a director / producer Crofwall is. The damage about UO had already been done.
/Sarcasm "Naturally" they will move from the GTX 980 to GTY 100. Oh wait, you wanted something that makes sense... can we fire the marketing droids who love creating confusion over recycling the same models numbers yet?
Git is wonderful for text files but horrible for (large) binary files. Will git ever be patched or re-architectured to allow it to handle large binary files better instead of them clogging up the history?
1. If you're constantly upgrading you're doing it wrong. You should only buy a new GPU that moves you up at least 3 tiers.
2. I guess you don't play any MMOs such as WoW, any RTSs such as Starcraft, or use any mods for Skyrim, Minecraft, etc. Consoles aren't always even viable in some cases. If all you care about is dumb button mashers such as Diablo 3, or Destiny then sure, knock yourself out. Meanwhile some of us will be checking out the free Path of Exile and other PC only games.
3. I've been building my custom gaming rigs since 1990. These days you can save a bundle by getting parts from NewEgg or MicroCenter. Order an i7, with a Hyper 212 EVO cooler, 16 GB RAM, a 256 GB SSD, and that $500 you spent on a GPU will give you a gaming rig that will last **years**.
4. I guess you don't care about framerate or resolution. Consoles can barely do 1080p @ 60 fps. Meanwhile over in PC land we're gaming at 120+ Hz with G-Sync / FreeSync Desktops resolutions are running at 2560x1440, the incorrectly labeled "2K" @ 3840x2160, or even higher such as Vanishing of Ethan Carter @ 8K.
Consoles are basically a 4 year old PC. Apples and Oranges. Different strokes for different folks.
Punctuators are all the usual bits of punctuation which are meaningful to C and C++. All but three of the punctuation characters in ASCII are C punctuators. The exceptions are â@â(TM), â$â(TM), and â`â(TM). In addition, all the two- and three-character operators are punctuators
In ASCII, the only other characters are â@â(TM), â$â(TM), â`â(TM), and control characters other than NUL (all bits zero). (Note that â$â(TM) is normally considered a letter.)
Why is $ even considered a letter in the first place? GCC gives this reason:
As an extension, GCC treats â$â(TM) as a letter. This is for compatibility with some systems, such as VMS, where â$â(TM) is commonly used in system-defined function and object names.
The more interesting question is why is Microsoft emulating this non-standard behavior?
> Macro names must follow the same rules as variable names, ie, letters, numbers, and underscores only;
That is an artificial rule; one would think that the preprocessor is supposed to be independent of the language. i.e. Why can I use C's preprocessor for a language like Perl ? The problem is that the pre-processor's definition of what constitutes a character token is too limited, it should only reject existing symbols that have are predefined operators (i.e. have a mathematical definition) and not blacklist other non-used symbols. If the preprocessor was properly written to do a search-and-replace then this wouldn't be an issue.
This points to a bigger problem though. Why is my source code limited to sub-set of ASCII? Why can't I include Unicode in comments?
> You also forgot the BYTE, WORD, LONG, etc. types all over the Windows API. Sure, they're older than stdint.h, but they're yet another buttload of type aliases to keep track of.
I didn't mention it because that is a separate issue. Microsoft's stupidity is not part of C++, though they seem to have inherited some of it.
I guess someone at Microsoft liked C's "double", and hated the inconsistency with "float" so they added an aliasSystem.Single in C# !
Agreed that CUDA and OpenCL are great secondary and tertiary ways of heterogeneous multi-core programming.
Not sure what your beef again OpenMP is. OpenMP makes it trivial to add multi-threading to your app.
When did C++ get thread control again? Oh yeah, it wasn't until C++11 and you STILL had to wait for compilers to implement it. In the mean-time OpenMP was already here, and working for years. Considering OpenMP has been around for 18 years, calling it a hack when C++ ignored the whole standardization of multi-threading for YEARS is pretty fucking arrogant -- especially when Intel's, Microsoft's and GCC's compilers have natively supported OpenMP for years. What were Windows users supposed to use in the mean-time for portability? A port of pthreads wasn't even available for Win32 until ~2001 if this page is correct.
There are problems with std::future as this committee paper points out:
Crap like long long, "long double", etc. should have been deprecated in year X, and removed in year X+5. Are they going to add "long long long" someday?? Having types like "double" in 2015 is just retarded -- replace it with "float64_t", and the fore mentioned long double with the clear "float80_t". Bandaging the problem like int_fast32_tdoesn't solve anything. How many fucking integers types does the compiler need to throw at us?? short, long, long long, int, long int, int_fast32_t, int_least32_t, etc. and I'm not even talking about MS's hacks of __int32, __int64, etc. Simplify the dam language already!!! Set year 2020 as the date when these barbaric types are deprecated, and year 2030 when they are removed.
Modules have been in a constant state of on-again-off-again for over 10 years:
The pre-processor is STILL broken. One would expect #define token operation to work for ALL user-defined tokens. i.e. This isn't rocket science, just a basic Search-and-Replace:
#define @(func) printf("%s\n",func)
void foo() {
@(__func__); }
// Hell, even this should work #define @ printf("LOL. Your pre-processor is broken. HA-HA!\n" )
There are no standard pre-processor macros for function names as a string. GCC has the excellent __func__ which Microsoft finally got around to implementing C99 N2340 in Visual Studio 2015!
The C++ committee failed to learn the first lesson about design:
* "Needlessly complexity is a symptom of bad design."
Or paraphrased from Einstein:
* "Things should be as simple as possible, but no simpler"
As an ex-hardcore gamer let me know when ALL my favorite games run natively under Linux; not emulated with a performance hit, or buggy implementation of Wine.
I prefer OSX and Linux for development but the reality is that Windows is the where the majority of new games are (only) released on.
Slashdot Mirror
You keep using this word "best". It doesn't mean what you think it means.
> UO was the most popular mmorpg until EQ came out. EQ was the most popular mmorpg until WoW came out. WoW has been the most popular mmorpg ever since.
FTFY.
Your logic is akin to McDonalds being the best simply because they are the most popular.
Quality != Quantity.
That sums up fazebook 100%. :-/
Completely disagree with your first statement. I played UO for 4 years (Lake Superior FTW). I lost many friends who quit due to rampant unwanted PK'ing.
By the time Trammel came out most of us stayed for a little while and then said "Fuck it." The game was already old to us "veterans". New content only delayed saying goodbye.
Yeah the 3D clients were a complete clusterfuck. They actually shipped more then one 3D client? wow.
UO Renaissance was like kicking a dead horse. The people who stayed weren't interested in trying new games -- they stayed because of the social aspect.
I don't know how bad a director / producer Crofwall is. The damage about UO had already been done.
/Sarcasm "Naturally" they will move from the GTX 980 to GTY 100. Oh wait, you wanted something that makes sense ... can we fire the marketing droids who love creating confusion over recycling the same models numbers yet?
I know.
Like WTF? We need a court to determine what the hell I can block?
Agreed. Can we file this under:
No Shit, Sherlock
Yeah, Windows 10 looks like shit. /Oblg. Windows 1 vs Windows 8
* http://gaspull.geeksaresexytec...
Ah, so basically Silicon Valley 2.0 but outside computers. Got it.
> It's a conspiracy between Microsoft and the CPU manufacturers
Blast from the past! Haven't seen the label "Wintel" mentioned in "eons."
i.e. /Oblg. "What Andy [Grove] giveth, Bill [Gates] taketh away."
Bloody lazy editors.
I would also add:
Git is wonderful for text files but horrible for (large) binary files. Will git ever be patched or re-architectured to allow it to handle large binary files better instead of them clogging up the history?
> If the Confederate Battle Flag is now a symbol of racism and must be banned, what about the gray soldier's uniform? Do we ban that, too?
This 100%.
There's 3 problems with censorship:
1. It quickly becomes a slippery slope banning everything with no end in sight. Who decides what is "offensive" ?
2. Only cowards censor.
3. Ignoring the past doesn't make it go away.
1. If you're constantly upgrading you're doing it wrong. You should only buy a new GPU that moves you up at least 3 tiers.
2. I guess you don't play any MMOs such as WoW, any RTSs such as Starcraft, or use any mods for Skyrim, Minecraft, etc. Consoles aren't always even viable in some cases. If all you care about is dumb button mashers such as Diablo 3, or Destiny then sure, knock yourself out. Meanwhile some of us will be checking out the free Path of Exile and other PC only games.
3. I've been building my custom gaming rigs since 1990. These days you can save a bundle by getting parts from NewEgg or MicroCenter. Order an i7, with a Hyper 212 EVO cooler, 16 GB RAM, a 256 GB SSD, and that $500 you spent on a GPU will give you a gaming rig that will last **years**.
4. I guess you don't care about framerate or resolution. Consoles can barely do 1080p @ 60 fps. Meanwhile over in PC land we're gaming at 120+ Hz with G-Sync / FreeSync Desktops resolutions are running at 2560x1440, the incorrectly labeled "2K" @ 3840x2160, or even higher such as Vanishing of Ethan Carter @ 8K.
Consoles are basically a 4 year old PC. Apples and Oranges. Different strokes for different folks.
So that it immediately sticks out instead of using an alphabetical character which would probably be lost as "noise."
> The point is that it's not standard.
That's not the entire picture.
GCC Tokenization says this:
And MSVC as well.
> You also forgot the BYTE, WORD, LONG, etc. types all over the Windows API. Sure, they're older than stdint.h, but they're yet another buttload of type aliases to keep track of.
I didn't mention it because that is a separate issue. Microsoft's stupidity is not part of C++, though they seem to have inherited some of it.
I guess someone at Microsoft liked C's "double", and hated the inconsistency with "float" so they added an alias System.Single in C# !
In contradistinction to System.Double
You're comparing Apple and Oranges.
The PDP had 36-bit address space. Are there any modern CPU's that don't use powers-of-2 for registers and address space?
Instead of fixing the language and compiler, is a hack. We only need a few basic types built into the language.
Deprecate and Remove this "short" and "long" stupidity. It isn't 1972 anymore.
And that explains why $ is accepted but not @ how again?
#define $ printf("Works!\n")
#define @ printf("Nope\n")
Looks like a master did answer it; discusses a Factorial Number System, provided code, and even ended it with:
TL:DR; You're code is already "clean" and correct.
Mod parent up +1 insightful. Well said!
As someone else pointed out in the thread Report: Aging Java Components To Blame For Massively Buggy Open-Source Software from just a few days ago (June 16):
* "A good programmer knows when to use external libraries. A great programmer knows when not to."
To summarize: Great programmers know how to manage code complexity. Poor ones don't.
Agreed that CUDA and OpenCL are great secondary and tertiary ways of heterogeneous multi-core programming.
Not sure what your beef again OpenMP is. OpenMP makes it trivial to add multi-threading to your app.
When did C++ get thread control again? Oh yeah, it wasn't until C++11 and you STILL had to wait for compilers to implement it. In the mean-time OpenMP was already here, and working for years. Considering OpenMP has been around for 18 years, calling it a hack when C++ ignored the whole standardization of multi-threading for YEARS is pretty fucking arrogant -- especially when Intel's, Microsoft's and GCC's compilers have natively supported OpenMP for years. What were Windows users supposed to use in the mean-time for portability? A port of pthreads wasn't even available for Win32 until ~2001 if this page is correct.
There are problems with std::future as this committee paper points out:
* N3964 (March 2014)
Even co-routines are still relatively new:
* N4134 (Oct 2014)
C++11 std::thread is great for the future. OpenMP was a perfectly fine solution when C++ didn't even have one back in the day.
This 100%. C++ has become a clusterfuck of over-engineering and I say that as someone who has worked on a C++ compiler.
* /Oblg. Comedy: Hitler on C++
When you have even committee members admit they only use a sub-set then you know the language is too big.
The C++ committee recognizes there are many problems with C++ iostreams but nothing is being done towards performance and type safety.
The committee would rather argue over the rare case of multi-dispatch / multi-methods then fix core issues.
* http://www.stroustrup.com/mult...
Crap like long long, "long double", etc. should have been deprecated in year X, and removed in year X+5. Are they going to add "long long long" someday?? Having types like "double" in 2015 is just retarded -- replace it with "float64_t", and the fore mentioned long double with the clear "float80_t". Bandaging the problem like int_fast32_t doesn't solve anything. How many fucking integers types does the compiler need to throw at us?? short, long, long long, int, long int, int_fast32_t, int_least32_t, etc. and I'm not even talking about MS's hacks of __int32, __int64, etc. Simplify the dam language already!!! Set year 2020 as the date when these barbaric types are deprecated, and year 2030 when they are removed.
Modules have been in a constant state of on-again-off-again for over 10 years:
* First mention N2073 (Sept.2006)
* Revived N4047 (May 2014)
* 2nd draft N4214 (Oct. 2014)
* 3rd draft N4465 (April 2015)
* Wording N4466 (April 2015)
The pre-processor is STILL broken. One would expect #define token operation to work for ALL user-defined tokens. i.e. This isn't rocket science, just a basic Search-and-Replace:
There are no standard pre-processor macros for function names as a string. GCC has the excellent __func__ which Microsoft finally got around to implementing C99 N2340 in Visual Studio 2015!
The C++ committee failed to learn the first lesson about design:
* "Needlessly complexity is a symptom of bad design."
Or paraphrased from Einstein:
* "Things should be as simple as possible, but no simpler"
/Oblg. but MongoDB has webscale
Perfect analysis of all the UI fails.
Just leave the dam site alone. It was working fine the way it was before.
As an ex-hardcore gamer let me know when ALL my favorite games run natively under Linux; not emulated with a performance hit, or buggy implementation of Wine.
I prefer OSX and Linux for development but the reality is that Windows is the where the majority of new games are (only) released on.