skysight-inc/HackerNews huggingface dataset:
With Windows, for your $100 license fee you're getting support and a level of guaranteed functionality. Similar with MacOS, the cost is embedded in the purchase of the hardware and it's guaranteed to work and be supported for multiple versions.

Linux is free. That's incredible, but it means there's no one paid to help you.

When Wi-Fi drivers don't work, mouse doesn't work like you expect it, computer doesn't hibernate properly, or computer doesn't boot, no one is paid to solve your problem.

For computer mechanics and tinkerers, maybe updating BIOS to fix wifi not working is fun or a mild annoyance. For me...I need to get work done. I pay thousands for a computer so I can do my work.

With Linux on a Windows laptop you get none of that. There's an incredible Linux community, but why make them work for free on fixing your mouse?

A Linux-first laptop is one which comes with Linux support from the vendor. That means they've done work ahead of time to make it specifically work for your exact configuration - processor, wifi card, ram, ssd, touchpad. And that with future Linux updates they will continue to update and support your hardware.

The idea of using an OS without vendor support is like Russian roulette for a non-programmer like me. That's why I bought my Linux laptop from System76, a Linux-focused vendor.
> The NSA made Juniper use a backdoored algorithm

It's very important to clarify that the NSA didn't make them use it. The DoD required it as terms for future contracts. Juniper grabbed the money in knowing exchange for putting their customers at risk.

Why does that distinction matter? It dramatically increases Juniper's culpability in the scheme. If the DoD had actually forced them to use it, that dramatically reduces Juniper's culpability.
By big I mean overweight. I’m 5’9”/175cm. Lightest I’ve been as an adult is 90kg.
This is no longer a good reason since Postgres and MySQL support JSON with indexing.

Also, you don't actually need to define relationships. Rails for eons never did this at the database level.
forever, or until rust version update (might be often for nightly builds), or until build flag change or cargo clean, whichever happens first. It's also only a per-project target directory (not across all projects you compile).
I agree with you. I think the monopolists would respond that this is research that should be done by the doctor, not the patient. Patients doing their own research can be dangerous.
Postgres was first to the party but MySQL supports that too since 5.6 or 5.7, I can't remember.
C++ uses apostrophes. If you want to use numbers in header files that are common to both C and C++ code, you want the syntax to be the same.
Decision trees within a molecular memristor
Exploring Special Relativity
Pellagra in the United States
You're nitpicking one example. Putting base64 into std makes the higher level comment go from complaining about 100 dependencies to complaining about 99 dependencies.

So maybe it's harder to work out than you think.
Better Than Wall Street Bets? Millennial Bets Beats the Beast with Bigger Data
Nature article - https://www.nature.com/articles/s41586-021-03748-0
So the study you referenced was ordered by the Minister of the Interior, and it's been the most heavily cited study in the past few years.

If you read it, you'll find it explicitly states they could not establish a causal relationship between investors and increased prices. (i.e. it says exactly what I stated).

They do find a correlation (which is heavily referenced in the news and misinterpreted), which would be expected. Investors who study the market and are investing professionally, are more likely than the average, and definitely more likely than below-average, to invest in neighbourhoods which turn out to see more price increases than neighbourhoods that investors chose not to invest in. That's of course because it's their job and their expertise. It doesn't mean they're causing the price increases.

It's a bit like saying there's a correlation in prices between prices of stocks of companies that professional investors choose to invest in or not. That's obvious, professional investors seek returns, and are expected to invest in such companies. But the investors aren't causing the tech stocks to become valuable. They simply are, by way of their profits. Google (once established) isn't high-value because investors choose to buy its shares. Investors detect the value and pursue to own it. Real estate is no different. Which is why the study found a correlation, but explicitly did not establish a causal relationship.
It's amazing how business seems to understand the free market when it's selling to customers, but can't seem figure out the free market when it comes to hiring labor.
I would choose AWS. They simply seem to have the most complete offering. They have years of experience with offering cloud solutions and they keep churning out new features.
You are correct that in the 19th and early 20th century, we used to 'pirate' just about everything. Thomas Edison made a fair amount of money doing this with movies, for example.

However, you are incorrect about this particular item. Sure, one can produce a font file that is licensed and distributed with a computer/web browser/whatever and it's pretty easy for a determined large group of users to not pay for more than a single copy of said font. At the very least, a user can take said font rasterize / embed it in a thrilling rendition of 'Mary Had a Little Lamb' along with every other letter/symbol the typeface provides entirely legally that all are free to use. More commonly, someone else can re-implement the font that is an (almost?) perfect copy of the original. That's how the computing world got all of those TrueType fonts that were knock-offs of Adobe's Type I fonts and a big part of why Postscript is not really a thing for most users anymore.

See https://www.copyright.gov/circs/circ33.pdf

"Copyright law does not protect typeface or mere variations of typographical ornamentation or let-
tering. A typeface is a set of letters, numbers, or other characters with repeating design elements that
is intended to be used in composing text or other combinations of characters, including calligraphy.
Generally, typeface, fonts, and lettering are building blocks of expression that are used to create
works of authorship. The Office cannot register a claim to copyright in typeface or mere variations
of typographic ornamentation or lettering, regardless of whether the typeface is commonly used
or unique. There are some very limited cases where the Office may register some types of typeface,
typefont, lettering, or calligraphy. For more information, see chapter 900 , section 906.4 of the
Compendium. To register copyrightable content, you should describe the surface decoration or other
ornamentation and should explain how it is separable from the typeface characters."

Notice the 'building blocks of expression'... that's the whole First Amendment bit. IIRC, there was a Supreme Court case about this.
What the hell are you talking about?
My info is first hand.
A combination of SQL, Redis, ES, and Columnar stores in a single package.
When building YugabyteDB, we reuse the "upper half" of PostgreSQL just like Amazon Aurora PostgreSQL and hence support most of the functionality in PG (including advanced ones like triggers, stored procedures, full suite of indexes like partial/expression/function indexes, extensions, etc).

We think a lot about this exact question. Here are some of the things YugabyteDB can do as a "modern database" that a PostgreSQL/MySQL cannot (or will struggle to):

* High availability with resilience / zero data loss on failures and upgrades. This is because of the inherent architecture, whereas with traditional leader-follower replication you could lose data and with solutions like Patroni, you can lose availability / optimal utilization of the cluster resources.

* Scaling the database. This includes scaling transactions, connections and data sets *without* complicating the app (like having to read from replicas some times and from the primary other times depending on the query). Scaling connections is also important for lambdas/functions style apps in the cloud, as they could all try to connect to the DB in a short burst.

* Replicating data across regions. Use cases like geo-partitioning, multi-region sync replication to tolerate a region failure without compromising ACID properties. Some folks think this is far fetched - its not. Examples: the recent fire on an OVH datacenter and the Texas snowstorm both caused regional outages.

* Built-in async replication. Typically, async replication of data is "external" to DBs like PG and MySQL. In YugabyteDB, since replication is a first-class feature, it is supported out of the box.

* Follower reads / reads from nearest region with programmatic bounds. So read stale data for a particular query from the local region if the data is no more than x seconds old.

* We recently enhanced the JDBC driver to be cluster aware, eliminating the need to maintain an external load balancer because each node of the cluster is "aware" of the other nodes at all times - including node failures / add / remove / etc.

* Finally, we give users control over how data is distributed across nodes - for example, do you want to preserve ASC/DESC ordering of the PKs or use a HASH based distribution of data.

There are a few others, but this should give an idea.

(Disclosure: I am the cto/co-founder of Yugabyte)
I can't imagine flood insurance is very cheap in these locations and I don't think this is an imminent domain type situation where the government would buy houses. At some point, people will be ruined financially and won't be able to rebuild.

Other wealthier places may be able to use municipal bonds to fight sea level rise. In the valley in Foster City, the choice was between pricey flood insurance and a cheaper municipal bond to construct a robust levee and the latter was chosen. The city is small enough and the residents were wealthy enough to do it.

I'm kind of curious if anyone will attempt to damn up or construct locks under the golden gate bridge. I think the valley could be wealthy enough to do it.
Just a note that 100% leverage would mean that you’re borrowing against 100% of the portion of the asset you bought to purchase more of the asset. I.e. you put 50% money down and borrowed to buy the other 50%.

A typical 20% down-payment in the US gets you 400% leverage (you used your 20% ownership 4 times over in order to purchase the other 80%).

5% down gets you 1900% leverage.

If you put $50000 down (5%) on a $1M home, it rises by 1% ($10000) and you sell it, then you just made a 20% return on your initial investment. You were leveraged 1900%, and so you got a return 1900% above what you would have without borrowing any $. Nobody serious advises that kind of leverage on any asset except for real-estate, AFAIK.
You gain the value of whatever service you’re using. It’s the same approach of monetizing a site with ads, except instead of “paying” for the site with your data or eyeballs, you’re paying with your bandwidth.

I actually quite like this idea. Any site/app/etc that is free has to make money, at the very least to pay for infrastructure, and I find this a lot less invasive than surveillance, and not “arrogant” at all.
There don't seem to be many practical applications of integer factoring - basically it's good for cracking PKI. On the other hand these recommender algorithms looked really useful for the applications that folks use recommenders in now and for extending to deal with potentially other sparse matrix problems as well. Which is good because the paper here produced a good classical alternative.

This is a problem for QC though because there really aren't many actual algorithms to run on these things that are going to be that useful afaik. At least with analytical complexity results (I think quantum neural nets don't have these yet?) - I would love to see counter examples!

Note - a lot of QC algorithms provide only modest speedups like ^2 improvements - the ^n improvements are the ones we want and are v.rare.
There's a downside to Python's batteries-included approach though:

https://leancrew.com/all-this/2012/04/where-modules-go-to-di...

HN discussion: https://news.ycombinator.com/item?id=3913182

The obvious compromise would be to let libraries bake as third-party projects for a good long while until there's a fair amount of consensus that they're the Right Thing To Do, then pull them into the standard library. Java's Joda-Time would be one example.
That documentary was the first thing that came to mind. That and Jon Julio, crazy guy.
I wonder if Amsterdam specifically is filled with single-family houses. I suppose some larger apartment houses must exist, housing a few families.
Love the octile idea. How hard would this be to expand to the top 100 metro areas? I would like to see comparisons to Texas and Florida metros specifically.
Another few benefits with Bazel is that your build is mostly hermetic and reproducible. I've never had to run `bazel clean` and the output sha of your builds will always be the same (good for signing and security). You can also use remote build execution (RBE) to run your builds in parallel. This makes for a massive performance boost when you're compiling a lot of libraries (packages, source files, etc).

It also models your source code in your build system (exposing libraries, binaries, etc).

I'd love to see a performance comparison with `rules_rust`.
You're right! There's too much money invested - and to be made! People will just have to suffer. Let's keep our focus on what's important.
My papillon becomes suspicious after the first fake throw.
search - really the holy grail. Combine full text search (with tf-idf or bm-25 support. Not the kind that postgres/mysql does).

This is a tricky engineering problem - have two kinds of indexes in the same database. But disk space is cheap. Network is expensive
(especially if you're on AWS).
I suspect that it has to do with any trend that gets too big, and the only antidote is to make the rules into a moving target. This happened with punk rock when I was into that. At some point, the punk bands rebelled against punk fashion, and started showing up in worn but otherwise regular looking street clothes.
Fakturo
3) Fine tuned control over query plans if I want it.

I feel like when most people say this, what they really want is a better query planner.

The optimum query plan depends on a lot of dynamically changing factors: system load, free RAM, and of course the data in the tables themselves. Any hints we give the query planner are going to help at certain times and be somewhere between "suboptimial" and "disasterous" at most other times.

It's certainly true that the query planners in major RDBMS could be better or, at least, give insight into why they made the choices they did.

It would be cool if EXPLAIN ANALYZE also perhaps showed other query plans the planner considered but discarded, and why. Imagine if the planner tried multiple plans and adjusted itself accordingly.

For Postgres in particular, I think the user-specified costs in pg.conf like `seq_page_cost` and `random_page_cost` feel like one obvious area for improvement: why am I guessing at these values? Postgres should be determining and adjusting these costs on the fly. But, I could be wrong.
This depends on what the library does, of course. From a quick Google I believe the parent has made several packages, like a front-end to help with XML trees or a full wrapper around procfs. Libraries that complex (especially with their dependencies) can take significant time to compile, it's just a consequence of their complexity.

Some smaller libraries I've seen that just do some annoying-to-test but simple string manipulations have had similar compile times, mostly because they include specific versions of advanced logging or error reporting libraries for no obvious reason.
It’s an interesting scenario. Your wheels touch the ground; you engage reverse thrust and it instantly fails; you are rolling at dangerous landing speed but now can’t go around?

Relatedly, I wonder why did the pilots not engage the regular brakes ASAP.
On the early Android years I followed with interest what each Google IO brought.

Nowadays I don't care.

Android Java is still cherry picking whatever Google feels like, NDK offers enough for multimedia stuff and mobile Chrome brings enough updates for mobile Web, and most apps are anyway doable as Web sites.

Most OS updates from last years seem just being updates for the sake of forcing everyone to update which APIs they are using on their apps anyway.
True. Adding an extra, capable person to an incredibly small number of people who've considered a problem is a huge increase in total throughput on it. Might be that there isn't much more to it.
This is a really good insight - the trope of the "frustrated scholar-official" is extremely prominent in the Chinese literary tradition. That being said, the ideal of "becom[ing] hermits and enjoy[ing] their life happily after" was something of a literary conceit; in most of the actual literature written by people who tried to do this, there's an extremely strong tension between the idealized/romanticized apolitical world of the hermit, and the reality that farming was very hard labor and not something most literati particularly enjoyed. Probably the most famous example of this is the poetry of Tao Yuanming. (Note: I wrote my Master's thesis on depictions of eremitism in ancient/early medieval China.)
> and the friction for adding new stuff is high

Not really, it's just a 'go get'.
Problem drinkers go through withdrawals. Problem drinkers have lost their job, spouse, kids, or gone to jail. Problem drinkers don’t exercise, they taper and try and get sober or avoid the withdrawal by getting drunk again.

Anything else is normal, binges are unhealthy but it’s not a problem until you’ve binged enough to kindle your brain. Which at that point you’re getting withdrawals and you’ve got a problem.
I have found tailscale to be far more superior. For one, it actually works behind double NAT whereas zerotier just doesn’t
> I imagine there’s zero reasons for using ground spoilers or reverse thrusters in the air, and doing so would probably cause a complete loss of aircraft.

It has, on several occasions, although I'm not aware of any where it was a commanded deployment of reversers in flight.

https://en.wikipedia.org/wiki/Lauda_Air_Flight_004
https://en.wikipedia.org/wiki/TAM_Transportes_Aéreos_Regiona...
Here's my quick partial history of Plain Text Accounting (PTA), to catch you up:

- 2003: John Wiegley creates the field with the Ledger command line tool and its file format.

- 2007, 2008: I and Martin Blais create two new "ledgerlikes", hledger and Beancount, with their own technologies/priorities/maintenance styles.

- 2003-present: Community grows; many helper scripts, tools, docs, and other ledgerlikes appear.

- 2016: To grow the ecosystem, organise resources, and reduce support effort, I coin the Plain Text Accounting phrase and set up #plaintextaccounting IRC channel and https://plaintextaccounting.org. (And in all honesty, also to encourage objective comparison shopping and regain a little oxygen for Ledger alternatives).

- 2017: Colin Dean sets up the plaintextaccounting subreddit.

- 2021: The community continues to grow. The IRC chat is bridged with a Matrix room. Ledger has been "done" for many years but may have a new release soon. hledger has been steadily developing, with quarterly releases. Beancount is in process of a big rewrite. There are some other strong ledgerlikes, currently with much smaller userbases.
But they're not saying "don't always use the names Alice and Bob." They're saying "you're never again allowed to use the names Alice and Bob."
One thing I find really interesting from Redis that I would love in a relational database is the concept of ‘blocking’ queries, which block until they get a result.

For example: https://redis.io/commands/BLPOP

If I could do something like:

Select id, msg
From job
Where id > 1224

And have that query block until there actually was a job with an id > 1224, it would open up some interesting use cases.
That sounds like a riddle. Do the trendsetters control fashion, or does fashion control the trendsetters?

It's probably a complex dynamical interaction.

The fact that the favored brands kept changing though, suggests to me that the corporations weren't exactly in control (otherwise the first winning brand would have presumably preferred to permanently monopolize the market).
The non-amp link seems to be broken, this works for me on mobile: https://www.sfgate.com/news/amp/Health-Dept-Stop-taking-live...
Strange thought: up until 2010-11 Vimeo was a vastly superior platform in terms of service quality(then Google stepped up the game of course). But it does make me wonder what would have happened if Google had bought Vimeo instead and where would either be today
Read, work, speak to people, look out of the window, drink some tea, nothing at all - there are many ways to spend time in a train. The commute would have been just as long (if not longer) by car but that would be time wasted instead of time for myself. Seeing those traffic jams from behind the train window (in the morning, by the time I went home the evening rush was already over) just was the icing on the cake, imagine sitting there in a tin can, waiting for the tin can in front of you to move, with another tin can behind you waiting for you to move...
This is exactly how they "make" a company do something. Look at what happened to the Qwest (IIRC?) CEO to see what happens if you refuse these contracts.
Not sure if they edited the comment after you commented, but that is a bitfield now, at least
I don't know if anybody from CockroachDB is reading this but their article[1] on serializable transactions is somewhat questionable, as it compares CockroachDB's Serializable to Postgres's Read Committed, which seems to imply CockroachDB is better. Of course, Postgres has serializable as well. The only novelty in the article is that Cockroach DB runs Serializable by default, so I am not sure what that comparison was doing.

[1] https://www.cockroachlabs.com/docs/stable/demo-serializable....
Funny this should come up.

I'm now in San Diego near the beach, where there are many miles of boardwalk, perfect for blading. First thing I did was buy a pair of skates (k2 84 boa). I love going out in the early evening to watch the sunset.

As I skate by with a big smile on my face, I often hear tourists say they should get some.
Informative as always man
Now I need a "top 10 myths about driving in Japan". I thought Japanese drivers obeyed everything to the letter. I also thought Japan was a tiny car market and defacto pedestrian (its one of the biggest markets).
I stopped because if I did it too much my knees really hurt.
They totally understand but they also know that lying and propaganda work extremely well and are cheaper.
Why not do tech in the marine industry? Even software devs in that industry get to do on water testing.
I too wonder if certain "unsolvable" problems could be solved by bright minds if presented as something as mundane as "homework".

The 4 minute mile was thought to be impossible for a long time. Then within a year of a it being broken - countless other athletes also ran 4 minute miles because they now knew it was actually possible.

It can be surprising just how effective limiting beliefs can be.
Sure, fair point.

Nevertheless, vaccines do significantly still reduce your risk of infection. Agreed on the rest.
Wildly reinvented wind turbine generates five times more energy t