skysight-inc/HackerNews huggingface dataset:
Haskell is not declarative. It is a specific form of lazy + graph-reductive. Thinking of it as declarative leads to polynomial exponential runtime cost in CPU/memory and not understanding why or how to fix it.

https://stackoverflow.com/questions/40130014/why-is-haskell-...
Anybody done some "diff - u [vanilla] [vendor] > patch" work for these SBCs to fork their kernel? Maybe keep it up to mainline?
This paper is very light on details. It defines "RInK architecture" as something which uses stateless application servers w/ key-value store as backend (Redis/Memcached). Section 3 then shows that it's faster to use a stateful application server, but skips any details about scaling/durability which makes the comparison kinda strange. Are they really just comparing a single-threaded in-memory application server with a scalable system of stateless application servers?

Their solution (LInK) is a key-value system "as a library": You link it into your application servers and you can then store data (they become stateful). The system will automatically handle sharding, replication, consistency and so on. From your perspective you're working directly on memory. You still need to implement marshalling, but this is only used for sharding/replication across nodes (which the system handles completely for you).

They say nothing about how this system handles data consistency/replication/durability, so it's a bit tricky to assess it. They also have this nice note: "(since, for performance, persistence of state is not guaranteed)".

Summary: This is a system which couples your application logic with your persistence layer (in the same OS process). This can give you great performance as they co-side with each other.

Looks like a very cool project, and I'm actually surprised there not more "database as a library"-projects out there.
> Any longtime Cloudflare users comment on how rare an event this sort of thing is?

I've been a Cloudflare user for 7+ years and a Cloudflare Enterprise user for 2 years. Before joining Enterprise, Cloudflare would suffer some kind of global or localized network outage (that impacted our operation) about once or twice a year. Most localized ones don't really get reflected on the status page properly. After joining Enterprise, this is actually the first observed incident we've encountered so far.

Though it might not be a Cloudflare-only thing because funny thing is... Verizon Fios is also down for everyone I've talked to this morning.
While I find your inlined example very bad to read, I think there are many attemps IDEs do for this. I remember some showing the function stub of a called function when moving the mouse on the call instruction. I also know multiple editors that allow to quickly browse the source code with CTRL+Enter (or CTRL+Mouse click) in a similar fashion as we click on links in the web. I personally never found indirection to be a problem. It's rather the solution.
Is everything in iambic pentameter?
probably just using ETS out of the box
Before you use a password manager
I think the point is that RDBMS are considered stodgy and uncool despite the fact that they can be extremely sophisticated and powerful.

Cheap, "faster," less-reliable stores became very big around the Mongo explosion - and don't get me wrong they can have a place, particularly Memcached and Redis which are great for ephemeral data - but you can do a lot of that with a RDBMS.
You had me until thermodynamics. We're obviously not getting every substance in our bloodstream like we are with plastics so I don't think thermodynamics is the issue here.
The etiquette is to not discuss votes on your comments. For what is worth, I suspect people dislike the snideness and lack of effort in the comment, not the notion of financial education.
> I finally have a good reference to point folks to when I get the question about why I'm not using redis.

What are you using instead?
I also have never had issues with REI for sporting goods/outdoor gear, or Barnes and Nobles for books.

If I can avoid Amazon I will, if I can’t I try to order directly from the manufacturer and no other seller.
When I was 9, I cried all night because I realized that one day, we might meet aliens and go to other galaxies and whatnot, and I would just be dust in the ground by then. The thought of thousands, millions of years of events and me just having been a blip, felt crushing. And there are many people I miss, and many people who died before I was born I would have loved to get to know; that I "made peace" with that doesn't mean it doesn't make me sad. It is sad, it's sad that people die, even after a long life. It's sad for friendships to end. But that I'm sad doesn't mean I'm not also happy and grateful, and prefer to be content with being a single finite thread in a much bigger tapestry of life, rather than just going on forever, kinda defacing that tapestry.

I mean, that's the binary "immortality" option. I'm not against medicine, or people living longer. But if someone genuinely wants to live forever forever, I really would question how much they thought it through.
I'm less inclined to think this is a message from billionaires, and more a message from the NYT
> all the banks in your sources involved in money laundering of "Russian money" are big non-Russian (Dutch, German, Estonian, UK, Swedish, French and so on) banks

And Revolut is a non-Russian service. Hence the comparison.

(Money laundering has three steps [1]. Dirty Russian money is typically placed with Russian banks. It is then layered between Russian and non-Russian banks before being integrated by a non-Russian bank, thereby masking its origins. Given the amount of dirty money flowing out of Russia, a Russian account tends to gather more scrutiny than e.g. a Danish one in the same way a Colombian account garners more scrutiny than a Miami one.)

[1] https://en.m.wikipedia.org/wiki/Money_laundering
Step 1: Fire the army of accountants they no doubt have to find every little tax trick and loophole to reduce the taxes they pay now.

Step 2: Send in extra. Whatever they believe the rate should be. The IRS won't complain.
Isn't a stateful service basically the actor model with optional persistence, like in Akka.Persistence model?
In theory, this abstraction of small details is not a problem, but in cases like this, I would prefer to see the inlined version, simply because, in many languages, a function call raises the possibility that it has side-effects that you might want to know about. In code that is abstracted to the max, that is sometimes a difficult question to answer, even if your IDE lets you easily trace the call stack as you read.

There is a related problem that causes more trouble, but it cannot really be blamed on the initial abstraction. It goes like this: you have something, such as a foo-ness test, that is needed in several places, so you abstract it as a function for all the right reasons. Later on, one of those uses changes, and needs slightly different logic than the other cases. Instead of writing a new function (that may, as part of its implementation, call the original), the person making this change (not you, of course!) modifies the original function to handle both cases. This, by itself, makes the code more complex than necessary, and it gets worse if the criterion for which path is taken in the function is not something that has any significance for someone who arrived at this function through reading the code for one of the other cases that call it. And if the new path has a side effect, now all the other cases are also calling a function that potentially has side effects...

This is how code rots.
Human beings are astounding! Assuming the Earth is about 5.972 sextillion (1,000 trillion) metric tons, we've converted .000000000000134 of the Earth into plastic. No other species could have accomplished this. A testament to our ingenuity.
As an aside, there is something to be said about the size of Cloudflare when global network problems are reported as being Cloudflare issues.
We've used Apache Thrift for the same reason on some projects.
That's the story that we have as the public - Slack started as a chat feature within another project.

Similarly, Youtube's supposed origin story is that it was the video part of a dating app. At that time, online dating apps were being funded by VCs (OkCupid and even HotOrNot may have been still going strong) so it makes sense.

The primary point should be that to find unicorns investors should be looking for good founders and teams first and products second fundamentally because products are flexible and plentiful while talent and ambition in the same body is not. This is what I think YC is also attempting to do.
> Large debris are just the tip of the iceberg.

One reason for The Ocean Cleanup's current work is to get the larger parts now, before they degrade to microplastics.
Erlang/OTP provides a system of stateful processes that communicate via message passing, with a focus on resiliency and fault tolerance.

These processes can seamlessly interoperate while running on multiple machines.

This makes building stateful application servers a pretty natural fit.
I like IntelliJ's "Quick Definition" shortcut for this. It allows me to see the definition of a function in a popup window so I can quickly glance at what a certain function does without the full context switch.
There's one thing I don't understand about this all, it looks like Allegheny Technologies Incorporated (AS396531, a suspected original leaker) was originally announcing 192.92.159.0/24.

How the heck did their peers not manage to filter a sudden announcement for a range big enough that it managed to snag both 8.8.8.8 and 1.1.1.1. Do upstreams really allow a tiny /24 AS to randomly announce a /4 and get away with it? Or am I misunderstanding something fundamental about how BGP routes are allowed to propagate?
Yeah. The length of commute that people are willing to tolerate is approximately constant, so as transport provision increases the number of people who work in a given city increases, capped by that same commute time. Given the value of agglomeration effects (there was a recent piece here on how authors are more productive if they work around others), isn't that what we want?
You're not far off, I'd analogise as

"redis, but compiled into your app, with all the necessary bits to make that work like you'd hope (consistent hashing/replication), (native data structures)"
Stateful applications with the linklet abstraction seem a nightmare to operate just like plain old stateful webapps that keep sessions in memory (requiring sticky sessions and annoying users when shut down).

I understand the dislike for using in-memory databases as a json store (by reading/writing entire objects at once), but if you're using Redis this way, you're doing it wrong.

Another thing that the authors authors seem to forget is that "rinks" also provide coordination across multiple instances. Locks, atomic operations, transactions, even pub/sub is useful to get the right amount of coordination between instances (see my take on preventing cache stampedes https://github.com/kristoff-it/redis-memolock).

Once you move to their new version of stateful instances you get all the operational downsides and lose all the coordination features. "auto sharding" is not going to be enough to solve all coordination problems.

Calendars are a good example of a domain that is tricky to model as a bunch of kv operations, but nothing that can't be reasonably decomposed by applying DDD + the repository pattern + transactions + lua scripts (in the case of Redis). And if you end up with something that is computationally expensive, then it means that you need a custom data structure and maybe an algorithm optimized for it, and this is where Redis Modules come in.

The real domain of "rinks" is not your business domain, but the implementation domain of data structures, algorithms, asymptotic complexity etc. Thinking that the focus at that level should not be on compsci, but on the business domain, will inevitably produce bad performance.
There's even databases that are focused on increasing the capabilities of rdbms.

Point is that sqlite could take people way further than they think. Postgres incredibly far. By the time you need a caching layer where key value stores shine best you have many options you can do and resources to do them.
I'm somewhat baffled by this simultaneous behavior- if the rich want to be taxed, they have all the wealth to make it happen. Hire lobbyists to close tax loopholes. Hire lawyers to go after the rich who tax-evade or the accountants that support them. Donate heavily to politicians who support taxing the rich. Invest in muckraking journalism. Donate money to economics academia with strings attached that force academia to teach taxing-the-rich doctrine.

What I see here is a small minority of wealthy people who are already invested in the social politics of being a wealthy progressive but are not putting the money where the mouth is. Are there wealthy progressives putting a Koch brothers strategy on their political goals? Why or why not?
I have no money and have no intention of acquiring any.
Google spent ten years researching what makes the 'perfect' manager
I find your example actually being a counter-example. The comment should rather be at the top of the definition/implementation of is_legacy_user, so IDEs and users can read and extract it when neccessary (thinking of Javadoc/Python's docstrings). The obvious advantage is that you want to keep comment and function in sync, and not all the calling points distributed around the code. Also, your example is a counterexample because the function name should be spelling, and a comment like

/* Checks if Foo */
is_foo(...)

obviously duplicates the same information.
Too bad Medium is a politically biased fake news rag. Seek other employment for legitimacy.
This doesn't solve the problem generally. The goal is to get ALL such folks to pay up, not just the volunteers.
"Steel Bank Common Lisp: because sometimes C abstracts away too much"

https://www.pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembl...
I came here to comment the same thing. Cloudflare is too big.
> Additionally: when you're up for buying a house and all the lender bank has to look is the credit score, you will be paying more interest than if you apply for a credit at the bank that has handled your business over decades

[citation required]

In my experience neither credit score nor past business have a significant impact on interest rate. Price and value of the house is everything.
Also, they can disengage from tax avoidance schemes and pay full price on taxes.

I’m all for billionaires paying more, but two things: the billions from billionaires don’t add much to taxes (it’d be more principle than anything), two, this is socialistic thinking on the part of the billionaires trying to coerce this on others. They don’t want to do it unless others do it.
Unfortunately chargebacks aren't as simple in the EU, in addition to country-specific rules that make them hard to use in some countries.
How to enhance mobile interactions for users
They presumably don't want to be the only rich people carrying the extra tax burden.
Huh, the new cores are Spectre vulnerable for the first time for RPi.
No, it doesn’t need to be the case that you become a self employed contractor.
It's not seen as a big deal here in Sweden, partially because of history, and partially because of banking regulations, with some of those being EU regulations.

Note that I don't believe having companies - especially large ones that isn't primarily banks - in control of payments of any kind is a good idea, I think it's a terrible idea.

Yes, us Swedes use cards a lot, and almost every card in Sweden has Visa or MasterCard stamped on it.
Most are debit cards, and the well know logos weren't there to begin with. Initially, almost all cards were debit cards issued by the various Swedish banks. Banks that people used to trust back then.

While those payment systems are technically private, they aren't perceived as such. Maybe because of the banks, maybe because they are regulated quite heavily, but people generally have confidence they won't be cut off by the bank. Personally I don't know anyone, or have heard of anyone getting denied a debit card. While that's not a useful statistic, it shows why people might perceive it the way they do.

Since 2017 the laws implementating the then new EU banking directives demands that the banks must offer any basic payment solution/product to everyone if they offer it to anyone. There are some exceptions, mostly regarding money and banking fraud, but it seems to be somewhat rare in practice, at least it doesn't seem to have garnered much attention in news.

There are however talks of introducing some kind of legal tender laws, as it is currently possible to get into a situation where you have money, but can't pay. Which is obviously terrible.
Slicer paper: https://ai.google/research/pubs/pub46921
Then they can't pretend to care about desktop users anymore - I just think it'll damage them and their brand in the long term.
It says tax us, not tax me. The difference is the core principle of taxation: very few people would voluntarily pay 30% of income or so, but a clear majority supports the requirement for everyone, including themselves, to do so.

Put another way: taxation is one cooperative solution to a prisoners' dilemma.
How crazy is it that we allow companies to take a percentage cut of EVERY transaction we make? How often do you NOT use a credit card or some other payment system with a middleman? It's become so commonplace that the idea of replacing cash entirely seems normal to people. And yet this normal state of things involves a middleman taking a cut of EVERY transaction!

Jurisdictions literally have to enact laws today to prevent businesses from going completely cashless, which essentially means jurisdictions have to enact laws to prevent middlemen from taking a cut of EVERY transaction made.

The cash system does not require middlemen in order to transact. And people have historically not been denied the ability to handle cash, as they are denied credit cards or bank accounts today (yes, a sizable number of people are denied even bank accounts and/or are forced into bank accounts with high monthly fees in order to just get a debit card, which is arguably the most basic requirement for purchasing most things today). With cash, people who had some financial difficulty do not get extorted even more (in the form of having to pay for "subprime" services) on top of an already existing percentage cut of every transaction that the middlemen already take.

Unless a new platform can reliably offer a no-fee or at least an absolutely ridiculously low fee transaction platform that absolutely does not deny anyone access nor extort anyone for the ability to gain access, AND we can be reasonably assured that no central organization is using it as a tool to load people onto its platform for later extortion....essentially unless we can get almost exactly the same open access as cash...unless we can get that, I don't support it, and probably neither should you.

(Disclaimer: I admittedly haven't looked into the details of Libra yet)
Same FIOS issues for me. Any idea how this is all related?
OK, here's a scenario.

You're hosting an event. You want to provide the attendees (~2000 people) with water. Do you provide large water carafes with spigots, and disposable (4-10oz) cups? Or do you provide (20-30oz) water bottles?

In my experience, people (especially college students, since that's the demographic I'm used to working with) are much more likely to hold onto a water bottle until they finish all 20oz or so, but grab a cup, fill it, drain it, and throw it away...then go back 20 minutes later and repeat the process.
Yes unfortunately my example is not very readable, but it was to illustrate the idea of including the sources of the called functions.

Indeed, many IDEs allow you to easily display the source code of one function at a time, by navigating to the sources of the function or by displaying it in a pop-up, but the idea I had in mind is to be able to view the source code of the function with all its dependencies at a glance.
SQLite (:memory:), lmdb, berkeleydb, memcached-over-unix-socket, APCu (php), EHCache (java)..

I'm sure there are others; I don't get what this paper presents that is new
Always had a feeling about this company. Thanks for bringing it to my attention. I'll be closing my account after this summer.

I only signed up because no other service offers virtual credit cards that you can only use 1 time. :/
So they aren't volunteering, they want to force other people to pay.

And perhaps give themselves a moat by making it harder for the competition or newcomers.

Great. So much for their altruism.
> Do you think there's any other architecture that would've had better results -while still not taking too long to train?

You could easily finetune a pretrained GPT2 model on your lovecraft dataset : https://github.com/minimaxir/gpt-2-simple
TL;DR of the authors argument is that you could plant someone inside Lets Encrypt to take over the KMS. No further mention of how, goes on bashing it because its free and has no "skin in the game". And all of his worries are due to the people managing certs in an organisation, not Lets Encrypt itself.

Follow by a careful pointer that you should buy certs from a CA and not trust "free" stuff. And on top of that BUY CYBER INSURANCE.

Jesus, is this the new hot thing in online marketing? Love the name drop of Digi Cert in it too. Gonna go buy some certs of them /s
APIs are interfaces (it’s right in the name!) and should never be directly tied to implementation because:

1. the interfaces must remain stable to the outside world that relies on them

2. They select what underlying resources and functionality is accessible by outside users, and what is hidden. A lot of your internal implementation is either a mess, “temporary”, insecure or intentionally internal.

3. They control access to the internal application through authentication, authorization, security, and translating data in both directions.

4. When the internal representation changes, they map the new implementation to the old interface to ensure the system remains reliable to API consumers.

5. They offer migration paths when change is necessary

That being said...

Auto API generators are really useful for internal systems where you control the underlying system, the API, and all systems relying on the API.

They are also useful to build an initial API that you plan to fork.
Maybe not directly scamming exploiting this mechanism, but it might destroy the healthy habit of URL checking and being aware of what is going on. Instead people are given a false "seamless" experience. In the future similar white lies might be adopted by other companies, and eventually exploited. Just like the endless bombardment of cookies warnings trained people to just click through "OK"s and "Accept"s. Paired with introduction of the new Google portals, people might get used to opening a site within a site, or a site that is not the site. Now you can scam people by making them believe your shady website has a seamless Paypal/Visa portal, but it's just a css copycat and a private database of fools.

I don't know why I'm always weary of increased levels of abstraction in interfaces.
Hypersonic Missiles Are Unstoppable, and They’re Starting a New Global Arms Race
It's not entirely a hack, but it's a perception trick that makes Chrome seem faster despite it not rendering as quickly as FF.
I have a year-old startup and this is the first major Internet outage we've had to deal with... was really awesome to have your play-by-play and definitely changed our incident response (for the better!). Thank you so much.