from unix to c to java to opengl (or whatever gl fuck). and these idiots say, well but it is fast! it's efficient! the problem with these fuckheads is that they don't really understand math or meaning of efficiency, they just know micro-tuning and memory address.
Conversation
Notices
-
∑ XahLee (xahlee@noagendasocial.com)'s status on Friday, 16-Feb-2018 00:11:27 EST ∑ XahLee
-
∑ XahLee (xahlee@noagendasocial.com)'s status on Friday, 16-Feb-2018 00:11:40 EST ∑ XahLee
but today programer, i think the hard-ware based mindset is slightly going away. Partly because, new generation don't know it at all anymore. (e.g. witness the js frontend codecamp fucks.) Partly because, langs like haskell, or golang, are teaching programing to understand the separation of efficiency and abstraction concerns.
-
∑ XahLee (xahlee@noagendasocial.com)'s status on Friday, 16-Feb-2018 10:31:23 EST ∑ XahLee
one of the example typical hacker get confused is Bitmask Used as Boolean Parameters. It's a example of pseudo-efficiency trumps language design.
Programing Language Design: the Hack of Bitmask Used as Boolean Parameters
http://xahlee.info/UnixResource_dir/writ/bitmask.htmlthis happens for languages up to about 2005, but not after.
-
∑ XahLee (xahlee@noagendasocial.com)'s status on Friday, 16-Feb-2018 10:34:15 EST ∑ XahLee
1 example of pseudo-efficiency trumps language design is Bitmask Used as Boolean Parameters. See
http://xahlee.info/UnixResource_dir/writ/bitmask.html
typical hacker get confused by this, and defends it vociferously.
this happens for languages up to about 2005, but not after.
-
-