skysight-inc/HackerNews huggingface dataset:
> ideas coming from ad design

One of the things that bugs me most about many "modern" product pages is that they are often designed to look like brochures. Flashy and eye-catching, but with very little content or meaningful organization.

Most of the time I was brought to the page by an actual advertisement, or some content performing a similar function, and I am on the page now, looking for information. It's a bit like going to a restaurant and getting a pamphlet promoting the atmosphere and decor instead of a menu.

I scrolled though many sites advertising devices, looking for that elusive little table that summarizes the data I'm looking for, variously called 'features' or 'specs' or whatever. But these days even those sections are full of non-information like "all day battery life* " (That star is pointing nowhere).

I'm open to the possibility that I'm using the internet wrong. Perhaps there's a very good reason that the last place I should expect to find information about a product is on the product's own page.
I don't think you even need generation ships, if you can maintain a constant acceleration. And with constant acceleration, going to our nearest potentially habitable neighbor isn't that much further, subjective-time-wise, than it is to Andromeda.

Assuming acceleration of 1g, from here to Alpha Centauri, it would take 6 years objective, 3.5 subjective. To the center of the galaxy, it would take 27,000 years objective, but only 20 years subjective. Magellanic clouds? 162k years objective, but only 23 years subjective! 28 years to Andromeda.

Fuel may be in short supply, but relativity really works for you - ignoring abrasion and impacts, if you can get to one galaxy, you can get to most others in your neighborhood.

(All calculations derived from http://spacetravel.nathangeffen.webfactional.com/spacetravel..., because I'm too lazy to do it by hand.)
OS X Survival Guide
Worth noting that the person defending express is Eran Hammer - the of one of it's biggest competitors, hapi (hapijs.com)
Take a look at confd, a single statically-linked executable that can expand config file templates using environment variables:

https://github.com/kelseyhightower/confd

Basically, you add confd into your Docker image and execute it at runtime to do just-in-time config file generation. Here's an example for nginx:

https://github.com/grosskur/nginx-confd-dockerfile

You can create separate environment variable files for beta/staging/prod and pass --env-file to "docker run".

This lets you use the same Docker image across all your environments and avoid the operational complexity of mounting config files in Docker volumes.
Yeah, if this could also tell me through Untappd whether I've had a beer before and how I rated it, that would be perfect.

I'm on a mission to try 1,000 different beers on Untappd, and this could really help with that.
List matching tends to be fairly useful even its very limited form in my lib. Its basically arity match + de-structure. It doesn't nest like full fat pattern matching.

I don't see how tuple matching is as useful (over your 'With' fn or my 'Apply') unless it can nest, especially with matches on union types.
e.g (Maybe a, b) | (Nothing, b)

Basically I feel like such a thing is going to be very hard in C# to achieve with any sort of usable api. I personally took the route of the api being more important than whether any sort of decent abstraction is actually there behind the scenes - I didn't mind writing 100's lines of boilerplate to get the result and behaviour I wanted.

Its great to see more functional support for C# from the community and I look forward to using your lib in the future!
The Rust team plans to launch a central package registry at (running a server written in Rust :) before Rust 1.0.
Social Media Marketing (Free to Attend)
The importance lies in that C# is becoming one of the first truly, for lack of a better word, "programmable" programming languages.

The One Language to rule them all? Maybe not, but definitely making incredible progress.
We're not talking about arbitrary control; we're talking about one specific set of restrictions designed specifically for the protection of freedom. It's quite possible they fail at that, compared to alternatives, but it is not at all incomprehensible that they might succeed - restricting some behavior often leads to more freedom in general, especially when that behavior involves exercise of power over others. Proof of existence, by example: Selling a knife with a "this can't be used for mugging" clause - in a world where mugging wasn't illegal - restricts the freedom of the purchaser but only when you don't consider those they would impact if they exercised that freedom. To be clear, I'm not saying "selling proprietary software is exactly like mugging"; I'm just saying your general "restrictions always mean less freedom" doesn't hold up.

All of this is not to say that I think it's entirely clear that copyleft licenses do lead to more freedom overall. My initial statement was precisely that it's not particularly clear. My personal expectation (which I'd argue for if we want to go down that path but hold weakly in that I consider other views reasonable) is that it varies from case to case.
And the last paragraph is the main problem. The ship would get torn apart from lone atoms and to actually stop yourself you need an exponential amount of fuel, because you need to accelerate ( much more than )half of it just to stop yourself.

Even if you protect yourself from relativistic atoms, they still create a drag. And that happens before you reach 0.99c.
C.S. Friedman's Coldfire Trilogy takes place on a planet where the only two significant external light sources are the local star and the core of the nearest galaxy. This enables a plot point where the surface of the planet occasionally experiences intervals of the lowest light levels possible.

Had this been known at the time, she could have simply dispensed with the light from the nearest galaxy altogether.

Similarly, the planet Krikkit, as described in Douglas Adams' Hitchhiker's Guide "Trilogy", would not necessarily be all that unique or unusual.
Thank you. Doing a join on an SSD isn't as big a deal as on a spinning platter. Find the N regions of storage and pull 'em in. (replace tricky disk scheduling algos for simple FIFO or priority queue of requests)

Many of these denormalized "document" storage systems are likely to look like real legacy cluster-bombs in a few years.
Synthetic cannabinoids, “research chemicals” and the war on drugs
True, if you want full and predictable memory/cache performance you need to rent a full-machine VM (usually 8xlarge) or bare metal.
Very refreshing idea! I can't tell from the site if you let users upload their own ratings after trying a pint but I think that would a great feature and also a great independent source of reviews for the app.
Now maybe we can extract the active ingredients and make a better, more effective therapy with fewer side effects, instead of making people damage their lungs smoking a weed to get this into them, or making them eat fatty foods and damaging the rest of their bodies.
That's due to hardware acceleration so really Chrome is buggy. I don't really know what to do about that.
The canonical sci-fi short story about this is the darkly humorous "Computers Don't Argue", written by Gordon Dickson all the way back in 1965.

Link: http://www.atariarchives.org/bcc2/showpage.php?page=133
It's probably useful to distinguish between "people with IPv6" and "people without IPv4" when discussing the realized utility of IPv6 support.
The Startup That Built Google’s First Self-Driving Car
My rant on C++'s operator new (2006)
If you're going to do Seattle to San Diego, make sure you're on CA 1 for as much of the California part as possible. 101 in California is a drab, boring drive.
I have tried VoltDB, it's nice for scaling low latency data access (realtime bidding / adserving is one use case it shines)
Awesome! I just finished a project doing beer recommendations, and I wanted to use the RateBeer data but they put up a notice that they were not giving out API access anymore. We went with BreweryDB and were trying to add some ratings ourselves, which was sufficient for our project.

How did you get the use of RateBeers API?
This is a little long, but it's a must read for anyone interested in real-life consequences of computer bugs.

Basically, new software was pushed to seven of eight servers at Knight, one of the biggest players on Wall Street. A flag activating the new software was repurposed from very old inactive software that was still on the servers.

The new software ran fine on seven servers, but the flag activated the old software on the eighth server, which promptly started doing something completely insane as far as financial markets are concerned. A few minutes later people removed the new software. But didn't change the flag. So then:

(the old software) jumped in to fill that void
and was now running on all eight servers
simultaneously, buying on the offer,
selling on the bid.

Knight lost over $400 million in under an hour, and was forced to eventually sell out to one of their biggest competitors.
Hi, yes you're right - you can reference an image ID. However, as soon as you go to the network you're lost - any apt-get/yum update or install could break your system in surprising ways.

Having done _lots_ of builds lately I can vouch for that (see my blog for some examples).

In the end the image ID _is_ useful, but the dockerfile itself has limitations.

I agree with your last point as well - my evangelism comes from solving problems at my company in this way (which I know are not uncommon problems) rather than any belief that it beats others objectively.
The problem with things like pthreads in PHP is that 98% of the time your runtime is via mod_php5, and spinning threads off of an Apache worker instance is one of the worst ideas imaginable.

I (once, ignorantly) tried to do some kind of super lightweight background-like worker with pthreads in PHP instead of bringing in a full queue and worker design and it turned out that there is absolutely 0 capability of doing it with the slightest hint of sanity. Having libraries like that is cool, but it's not for what PHP was designed for: web pages. Arguably and controversially, web applications are even a stretch for the language, but the support is and has been getting better with actual classes, namespaces, and tooling support like Composer and agreed-upon libraries like Doctrine. Then again, I just fled a company who's entire infrastructure was dependent on cronjobs running tasks using relational databases as queuing mechanisms with very little use of ORMs. It doesn't really matter if the language gets better, because the bar isn't really getting raised, unfortunately. After making the language more desirable (which has been done), a community effort needs to be made to shame and call out bad code, which might end up requiring a jump to 6.0 finally and breaking backwards compatibility with everything that's changed since 4.x (mysql_escape_string, mysql_x instead of mysqli_x or PDO, etc.) At least non-parseable code isn't going to fester bad practices.
The reason why sysvinit runs on FreeBSD and HURD kernels is that those kernels have implemented the Linux procfs file system.

https://teythoon.cryptobitch.de/posts/on-portability-of-init...

Besides, none of these are release architectures, so why should their limitations restrict what features >99.9% of Debian users have available?
I want to point out that in the thread here on HN (https://news.ycombinator.com/item?id=8631022) about that Netflix article, the top comment debunks the myth that the list-of-handlers was the issue slowing them down.

While creating a grammar from the combination of the regular expressions (which is why you can't just have a hash) is definitely a solution (quite possibly THE solution), that's definitely not an MVP-type of solution, and is pretty non-trivial.

The actual problem was them constantly adding handlers by accident.

One of the reasons I love and use HN so much (I give almost no other site so much pull on my personal opinion) is that smart (or very careful and well-read dumb people) leave well-thought-out comments like the one I mentioned.
How do you charge monthly for an Iphone or Android App?
I have an phone app I'm working on but I want to charge monthly on it. If I just release it to the app/play stores for free, can I add a login screen to block random people from using the app who haven't paid?
How I Lost My Reason but Found My Passion
Hacker school
Hey guys please tell me how I can get visa for hacker school.I am from Pakistan please tell I love programing...
How do you find good tenants? Do your tenants tend to stay for long periods or do you have a lot of turn over? Thanks!
It's time for Apple to open up
Responses are already firing in:
https://news.ycombinator.com/item?id=8632220
A couple points I would make with respect to the article:

- In-memory databases offer few advantages over a disk-backed database with a properly designed I/O scheduler. In-memory databases are generally only faster if the disk-backed database uses mmap() for cache replacement or similarly terrible I/O scheduling. The big advantage of in-memory databases is that you avoid the enormously complicated implementation task of writing a good I/O scheduler and disk cache. For the user, there is little performance difference for a given workload on a given piece of server hardware.

- Data structure and algorithms have long existed for supercomputing applications that are very effective at exploiting cache and RAM locality. Most supercomputing applications are actually bottlenecked by memory bandwidth (not compute). Few databases do things this way -- it is a bit outside the evolutionary history of database internals -- because few database designers have experience optimizing for memory bandwidth. This is one of the reasons that some disk-backed databases like SpaceCurve have much higher throughput than in-memory databases: excellent I/O scheduling (no I/O bottlenecks) and memory bandwidth optimized internals (higher throughput of what is in cache).

The trend in database engines is highly pipelined execution paths within a single thread with almost no coordination or interactions between threads. If you look at codes that are designed to optimize memory bandwidth, this is the way they are designed. No context switching and virtually no shared data structures. Properly implemented, you can easily saturate both sides of a 10GbE NIC on a modest server simultaneously for many database workloads.
Fortunately for your use case, Rust provides a reference-counted type in the standard library that does indeed feature weak pointers to break cycles. It's like C++'s `shared_ptr`, except safer and faster (since Rust's safety rules mean that we can prove that the refcounted data isn't shared between threads, and hence we don't need to resort to atomic operations). All of these are possible because of a thin layer of `unsafe` code on the ground, which we then wrap in a safe interface.

> We do not need yet another unsafe language. We have plenty of those.

I sadly must disagree. If safety were truly paramount, people would have dropped C++ entirely in favor of Java in the 90s. The people still using C++ aren't idiots, they just have requirements with respect to efficiency, control, determinism, and expressiveness that other languages don't match. Rust exists to provide an alternative to these people, so that we can at last bring some semblance of safety to domains with the requirements intimated above.

> The day there's a CERT advisory for a buffer overflow in a Rust program,
> Rust has failed.

I dread that day, and yet I know that it's inevitable. In the meantime, that same buffer-overflowing Rust program may well have produced ten times the CERT advisories had it been written in C. I'm not an absolutist; I'll take that improvement as a win.

> I used to work on this problem, about a decade ago.
> I was trying to figure out how to make C++ safe.

Honestly, the Rust developers would love your perspective if you'd like to take a harder look at Rust.
So I was a bit unclear on the parent's post but I don't think this time was on a route lookup if I'm reading the thread and post correctly the static file handler getting inserted multiple times. This handler will generally match on any route but then is doing something like "if file exists, return static file, if not look for the next handler" in this case the "if file exists" part was the "path check" thats taking 1 ms and was happening multiple times.

I could be wrong but it seems like the design of the route lookup mechanism (the global array) was actually a bit of a red herring, the real issue was the ability to attach multiple instances of the same handler to the same route.

Something was adding the same Express.js provided static route handler 10 times an hour. Further benchmarking revealed merely iterating through each of these handler instances cost about 1 ms of CPU time.
PRL = Physics Review Letters, paper in question: http://arxiv.org/pdf/1411.4849v1.pdf.

Of course the PRL version will not be CC-BY and citations that reference it will likely not find the CC-BY version. I wonder if it will matter in any material way to PRL - no more so at least than the situation where papers are available direct from a repository on an author's personal webpage. The pre-print already being on Arxiv.org probably makes far more impact than the use of a CC license?
There is a line between "professional programmers" and "dangerous script kiddies."

You need a lot of clout to draw that line, you are going to upset a lot of people on the bottom half of the stratification, and you really need to work hard to convince a lot of programmers that creating a professional organization is a good idea, for some unknown reason.
OpenSCAD is decently reliable up to a certain amount of objects/vertices. Once I reach a limit rendering becomes too slow and sometimes makes OpenSCAD crash. What I ended up doing is to model individual parts (which is a good idea anyway, and OpenSCAD parametric modules work great for that) that I render to STLs individually, then import the STLs for everything but the part I am working on.
In my view, Turing's results are equivalent in computer science (an important part of software creation) to Pythagoras' theorem in geometry (an important part of architecture): incredibly insightful, fundamental, everlasting and useful. Used directly or indirectly in all early works, respectively, in software and architecture. And only a tiny part of the foundational understanding necessary for really mastering the discipline, a level I think we still haven't reached in software.
The Drake Equation[0] is probably the most famous attempt at a "resolution" to the Fermi paradox and I haven't seen any that realistically try to implement a term involving the likelihood that a civilization might colonize neighboring star systems. Would a civilization that has colonized multiple near-by star systems be considerably noisier/more-detectable than one confined to a single star system?

[0]: https://en.wikipedia.org/wiki/Drake_equation
That started getting airborne at a much lower speed than I expected. Crazy.
Well, so long as I'm spitballing my dreamDB's "continuous views", then why not have a concept of "foreign documents"? Let's define "foreign documents" as a type of field that is an exact copy of a document in a separate table. This field gets updated when the original document is updated.

This could apply to denormalization really well! For example: let's say you have a table called "items", a table called "customers" and a table called "sales". A sales document is just a item foreign document + a customer foreign document + a date.

The item foreign document is literally an exact a copy of a document in your items table that gets updated whenever the original gets updated. So if you change the customer information, the customer information in the corresponding "sales" documents get updated.

This is a terrible example because it's not a useful/practical use case, but maybe it could be useful if you have enough data where this join is unreasonable.

You can use the same architecture to update your continuous views as you do for your foreign documents. And add the same syntax with throttling and whatnot.
Everyone should read the terms & agreements too.
Our "understanding" of the universe is the classic example of the problem of extrapolating from an example of one.
Amageddon: Seattle's Increasingly Obvious Future
MongoDB vs. SQL: Day 1-2
"0b" [that's a copy paste, the Xi doesn't appear, the super and subscript letters do, the pi doesn't show] I'm going to guess that is why?

Though the OP does say "The discovery of the particles, known as Xi_b'- and Xi_b*-, were announced by CERN [...]"

𝛯′⁻ works in unicode, but I can't get the subscript b nor superscript asterisk in there (cf. http://en.wikipedia.org/wiki/Unicode_subscripts_and_superscr...).
Countless subtle race conditions and security issues in the shell spaghetti that makes up real-world init scripts indicate that it's not a "solved problem".
how come nobody noticed qwantz.com's T-Rex yet!
It is not just 'syntax'. Also I think a substantial portion of developers or the programming industry at large do not think these sort of tools are `useless`.
I've been really interested in tdcs for a long time, simply out of curiosities' sake, but the tdcs subreddit is private and there aren't many good resources for people who aren't sure they want to commmit to the heavier stuff.
Well, the same engineer who didn't figure that out went ahead and profiled things, drew some pretty graphs, actually bothered to write a blog post to put his thoughts for public review. IMO, that is all some good engineering :-)

But you made me think what I said. I would say this sort of gets into the programmer / engineer debate. Netflix has good progammers like most companies. Good engineers (in my books) are very hard to find. These people are good at being at peace with tradeoffs and understand the requirements of a business at a much deeper level than programmers. Programmers just want to have fun with computers (and there is nothing wrong about that).
GWT is open source and is being used / developed outside of Google, so it'll hardly be abandoned even if google left it. But Google is still using it heavily, see Inbox which just came out and uses GWT.

Also, angular and dart are slow as shit compared to GWT.
It was a dark age, and void stars filled the console. Many a core were dumped. An age where boys became men!

:-)
Questions with Vim’s Creator, Bram Moolenaar
... Well before. You didn't hear that from me, though...
Rocks have fallen out of the sky randomly for billions of years too - sometimes killing whole species and so forth.

The fact that something has been happening "for billions of years" is not a reason to ignore it.
And for Dublin: http://www.softwareontheside.info/2014/03/sailbus-dublin.htm...

One of the city bike apps also supports Dublin along with a lot of other cities in Europe.
This isn't that groundbreaking - there are plenty of 1:1 ratio screens that are made and sold for the air traffic control industry:

http://www.barco.com/en/Products-Solutions/Displays-monitors...

However, what would be interesting is if this was priced at normal monitor prices ... the ATC monitors are incredibly expensive.
Preddithunt: producthunt for everyone
“This type of image analysis task is not well suited to automation. There’s no computer algorithm that can go in and autoselect targets for you, it’s a human endeavour. If we can help people pay attention for long periods of times, that‘s really important,”

at the very least, they should save the images and targets to use as training data, since that's being generated manually already. then they could see how predictive of a model could be generated, instead of just guessing that it would be bad.