skysight-inc/HackerNews huggingface dataset:
While I appreciate PostgreSQL every day, am I the only one who thinks this is a rather bad idea? The row based engine of PG is the antithesis of efficient storage and retrieval of timeseries of similar patterns, yielding almost no compression. Columnar storage should naturally be much better at that (BigQuery, Redshift, Citus), culminating in purpose built stores like Influx, Prometheus or KDB. Prometheus for example manages to compress an average 64-bit FP sample including metadata to just 1.3-3.3 bytes depending on engine. As most DB stuff is I/O bound, that usually translates into at least an order of magnitude faster lookups.
Then why don't we just forgo human drivers, if it's only about the engineering teams. Just have self driving cars battling it out.

In my opinion, F1 should go back to manual transmission, and no driver assists. Do whatever else you want to make the car perfect, but the driver must be in control of the entire machine.

Just look at the 80's in those monstrous turbo V6's approaching 1500HP, no traction control, no power steering, and manual transmission. THAT was driving.
http://www.Reminde.rs - Recurring SMS and Email Reminders
>Ofttimes once many people move to an area and buy homes at artificially-inflated prices, the local economy tanks and everyone is stuck with their overpriced home.

At other times, a city grows so fast and rents go up so much in a few years that a house shields you from it.

I bought my house "late" (i.e. when prices were on an increasing curve). Less than 3 years later, too many 2 bedroom apartments charge more for rent than my much bigger house. If I were to sell now, I'd make a profit, even after you account for real estate fees, etc.

Obviously, my case is not the norm. But neither is your scenario.

>https://www.google.com/search?q=buying+a+home+is+not+worth+i....

Oh, please! The first rule of Google searching is: Do not ask it to return what you are looking for!
The other thing that WEC has that Formula 1 doesn't is the chaos and excitement caused by multiple classes of car competing at the same time. It's not just a matter of negotiating your car around all the other cars that are pretty much identical to yours. You have to negotiate around cars that are both slower and faster. Dealing with traffic is a major aspect of WEC, and it's something that's entirely lacking from F1.
Why you shouldn't walk on escalators
Thrift and protobufs are underappreciated. Better integration in something similar to the Swagger Editor would give these a much more comfortable home and allow them to see adoption in the web world, where people generally expect things to be a little softer.

I've never really liked the REST paradigm, so I'd be pleased to see it die.

My biggest complaint with Thrift: they still make you do some convoluted hacks to get a two-way ("streaming") connection in the RPC, and when this is discussed, they usually kibosh it pretty quickly by saying it's an unsupported case and that you can find some hacks online, but they don't want to talk about it any further.

This may not have been a big problem for them before gRPC was released for protobufs, but it's definitely something that's worthy of attention and response now. I know lots of people who are going with protobufs instead because of this.

The other thing is that while Thrift boasts a lot of language compatibility, several of these are buggy.
I think the term "alt-right" at this point is just a catch-all derogatory for shitty people who happen to be a certain type of nationalist rightist, in much the same way that "SJW" refers to shitty people who happen to be associated with the social justice movement.

Before the election, there was a narrower meaning, but as soon as the Clinton campaign mentioned it and the media picked it up, any hope of the term having any concrete meaning was lost forever. (This isn't helped by the fact that people love using it to attack arbitrary conservatives, in much the same way that SJW is sometimes used to attack anyone who expresses views supportive of social justice without behaving badly).

EDIT: I don't let myself get worked up about downvotes in political conversations, but this one has me pretty curious. My comment wasn't even remotely offensive to any part of the political spectrum.
Exactly. The lack of full time income for two years is a sizeable expense. Instead of being $40k in the hole after two years, they could have had $40k in the bank. At an average 5% rate of return, that is almost $300,000 after 40 years. That is loss of about $7,500 per year until retirement simply by spending time in school instead of at work for two years. You don't even need to get into tuition and other costs.

It was once promised that getting a degree would increase your job income by more than that $7,500 (or whatever number fits the situation). But incomes have been stagnant for 40+ years, with no sign of that changing. Without rising incomes, incomes simply aren't rising to compensate for the growing postsecondary educated populace.
I've pinged someone on the team whose a big more familiar with our clustering, so hopefully they can give you a more detailed response soon.
Has that 1979 law been proven in court to be valid about the kind of things we are talking about now, and can you link the specific cases, please? :=)
Ubuntu are trying for ease-of-use and it's a noble goal. But if you are going to judge them only on ease-of-use, then it is difficult for them to compete with the resources of Apple, who are the richest company on the planet.

My point was that there are quality open-source projects out there, after you appeared to assert otherwise. But ease-of-use is not something developers/startups seem to be interested in spending time on.

If you want me to qualify stable, then let's compare Apple's bidirectional iCloud sync to Unison, or Time Machine to ZFS snapshots.
Google has substantial leverage with the Android trademarks and the Play store ecosystem.
Mostly Ruby vs Python, though I think that's a big distinction. Rails is Ruby's killer app, but Python has killer apps in many things, so if you want to integrate something else (like Machine Learning for example) easily into your code, then Django (because it is Python which has a lot better support for ML) makes that so much easier.
A few counterpoints as I drift by:

The HAL hypermedia format is in use at Comcast, powering the Xfinity TV API. Not only does it take advantage of hypermedia and HATEOAS, it also splits requests/responses in order to make the most use of HTTP caches. https://boston2016.apistrat.com/speakers/ben-greenberg

Dunno if you're serious about not seeing how one could write a HATEOAS-driven client library or if I'm being trolled, but here's one that I wrote a couple of years ago: https://github.com/gamache/hyperresource There are many others as well (especially for the HAL format).
Check out Stoplight.io for a good tool for managing swagger documentation. It's a lot easier than managing the YAML itself.
> but the UX is still lacking a lot

I disagree. I moved from a MBP to a notebook with Arch and i3. The UX of a tiling window manager such as i3 is in my opinion much better and more efficient than the floating wm on OSX. There is no real tiling wm for OSX (don't mention divvy here, it's a nice tool but far away from a real tiling wm).
A single-node version is currently available for download. A clustered version is in the works.

Adding clustering on sounds like the hardest part.
Desperation time (the future of global capitalism vs. socialism )
It seem to me now that both Quake 3 Arena engine and of course the best RTS that our civilization have been able to make and really balance with some kind of magical equilibrium between 3 truly different races are well and alive in research labs and currently both styles of games with comebacks in the pipeline the champions nonsense in the FPS side of things and the new broodwar from blizzard.

One can argue that Chess or Go are friking old games and that we need to make Chess 4000 and or invent a new go, same apply to the good old broodwar from 98.
Ask HN: Minimum Authentication/Authorization Features for a on Prem Web App?
I've developed a web application (an event Dashboard really) that is starting to get more users, but it doesn't have any authentication yet, instead it relies on the user to setup their own authenticating reverse proxy, and as you might expect, authentication is a highly requested feature.

The app so far is something install on-prem, I don't have a cloud hosted version, but don't want to rule it out. Its mostly likely to be used by the IT and/or security team and small to medium size orgs.

What are the minimum features of AA I should be offering? Its not that hard to simply add .htpasswd type auth, but its something I want to attempt to get right the first time.

If it matters, its a single page web app built with Angular 2, and the backend is Golang.

I need to think about some sort of RBAC and/or ACLs as well.

Thanks for any input.
You wouldn't really even need to put the keyboard and serial port in the cart. The GBA already has the link cable, which could be used for serial data.
I think AI, in this case, is overkill. Create ~10 common enemy class and spawn them based on your strategy history, equipment and game pace. Each and every enemy would act differently like if you were more on sniping side, you would get snipers and fast units spawned. With mediocre AI this would make the game appear as having very good AI to regular player.
You've missed a step. After enabling Developer Mode, you need to enable support for WSL in Programs and Features, then restart Windows.
So I don't know about the data layout here (and definitely agree with you re: column stores), but if you look at stuff like cstore_fdw[0], I think the data layout is also somewhat configurable under the hood. So "based on postgresql" doesn't necessarily mean "uses the same storage" - it could have its own columnar storage with the postgres query planning, connection management and other infrastructure on top, perhaps?

[0] https://github.com/citusdata/cstore_fdw
Divvy is my go-to window manager on macOS. I've got it set up to arrange windows on each edge as well as a "communication" window in the upper left corner of the screen for Slack, etc...
Amino Healthcare Data Platform: 9B Real-Time Insurance Claims
REST, if one insists on using it, should really be layered over top of something saner like gRPC or Thrift.

Personally, I've always found REST troublesome and overhyped. There's always a few incidents where you spend hours trying to figure out why something isn't working before realizing you had the wrong method on the request. There's no reason the thing you actually want to do to a resource should be tucked away in some header that's not always easy to access or see, it's just asking for trouble.
I believe the MacArthur Foundation will be contacting you soon.
Kay is bang on.

1. http://worrydream.com/TheWebOfAlexandria/

2. https://en.wikipedia.org/wiki/Link_rot

3. Comment elsewhere in this thread about how we have been forced into turning a document system into a VM.
Bureaucrats have taken over F1 and turned an amazing sport into a mind-numbing event for the nouveau riche to flaunt their $$ and poor taste.

At least the North American races retain some of that spirit - people care about the racing and the cars. In Asia it is already an afterparty that people attend where a car race sort-of breaks out.
The entire idea of needing to maintain (develop, improve, update) a product beyond the point of sale is a fairly new one.

But not in computers. Even in the 80ies, we would buy new version of MS-DOS for our existing hardware.

The difference is that on most normal computers (except Apple), software was/is decoupled from hardware, they have different manufacturers. Software developers want to reach an as large as possible audience, so it is typically not in there interest to support only the latest hardware iteration.
> It's impossible for me to see how it would be possible to write a HATEOAS client, and I can't in practice see anyone doing so.

There's nothing complicated about a client that understands Hypermedia links. You start at the root, it'll give you a set of links to follow, and you recurse. Here's a browser that can take a HATEOAS-compatible API and will let you work your way through the API: http://dracoblue.github.io/hateoas-browser/

> Optimizing for HATEOAS seems to me to be optimizing for entirely the wrong metrics, and a complete waste of development time and effort.

Correct. HATEOAS is a neat parlor trick: point a dumb client at your API and watch it enumerate all the possible operations. Wow! The problem is that APIs aren't consumed that way, they're consumed by humans who need to decide which API calls to make based on user actions in the application... so developers will resort to consulting documentation in order to piece together the correct calls in the correct order. That's not something you can encode through Hypermedia. At best you can just model the relations between calls, but not the "how" or "why" of everything.
Most of my workmates have them. They look like glossy mirrors, and several complain about it. When you can see your reflection in them, plus all the room lighting, that's a terrible quality for a general purpose display. Meanwhile I have a much cheaper matt Dell monitor which is much more fit for purpose, and I don't suffer from the glare and reflections.
Definitely agree — and that's not a knock against checklists.

Externalizing a process that previously existed only in someone's head is a win. Creating a checklist is a straightforward framework for such externalizing, and allows you to separate the question "how do I accomplish my goal?" from the question "how do I express this with code?" (like writing pseudocode before real code).

Whether a process is automated or manual, there's always room for error if the surrounding context changes. When an automated process is annotated _like_ a checklist, I find that I get the best of both worlds: minimal affordance for human error with a clearly described thought process to fall back on in the event of a problem.

(It's also not terribly uncommon to have steps that can't be fully automated, like authenticating to a VPN with 2FA under certain security frameworks...!)
Depends on the exact case, but I've managed to convert many-step deployments into single-step ansible playbooks in not much longer than it takes to run them once.

Even at our super tiny 3-person operation this has saved a massive amount of time - it's even more valuable when it's panic time because a server went down due to disk or ISP failure and you know you have an ansible script that can get a new server up in 3 minutes flat while you grab the backup.
The Garage door often _is_ a home door.
penrose wrote a whole book walking through his argument around deep AI (and providing a gentle explanation of gödel's incompleteness theorem in the process): https://en.wikipedia.org/wiki/The_Emperor%27s_New_Mind
The touchpad is literally the single hurdle to me going back to a windows/linux laptop.
Author here - I've created all the diagrams, though I've received really helpful editorial input from Shan Carter and Chris Olah. If you feel like doing some archeology, you can see for yourself the really ugly drafts in the github history - it isn't pretty!

I think these visualizations are deceptively easy to create. Javascript is a powerful language with many libraries, and in my experience, it just took a few nudges at exactly the right spots from Shan to go from an idea in my head to fully fledged diagram in distill. The tricky part has always been figuring out what to visualize, and if you're a researcher with an clever idea for a visualization, I recommend you reach out to the distill team.
Hm. So that helps with high-frequency noise. Any progress on what to do when the dimensions are of vastly different scales? I have an old physics engine which had to solve about 20-value nonlinear differential equations. During a collision, the equations go stiff, and some dimensions may be 10 orders of magnitude steeper than others. Gradient descent then faces very steep knife edges. This is called a "stiff system" numerically.
As a hobby, I'm working on a project that allows you to run a subset of the AWS infrastructure on your local machine. Yes, there are related projects such as Serverless and more recently LocalStack from Atlassian but my intent is to focus solely on Lambdas written in Java and I'm learning a lot about the AWS APIs and orchestration semantics along the way. I try to leverage existing open source projects (DynamoDBLocal, Kinesalite, etc.) running in Docker containers and provide the glue to do things like spin up an entire system locally while being able to debug Lambdas, etc. I'm working on it in the open here: https://github.com/digitalsanctum/lambda
You, sir, are a mad man and a genius.
This sounds amazing. Is there anywhere I can learn about your wetsuit technology? I'm interested in the crossover to surfing.
You know, when I look at their statement about this being an LTS, it seems (to my understanding) that they have a slightly different definition of what support means in this context.

"This version has been designated as a long-term support (LTS) release, which means that security and data loss fixes will be applied for at least the next three years. It will also receive fixes for crashing bugs, major functionality bugs in newly-introduced features, and regressions from older versions of Django for the next eight months until December 2017"

I expect that something like a "crashing bug" would be something that would be supported in an LTS, but here they're specifically excluding such bugs from the full three year duration. If stability were a priority, I'm not sure I would look at this any differently than an 8 month release.

To be fair, I don't work in this space, so I may have a skewed perspective, but the 8 month limitation items did catch me off guard.
3 ongoing projects:

1: Write 1 blog post a week on blog.benroux.me

2: Continue to improve automatic spam moderation with detextion.io

3: Write an iOS dictionary app that tracks every word you look up and sends you words every week from that list to help you remember them moving forward
X-FORCE 2017 KEYGEN FOR ALL AUTODESK 2017 PRODUCTS
Lego Macintosh Classic with e-paper display running docker
It would be really, really great if you could somehow hook this up to Discourse so people could comment on and ask questions about the article. Allowing people to ask questions and having others answer like MathOverflow would I think bring a lot more clarity. Many different kinds of people want to understand material like this but may need the math unpacked in different ways.
I'm not sure I totally understand the question.

A simple username/email and password solution seems like it'd solve authentication, but isn't that obvious?

Authorization depends totally on what your app actually needs, e.g., do different users have different roles? How fine-grained does the authorization need to be?
We do acknowledge that storage is not our strong suit, but we think the benefits of having SQL and being able to integrate easily with non-time-series data is a big win itself. Certainly if storage is an issue for you, TimescaleDB is probably not the right choice. But if it isn't, and you are doing more advanced queries (including JOINs or across multiple metrics), TimescaleDB provides a compelling solution in our view.
Half-life 1 have incredible AI from boids that present a flock behavior to coackroaches that are scared of the light or the player, just to mention two attention to detail examples.
Ok. May I ask what your source of data is? I am using Yelp's API currently.
My brother runs a movie web site in Chinese, that has some traffic. He's a writer, not a developer, but he learned some basic HTML some 15 years ago and has been publishing articles in raw HTML files since then.

The site is as web 1.0 as it can get, and he wants to modernize it. I'm a developer.

My side project currently is to help with this. It's actually fun to work on.

There's no breakthroughs or interesting science/engineering problems being solved. It's just a mix of things that make it fun. Everything from picking a proper CMS with a list of interesting requirements (easy to use, as attack-proof as possible [i.e. not Wordpress], as few moving pieces as possible but easy content authoring), converting old pages from HTML to some markdown format for future-proofing, making sure old URLs work and redirect to new URLs with better SEO formats, converting old Chinese encoding (Big5!) to Unicode, responsive design of pages/mobile focus, adding AMP and FB Instant Articles features, and so on. It's a mixture of building a CMS in 2017 and rethinking how a modern content site should be.
I'm personally very happy to have your feedback here. My parents, too, use Ubuntu :-) They love it, and I love that I can fix their computer for them. Thanks for the feedback and I'll take it to heart.
then you make a lot.
What data? Run it through a proxy and check.
>I had these same issues. It took me considerably more time and effort to write a Swagger spec and get the UI to actually behave than it did to write my entire API and some simple docs in markdown.

It's definitely going to be faster to just write it at first. Swagger, and everything like it, is an investment.

>I also tried out the "codegen" and a few other projects that generate boilerplate from a spec (for Python) - the code it generated was frustrating, lengthy, and much more complex than the simple endpoints that I quickly wrote from scratch.

That's auto-generated code for you. Can't rival humans (yet), but that doesn't automatically mean it's not useful.

Compare hand-rolled ASM with compiler-rolled ASM for an example. Human-written ASM will often be much more compact and readable, sometimes even more performant, but then you have to write ASM instead of letting the compiler do it for you.
Currently we are using the default storage mechanism in Postgres, but have had discussions on alternatives and other ways to compress our storage footprint.