skysight-inc/HackerNews huggingface dataset:
It's because some people really do like complexity.

They like writing 200 pages of documentation. And some like reading it. They want complexity. Keep adding stuff.

I remember reading one of the Windows programmers' hero's writing about some massive document of several hundred pages he wrote while on the Excel team at Microsoft and being overjoyed when he learned Bill Gates had actually looked at it.

I remember reading a post by some programmer on Sitepoint boasting about his program that was so complex it would make your eyes burn, or something like that. He was bragging about this.

I recall all the people in mailing lists and forums who get annoyed when anyone talks about conserving memory or disk space. The reason? Because these resources are so plentiful we can afford to waste them. That is a truly great reason. Brilliant.

I once had a colleague who said software is like a gas. It expands to fill space.

There are a great majority of prorammers who are not only OK with this state of affairs but they seek to preserve it. They get defensive when confronted with spending effort to simplify something.

There's a lot of discussion of simplicity that is just lip service. The truth is, simplicity is not easy. It is not a matter of adding more stuff. And we know programmers are lazy. Simplicity, real simplicity - removing stuff, would make many programmers uncomfortable. It would remove them from their comfort zone.

Simplicity is not burying things under five layers of abstraction so that it fits someone's preferred way to model a solution.

Simplicity is taking away things that are not essential until nothing further can be taken out.

It is cutting things down to size.

Achieveing simplicity means reducing someone's 200 pages documentation or their dizzyingly complex program whose source "will make your eyes burn". It may include using compact symbols instead of someridiculouslylongfunctionname. It means some stuff that someone spent time producing must get cut out.

The creators of complexity are not going to be happy with this. Because they like complexity. They like verbosity. It's comforting. They detest what appears to be cryptic.

That is the price of simplicity. To achieve it in today's programming environment involves offending some people. As such, we avoid it. We discuss it, but we really just dance around it much of the time. Let the complexity continue. We can pretend more abstraction equals more simplicity. Be happy, be productive and have fun.

Meanwhile the connoiseurs of simplicity are marginalised, often leaving them to write occasional blog posts like this one and to work on their simple projects in relative isolation. Embedded programmers know the feeling. Those who appreciate simplicity, and really do trim things down to size, are not the majority.

Keep posting those articles on Forth, hoping someday people might catch on.
Kickstarter is starting to fill this gap.
I had a similar reaction to libpng and attempted to write the simplest orthogonal decoder:
https://github.com/martine/sfpng
> * Officers will be able to turn the cameras on or off at their discretion.*

That part seems to render much of the experiment useless, sadly.
There are a lot of claims made here with regards to how end-users will effectively like to download and try apps from the metro store and take the time to write a good reasoned review about their experience.

Given the average response i've heard from end-users however, i somewhat doubt this. Most people i've talked to simply hate metro. Looking at other app stores, most reviews i've seen are low quality and emotionally driven.

Will be interesting to see how it all pans out.
The whole point is that the customers are getting something in return. They open their mobile device and look up which venues have people at the moment, so they know where to go. In fact, it sounds like that's the only thing this app does.

The only problem is what rdl said--that some customers might think the cameras are actually doing some kind of facial recognition and storing the results (which you wouldn't get from the regular security cameras already at those places) as opposed to just counting how many customers each place has. But then again, customers who aren't going to trust the maker of this app might as well assume that the government is also secretly connecting all street cameras to facial recognition software with huge hard drives to spy on us. Which could be true, but if those people are already willing to go out in public with their faces oncovered, they shouldn't be further afraid of going to these bars.
Never deal with DNS propagation again
That's very alarming, but also pre-exists this DOJ precedent. Hopefully this gets tested and validated in court soon.
There is a great presentation [1] by Rich Hickey about simplicity. He makes a point in keeping the words "simple" and "easy" semantically separate. This post is a wonderful example why that makes lots of sense. None of these examples really show anything that's decidedly simple. They're all about ease of use and backward compatibility (which is a particular case of ease of use).

It seems like "easy" can be further subdivided into several useful and objective categories. Clearly, libpng was only concerned with some aspects of "easy" (portability) and not others.

Also, I absolutely hate the kind of fatalism you often see in SE articles. "Oh, gosh, nothing is really simple, nothing really is bug-free, nothing is really good, so you shouldn't even try."

[1] http://www.infoq.com/presentations/Simple-Made-Easy
Best Time to Shopping
Best Time to Shopping Save 30-60% on Quality products shop today, Savings end soon Best Time to Shopping
This. A lot of people forget that Elon Musk spent a large portion of his own money to fund new ventures from Paypal. Bill Gates is helping many disadvantaged people around the world with the money he earned from Microsoft. I'd also like to point out that a lot of these Internet companies contribute to charities, so the money isn't just a 100% flow up the hierarchy.
This flight on its own isn't "disruptive", but the process that it's a part of might be. The purpose of this flight is just to prove that the technology works. The process might be disruptive if it continues its cost cutting and space flight becomes cheaper and more accessible.
Ten+ Travel Tips – Things To Know Before You Go
No, because I don't understand the process they would need to measure, and neither do you
It's odd how this is the 6th definition. It seems "default" is used in this context the most, at least recently.
It's a private funded commercial flight that is cheaper than any other similar launch ever made by a government.
مسلسل مذكرات عائليه جدا الحلقة الاخيرة 
مسلسل مذكرات عائليه جدا الحلقة الاخيرة

مذكرات ,عائليه ,جدا, الاخيرة

http://tv.3uz.com/11708.html
Congratulations for having the only reasonable answer in the entire thread.
It's a step. This is the first time that a private company has ever docked with the International Space Station, a domain previously exclusive to a small club of federal governments.
Typically, they'll be offered options to buy stock for essentially nothing. Often there will be tricks though - for example it might take a couple of years in employment to be able to exercise all of the options.
http://plan9.bell-labs.com/plan9/

plan9 is more unix than unix. The Go language has channels which can be thought of as type-safe generalized Unix pipes. How cool is that?
This NASA stream is already live (the official spacex one is not yet). And it's showing an interview right now.

So there's something to watch while we wait for the launch.
In order to give an incentive for fruitful conversations, it would be nice if the numbers of answers to a post, and their scores, were added to the karma of its author. Something along these lines could work:

(sum (map (fn (score)
(if (< score 1) ; don't penalize users if answers are domnmedded
0
(+ 1 (floor (log (score))))))
children-scores))

This would only be granted to comments with a positive karma.

It could of course be computed offline after the thread has settled.

It would for reward people who ask questions that elicit either lots of answers or an highly upvoted one.

By using a logarithm, people would not be able to cheat by upvoting every answer to their posts (someting I automatically do out of courtesy, BTW, but many people don't).

----

Another thing: When the comments scores were visibles, people would rarely get more than two or three downmods unless they were obnoxious. There was a rule either tacit or explicit, I don't remember, not to downmod people lower than that, and if they were, it was corrected by other members of the community.

I have the impression that the score go much lower now, and are sometimes fatal to new users, who end up hell-banned and don't get a second chance. It may be nice to display the scores when they are below one.
Delhi Agra Jaipur Package Tour
Delhi Agra Jaipur Tour Package has three most popular travel destinations in India. On this tours package you will explore rich cultural and heritage destination of India.
Jaipur Car Rental
Rajasthan Car Rental Offer Car Rental Services in Jaipur, Jaipur Car Rentals, Car Rentals Jaipur, Luxury Car Rentals Jaipur, Mid Size Car Rentals Jaipur, Hire a Car in Jaipur, Hire a Cab in Jaipur, Valvo Service in Jaipur, A/C Bus Services in Jaipur, Taxi Rental Jaipur.
Walks And Walking in East Sussex - Free East Sussex walks and walking routes
Weren't those super-expensive? You know, the reason resistors are basic elements is among others that they're cheap..

I think a simple SiO layer, which is what this newest memristor tech is based on, could be super cheap.

Even if you can't build "big memristors", you could just parallel thousands of them in a single package. Then, they would start being approachable.

Besides, tiny capacitance hasn't stopped anyone from using the likes of varicaps, and huge inductance never stopped anyone from using an inductor. They have their place.

I, for one, want to see a discrete Memristor in all shapes and sizes. If we don't try it, and don't experiment with it, we might be shutting out 1/4 of all electronics.

Luckily, a lot of electronics companies do feel their responsibility as educators. That's why we have samples (I'll teach you to use my chip, and if you become an important circuit designer you'll use my chips in your designs), that's why we have lots of antiquated chips still in production (stuff like OTAs which is of interest only to miniscule hobbyist groups), that's why we can still buy devices in units.

I'm looking forward to it.
Well, spawn() and pctl() are actually more like a finer-grained fork(), without the necessity of, for example, O_CLOEXEC, or anything in fcntl. Between pctl() and Limbo's channels (on which Go's are patterned), a lot of what is required for security in "vanilla" Unix is unnecessary.

What I was trying to convey in the article (sorry if it was a bit vague) was that using functions available to the shell was the nice part, the actual advantage over regular Unix. That is to say, if a user passes '*[0-9]?.gz', you can call functions within the shell to handle the glob rather than having to implement them yourself, for example. The shell is also designed as a library, in other words. This includes things such as parsing sh's syntax, even.
Dragon: Journey to the ISS
It looks like the state of the art right now gives us absolutely huge devices that barely even make it off the ground. Does anybody have any confidence that a human powered helicopter could ever be practical for real transport? Unless we humans somehow manage to multiply our sustained power output by several times, I don't see this happening.
Why is each sentence on its own line?
In a similar tone, Sean Barrett stb_image.c is a good example - it's a reader for jpeg, psd, png, tag, etc. - http://nothings.org/stb_image.c

also a small writer - http://nothings.org/stb/stb_image_write.h - png, bmp, tag

on his page he has also small ttf reader
That is the NASA stream.
more disruptive than instagram or facebook, or both combined for that matter.
I don't think the average geek values simplicity all that much. We value power, flexibility, versatility. We value openness, interoperability, upgradeability. Simplicty? It's a distant 7th or 8th on the scale. That's why computers are the way they are, and we needed a company that really did value simplicity to create a new paradigm where users don't have to deal with libpng, winsock, antiviruses and other artifacts of the complexity that we, geeks, have wrought upon the world.

Edit: I'd go as far as to suggest that this desire for simplicity is a relatively new phenomenon that is closely linked to the rise of the New Apple... I personally didn't give a damn about simplicity (or didn't know that I did) before I got myself a Mac in 2007 or so. Since then, I've progressively raised simplicity as a top priority. Some friends of mine who are hardcore geeks too and never moved to Mac still don't care about simplicity. They also rarely use the slew of web 2.0 "simple" SaaS apps that have evolved over the last few years... They're happy with complexity, it seems (as I used to be).
Honestly, Merlin's meta commentary on the rest of the 5by5 network is what kills me, every time. I almost crashed on my way to work during the "King Marco" episode.
World Wound Care Devices Market (2012-2017)
Wound care devices market research report categorizes the global market on the basis of products and applications; forecasting revenues and analyzing trends in each of the submarkets.
Don Norman wrote a similar essay titled "The Trouble with UNIX" in 1981 [1], where he praised UNIX as an "elegant system", but criticised its commands for their "incoherent, inconsiderate design".

The greatest surprise actually is that Unix still lives on,
warts and all. The frustrations I experienced in the paper
were real and still exist today [1987].

In a similar vein, but also quite entertaining, is the UNIX-HATERS Handbook [2].

[1] http://books.google.co.nz/books?id=UqhjMVwYKJsC&lpg=PA25...
[2] http://www.simson.net/ref/ugh.pdf
You cannot be both simple and delux. LoseThos is not a general purpose OS. Nothing Windows can do will make it as simple and elegant and transparent as LoseThos.

Give-up! Yer fucked.

God says...

C:\Text\PARADISE.TXT

tongues;
In darkness, and with dangers compassed round,
And solitude; yet not alone, while thou
Visitest my slumbers nightly, or when morn
Purples the east: still govern thou my song,
Urania, and fit audience find, though few.
But drive far off the barbarous dissonance
Of Bacchus and his revellers, the race
Of that wild rout that tore the Thracian bard
In Rhodope, where woods and rocks had ears
To rapture, till the savage clamour drowned
Both harp and voice; nor could the Muse defend
Her son.

You cannot support legacy and be cruft-free beautiful.

God says...
C:\Text\YANKEE.TXT

tocracy, howsoever pruned, is rightly an insult; but if you
are born and brought up under that sort of arrangement you probably
never find it out for yourself, and don't believe it when somebody
else tells you. It is enough to make a body ashamed of his race
to think of the sort of froth that has always occupied its thrones
without shadow of right or reason, and the seventh-rate people
that have always figured as its aristocracies--a company of monarchs
and nobles who, as a rule, would have achieve
What insight does the author have to offer with this essay? It's easy to complain about complexity, harder to offer a simpler but equally capable alternative.

The author makes it sound like simple is easy. As if it's just a matter of saying no to complexity, like saying no to memcpy() whenever we have a memmove() that's good enough.

This is not the case. Simple is not easy. On the contrary, simple is hard. So you think "ls" has too many command-line flags; how are you going to cut the number in half? Which ones do we keep and which ones get axed? How are you going to provide for all the same use cases that those 35 flags were added for?

I'm not saying it's impossible and in fact I think it's a very worthwhile and noble cause. But it's long, tedious, hard work, and I say this as someone who has a nearly obsessive devotion to writing small and simple software.

Let me tell you what it's like to design small and simple software that is practical enough to actually use. The most important part by far is to leave out anything you possibly can. If there is a feature or abstraction that could be implemented on top of your software with equal efficiency as what you could do by implementing it internally, LEAVE IT OUT. The feature that seems so cool to you now is going to get in someone's way later on. Your attempts to be "helpful" are going to be the next generation's bloat.

This is where I think the famous Worse Is Better essay (http://www.jwz.org/doc/worse-is-better.html) goes wrong. To the MIT guy the "right thing" is for the system to implement complex recovery logic to hide from the user that a system routine was interrupted. And why? So the user doesn't have to check and retry themselves? The code to do this is trivial and can trivially be implemented in a library that everyone can then share.

The key to long-term simplicity is LAYERING. The lowest layers should implement a very general and reusable abstraction, and be as absolutely non-opinionated as possible. Layers on top can tend more towards policy. If a higher layer is too opinionated, a user can always drop down to a lower layer.

I haven't actually used libpng, but from a glance at the sample code that the author is complaining about I'm inclined to say that the author's complaint is misdirected. It looks like png is a well-designed, though very low-level API. Using low-level APIs often requires a lot of steps; this is because the overall task is broken down into its most primitive steps. Unless some of these steps are redundant this does not mean that the software is too complex. Rather it means that the author would prefer a high-level API instead of the low-level one. But don't demand that the lower-level API be hidden in the name of "simplicity" -- that will make someone else's life harder when their use case is not what the designers of the high-level API had in mind.
And yet the example give with Qt, stays with Qt only. I can't reuse any code written with Qt classes, unless I want to use Qt.

But I can reuse small libraries almost anywhere - zlib, libtommath, tomcrypt, lzo1x, etc. The smaller they are, often it's easier, and the less platform specific they use, or alternatively the less platform-specific primitives they use the more reuse.

Reuse in binary sense, or blackbox-ish sense. Not really extending them, just putting them to use as they are.
i liak ham, iz gud
self suppert the ham liak scenario, iz gud
Because it's a very short hop from what's described here to full-on tracking, and some marketing company knowing where you are, what you're doing and who you're with at all times.

It's a similar situation to Google's street view - sure, it's in theory in the public domain, but when you start aggregating this sort of thing and making it searchable, it's different.
The gender pay gap is a complete myth and noting but propaganda. In fact, accounted for hours, women actually earn slightly more than men. Seriously, if any employer can get a woman to do the same job as a man then why on earth does anyone even bother to hire men in the first place?
真人公仔
Well, if you ignore the fact that 95% of the US space industry is private contractors then sure. I mean they are only going because they are being paid to go there.
Cheap Web Hosting
Web hosting from just £1.50 a month and FREE domain name. The most affordable hosting solution in the UK. Whether a personal page, a blog or even a web store, you will find the perfect solution right here. One last thing, you get a FREE domain on all packages when you sign up for at least a year!
No Execute is one of my favorite (semi-) blogs!

I couldn't agree more about the Atlast writeup. I'm glad for the vast proliferation of Lua, if for no other reason than it has made scriptability a library. I can certainly believe you've never heard of my fork. I actually feel bad because it's still "in beta", being a work in progress. I've been meaning to send a patch to Mr. Walker for the 64-bit issues, but there's always another bug or feature in the way, and I've held off on a "real" (tarballs on a server, documentation) release until I ping him and fix some bugs.

Regarding 9atom, I don't recall any difficulties booting from USB, but it was a while back, and I didn't quite get it installed. I've been running 9front for the most part when I run Plan 9.
I always love to learn from other people success or failure, especially customer development, which is my field of expertise. so yeah, you can count me in.
to me at least it proves that such a complicated project can be pulled off by private company that in majority is not dependent off the government.

and hell yes, I stayed up to see it live!!
They are carrying the mail for the government right now, and will eventually use this experience to go farther on their own.
Slow new day?
You really don't know what you are talking about, Android is only originally built around the Nexus device Google is launching with the particular version of the OS, it is a huge effort to make compatible drivers for all the different pieces of tech that goes in to the different Android devices. Hence why it took so long for the Nexus S to get Android 4.0 Ice Cream Sandwich, not to mention the plethora of other devices still waiting on a port.
Logic is completely absent from your argument. Imagine you are a your typical US high school graduate, and the message you've gotten for years was that women are better at anything, that they are more likely to finish school, get a degree etc. pp. Somehow, you think you want to fight the odds, and have a look around, wondering what you might study. You find that many departments at university lack rigor and due to your preference for logical thinking you go into science/engineering because you find them more welcoming than, say, male-bashing on an institutional level like in Gender Studies and humanities.

The claim that there is a shortage has nothing to do with the fact that tech is more welcoming to men. It's two completely separate issues. Or do you think that just hiring a bunch of unqualified women (or men) will be what solves the problem? There is a lack of skills, not bodies, and it takes some hard work to acquire those skills. Because there are not enough skilled people around, and because tech is booming, there is now a shortage. (I doubt that it's as bad as you think it is. Just look at the Dice board for plenty of disgruntled IT people.)

Maybe we should encourage more men to actually consider college. What about that? Sure, it doesn't gel well with your feminist agenda.

Lastly, do you actually work in tech or are you merely on a PR trip? Sockpuppets are quite common these days and I wouldn't be surprised if some "think tank" had sent a couple of drones to pollute the otherwise intelligent discussion on HN.
Class makes the income, not the other way around.
Top 11 Funny Reactions To Facebook IPO
ARGO RMT
The top 8 web standards myths debunked
Virtual machine is not required for sandboxing C++ apps in 21st century.

[1] http://code.google.com/p/nativeclient/

[2] http://www.cl.cam.ac.uk/research/security/capsicum/
What you are arguing for is efficiency, not simplicity. Cryptic and highly compact routines, symbols instead of telling names and memory / disk space conservation beyond the point of diminishing returns, all increase complexity, rather than reduce it.
Kicks for Good Cause in Middlebury
Self Defense Training for Women: If you want to develop your physical, mental and spiritual strength then contact Hoosier Tae Kwon Do, Inc. We Provides Taekwondo Training, Self Defense Classes for Women and Self Defense Training for Women.
I'm reading through No Execute now and it's fantastic so far.

Thanks again for redirecting our attention toward some quality stuff.

I'm psyched to get some version of Plan9 running on a netbook. Plan9 is work of art.