strong. I don't want to say "failing" just very poor memory and the like caused by very poor health. One case is a man who was in the tech industry years ago, but that doesn't mean that as his mind was harmed by the effects of illness he could continue to make sense of Google's ever changing interface. He didn't have a problem with mail so much (he used thunderbird, so that interface wasn't changing), but he couldn't navigate Google's changing phone service interfaces. Combine that with poor eyesite and problems with phone drivers that occasionally have to reload ... and there would be days when he had no phone service until someone came by and fixed his computer.

Keep in mind that there are people (once again the same man) who at times find simply dialing a phone too hard. Maybe they're too slow for hospital phone that gives you 20 seconds of dial tone then gives up, or worse gives you 20 seconds but no audio cue like a dialtone.

For such people you need interfaces designed differently than ones for average customers. You need interfaces that NEVER change. You need interfaces that have no time-outs. You need interfaces that force modal interactions rather than assuming that the user will NOTICE something.

the SJW took over 4chan? Oh God. What a massacre that must have been.

1. Hire that Taylor back or
2. Explain why she was fired

They've done nothing at all. And the only thing to apologize for other than firing a well liked person for no apparent reason is the fact that Pao laughed at her users to their faces. And no one is going to believe that she means an apology for that.

Typing this in Microsoft Bob.

Pure functional programming is pretty horrible too.

Take the classic book, "numerical recipes in Fortran"
( http://apps.nrbook.com/fortran... ) and try to convert all of the routines in there to pure functional style with no mutable variables, structures, arrays and no non-recursive loops.

Big step backwards. It will be horrible, it will obscure the code and it will run slowly.

It's funny that computer science doesn't build on old successes. They had good computer languages for doing math going back to the 50s but the latest and greatest bullshit being pushed in academia can't even do what they did in the 50's well.

I don't see why you can't have multistage compiling so that you can use the full power of (whatever language) at "compile" time.

You should be able to have mutable data structures at compile time.

You should be able to have tables and arrays.

And custom file and network io.

Security hole? Like running a bash script isn't a security hole.

Metaprogramming is wonderful. C++ templates are horrible.

"Captain, you're asking me to work with equipment which hardly very far ahead of stone knives and bearskins. " - Mr. Spock

Now write the screenplay!

Nonsense.

No one should ever have to work with C++ metaprogramming in their work.

It should not be encouraged. It's a horrible dead end. Sadly it isn't the only dead end in computer science.

It's also that C++ requires so many workarounds for template metaprogramming, so many help libraries, so many types, that writing, say template metaprogramming library that plays nice with Boost takes an infinitude of time and detail.

Syntax isn't the majority of the problem. The rest of it is even worse.

someone was asking for the luajit implementer, Mike Pall, to add copying data structures as something optimized by the compiler and he was told that not sharing structures was a "code smell"

Oh God. The implementer is so out of touch and focused on low level efficiency that he doesn't recognize the basics of reliable programming.

I've done that sort of metaprogramming. Years ago I wrote a compile-time Lisp interpreter. It's a HORRIBLE language.

Look, say you have some advanced feature. You could write a library in scheme - it will take you 1 day to a week.

You could write it in C++ templates. It will have a worse feature set than the scheme version, it will be much less readable (not that scheme is readable) and much harder to use. It will have unusable error messages. And a mockup version will take you months to write.

Getting your mockup embedded in Boost and working well with it will take the help of a bunch of experts and a two or three times as much work.

If you want it included in the Boost libraries, you'll need a couple years of work integrating it and getting it approved.

Horrible.

old stuff is old

in 1953.

That said, Barry Rubin was a disappointment to me. He spent the last few years of his life inciting the tea party tards on PJ Media throwing mad tantrums over Obama, afraid that anyone who doesn't seem 100% deferential must be working for Satan himself and bringing the final Holocaust.

you