skysight-inc/HackerNews huggingface dataset:
Surprisingly similar to what Lilly wrote in 1968: "PROGRAMMING AND METAPROGAMMING IN THE HUMAN BIOCOMPUTER" [0]

A very good book, even though you should not take it literally, quote from the preface:

Eventually the cerebral cortex appeared as an expanding new highlevel computer controlling the structurally lower
levels of the nervous system, the lower builtin programs. For the first time learning and its faster adaptation to a
rapidly changing environment began to appear. Further, as this new cortex expanded over several millions of years,
a critical size cortex was reached. At this level of structure, a new capability emerged: learning to learn.

[0]: http://nekhbet.leary.csoft.net/biocomputer.pdf

Edit (further context):

To avoid the necessity of repeating learning to learn, symbols, metaphors, models each time, I symbolize the under-
lying idea in these operations as metaprogramming. Metaprogramming appears at a critical cortical size-the cerebral
computer must have a large enough number of interconnected circuits of sufficient quality for the operations of meta-
programming to exist in that biocomputer.
Essentially, metaprogramming is an operation in which a central control system controls hundreds of thousands of
programs operating in parallel simultaneously.
If you buy a higher fare class you won't get bumped -- or extremely rarely. I fly 60,000 miles per year and I have never been bumped. But I also don't buy bulk-fare consolidator tickets from travelocity-type sellers either.

Involuntary bumps are extremely rare statistically anyway.
Splice is a user-friendly version control and backup system that supports Ableton, logic and FL Studio.

https://splice.com/
Yeah, I stalled out a bit around there too, but I felt like things picked back up with the chapter "One Mile" which is a very extensive neighborhood study of the effect of a single mile of the Cross-Bronx Expressway that cut through the (working class Jewish) East Tremont neighborhood.

Also, don't you want to know how his reign eventually met its end?
Actually, releasing faster might help avoid regressions since a faster release cycle requires you to focus more on continuous testing practices. With, say, one release every 2 years, you can easily put off testing until a few weeks before the release, at which point regressions are found and panic ensues. If you release every few weeks, you need to be testing all the time to find regressions in time, so you will be forced to automate it.

See, for example, this recent article on why web browsers switched to a more rapid release schedule: https://arstechnica.com/information-technology/2017/04/mozil...
> I prefer no refunds for no-show policy myself, that is how it works when I buy a ticket to see a play.

What about if you are flying long haul and linking up to a domestic flight on another airline? "Oh, we can't help you because your previous flight was delayed due to weather/mechanical/congestion.you should have flown on one carrier even if the price was 2x"?

Airport congestion is a big issue in the US, as is weather related delays.
Rails 5.1 released
A 30mph average is excellent compared to bicycling or mass transit.
Exactly, even when you add in the transfer fee proposed here. Any rational ticket holder wouldn't sell their ticket for less than [what they paid for it] + [the transfer fee], and that means the airline let someone else get money they could have got if they had just sold the ticket directly to the second person.

The only scenario where this would be useful is if the the original purchaser is willing to sell their ticket at a loss for some reason, e.g. if they know they can't make it and just need to minimize their losses. But at least Southwest airlines already has a customer-friendly solution here, they will credit you the full price of the ticket for a future flight, for most tickets at least.
Overbooking is key for maximizing producer surplus. Whether or not that is economically advantageous to the economy as a whole is a different and more complex question.

But the notion that a company maximizing it's surplus is _always_ beneficial to consumers is tricky but more likely false within the confines of my limited understanding of contemporary economic theory.
Worth remembering that Google paid this guy over $120 Million in compensation. He is a tech "1%"er, which really is saying a lot. That is hedge fund money.

I'm not certain, but I think the average engineer would feel more loyalty to a company that has given them multi-generational wealth.

I'm all for engineers getting paid, but in this case the guy didn't even have to do what most wealthy engineers do: deliver an actual successful product to market.
That...seems very surprising to me. I've used almost exactly the same set of languages, and I found the Rust syntax incredibly familiar. There are times when (especially if you use a lot of boxing and ref-counting) that you can get a touch of operator soup, but that's not that often. Anyways, the languages feel very similar to me.
United to offer passengers up to $10,000 to surrender seats
Try this - https://www.dropbox.com/help/9281
Jeff Bezos Is Just $5B Away from Being the World's Richest Person
> address the risk eavesdropping due to 'bleed style exploits while transmitting my passphrase to BB servers

You are correct. There is a "window of decreased security" where IF there was a zero day hack on the same day you prepared a restore -> your data might be compromised.

> The passphrase should stay on my hardware period.

For some customers and some data, that is true. If you would PREFER to lose your data than to have even a 0.000001% chance of that data being read by hackers then I totally agree with you. A good example is if you will immediately be arrested and sent to jail for the rest of your life if the information in your files is ever discovered, then you should keep the passphrase on your hardware (or preferably only in your head and never written down).

But let's say the data is simply all your pictures of your dogs and your vacations? That type of customer might value increasing the chance of getting the data back over the ultimate security solution. Having a recoverable password lowers security (because anybody who gains access to your email can now access your data) but it increases the chance of data recovery. People forget passwords sometimes.

Different customers have different preferences, and Backblaze tries to offer several valid choices and let the customer decide which one to use.
You are going to get in situations where the "answer" brings up a topic like the "halting problem". The asker might not be satisfied with that.

Or what if the asker has a misunderstanding of computer architecture? "Help, my multithreaded program is crashing!"
Same thing with etymologies: if it has a funny story and not "from the PIE kwa* or possible borrowed during the late 5th century meaning basically the same thing" then it's probably false.
Yeah, they're super flexible, Southwest is pretty amazing.
Wouldn't a better comparison be against people who got Fred or quit?

A divorce can both be a good or a bad thing (for at least one party it should be an expected net benefit compared to the situation before)
> The writer "meant it to mean" that, given a static REST-backend codebase, there will essentially be a static set of message schemas that will flow over the wire. (In "really dedicated to HTTP principles" REST, these are each indicated with their own [...] media type.)

Which might, more to the point, include "application/graphql".

In real REST, semantics are determined by media types of resource representations supported by endpoints.

REST is not limited to mapping CRUD operations on a crude data model to HTTP verbs.
U.K. startup uses recycled plastic to build stronger roads
I think his exceptionalism can be accounted for based on the lawsuit.
Thank you for the comparison. This basically matches my experience as well. Hoping your post gets up to the top.
He made many truly stupid mistakes. But the article is generally clueless. Sure, the Silk Road server leaked the IP of that cafe. But adversaries wouldn't have known that unless his onion server had leaked its physical IP in an Apache error header. And then there were the posts on Stack Exchange and Bitcoin Forum that leaked his real name. Oh, and those fake IDs. Homeland Security found them, before the FBI had a clear bead on him, and he told them that he might have bought them on Silk Road.
I only use ripgrep these days.
In fairness, almost all politicians engage in euphemisms to describe their policies. "Forcible redistribution of wealth" vs "safety net", for example.

It's just that this time you happen to disagree with the policy being given the Newspeak treatment.
So, since these positions are essentially the exact opposite, you're saying you're uninformed, and that this is scary to you?
This is just a teaser for the book obviously... as all this has already been written about multiple times over elsewhere. Perhaps the only additive here is the parallels they draw to SV starups in general and how business itself has become increasing ruthless and universally corrupting; turning wideeyed entrepreneurs into ravenous cash-eating beasts. Seems to beg the question to whether Ross was any different...
Have you read the Presidents Commission on Intelligence Oversight report? Nothing you said is true: the NSA had informed congress and the courts of everything.
Yeah, I am always confused by people who seem to think you need a good reason to fire someone. In almost every state, this isn't the case; as long as you don't fire someone for one of the defined illegal reasons, you are fine. You can fire someone because you flipped a coin, or because you just felt like firing someone.
Yeah, sitting here rewinding dozens of times on Youtube I can see a couple of his tricks. But they all require insane dexterity and coordination. We see in the intro that he's capable of that, which I guess he could have skipped if he wanted to conceal that for us. And that vest of his is clearly not ordinary at all. But I think almost getting it makes it even more impressive really, which is why I think he hints at some of it. It's pretty beautiful.
Here's a much more thorough post on why it's fast. mmap is only a small part of it (a bunch of the grep implementations mmap)

http://blog.burntsushi.net/ripgrep/
From the article: "The image has not been validated or calibrated. A validated/calibrated image will be archived with the Planetary Data System in 2018".

Anyone knows what calibration/validation means in this case? I hope there are higher-res versions coming down.
there was a joke posting on an internal alias that showed the internal /etc/aliases file for Google which had the mailing list going to '|/usr/bin/no'[1] :) I would be interested to know if anyone still there had ever tried that and gotten a yes answer. The three times I used the process it was always denied.

[1] To understand the meta-joke there is actually a /usr/bin/yes program but in the standard distribution there isn't a /usr/bin/no :-)
Fentanyl is also dangerous because the lethal dose is close to the recreational dose so even knowing the purity and doses is risky.
Does the (+) button open a file-open prompt, or is it a list of all previously opened projects?

If it's the former, then it's absolutely useless for my use-case, and a great example of removed functionality.

If it's the latter, then they have gone backwards in UX design (for my personal use case) - that is, it is now an additional layer of barrier for me to see and access all my projects, for what benefit? What problem is this solving?

If the only answer to the previous question is something to the effect of "cleaner UI" or "less clutter" then there is a fundamental problem with how they approach updates.

It really sucks that this is even a thing, because I feel bad for shitting on Atlassian so much, when I use Sourcetree almost exclusively, and have for quite a long time.
I think the biggest problem is the way the economy "booms" based on credit, which led to things like derivatives to take advantage of them. Housing is a good example here.
If you're using F# backend, Gluon generates a typescript RPC. Its saved my team many times. http://www.tachyus.com/gluon/
> The event loop is only used when there is nothing going on.

In async applications event loop is what actually executes your code and performs IO. In essence, event loops are under load all the time.
We take a lot of science's achievements for granted, but if you pause and think about it for a moment it's mind boggling. That thing is 1,5 bn kms away.
> The browser could recognize a Log In link, follow it in the background, and log you in,

As a web developer, this is exactly what I don't want. Just the other day I got bit by font boosting on Mobile Chrome. Couldn't figure out for the life of me why my h1 was bigger than I had explicitly specified. No traces of anything going on on the desktop either. Turns out, my page was being tampered with because someone at Chrome had a "brilliant" idea for mobile. The fix is to specify max-height to something inconsequential like 1000000px. My page just had a header, but font boosting destroys navigation menus and tiles too. Thank you but no thank you.

There cannot be any conflict between browser and web developer. If we have to fight and hack one another, we're both failing.

Font boosting needs to be explicit. And nothing should be done without the explicit intent of the author of the page.

If the browser wants to provide automatic login, then great. Please outline exactly how to enable it, make it as easy and automated as possible, and help decrease my workload. Thank you and thank you.
Bald guy here. Currently using DSC. Can you link that safety razor you bought?

Thanks.
Doing open source in my free time, I've found solace in realizing what is worse than getting barrage of unresearched, silly, or perhaps bad questions:

Getting no questions at all.

This means that nobody is using your project, and that makes me feel defeated far more than having person ask me why he uploaded my project's python files to public_html on his $2 shared hosting, and no app is showing up in his browser.
Progressive taxes are not linear, they are at least quadratic. The way many property taxes are set up now in the states, they are flat taxes by zoning - ie, residential pays a fixed rate.

I would absolutely argue for progressive property taxes, and that you either need steep progressive property taxes or homesteading rights to avoid the current bubble of land hoarding by the rich, but we don't have those now, and they should fund other things (and at a much less granular scale) than public education.
While it is not part of the memory safety guarantee of safe Rust, in practice it is much harder to accidentally leak memory in Rust than in C++. There is no counterpart to the C++ new operator in Rust; no commonly-used language feature or standard library function puts the burden of explicitly freeing memory on the programmer.

For those who are interested in why leaking memory isn't disallowed by Rusts safety guarantees, have a look at the documentation of the (AFAIK) only safe function in the standard library that leaks memory: https://doc.rust-lang.org/std/mem/fn.forget.html
The issue I have with that is then these middle-men buyers would step in like they do for NFL and concert tickets, buying up all/most supply almost immediately when it becomes available for any reasonably popular flight. Then they charge double the price, and there's not much one could do other than pay double or not fly.
The syntax is really on the same as C-Style languages, minus the extra lifetimes bits.
https://news.ycombinator.com/item?id=14214772 is more newsy so we'll treat this one as a semidupe (there probably being no need for 2 Levandowskis in the top 4).
It's a minimal testcase; minimal. I thought the blog post was pretty clear that it had nothing to do with how the object was used after (e.g. if it was immediately destructed or not) and even linked to a real world example that would disprove that.

Hence why your holier than thou attitude about not writing smelly code is just asinine and not helpful. It plays into a mindset that people who write "good code" don't have to worry about 'esoteric' bug reports (e.g. like security advisories).
I feel the same way. Don't know any software engineers or developers outside of work, rarely meet anyone in the field outside of the odd meetup (and usually not even then) and come from a family who work in other industries.

However, I suspect it might be a location/culture thing more than anything personal. I mean, over here in London it seems like most people in the tech industry don't really care for it as a passion or hobby, but just treat programming like a 9-5 job without any extra side projects going on outside of that.

Maybe that's the case in Chicago where you are too. Maybe most of the companies there are filled with people who at the end of the day just don't care about tech as much as Silicon Valley folk do. Maybe for them it's just a 9-5 deal like it is for many folk here. There's nothing unusual about that.
Discussed here: https://news.ycombinator.com/item?id=14214772
Ask HN: What MySQL IDE do you use?
MySQLWorkbench is nice, but crashes a lot and isn't very customizable (for example, there's no way to do light-font-on-dark-screen).
Sequel Pro is nicer in that regard, but it doesn't support multi-tab within the same connection and further "doesn't regard itself as a query editor."
There's no save-as selection on the menu. If you use the keyboard shortcut, it'll try to save over whatever you last saved, regardless of tab.

I'm happy to pay for something good, especially if it's cross-platform; is there something good that people use?
A damages award could be large enough to change the economics of Uber's project.
Thank you for sharing will definitely check this out
Indeed very simple and maintainable chat app
Haha, yeah go ahead and try to fight this battle. You'll lose.

I'm constantly baffled by bug reports I receive. From other people who work at my company. A tech company. A large one. You've heard of it.

We log every operation in our API. I cache errors, and the API returns a JSON formatted error with a GUID that correlates to the operation that failed, so if I have a GUID I can look at exactly what happened every step of the way, and what went wrong, in the logs.

Most of the time, all I need to fix a bug or tell you why you're having a problem is the GUID from the error message. You don't even need to ASK a question. I log stack traces of any exceptions that occur so our logs are almost as good as running the software through a debugger.

The bug reports I'd expect and want?

"Hey, I got this error message that I copy/pasted below...can you tell me what's going on?"

<two line error message>

I have NEVER gotten that bug report. The bug reports I get?

"Hey I think your system is down."

"Is something wrong with your system?"

"I tried to do something and got an error. Is something wrong? No, I don't know what the error was."

"We're getting this weird error when we try X. I dunno, it was just weird. It works now though."

"I think the data you're returning is wrong."

Or my favorite:

"Hey, we've been discussing this issue we've had with <upstream system> that depends on your system. We assumed your system has been down for the last couple of days and have been blaming your team in email threads you're not on because <upstream system> isn't working. Nobody told you or your team. When is your system going to be fixed? No we don't have any examples or any record of error messages from your system."

(Resolution: problem is bug in <upstream system>)
You used to be able to do this in the long-ago; you'd even see people selling tickets in the classified section of the newspaper (kids, ask your parents).

The problem is, the airlines would rather make more money by selling the new person the ticket at an inflated price (presumably if they cared enough to save money, they'd have bought in advance), and from you as well in ticket change fees. This was sold to us as a post-9/11 fix to ensure terrorists didn't buy tickets, but I doubt that was the underlying reason.
Eight? Scratch.
Erm, no. You can do shared thread storage, in Python, it's just that it doesn't really scale. I've done it for small daemons without significant hassle, and even wrote my own Go-like CSP helper: https://github.com/rcarmo/python-utils/blob/master/taskkit.p...
The prime purpose of CT is unification, showing that many familiar things are instances of the same idea. In that sense CT is shallow, you can always in principle do without CT what you can do with. But without the abstract view afforded by CT, you may not see similarities.

Here are moderately practical things that came from CT.

- CAML, the predecessor to OCaml had a virtual machine based on category theory.

- Monadic effect handling, which is an approach to modularising computation, is based on category theory.

- Remarkably, Bell's theorem from physics and database theory share a surprising amount of structure, see [1].

- Modern libraries like Scala's Scalaz.

[1] S. Abramsky, Relational Databases and Bells Theorem.
We detached this subthread from https://news.ycombinator.com/item?id=14214782 and marked it off-topic.
Even if the free market choice could do it, I would still want regulation. Because there's no reason to allow them to act in this manner, so just bar them from doing so altogether.
The problem here is really selling all seats for the same price.

Airlines know that some customers are price-sensitive, e.g. those planning a trip months in advance, and some customers less so, e.g. business people flying out to a last-minute meeting.

So if they just sold all the tickets for the "average" price, they simply wouldn't get as many customers, because all the price-sensitive customers would go to their competitors still doing things the old way, and there's no guarantee that they will attract enough of the less price-sensitive customers, unless they lowered prices even more than the previous average, and if they actually make less than the current average price, this is simply not a viable plan.

In addition, since the customers you have left tend to book later, you won't know for sure if you're filling up your plane or not until closer to the departure date, and that could potentially wreak havoc when allocating planes to routes.
... and if you do heed the advice of the OP, and post a well-considered question on stackoverflow, researched to the best of your ability, you will often get back a withering dismissal from some asshole who has taken it upon himself to police against "bad questions".
From the nomx respone:

> Contrary to the blogger's claim that this was an easy, simply hack, in fact, the blogger couldn't make the code work and requested other participants to support his attempts and publicly stated so on his blog. The "payload" he developed was from a third party named Paul.

That's embarassingly bad logic. The fact that this particular guy wasn't an expert at XSS doesn't make the hack hard, and the fact that it exists at all is the issue. What a bunch of fuckin' jokers.
> Makes me wonder if there's an opportunity here. Some service where you can actually pay money up front to guarantee an answer to your question, regardless of how it's worded and expect it done within a short time frame. Kind of like the Stack Exchange sites, except for people with more money than patience.

Bountify sort of fits this. https://bountify.co/
> * "Levandowski was deceiving Google almost from the moment it hired him to work on the Street View maps project back in 2007."

I read this, and immediately wondered why Google didn't immediately fire him? Seriously. When you find out someone is taking your IP and using it for his own profit, you don't put the guy on a sensitive project. I don't care how talented he is, he couldn't be trusted.