Hacker News Reader

Comment by panic | Hacker News Reader

I can't believe anyone is still considering $HYPED_TECHNOLOGY in $CURRENT_YEAR. We at $NO_PROFIT_STARTUP gave it our best shot, but the bugs they mention aren't as small as they seem -- they completely sank the project. At this point it's clear that $HYPED_TECHNOLOGY is falling behind on both adoption and ergonomics to $TRENDY_TECHNOLOGY, which handles these issues in a much cleaner and more scalable way. We'd strongly suggest anyone considering $HYPED_TECHNOLOGY to take a closer look before following the advice in this post.

View on HN

Right, and those cowboys at SFAMOUS_COMPANY obviously haven't read the latest blog posts that clearly show $HYPED_TECHNOLOGY doesn't support $HIPSTER_PARADIGM in an async I/O functional stackless copy on write environment, meaning $FLASHY_LANGUAGE can't be used with dependent types unless you don't mind your static analyser giving false positives every time you try to multiplex coroutines in your template meta-programming frameworks; what were they thinking?

You all have it so wrong! We should go back to $REALLY_BASIC_TECH that we already had in $HAPPIER_TIMES and clearly solves your $OBVIOUSLY_SIMPLE_USECASE.

Here's the place in Englebart's 1969 Mother of All Demos where $SUPPOSEDLY_NEW_TECH was first shown. You kids have done nothing for a generation.

I don't know why we are all still talking about $FANCY_FEATURE. [Lisp|Erlang|Smalltalk] have been doing this for years.

Look man, it's relevant because $ESOTERIC_LANGUAGE is much harder to hire for than $MUNDANE_LANGUAGE that is taught in most CS programs now. It's not like anyone with 4 years of post-High School education can learn anything. And we certainly wouldn't invest any time in teaching them anything. All of our graduates jump ship to $TRENDY_STARTUP after less than 2 years with us so they have no loyalty anyway.

If you've been following this industry long enough, you'd know that $REALLY_BASIC_TECH was introduced in $HAPPIER_TIMES to replace a solution that is conceptually very similar to $HYPED_TECHNOLOGY. If you wait long enough there will be a new spin on $REALLY_BASIC_TECH once the next cycle of computer hardware becomes ubiquitous.

Exactly! Everyone knows that $HYPED_TECH is just reinventing the wheel that $OLD_TECH already invented, and back in those days we were handling hundreds of $MULTIPLES of users a $TIME_UNIT on a single machine with only 64 ${SI_PREFIX}bytes of RAM over a dial-up connection.

I'm excited to see what will go on this page for this thread: http://n-gate.com/

are we seeing the start of true meta-forums ? Place where we don't talk about one subject, but just have generic conversation about ranges of topic in one conversation ?

Precedent: http://bash.org/?23396

export MEDIUM=$MESSAGE

Line 1 Position 28: "SFAMOUS_COMPANY" identified not known. Perhaps you meant $FAMOUS_COMPANY instead ?

I'm still waiting for an anime that adopts programmer-lingo for its mecha-fight scenes technobabble.

We hear you. We at $SOON_TO_BE_FAMOUS_COMPANY spent $N_YEARS developing our own version of $HYPED_TECHNOLOGY, because $HYPED_TECHNOLOGY didn't quite fit our use case in that we couldn't understand how to operate it well on our environment.

Look for our 25 part blog series at http://$SOON_TO_BE_FAMOUS_COMPANY.com/blog/#WEAREFUCKINGNINJ... on how to operate our version of $HYPED_TECHNOLOGY well on your environment.

Did you consider $EVEN_WORSE_HYPED_TECHNOLOGY? Based on a keyword match with some academic paper I didn't understand and my poor understanding of virtualization, containers, and latency, it could solve all your problems.

I cover this in my article titled "$HYPED_TECHNOLOGY considered harmful".

We burned through $HUGE_AMOUNT_OF_VC_MONEY before we realized this.

Reply on news.ycombinator.com