froh42

So I prefer to choose a language where I can nicely express the intent of what I code. Java is a good compromise, because it's easy to follow (even if it's quite verbose and mainly stuck in the world of nouns).

C++ is hard for that. It's an extremely complex language that got extended over the years and it takes a quite long time to master, for example compared to Java.

Yes I know, C++ is more "capable" than Java but it's not efficient in the hours-spend-per-solved-problem way of things.

Yes I know, there are you C++ whiz kids out there who are insanely fast using the language. But I experienced teams using it, and in a team C++ does not scale well. Adding more and more features to it makes it a cool language, but not one which I like to use in my day job.

And I'm not sure what I'd use it for. I use Java for the day-to-day boring "enterprise" world, twiddle around with dynamic languages for the hobby (yay to the recurrence of lisp!) and for close to the hardware stuff I'd use plain C - which is a not so bad language at all. And it's hard to beat speed-wise, writing C++ that keeps up with C is possible but not trivial.

And if I'd have to look forward I'd check out rust or go or even look at some really mindbending stuff like erlang. Parallelism can't be evaded in the modern world and using a language tailored to that is a great thing. (Yea, I'm sure there also is a C++ library implementing the actor model).

http://www.ndr.de/fernsehen/sendungen/extra_3/extra-3-Der-Ir...

Oh and the song with english subtitles: https://www.youtube.com/watch?v=R2e2yHjc_mc

By the way, what's the amount Wired would make on ads if I read that article? A few cents? That's probably what I'd pay given a good micropayment system for reading that single article. I'm not interested in a subscription (and even less in my personal data being in their database along with that subscription).

Those things never describe real workloads - in such a view a Porsche is always better than a truck because it accelerates faster. Tough luck if the workload is shipping 20 tons of manure. Put that in your Porsche.

It's just stupid to reduce such a portal to only questions that can be answered by RTFM.

Questions that need discussion due to missing information should be voted away, I agree on that. But some allow subjective answers - and those are frequently those that require experience. (What's the best way to solve this-and-that? It depends, in situation a use solution A because, in situation b use solution B because, ...) Such questions typically are being closed by the moderators as well. And frequently the person who asks is not aware of all the factors influencing a solution, so there's a lot of useful information in such questions.

- Either they couldn't find it. Then my answer will help. - Or they were to stupid/lazy to search. Then they're not worthy of my ire.

By the way, showing a talented beginner where good documentation is - I think that's frequently the best way to help them along.

From time to time I still use it, but for me it has jumped the shark.

https://en.wikipedia.org/wiki/Tiling_window_manager

While feeling the shortcomings of a window system, I never felt like I could productively work with a tiling manager, since I frequently overlap windows as a mechanism for easy access ... and there are lots of popup windows I don't want to cover the main application.

Oh yes, and I purposefully keep my Mac apps out of Full screen mode (and use a keyboard shortcut to maximize when needed, keeping out of full screen).

And if you start considering the computer architecture think about caches, memory latency and bursting first. Use a cache-conscious data structure.

Optimizing at the register level is ridiculous, this is the least place where you get significant returns for the effort you spend.

Oh, and make it correct first, make it fast second. Use a profiler.

Writing code generators, inventing the wheel over and over again.

However there are several factions (pro- and anti-Microsoft) at work and only time will tell what happens.

Some years ago I had the same idea and realized something like that with the C-Preprocessor in a C++-Codebase.

When did my Todo's expire? AFTER testing, just before a new release. With my idea of exipiring Todos I created a major pain in the butt for the team.

It would be different if some other "sort of" alarm would be raised when TODOs proliferate, but a failure in the code is not a good solution. (i.e. hook a todo checker into your contious build system, let the nightly build raise hell when there are too many todos - but do not fail the production code.)

But it's scrolling web pages again, which seem to be all the hype in 2013 just as flash intros have been some years ago. Aren't there any nice templates NOT following current styles and offering structure for content?

I have to update the web page holding my CV as I have updated it in 2006 the last time. Woah, how dated would my page look in 2019 if I use a silding page now.

Oooh, and I just imagine hacker news as "2013-glitz" page. Bling, bling, look we can scroll stock photos from a cheapo stock photo site. One carousel per story, two HERO UNIT words of headline. This story would show some cool young guys at a mac, one pointing, HERO UNIT reads "Starter HTML."

Scroll down half a mile to see the next story.

BTW. any predictions what the post-flat-parallax-photo-sliding web trend will be?

Sorry to be a party pooper, but I saw one scrolling page to many and I'll rant about these from now on regularily. The last straw that happened to me (a Java developer) was http://spring.io/. It's so low on content that its information-vaccum might endanger the universe by sucking in all other data leaving all but a low radiation void.

Now it turns out our friend betrayed us. It views us as the enemy. Everything imagined as a paranoid bad joke is true.

But the worst of all: In the USA there is no outcry. The people don't even care about this. Thus: We are not seen as friends.

Greatly done, USA. From now on you are alone. Fuck yourself.

If this feeling ever stops it means I've stopped learning and stopped personal progress. I'll stop coding that day.

Thankfully it didn't go away for the last 30 years I was programming, so it will probably stay with me a little longer.