skysight-inc/HackerNews huggingface dataset:
I think we parsed OP's original point differently. He said: "Its the same for the USA as it has 126 Trillion in unfunded liabilities. In the next 30 years, the US will face the same problems as cities are today."

The term "US" here means "United States i.e. the federal government" not "United States as a whole country," since in the second sentence it is comparing the federal government's problems to those of cities.

And the reason I think OP overstates the severity of the problem is because state finances aren't your problem if you don't live in that state, while federal finances are everyone's problem. Essentially, what OP is saying is: "even if you don't live in Illinois or California, you'll be facing the same problems in 30 years because the federal government has problems that are just as bad." But the federal government's problems are a lot less bad. Which is good, because you can move out of Illinois or California much easier than moving out of the U.S.

> Also, if governments are serious about honoring pensions, they should be accounted for on par with their bonds

The crucial distinction is that re-negging on bonds affects your finances going forward (increases borrowing costs), while re-negging on pensions does not.

> Framing it as "like tentative road construction" is trying to have it both ways

I think you misread my post here. I didn't say pensions are like just another public service, I said Medicare is, unlike pensions. Nobody bargained for a particular number of Medicare dollars in 30 years in return for doing a particular job. That's why the Federal government is in better shape--most of its obligations are things that aren't considered (legally and politically) guarantees in the same way as pensions.
Another "write your text here" and nothing more app.

I'm not questioning the usefulness of this, but why do we have so many simple apps like these? People writing code to do the same thing over and over again, aren't you bored?
Many non-networked systems neither need nor support updates.

If your system is networked, there is always the risk of security updates being required. This can be minimised by extreme effort, but if you have to support SSL/TLS? At least you need a way of deprecating the vulnerable ciphersuites.

Would you want a web browser with zero updates? It would gradually become a handicap.

For consumer equipment, "zero maintenance" means "disposable": in the event of trouble, throw it away and buy a new one. Good for manufacturer turnover, not so good for the environment.

The other option is simply 100% outsourced maintenance, which has long been an option. Some mainframes would even do their own fault reporting, all you'd have to do is say hi to the technician and let him into the building.
> I really wish more languages picked up S-expressions, because they're easy to machine-generate.

This could easily be solved using a well-defined AST and a simple s-expression based AST printer/parser. That not many languages do that (one notable exception is Julia) is a shame!
I heard about this effect before....great read. I am absorbing as much as I can!
Prior discussion: https://news.ycombinator.com/item?id=9908312
> I, well, one my companies, have been using mongo for a while without any problems. I cannot comment about is reliability but as a business tool, in the niche area we operate, it served us well.

The issues I listed provably exist. That you haven't run into them yet doesn't change that - and quite likely, you might not even know whether you've run into it.

Losing data or having your database open to the wide internet, for example, are two scenarios that you will likely not be aware of unless you explicitly test for them.

> I've got nothing against relation databases but there are not a solution to every single problem.

And if you'd read my post carefully, you would've seen that I make no such claim. They do solve many problems, however.

> Heck, why not decide first if you can use flat files?

Flat files are rarely the correct solution. Race conditions ahoy!

> Do you really need to query and join. Not all problems require that sort of thing.

Many do. And even if they don't, MongoDB is still not the right choice.
Rank and Bank: Link building that works (SEO)
Neither. I think something entirely new will need to come along in order to dominate the hiring market.
Google Answers 2002-2006
Google Wave 2009-2010
Google Reader 2005-2013
The list goes on

Google has been like this from very early on. I won't be surprised if I wake up to the news that gmail is getting the axe should google decide that the product is no longer commercially viable.
Now with PostgreSQL 9.4 there isn't really any reason to use MongoDB (JSONB is better suited than BSON). For any other use CouchDB.
> as good as Postgres, but with JSON (!).

PostgreSQL has supported JSON for a good while now, I've even explicitly linked to it in my post. And no, MongoDB is certainly not 'as good' - many of the problems listed simply do not exist in PostgreSQL.
> The message warning you that 32bit builds are not safe for storing more than 2GB of data is larger than the download button itself. If don't see this, you should probably be not in charge of storing any data anyways.

That's all well and good, but reporting writes as successful and silently failing when your data ticks over 2 GB instead of throwing errors or doing something useful like that is more what the complaint is about. Obviously, you could set up monitors on your data storage and alarm if it reaches 1.75 GB, but if you're mature enough to do that, you're mature enough to use a real database solution.
Thank you. I'm on Team Treehouse at the moment for Web Dev track. I will check out codeschool too.
The author is cataloguing some of Mongo's "paper cuts," i.e., issues for which warnings and known workarounds exist but that really make the development experience less pleasant.

For MongoDB's actual limitations, read aphyr's Call Me Maybe series.
Because people have slightly differing taste and opinion about how such an app should work and what it should look like. And because it has a relatively clear scope, many people actually build them.
clicked on the link hoping it would explain why I might need to use currying.
This was why I was interested in knowing if Go language is ready for system admin stuff:

http://radar.oreilly.com/2013/07/go-programming-language-for...
What anime community do you use now? r/anime was always terrible. I've "outgrown" 4chan, but /a/ is still the best community I know of. I mostly just do my own thing and talk to my few friends who also watch.
ElasticSearch is trivial to set up, especially if we're talking about a small project like a hackathon.

It's not without its problems but ES's first-fifteen-minutes story is pretty good.
“Do I want to work 60+ hour weeks and have barely any vacation time?”
“Is there more to life than work?”
...and the rest...

It's pretty normal for people in their 20's to consider all of those questions, regardless of passport status.
FTA: "Inside Carswell’s visiting room one recent afternoon, Jones opened the tattered blue Bible she brought in with her 16 years ago and turned to her daughter, Clenesha Garland. She gently pushed a strand of hair off her daughter’s forehead. They read the Bible together when Garland visits every couple of weeks."

Sometimes I wonder whether these sentencing laws are influenced by religion.
Yeah, sorry about that. I realized afterwards that a better title would probably have been "Writing a Curry Function in JavaScript".
yousoundmad
I recommend setting aside these scare stories about mongodb after you read the instructions on how to check that writes succeed, and look into replication. Sure mongodb has its problems but a few years ago I helped a customer run mongodb at very large scale.

Meteor.js is a fantastic development system (if you can live with needing sticky sessions and you need its features).
> These things are designed for use by people running them on servers that are not directly exposed to the internet.

Just as well internal attacks and fraud are never a thing, and pivoting attacks up a chain of successively less secure components never happens.
There would be. Because someone who only knows html and css has never really encountered an if-else statement in there entire lives. It's really hard for me to consider someone who doesn't know what an if-else statement to be a "programmer".

Perhaps, though, I can still refer to these people as "developers."
The entire library in the name of the library? Crazy! How would you input that on the computer when you wanted to reference it, though?
Second-order retweets as a measure of retweet quality has been a thing since as far back as 2011.
About 80% rewrite: it is poor abstraction problem rather then vendor lock-in one
That depends on your browser.
Hi there -- please share how one can find out how many websites are sharing a host via Bing.

Thanks!
Right. I am so sick and tired of MongoDB defenders saying "read the manual" after aphyr has found multiple faults in MongoDB that directly conflict with the documentation.
A database built by people who are careless with my data is not a database worth paying attention to, even when particular problems are remedied.
That's different. What do you call someone who knows html and css but no javascript? "Designer" might be the industry term.
In fact it's quite literally the opposite of true.

Edit: In the sense that there are many, many well-regarded and used NoSql databases.
Not in any way "Hacker News"
No matter how much of an outlier each one of these cases is, this is fucking tragic. Life in prison was harsh for the Ulbricht case, she had a single count.
ElasticSearch takes less than 5 minutes to set up, and you literally just perform HTTP requests against it. In my opinion it is much easier than setting up MongoDB.
That 32bit startup warning has been in place since 2009. It was in the README in 2008 (IIRC, pre-1.0).

https://github.com/mongodb/mongo/commit/b3322b86a014683018ac...

There's plenty in Mongo to complain about, but grousing about the 32-bit limitation just makes you look like you're bad at reading introductory documentation.
I've used MongoDB recently for the first time, for an internal project. Being schemaless, I believe it did speed up development time significantly, and allowed me to add stuff more gradually, but you could say that's just a way to indulge a certain laziness of design. Now that the project has matured, stepping back I can see how a relational database would be a better fit, but if I had used a rdbms from the beginning I might have not "shipped" quite as quickly. Swapping it out for a real rdbms will mean changing a couple of classes anyway, nothing dramatic.

So uhm, I don't agree that it's not good for prototyping; if your final code ends up having a decent abstraction level, it should not matter what you picked on day 1 anyway.
If you don't need to QUERY, just use a file system.
Desktop sites started doing that too. See the wired story on Russian maps, I had to scale it down to 66% to not feel like I was 3 centimeters from the screen. I don't get it.
The images on those magazine covers shown in the article bring back memories of life growing up in the Arizona desert long before it became so populated.

As a kid I could hike for miles in the wilderness, among huge saguaro cactus and all the other living things inhabiting the desert. Over the sequence of many seasons the subtle beauty of that environment gradually revealed itself. The desert contained its own unique spirit which Desert was aiming to convey. I'd rate it a success, the photos were accurate, capturing a glimpse of the desert's essence.

Another magazine, maybe more familiar, is Arizona Highways, first published in the 1920's. AH also presented spectacular pictures of the state's assets, which were a treasure, though it had a more "glossy", promotional style to it. My mother worked for AH for many years (as a proofreader), so I suppose I'm predisposed to rate it favorably, though I admit it's possibly not as refined as its rival.

Loving the desert was not easy, an acquired taste for most. The magazines were a beacon for a subset of readers who were drawn to explore the region, and settle there. The incredible sprawl that now engulfs the Southwest deserts has disturbed the environment and diminished its value. We should hope the few who still care will preserve what remains of the desert as it was a century ago.
I think Linkedin: More intelligence data on the prospective job candidates and employers and head hunters will gravitate towards that.
Hey bootload, you are right. I AM more than my job. I just like to throw that in there once in a while. The mistake is people reading and taking this literally, as if I can't do anything else or my numerous life experiences don't amount to anything when starting a Startup.
Relationships in MongoDB are commonly stored as ObjectID references, and (at least on node) the default Mongo client (Mongoose) makes you write schemas to enforce these.

I think Mongo is awful too, and I'm sure there are problems with this approach - I'd love for someone with more DB knowledge to go into details - but saying there are 'no relations' seems to be an oversimplification.
Also the day I joined. I think it was the day PG posted it on reddit.
One example is it would allow you to pass arguments to callbacks other than those passed by whoever is using the callback (my example because it's the relevant part I use most frequently)

There are infinite examples for this sort of thing in real development scenarioes
I rarely see sites where I cannot zoom in. Many do not let me zoom out though. Instead, they display what feels like 4 words per line.
That would be the other one, Firefox.
Show HN: Engineering Entrepreneurship – Tic Tac Toe
I haven't done sysadmin work in years and years, but I don't see why that article makes any case at all for it.
Especially if you're doing any kind of transpiling (es6/7 features).
There's a mongodb JS API driver that talks to Postgres IIRC. Postgres 'json' data type is also apparently faster than Mongo. Anyone played with it?
Yeah, that contributed, but it wasn't any worse than most other CRUD apps I've seen.
It’s often the case that writing a bit of infrastructure for something is a valuable exercise in and of itself.

So we can debate how often you’d need to curry a function, but I feel safe suggesting that writing your own curry function (or reading along with an essay that does the same with lively interest) is valuable.

Same with things like classes and mixins, there is now syntactic sugar for such things, but it’s always a good thing to have written your own MakeClass function at least once.
This points at a bigger issue, to be honest: it seems MongoDB is popular purely because of marketing and intentional hype.

Evidence for those claims that MongoDB is "fast" never materialized, nobody really knew where the claim came from, yet it was constantly repeated. They sponsor a lot of hackathons, and so on.
This made me giggle like a little girl though.
Mongoose isn't the default Node.js MongoDB driver, though it is very popular.
That's not helpful in this case. Most of lines points to 1da177e4, which is:

commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
Author: Linus Torvalds <torvalds@ppc970.osdl.org>
Date: Sat Apr 16 15:20:36 2005 -0700

Linux-2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it.
...
Not sure about producthunt, but you should be ready for what people uses to call the "network effect".

You cannot control who links and who clicks on the internet.

Architectures like AWS, with elastic databases, server instances, load balancers, bandwitch, ELBs and iops, auto scaling groups, etc... elastic horizontally and vertically, pay peer use, free tier available.

You can scale manually when needed (pre-scale-up and post-scale-down), or based on ELB visits, CPU/ram/load of instances behind the balancer, etc...

Just be sure to don't loose your logs if you need them, when instances are terminated by scaling activities.
I mean, a bloom filter isn't super difficult, but it's also probabilistic instead of deterministic.
> "In light of the law and the guidelines and what the court heard during the trial, I know Judge Solis followed the law. He's a very fair man."

This is where the rubber meets the road. We all need to think about what type of world we want to help build.

Maybe someday you will wield a small amount of power in some situation, and it will be very clear what you are expected to do, and you will have the burden, opportunity, privilege, honor, to refuse to be a part of it. That you will not put bricks in place to make the world worse, that you will defy expectations and put bricks where they actually belong.
There are a few. Mongo has excellent integration with Hadoop and is becoming very popular in the big data analytics space. Likewise it is gaining traction in the EDW space as a result of their partnerships.

Also it stills remains one of the simplest databases to setup and use making it still my goto for hacks/spikes.
Abstracting over your database only makes sense if you're writing something that's lowest common denominator. If your application runs equally well on MongoDB and something else you either are running poorly on both or you are spending a lot of resources on writing your abstraction layer.
OP here.

That was kind of my intent (learning exercise rather than super practical real-world technique) -- but I'll admit I probably could have picked a better title.
The article mentions CouchDB and other schematic-less, document DBS, which should be equally good for prototyping but suck less.
I think that contemporary platforms can't have distinctive graphics / audio where you can look at a screen and say "that's a ZX spectrum game!" or hear a buzz and know "it's a C64 tune!". So the distinctiveness gets limited to the physical design of the device (for the looks) and maybe some default start-up and other sounds (for the sound).

You said VR - I suppose the first VR platform with full field of view could be rather memorable, but the first software won't be ported especially for it unlike just about any ZX Spectrum game...

I feel that the limiting factor is now software, not hardware. There are way more great PS4 games in our imagination than in reality, while, with the ZX Spectrum, most of our imagination easily outran the platform's ability. This made each platform advancement more exciting. I couldn't care less when the new Samsung Galaxy 7 comes out because there's no software I want that my Galaxy 3 can't run.

But that's just how I feel as someone born 6 years after the ZX Spectrum. So someone younger will have to comment to really answer your question.
This isn't justice, isn't efficient, hasn't been effective and isn't economical either. It's good to see a small ray of sense being brought to bear on the matter. There is still a long way to go however.
Mongoose is a client-side library. It emulates relations and schemas client-side, as I also pointed out in the article.This also means that the database cannot optimize for relations and schemas, as it doesn't even know they exist.

Mongoose is also very much not the default MongoDB client in Node.js - it's a third-party client library by Automattic. The official client according to the MongoDB documentation is `mongodb` (https://www.npmjs.com/package/mongodb), which does not feature relations.
Maybe, but running unauthenticated databases on the public internet is negligent at best.
I'm actually job searching the moment and LinkedIn has a maybe 5-10% of the jobs that Indeed does. Even though LinkedIn's model is better in theory - most recruiter/employer types still post vancances on jobboards and use CV attachments.
Ramdajs links to an old article that explains it pretty well:

https://web.archive.org/web/20140714014530/http://hughfdjack...

Ramdajs: http://ramdajs.com/0.16/index.html
They don't come with one stock, sure, but there's nothing to stop you from going and buying the correct sized steel (or cheapo alloy) wheel and a decent tire that's the same size as the ones on the car and carrying it with you (and throwing the junky temporary spare out). Yeah it requires you to work a touch extra on the setup, but it is worth it. The extra full size spare will cost about the same as going with run flats vs non-run flats each time you swap out tires.

If you're interested, it's pretty easy to get the correct sized wheel from somewhere like RockAuto or Discount Tire Direct.
Well, I liked it, and I personally don’t mind the title. It’s about currying and JavaScript, and it’s interesting, so that meets my (possibly low) bar for upboating.
Setting up your own blog
From reading the comments here, it's definitely not just you.

But it's not a problem for me on my recent Samsung Galaxy. I actually prefer sites that don't delay to wait for a possible double-click. And accidentally resizing is a hassle because then I have to limit my thumb/finger movements to straight vertical lines, or else I'll end up scrolling horizontally as well.

When I had a smaller phone, I used a Dolphin browser, which reflowed text as well as resized fonts when I double-tapped. I thought that was fine. But if the default pinch/doubletap behavior is to zoom the whole page like Chrome does, I'd rather not deal with it.
evernote kind of apps don't work. Except Google Keep. Keep kinda works.
Whoa, this is a worrisome attitude.

1. The bugs that MongoDB historically suffers from are those that are unlikely to occur for most people, but when they do cause the most suffering. This is a combination of them being incredibly hard to replicate, but more insidiously that the system keeps working, it just has a small data corruption. This can obviously lead to huge problems down the line. The conclusion is firstly that just because you haven't seen a problem doesn't mean there isn't one, but also just because there isn't a big problem for you doesn't mean there won't be one in the future.

2. Databases have some of the most demanding testing around, due to the important requirements placed on them. There's a really good talk floating around from a guy at FoundationDB. The sorts of bugs that keep cropping up in MongoDB are the sorts of bugs that level of testing would find, which is a very bad smell. Thus, one should only resort to MongoDB if no other solution is reasonable.

But in reality, for most tasks something like Postgres (with JSON additions) or CouchDB etc is equally suitable and easy to use. This means that most new users of MongoDB can actually afford to use a better/less buggy database, they just choose not to.

3. Flat files are generally a silly idea mostly because of the additional tooling that databases give you. ORM systems make using a database much, much easier than using flat files, and the databases usually allow easy analytics. They also typically give better error messages, better performance, better extensibility etc. If it comes time to move your data into the cloud, you'll have a much easier time of it if you use a database etc. It's a win-win in almost every case.
Ok since nobody asked.. What is the tech stack behind?
Sit on their mailing lists, answer questions. See a bug? Write a patch for it. Pretty good gateway path in, and you'll build personal relationships.
Not the OP, but I often discover interesting github projects when browsing HN on mobile and would like to star the project (basically, a bookmark) or even fork it (if I think I'll want to make code changes and possible send a pr). Has happened a couple of times in the past week.
ES is wicked easy to setup and use, but it's not recommended as the primary data store for split-brain scenarios, IIRC.
The day I did join I was stupid and did use my memory for the password.

Latter I did create another account, yes.
In what way is it better than partial() from rambda or underscore? I have tried to see the potential in currying but gave up when I couldn't create a function with no parameters without calling it.