skysight-inc/HackerNews huggingface dataset:
I'll say straight away, IaC for things like AWS in my company at least is invaluable.. the thought of even trying to deploy services with user policies etc, let alone the mess people would make of that is a disaster.

Terraform done right with a provisioning account in the build system to deploy the IAC... It's brilliant. Hands down. Brilliant.
Trinity would have more sense, the impact for a Pentium 3/4 machine would be almost the same and there are KDE1 themes for QT3/KDE3 included in the main theme pack.
> The stupendous sums beings sent overseas but if it gets to domestic expenditure they ("our representatives") get all contentious

Most of the money "sent overseas" is actually spent locally (US "foreign aid" spent in US; Japanese "foreign aid" spent in Japan, etc).

For example, Ukraine is getting shells pulled from inventory (like giving the older, almost expired cans from your pantry to the food kitchen). The "Ukraine" money the WH and Senate want to spend will be spent on replentishment and building up capacity because the US has lost its capacity to rapidly build up production, and is worried about needing to fight another war.

A lot of food aid is actually sending surplus overseas to keep agricultural output high. Farm subsidies are a huge welfare plan to wealthy farmers (not poor ones) but the federal government doesn't want to risk a food shortage, so they support overproduction and send some of it overseas because there isn't enough local demand or much less foreign demand from rich trading partners.
As someone who tried to get Frama-C working on existing code: No, annotating existing code is not much easier than rewriting it. In fact, to make these annotations practical, I had to rewrite parts of the code anyway.
Sorry this happened to you. It is indeed correct that the Asahi installer does not support encryption, see https://github.com/AsahiLinux/asahi-installer/issues/137

It can be done, but it's not straightforward: https://davidalger.com/posts/fedora-asahi-remix-on-apple-sil...
> Git Integration

This is it for me. Does anyone know a good way of version controlling views in Postgres?
My only wish is that JSON in Postgres would be not sticking out like a sore thumb.

For example, why not address JSON paths as WHERE a.b.name = "king"
Adding an index means the write path suddenly became slower. Sometimes, a covering index will be very beneficial. « It depends » is usually the right answer. I’m fine with the engine telling me « this query is usually slow » and I investigate why. I’m not ok with the engine adding indices willy-nilly and suddenly writing to the DB is 10x slower.
I wouldn't trust Tuta like Proton

Tuta ran a blog post about how Microsoft was out to get them because users of Tuta couldn't create Microsoft accounts.

The kick?

It's because Tuta was incompetent and we're using the same domain for public users of their service as for internal corporate use. They registered the domain as an azure tenant to that point.

Then we're confused why users of @tuta couldn't create Microsoft accounts. The best part is disallowing "personal accounts" with azure tenant domains is a tenant setting. But they already committed multiple levels of security breakage by mixing anonymous and corporate use of the same domain.

I even tested that they infact had an azure tenant with the very domain they claimed Microsoft blocked.
Recording of the Rust Nation UK talk mentioned in the article:

https://www.youtube.com/watch?v=33FG6O3qejM
Surprised nobody is asking this.

In places like France this is even against the law, and personally I am of the opinion that it is for the better.
I mentioned Faiss, Annoy and USearch in the above description, but they require CGO for use in Go, as they're written in C++.

For Qdrant I didn't know it was embeddable at all, thanks for the correction! But requires CGO as well, right?
I think 99% of users aren't trying to train their own LLM with their data
Engineers are fungible. Disobeying the management can only cause job loss for the engineer, and won't change a thing in management.

The logic of punishing engineers comes from the false belief that engineers can all somehow synchronize their actions (through some kind of collective consciousness?) and coordinatedly disobey their supperiors in order to teach them a lesson.

The world doesn't work that way and you know it.
I use emClient. Its paid, but its a one time fee and the client works very well event with calendar integration (gmail and outlook).
I think they mean the likelihood of a person committing a crime for a second time is higher when they have already committed it once.
Yes, exactly. Many existing APIs are hard/impossible to connect to unless you are the user.
Changing the constitution is changing the law.
Yeast Bioflavoring in Beer: Complexity Decoded and Built Up Again
Unfortunately, I got in the habit of reading before bed. I inadvertently trained myself that reading leads to sleep. Now when I read, I very quickly start to feel sleepy.

So my advice would be to get in the habit of reading, but be mindful of the details of the habit you are establishing.
username checks out

"move fast and break things" was always a short-sighted fad in the context of infrastructure
> The shitlit that I read is totally inconsequential fiction

Same. Kindle Unlimited has an almost, uh, unlimited selection of light fluff detective fiction that's good for killing a few hours.

(Although I was pleasantly surprised by the DCI Logan series by JD Kirk which are actually amusing and fun to read.)
Infrastructure as Code is fine, its that the current implementations are too whacky and too manpower-intensive to make it worth it.

Good automation would be where you need less manpower afterwards..
FFmpeg is wonderful software. Growing up as a Windows user in the early 2000s, devices were far more picky than they are today about which video codecs they'd support. It was a non-trivial task as an 11yo trying to convert DivX .avis into an MP4 my old iPod Video could understand. Discovering ffmpeg and finding that someone was offering for free what I otherwise could only find under mountains of crappy shareware was a real watershed moment.

20 years later it's still a goto. Great tool.
dbt comes to mind
For anybody wondering about the new pinsyscalls(2) suggest having a look at
https://isopenbsdsecu.re/mitigations/pinsyscall/ . To be clear: I use OpenBSD on all my external-facing systems. I trust it infinitely more than any GNU/Linux distribution (esp with the recent xz.. "issue"), but I think it's important to do your own research and see what the contrarians say from time to time.
So you read about 780 books/year as a teen? I have doubts. Unless the average page count is under 100 maybe.
I'm sure that's due to the native swedes....
With the same logic you can say that contraceptives are not the answer because they aren't 100% effective.

Of cause IAC is mis-sold like anything new. It's not the end of all your problems. But as someone who's had to deal with the opposite too, infrastructure-as-a-weird-mystery-that-accidentally-happened-over-20-years-and-only-long-bearded-john-knows, IAC is fantastic.
A lot of people work in tech these days. A lot of people write blogs.

Anyway... back to scale, consistency, and speed - IAC.
I have used LFSR counter as a program counter in my relay CPU. Instead of building a 12bit half adder that increments +1 that would require 12 relays I got away with only 3 XORs and 3 relays. When assembling, the linker just scrambles program memory according to LFSR counting pattern and I get +1 counting behaviour :) This technique is used for some very tiny hard-coded CPUs (where program memory is not even ROM, but directly decoded datapath control, like decoded microops in real CPUs) that really need to save on area.
> you're the one who seem to want us to believe that you were innocent enough that throwing you out of the flat was completely unjust persecution; if that's what you want, then it's reasonable to expect you to account for how such a charge came to be filed against you.

Maybe you should check who you are replying to. I was originally answering your question about how things could take that long. I have no idea about OP, but I also provided an example of how cops will misconstrue things to simply get an arrest. In my own personal life, my parents had a cop search my car because they thought I was dealing drugs. The cop found a small ripped piece of paper (from who knows what), and claimed it was from rolling papers. So, I trust a cop saying "this is why X" about as far as you can throw toilet paper up their tree.

> rom a Baysean probability perspective, given no other evidence than what has been presented in this thread so far, which is more likely -- that the charges were dropped because they were a complete fantasy from the beginning, or because there were legal technicalities that would have made a conviction difficult?

In my experience, there is a far greater probability that they are completely fabricated nonsense.
It’s not a “booking system”. It’s a partner airline.

https://www.klm.com/

Just like you can book a Virgin airlines route via Delta.

https://thepointsguy.com/guide/airline-alliances/
For a second I thought he was talking about Facebook..
> To prevent deleting data by mistake, we invent soft-delete pattern by having a is_deleted column. However, this brings extra complexities around foreign key, unique index enforcement. Ideally, PostgreSQL could allow users to configure an archived table. The removed data is moved to the archived table first and purged after a configured retention period. This simplifies application logic and data compliance work.

You can get the same result by changing your is_deleted boolean field to a date_deleted date field. Then use a cron to purge all the records with dates older than the configured retention period.
The number of diseases in our lives even doesn't allow to have it under control. In this scenario, we should do a hundreds a tests every year. It's impossible to do it and even pay for all tests.
Positive feedback loop ? With the quality that it slowly reduces "original" content ?
Owl for Exchange (Thunderbird Plugin)
With the new Outlook’s miserable data collection policies, some of us don’t want to use Outlook but still need access to an exchange based mailbox. I’ve been using this for about a year and it works really well. Not affiliated, just a happy customer.
I find this interesting! Is there anything similar in the open source world? I have built projects with Supabase in the past and one of my gripes about it is that it becomes obnoxious to track what happens to the schema over time in version control with dozens of migration files. For example, you have no idea what the current state of a table or trigger is because there might be several updates that occured over four dozen migration files and you may not even be sure which files those changes are in. You have to just look at the database directly rather than the code.
Many interesting API usages must be bound to the user and must be payed based on usage so must be tied to the user. OpenAI doesn't provide ways to monetize GPTs so it is hard to justify spending on behalf of the user.
The big risk is that you'll outgrow the GUIs and end up with what amounts to code but all the logic is in YAML files instead.
This seems very hard in general to fix:

void x(int a, int b) {
int * p;
p = malloc(1);
if(a) {
free(p);
}
if(b) {
free(p);
}
}

It is possible that the program always guarantees that a!=b, but it would be hard to prove even with whole program analysis. Are you planning additional annotations or this is just not expected to work?
also Outlook for mobile

https://en.wikipedia.org/wiki/Microsoft_Outlook_(mobile_app)

Security
Outlook Mobile temporarily stores and indexes user data (including email, attachments, calendar information, and contacts), along with login credentials,[28] in a "secure" form on Microsoft Azure servers located in the United States.[29] On Exchange accounts, these servers identify as a single Exchange ActiveSync user in order to fetch e-mail. Additionally, the app does not support mobile device management, nor allows administrators to control how third-party cloud storage services are used with the app to interact with their users. Concerns surrounding these security issues have prompted some firms, including the European Parliament, to block the app on their Exchange servers.[30][31][32] Microsoft maintains a separate, pre-existing Outlook Web Access app for Android and iOS.[32]
Indexes aren't free. They take up storage space and reduce the performance of inserts. On top of that, if an index gets too big it can be really slow, the table needs partitioning instead.

In some applications you might value the performance of insert a lot more than select, and not want to pay for extra storage of the index.
Now I’m waiting for:

“Show HN: Multiplayer Towers of Hanoi in Postgres”
Like crypto, it's scammer catnip; lots of money sloshing around, most people don't really understand how it works, mentioning its shortcomings is kinda taboo in the community, going from dumb idea to thing which kinda looks like it might be a product if you don't poke it too hard requires minimal skill.

I think the same conditions also product a lot of _accidental_ scammers; people who aren't intentionally selling something impossible, but are merely too incompetent to realise that what they are promising is impossible (I think someone linked an LLM tool that claimed to _do your taxes for you_ here recently...).

That's not to say there's nothing to it, but it is a near-perfect playground for grifters.
A book a week is absurd, that’s like binge watching a multi season series each week. You’re wasting your life away.
Most of this stuff isn't addressing what makes Rust harder than, say, Go or C#. The pattern matching makes it if anything easier, since pattern matched dispatch is way easier to read than a bunch of complicated if/else blocks.

Rust is not garbage collected. It's a systems language, so it doesn't ship or run inside a big runtime. Rust's RAII and lifetime system does an admirable job of making most of the headaches and unsafe aspects of manual memory management fade into the background... until you throw in async.

After having used Rust for almost two years, I can confidently say that async and its interactions with memory are the hard part. (Edit: Making async code properly clean up after itself is also the hard part, unless you use a better async runtime than tokio.)

There are two paths with async. One is to use Arc<> everywhere, at which point Rust degrades into a more verbose version of Go but without automatic handling of circular references like you get with a good GC. You still get a thinner runtime and deterministic execution, which are benefits of a non-GC language at runtime, but you lose a lot of the efficiency and ergonomic benefits. You also end up with circular Arc<> references very easily if you have a task that owns two Arc<> classes that own tasks that own each other etc.

The second path with async is to use a scoped / structured concurrency library that lets tasks have lifetimes associated with them. Unfortunately those all come with not-entirely-safe warnings when used with tokio, and the underspecification of async in the standard library means the ecosystem has fixated on the runtime with nonexistent structured concurrency support (tokio) as the standard against which all other async runtimes link. You could use a superior async runtime like smol, but then you'd have to vendor/fork all your libraries.

TL;DR: async is still half-baked. The rest of Rust is actually easier than C++ and can be almost as easy as a language like C# once you grok lifetimes.

Edit:

IMHO tokio made a massive mistake in avoiding lifetimes associated with tasks and structured concurrency, probably on the speculation that this would be more confusing. It's not. It's more confusing not to have this, since you basically lose the entire lifetime system and its benefits in multithreaded async code. You also lose RAII in async code.

Rust also made a massive mistake in not more fully specifying async within the standard library and structuring it to be either runtime-included or runtime-agnostic. Until this happens async is half-baked and broken.
hashtext() works well
Vaguely reminiscent of https://en.wikipedia.org/wiki/Creature_from_the_Black_Lagoon...
Regardless of how we feel about using Git, it's comforting to know that Git loves us unconditionally.
How about Grey code? It's a one-bit change to 'increment'. Wonder if that would be about as simple.

FYI conversion between normal binary and grey code is to simply XOR successive pairs of bits.
Google plans to charge for AI-powered search engine
Freud observes correctly what is now called the difference between in-group and out-group violence. Human in-group violence is very low level.

No war starts with: "They or brothers and just like us, lets go to war with them". Humans must be primed for violence, but when it succeeds there is no limit.
_The_ Pareto? The thin-voiced lawyer who was the victim of Brazil's best prank call in the 80s?

No, A Pareto, the excellent economist.
>Rollback. If a new schema change introduces issues, versioning allows for safer rollbacks to previous stable states, minimizing downtime and impact on users.

Wonderful intention, not always easy/possible to pull off because you're not just managing the stateless structure, but the state which is stored by the structure. Migrations that drop columns by merging their data into another may well lose information and may do so in a way that makes the original data unrecoverable... not mentioning how to decide the information for any records possibly added after the dropping migration, but prior to running the rollback.

Sure, there are ways to handle these kind of scenarios, and sometimes in reversible ways... but there comes a point were a rollback looks more like moving forward adding a feature/capability than it does a return to a previous state.

Defining the "one true way" for migrations may cause more harm than good despite how convenient it may be. How migrators help you manage scenarios like rollback can vary from tool to tool and is part of the selection process when finding the right tool for your project. I've built a database migrator for my project which implements a non-traditional approach to migrations which works very well for my project, but would cause others to cringe with all sorts of objections. Sometimes an external tool is a better answer than an internal one.
I mostly work in an office now for my current client, but have the flexibility to be able to work from home if the need or want arises. It's great. My family lives in different cities, and I have the opportunity to visit them frequently because of this. I can take the less expensive trains and flights, because I don't necessarily have to travel on fridays and sundays. And of course I get to stay longer, and just work from home there.
Thank you, I did discover the 2nd link tutorial for setting up encryption but of course it's too late now for me (and to be honest, I wouldn't feel comfortable following that tutorial as it looks a very difficult and I wouldn't trust myself not to mess something up).
You refer to the ruminates who intentionally bring up and chew their cud over and over precisely because the iterative process they're engaged in allows them to break down and digest the material over time? And indeed is the only possible way they can "work through" the material?

The hubris to suppose those who ruminate are doing it simply to pass the time...
I recently switched my personal project to Mercurial, and boy it removed a whole lot of mental friction!
Reader's Digest Effect?
Imho, I think we've gone a bit overboard with Terraform at my company. Sure, it'll automate a bunch of stuff, but only a handful of people will really "get" it.

I think the rest of us who interact with it don't really fully understand what's going on. We've basically traded one set of scripts only a few folks understood (bash, perl) for Terraform in this case.

I totally see the benefits, but sometimes I feel like we try to force everything into it, even when it might not be the best fit.
Thanks, that was an interesting read. I'm curious how much real-world storage it would save for your average developer. Wonder if there's a nice little script out there you can run against an existing instance to get some kind of stats.
pijul
> The problem is outlook was actually good in the past.

That's not a problem, it's just a (dubious) statement.

The problem is to find a mail client that is good now. Thunderbird is the best.
I'm in the same boat. I've even installed Thunderbird and synced a mail account just to be able to find a specific mail that neither webmail nor the Android app were able to find.
I think this depends a great deal on whether it is first contact or whether it is with a known caller. For first contact, I prefer to have as much information as possible, and that includes facial expression etc. For known callers with whom a trust relationship has already been built, either voice or video is ok, voice often better given the lower cognitive effort required
> Android allows sideloading since forever and nothing like that ever happened there.

That's because developers don't care about android. There's not enough money to push an alternative App Store for the amount of work it takes.

Now that apple was forced to do it, now consumers are pretty much screwed if they want to use an app and care about privacy.

Just like when Apple opened up payments, it was never about "consumer freedom", it was "corporate freedom" to make it as hard as possible to cancel your subscription" and "corporate freedom" to profile your subscriptions to sell you more.

Just like how opening up wallet will just end in making banks richer and the user experience worse. Do you people actually think these poor multinational banks needed the government to help them because they couldn't compete? Man you are gullible.
The questions are always: is it better than what we had before? Are the "problems" common to other tools? Are there better alternatives? This article doesn't address any of these.

> I heard a story once of an engineer running a “terraform destroy” on his laptop — in the wrong tab. He was in the Prod directory — and starting nuking production. Realizing his mistake, he Control-C’d out of it, but it was too late.

That's the stupidest argument I have seen. If you do 'rm rf /' or 'DROP TABLE' in production, nothing can save you.
That's why insurance is heavily regulated and there are requirements on capital available for claims in order to operate in the jurisdiction. And of course savvy clients (like the ones managing $100MM container ships) will do due diligence on this as well.
What a beautifully simple, clear UI. The font rendering needs work: the rest is so easy to look to at.
A Critique of ANSI SQL Isolation Layers (Transaction Processing Book Followup)
I've given up on git a long time ago. At every place I worked there was a different set of rules and software to interface it. And at every place, there were git gurus, who are needed because every repo has places with labels like "this branch is cursed and bugged, ask xy before using". Not a week goes by without a git emergency. It's laughable that something like that is trusted with code.

I've also used svn for a long time, and I remember it fondly. With git, you use git. With svn, you can actually code. Since it's become non-optional to use git, I just use commits and logs. I don't even bother with branches anymore, they bug out too often. I've become so jaded about tools, and git is a major reason for it.
"Total Eclipse" by Annie Dillard (1982) [pdf]
Low bridges already include a margin of error in their max height signs. Kind of like how fuel gauges show zero but you can still drive dozens of miles.