58 karma · joined July 16, 2015
GeForce 256 integrated hardware vertex processing (transform and lighting), which Riva TNT and others did not - the CPU had to do this part.
The RCP of the Nintendo 64 was probably the first modern GPU integrating RSP for vertex processing and RDP for rasterization into a single chip.
"There will be no longer a Nord Stream 2. We will bring an end to it."
* if you want to design and play around with your grammar (builtin interpreter is very nice to try things out):
* once you want to actually implement your language:
https://cs3110.github.io/textbook/chapters/interp/intro.html
* some older tutorials:
https://web.archive.org/web/20051220013748/http://pllab.kais...
https://web.archive.org/web/20051220043933/http://pllab.kais...
NOTE: modern replacement for ocamlyacc: http://gallium.inria.fr/~fpottier/menhir/
(P.S.: as an unbeliver you won't be able to "see" the "Benefits™")
https://gforge.inria.fr/frs/download.php/latestfile/5298/Mod...
(Homepage: https://modernc.gforge.inria.fr/ )
https://caml.inria.fr/pub/docs/oreilly-book/html/index.html
I do not think it is a significant problem in C. It might be more of a problem in C++.
> You can use D in -betterC mode, write code pretty much just like you would in C, and not have that problem.
D is an improved, more polished version of _C++_, not C; "-betterC" mode is misleading, it is more of a "betterC++" mode (features: classes, exceptions, RAII, templates).
"The simplicity of C is more useful than the additional features of C++." -- (Sam Watkins) s/C++/D/g
Don't get me wrong: D would be a great replacement for _C++_, but not C. For a better C I would look at a subset of Go (GC would have to go away).
(Jonathan Blow: Ideas about a new programming language for games.) https://www.youtube.com/watch?v=TH9VCN6UkyQ&list=PLmV5I2fxai...
https://www.youtube.com/watch?v=UaFJ18aENkc https://www.youtube.com/watch?v=9W6wvHSMmzY https://www.youtube.com/watch?v=PqSCRnrq5I0
Some more:
"More" https://www.youtube.com/watch?v=Ud3PgQ_y170 "No Eligible Men" https://www.youtube.com/watch?v=tTxP7fPMnK4 "Seeing the hook" https://www.youtube.com/watch?v=Nv4jnWYCuEs "Remaining unplugged" https://www.youtube.com/watch?v=0KfQIEAGqhg "Hiding in morals" https://www.youtube.com/watch?v=RBslYOWiJlI
https://www.youtube.com/watch?v=LnWV4Yy6dOs
But hey, it may be just porn and videogames after all... who knows...
"An ironic side-effect of feminism is to free men from the burden of being the head of the house." https://www.youtube.com/watch?v=RPETpCVrH9Y
"Why you can't find a man: Hypergamy Floats" https://www.youtube.com/watch?v=4UWpmd1yjVc
my humble opinion: how much would "Immutable Types" add to the language? How much complexity would it add? Things can already be made immutable from outside by hiding them in private variables/struct elements.
The question is: why did Go became successful without having "Immutable Types"? (or "Reference Types", ADTs too please?) Maybe those things are just frills, "nice to have" features.
Example like "type ImmutableMapAndKey const map[const * const Object] const * const Object" looks like really ugly Go to me... this is starting to look like C++...
https://www.youtube.com/watch?v=cQ7STILAS0M (why Golang is Sucessful by Creator of Golang Rob-pike)
P.S.: I wouldn't mind having "Immutable Types", "Reference Types", ADTs, etc. in Go. But not if it means abandoning simplicity of the language.
git clone --depth=1 https://github.com/gcc-mirror/gcc.git
cloc gcc/gcc
{ "SyncDisabled": true }
into /etc/chromium/policies/managed/test_policy.json (for debian linux) seems to do the trick for now, unsure how long it lasts...
see: https://www.chromium.org/administrators/policy-list-3#SyncDi...