skysight-inc/HackerNews huggingface dataset:
Problem: once you have multiple such tables on a sheet, adding and removing rows or columns to such tables becomes hit and miss.

Numbers will happily shift down tables to make room, but Excel won’t.

Array formulas are another sort-of alternative for Numbers’ tables, but there, too, the implementation could be better. You can’t insert a row ‘inside’ a range of rows covered by an array formula, for example.
They seem to be indeed going strong. I don't really see a viable alternative to MongoDB (document db). Fits well in a lot of use cases.
Edit: we (Syncari) use MongoDB, we are not a very large customer but have a cluster that handles billions of documents
If all your fixtures are equally recent, it's likely that the toilet is the biggest use. But it might also be the most difficult one to reduce. In any case your per-capita consumption is already exemplary. Here in California the most extreme conservation measure they have managed to think up is households using more than 1000 gallons per day will be charged slightly more at the margins. I always look at these conservation proposals, then I look at my own bill, and I figure there's nothing I personally need to do.
I got this message as well on an account I only use to play forza horizon. It’s obviously not some kind of fraud detection and just a way to extract everyone’s phone number.
...refers to the architecture as x64, which is a very Microsoft thing and a bit of a misnomer.

No, it is not. Various Linux distributions even refer to it as "x64" in various places:

https://access.redhat.com/ecosystem/software/1474383
https://developers.redhat.com/products/openjdk/download
https://support.quest.com/download-install-detail/6109808

With that said, I personally use "amd64" which coincidentally, is the same thing Microsoft refers to it various places including Windows packaging itself:

https://docs.microsoft.com/en-us/windows/win32/midl/-amd64

This is definitely not a Microsoft thing.
This is a matter of style; we encourage writers to write this way and trust that readers know the difference between fact and opinion.

Go through a typical college writing class and the teacher will direct you to delete phrases like “I think” and “I believe” from your writing.
I find Ruby to be more straightforward than Python. In isolation, I’d argue Ruby is greatly more readable and understandable than Python.

In practice, Ruby code isn’t. Once someone starts doing advanced meta programming, get the shovel, because you’re going to kill whoever wrote it and need to bury the body.

Rails largely gets away with this by having opinionated design, good documentation, and a large user base who have already written answers to your questions.
This argument seems bizarre to me considering the volumes of money banks work with and the lack of programmers who only use banks that take Firefox. I'm not sure what you're expecting, that banks are just doing it to spite Mozilla?
I for one am glad to run a version that Eric S. Raymond has officially blessed.
> We’ll recover or replace up to three times within your three-year coverage. If by some freakish bad luck your bike is stolen a fourth time, we won’t be able to recover or replace your bike, but we will provide you with full tracking information so you can hunt it yourself.

From: https://www.vanmoof.com/en-US/peace-of-mind
I am sure in a memo like this they need to lay out all the practical business reasons why their company should make this move, but ever since this news [1] came out in 2019 I've suspected that Ring had other uses to the then richest man in the world, as a massive private surveillance system.

"Beginning in 2016, according to one source, Ring provided its Ukraine-based research and development team virtually unfettered access to a folder on Amazon’s S3 cloud storage service that contained every video created by every Ring camera around the world."

Now, you can easily imagine that this started as some engineers' innocent attempt to improve their machine learning algorithms. But at the same time, this system was purportedly active at the time of the Amazon acquisition, and while there is no way to prove their motives, this seems to me like a huge perk for someone who is one of the most powerful people in the world.

[1] https://theintercept.com/2019/01/10/amazon-ring-security-cam...
This FOSDEM conference from Frédéric Bisson might interest you: https://archive.fosdem.org/2020/schedule/event/retro_revivin...
some people have been using vim on a daily basis for years but have never used any directory functionality, only the text editing bits
I recently bought an ebike that doesn't include GPS tracking. I was thinking of hiding an Apple AirTag under the seat, but then I read this:

"AirTag is designed to discourage unwanted tracking. If someone else’s AirTag finds its way into your stuff, your iPhone will notice it’s traveling with you and send you an alert. After a while, if you still haven’t found it, the AirTag will start playing a sound to let you know it’s there.

Of course, if you happen to be with a friend who has an AirTag, or on a train with a whole bunch of people with AirTag, don’t worry. These alerts are triggered only when an AirTag is separated from its owner."

(https://www.apple.com/airtag/)

So in an effort to prevent stalkers from tagging victims, the AirTag beeps to give away the fact that it's tracking something "separated from its owner." This makes it useless for my use case because if my bike is stolen, it will be "separated from its owner."
From the original article:

>Whistleblower awards can range from 10 percent to 30 percent of the money collected when the monetary sanctions exceed $1 million.

The incentives work fine in this case. The whistleblower gets a fraction of the fine recovered from the perpetrator, so the net effect for the government is still positive.
Yes! One nice aspect of version controlled notes: change management "trail". Meaning that I don't have to note what specific changes occurred to a requirement in a project but can just change the requirement. If I need to research why something took longer than expected one of the first ways to research that is via file history from git or from Gitlab / Github's History user experiences.
As I've now learned, you used to work for the Internet Archive. You should probably start your statements with that.

> If you've taken no self-help measures to limit access...

robots.txt was a nice self-help measure.

> ... then bad actors, unobservable to you and regulators, will still be doing whatever they would like to do and can get away with.

Regulators still have to follow regulations. You are right that I can't stop someone from creating offline archives - but they're not really who I am worried about. Nor am I worried about the small servers that keep copies of documents during transmission, unless of course they're doing so for criminal reasons.
Loved this, your opener reminded me of a personal shift I decided recently. Because I have had family in politics, it had always floated around as an option, so for some time I was subconsciously like "let me muzzle myself on social media as if I may run" and today I've decided something like the opposite, "let me actively insure that I'm always able to say what I want by doing that now and if it cuts me out of something, then I probably never needed to be there."
Every one that I see is a pretty weak summary of a decades old idea, but presented like its new research.
I agree, ruby's @ and @@ probably will make it a bit harder to read for anyone that is new to both languages, plus it seems more lengthy to me, python wins.
Yeah, it's suspect when people complain about getting judged for their views, then fail to state what the views are. It often turns out that the views in question are something that people have good reason to disapprove of - racism, homophobia, transphobia, etc.
I don't really have enough experience with this stuff for my opinion to have value, but a lot of the opinions I see here appear to me to be dancing around the real question.

I disagree with the terminology in the article. "Soft deletion" suggests that the complexity is in the "soft" part, and that a common way of implementing it is problematic. I disagree. There isn't some orthogonal "soft vs hard" dimension to a generic concept of deletion. The complexity is in the meaning of deletion.

In accounting, you don't simply delete. Or when you do, you really do, and the two operations aren't the same in any meaningful sense. If you want data to still be available—whether it's for debugging or analysis or auditing or whatever—you should be thinking about the semantics of what you need, and structure your data model accordingly.

The `deleted_at` column approach is a DB design smell if it isn't supporting application logic (where "application" may include auditing or whatever). It works against the DB's mechanisms to maintain data integrity. FKs are just one example.

An example: consider the place where you want to keep historical data, but you're also going to be modifying your schema. If you use a `deleted_at` column, your migrations will start inventing more and more things that were simply not true at the time a deleted row was alive. It will lie to you. It's the same if you move data to a single deleted data table and then migrate that table repeatedly. For maximal semantic purity, you probably ought to leave "deleted" data in a historical table matching the historical schema, and then use views to glue things together for convenience. If you update the live data schema in an incompatible way, you might even be saved by the FK constraints on the archive tables.

But that's a pain, and whether or not it's less pain than the other approaches depends again on what deletion semantics you are targeting. Crossing your fingers and closing your eyes and hoping that your chosen mechanism's semantics are close enough to the semantics you need is going to bite you.

A `deleted_at` column can absolutely be the right solution if your rows have a status that changes over time, and one of the statuses that you're willing to support (with potentially brittle code) is "archived".
I would like that book but with Metric examples.
Doesn't your linked article explicitly say overbidding is going on?

But yep funnily enough the second highest bid would have generated a half decent return. The winners overbid because it was competitive, and they didn't feel smart when they found out how much higher they'd bid.

It's worth asking anyone who spent time bidding on these things. No one will tell you it's easy money or that there is underbidding going on.
If you're in the US, I wouldn't worry unless they try to sue you over it (in which case just show up to court and the judge will send them packing). They are very limited in recourse for even legitimate bills.
Software is underpriced for the value it generates.
No viable alternative? Why not one of the many other document db's, such as CouchDB? Genuinely curious what MongoDB does better in general than all the other document oriented databases.
I think the point is that most people just immediately type `pip install ...`, without thinking about which interpreter it's tied to.

It's fairly common for beginners to tell me they installed something using pip, then the Python interpreter can't find the package.
It's not half true. It's 95% true because you and others form judgements about each other but they:

1. Almost never stick for a long time.

2. Are rarely deemed important (most people are not vengeful).

3. Are usually minor.
> The main problem with views for this use case in practice is that they ossify your schema. Views and matviews are effectively a dependency tree, and many common types of schema evolution become substantally more difficult when the system forces you to wrap your DDL in a series of view drop/recreation steps.

You're not wrong, especially with the second part. I.e., deeply nested or convoluted dependencies between views can definitely make it awkward or painful to make adjustments near the root of the tree.

When I started this reply I was going to say "I hear you, but it's not an issue I run into very often". But that's not true. I've actually been burned by that moderately often, and have sometimes avoided or redesigned the root-level table change to avoid having to propagate all those changes to the rest of the dependency tree.

That said, in my experience (also mostly with postgres for this context) I feel like that's usually been more of a developer laziness issue (my own laziness that is), rather than an "ossified schema" issue. It's definitely a PITA when some simple change is going to break a dozen inter-connected views, but that's a coding issue not a deployment issue almost all of the time.

To be fair I don't really use matviews very often, but for true basic views I am guessing that the actual execution of the DDL to rebuild changed views is manageable in all but the most extreme cases. Even then there _should_ be a maintenance window of some sort available.

Thinking this thru a little bit, I believe the "anti-pattern" you're warning against isn't really views themselves but deeply nested/interconnected views (views that query other views, etc). I use views often (for this logical-delete type idiom for example) and I have rarely regretted it. I have often regretted creating complicated view-base dependency trees however, so I think I'm wholeheartedly in agreement on that point.
Insurance has to keep around info for the lifetime of the policy. For some products, that's decades.
I'm not following you at all. Carbon was an API for Mac OS X, not a programming language. It was a C API, not an Objective-C API. (Maybe you are mistaking it for Cocoa, which required Objective-C on 64-bit platforms.) What relationship does this have to the new Carbon programming language?

Google did clobber another programming language with Go.[1] It was a truly a-hole move.

[1] https://en.wikipedia.org/wiki/Go_(programming_language)#Nami...
MSFT is something else. Almost all developers were against Microsoft in the 2000s. Then they "embraced" OSS and Linux since they knew that going against developers would not get them far in the long run.

"Honeymoon" phase

They were catering to devs with free tools like vscode, WSL, etc..., A generous tier for GitHub (GitHub was bleeding devs right after they announced ms just bought them), etc..., Basically, pampering us.

"True colors" phase

The honeymoon is over and now they're showing their true colors. Copilot (devs do the heavy lifting stuff and they get all the goodies), vscode with different flavors (c# related issues), sunsetted atom in favor of vscode (one less competitor), etc..

There so much the dev community can tolerate before going nuclear on them.
Is is also due to the German 'green' party - Die Grünen - having grown out of and on the base of their resistance against nuclear power. Atomkraft? Nein danke ('Nuclear power? No thanks') together with the 'smiling sun logo' [1] have become so engrained in this organisation that it is comparable to sacrilege for 'greens' to acknowledge that they were wrong on this issue.

[1] https://de.wikipedia.org/wiki/Anti-Atomkraft-Bewegung_in_Deu...
> Majority of the streams are gone.

In Australia that's typical for many reasons. Are you sure they're not just seasonal flows?
Use the Active Voice.
Unfortunately the pip developers had the genius idea to add a "user install" mode which pip will default to in this situation. So if you're not root, you won't be able to mess up your system-global Python, but you can still mess up your user-global Python (deleting some ~/.local subfolders takes care of this).
The smelt is food for salmon. You can eat salmon. There is a pretty good and straightforward reason to preserve the delta smelt.
Was that related in any way to the water level, or just cooincidental?
My dad came one day in 1982 with one as they were given them for free. Plugged it, and gave me the manual to figure it out :)

The minitel is an anomaly a sort of black swan. One of those brilliant idea that is not obvious, maybe even not for its creators.

My mom (born in 1952) for the longest time was doing online shopping (La Redoute, CAMIF) through the minitel. She was doing her banking also through minitel.

I got my exam results through minitel... watching those lines appearing one by one was nail-bitting!

It was limited, but it still allowed my parents to do online shopping back in the 80's (40 years ago), and to some extent it put a lot of kids of my generation into computers. Even one French billionaire, Xavier Niel started with minitel "rose" (i.e. online porn) in mid-80's. The government paid for the R&D (CCETT) and the production (it was given for free at first). France was trying to come up with new technologies like the TGV (high speed train from 1981) or the phone card with EMV chip (1984) that you could use in booth to call (no more coins), and the minitel was one of them.

15 years later once at the University (like a mile away were the Minitel was born), my professor fondly reminded us the chaos when in 1985 the french government decided to distribute hundred of thousands of computers in all the schools, and that they had to train more than one hundred thousand teachers to computer science before the back to school. Fun times :)
Until metaprogramming, autoloading, DSLs and everything that eventually makes Ruby code unreadable takes place due to personal preferences.

Ruby is clever, it can be beautiful, but I've never seen a good codebase using it grow well without enforcing strictly opinionated ways of writing it to ensure maintainability. Which breaks a lot of the expectations of some Ruby developers that chose the language because they like to write it in their own way.
Plenty of long water supply tunnels around too[1].

[1] https://en.wikipedia.org/wiki/List_of_longest_tunnels
You hit the nail on the head. Today I was reading this (free) book chapter on the Sustainable Development Goals Series. Three quotes really stuck out to me.

1. Agri-food systems' pervasive externalities imply a divergence between the market price of foods and their social cost.

2. The COVID-19 pandemic has made clear that healthfulness, equity, resilience, and sustainability are interlinked, pre-competitive issues.

3. When faced with massive, systemic, even existential challenges, our ancestors envisioned and achieved remarkable innovations that ultimately begat the agri-food systems we have today, for good or for ill. It is time to do so again.

As we address these problems, we should really keep in mind the interconnectedness of water, food, health, environment, and society.

https://link.springer.com/chapter/10.1007/978-3-030-88802-2_...
I would fight to have your employer let you bring your bike inside. You will become overly familiar with freight elevators, but when your bike is sitting next to your desk all day, it's not going to get stolen.
SEC should use some of award damage to hire more people.
The internet has given everyone the tools to publish a personal newsletter/blog/profile-page, just as only the few could do so earlier. It not only allows essentially-free publishing to the whole public, but also extreme narrowcasting with any level of access-control one desires.

You've not made a case that personal writings should be treated any differently, on either copyright or privacy grounds, nor that the law does treat them any differently.

You've made unsupportable allegations of "flaunting privacy" or "direct attack on individual privacy", and accused those who simply reason from copyright-history as making "bad faith" arguments. And, you are asking for the roughly the same level of expansive copyright interpretation – not at all a feature of the jurisdictions where the Internet Archive primarly operates – that copyright maximalists and DRM advocates do.

Just as you misrepresented the Archive's process for exclusion as requiring a DMCA request – even though your own links complimented the Archive's "straightforward" process – you're now confusing an imaginary claim of "commons" (no rights) versus my narrower claim of traditional balance, fair use, and implied licenses.

And if you think the straightforward, sympathetic, norm-respecting noncommercial policies of the San Francisco' based Internet Archive are a threat to queer and other often-persecuted lifestyles – rather than the opaque data-collection efforts of hundreds of other unobserved entities, platforms, apps, & persistent threats, up to and including actual nation-states – I believe you've made a dangerous category error. The Wayback Machine is a friendly canary reminding people of the risk and responsive to their concerns; others represent the fatal dangers of privacy blowback.

Thanks for promoting my Twitter & old blog posts!

My current & former affiliations are well-disclosed across my web presences - and I often mention my once-upon-a-time Archive involvement here on HN if more directly commenting on Archive details, as opposed to broad principles involved.

But I've not been full-time there for about a decade – and the specific blogspot posts you've chosen to highlight actually predate my tenure at IA. I don't speak for IA nowadays, only myself, as myself.

Yes, my work history is congruent with my beliefs about privacy & copyright on the internet, and prominently disclosed. (My jobs don't dictate my views; my views dictate my jobs.)

Your broken links are, thankfully, available at the Wayback Machine:

2008 "Gordon Mohr Takes Us Inside the Internet Archives" https://web.archive.org/web/20080619045327/http://news.oreil...

2001 "Security Fears for Peers" https://web.archive.org/web/20010331094133/http://www.wired....

How heavenly it might be if only every paid employee (and potentially, compensated advocate) of big tech, big copyright, big nation-state, big regulation, and big ideologies – as they pile-on the votes & comments here & elsewhere – were similarly open about their affiliations!
Anything you bought was charged to your telephone account.
Sanders Slams Corporate Giveaways in Microchip Legislation
> That's what adds up to the temperature difference between the city and the countryside.

No, most of the difference is albedo difference meaning urban areas capture more radiant solar energy.
The OS is just part of what enables tracking; the cell company can track you just as easily regardless of OS. Apple's privacy claims are sheer marketing; their business is not so directly tied to mass surveillance like Google's, so they play the marketing game that the circumstances allow for.
While this is interesting, the project page is a little light on what it can do. Can the RPi feed streams of instructions to the N64? Can it act as a co-processor?

EDIT: more info on Twitter apparently: https://twitter.com/kbeckmann/status/1539738410063208454
Shopify partners with YouTube to scale the creator economy
They're saying it's as close to fair as they think we're going to see succeed.
I agree that having leverage is better than bluffing it. But under what circumstance is it advantageous to tell a potential acquirer that you think you'd either get acquired by them or go IPO? Isn't it better to let the acquirer think that you're open to transactions with other possible acquirers?

Or was the strategy here that he wanted to make them think they're competing with the massive riches received in an IPO?

I wouldn't question the strategy as much if it had just been executed during the acquisition courtship period. But it sounds like he made his feelings clear from the beginning, when he raised $1M from them (presumably quite a while earlier).

What's the benefit of that?