skysight-inc/HackerNews huggingface dataset:
> Yes turkeys but not paint chips. Remember when engines were catching ashes from the Iceland eruption that started to glassify inside the combustion chamber?

You're able to specifically recall and cite these more-or-less freak occurrences /because/ they are so rare. You're talking about an incident from > 13 years ago[0] and again - no one died.

Show me deaths from paint chips, volcanos, or any other potential risk. How many times a day do you nearly get killed in a car - you're a split second roll of the dice away from getting killed in a car every single day - which is much more common of course. As they say "close only counts in horseshoes and hand grenades".

> The 737MAX disasters were a matter of time. It was pure chance that they didn't happen in the US. The US is not safer here, just luckier. Despite Boeing trying to spin it on "those careless foreign operators".

Of course I followed the MCAS debacle but again, zooming out we're still talking about 346 total fatalities (worldwide) across two incidents that were 3-4 years ago. Using my medical errors comparison that's equivalent to roughly nine hours of deaths due to medical errors - in the US alone. All day, every day. In the time since the MCAS incidents which were riveting, worldwide news roughly 1m people have died from medical errors in the US.

Look at any other category of accidental death where the risk applies to a broad population. Nothing comes close to commercial aviation.

I don't mean to sound callous and reduce these deaths to statistics. If it were a friend or family member of mine I would feel very different but the stats are what they are and commercial aviation has an extremely impressive safety record.

We can care about multiple things simultaneously and Boeing (along with increasingly misplaced "trust" in them on the part of regulators) needs to get it together but speaking personally I feel safer on a plane than I do walking the streets of large cities (the murder rate in Chicago alone was nearly 2x MAX crashes last year alone), driving a car, visiting a hospital, or any other number of activities because the stats show it to be.

[0] - https://en.wikipedia.org/wiki/Air_travel_disruption_after_th...
> why anyone ever used Coffeescript

CoffeeScript was the front runner for 'Compile to JavaScript' technology. It was the first time we could write some sane frontend code.

Of course things like TypeScript came along and now we cannot unsee what we have already seen.
I feel like I wrote something on usenet with a similar title about imake in the early 90's ...
I hadn't heard of Bill Ackman before the Claudine Gay thing, but this is amazing: https://www.theatlantic.com/ideas/archive/2024/01/bill-ackma... (https://archive.is/ypLSo)
I think it adds value. It means that the commit was created using the author's credentials (to the extent that you trust GitHub and its lack of bugs). So the author can be trusted to some extent on these commits.

Although extending this signing ability to arbitrary commits via the codespaces API seems weird as the commit is no longer generated by GitHub. It seems now that you could generate some fake merge that changed data in a surprising way. Previously you knew that merges generated by GitHub would be "clean". Not that this changes much in practice.
SELinux Coloring Book
Why not "just" use an embedded DSL?
The red/blue split cannot be "removed" it is inherent.
There isn’t one technique that works all the time. Life is unfortunately about tradeoffs whenever you do something complex.
Red bricks won't magically disappear by sorting, just like dirt won't disappear when you wipe it off a surface.
It’s because YAML is designed first for readability.
I think alpha lies in how good the embedding space is rather than which db you use to store and retrieve. A typical tradeoff between accuracy and performance, and here accuracy will be more important in many cases esp for businesses and enterprises. With that, and existing database providers introducing their own support for vectors, this space might be commoditized in near term.

Re embeddings, you would likely get better results if you train your own embeddings model. A popular approach is ColBERT, which anecdotally outperforms vector search in border cases[1]. Second is training an embedding model using initial layers of an LLM. [2]. In Colbert's case once it's trained, you dont need a db to store the vectors.

[1]: https://twitter.com/arjunkmrm/status/1744741903646773674
[2]: https://huggingface.co/intfloat/e5-mistral-7b-instruct
The way you state your sentence indicates that you see this as a problem?
That works too. There are just a lot of tiny cognitive humps to get over when you try to manage env variables manually.

1. Find the text file in the password manager
2. Most people will not be fully conscious of which shell they're using and where's the RC file for that shell, and what variables already exist in your system that you want to keep Vs which ones you want to replace.

I built this because I'd use this just to save me some mental energy. It's obviously possible to solve this in other ways as well.
French regulator fines Amazon $35M over surveillance system of warehouse workers
I mean...building a data centre / PaaS with YAML is pretty cool

We used to have to shove servers in to racks ! Kids these days :D
Donor Bounties: A New Kind of Feature Bounty
there seems to be a limit...i could only downvote 4 of your comments (undowned afterward)...but i think all the karma thing is a kids game, it should disappear
Relax, I was pointing out a very objectively factual error in what you said. I’ve never felt compelled to comment before that’s all
Many of the statements are outdated, plus that async isn’t really a completed feature yet.
I don't know any Go so I'll try some pseudocode that hopefully maps across well enough.

main {
chan = makeChannel()
sendMsg(chan, "one")
sendMsg(chan, "two")
print(recvMsg(chan))
print(recvMsg(chan))
}

sendMsg(...) {
async {
// ...
}
}

I argue that this code is all-red when sendMsg is allowed to spawn an extra (green)thread to do its work (at the async keyword.) The order of the prints in main is unknown. If you remove the async, the code becomes all-blue and the order of the prints becomes known.
What is the best term to use for the people who are writing content on the web team? The ones who write blog entries, documentation, and marketing pages. The ones who mainly touch Markdown files.
I will tell you exactly why we template yaml.
Its the exact same reason every code base has ugly parts. And that's the evolution of complexity.

At first, you have a yaml file. No templates, no variables. Just a good old standard yaml.
Then, suddenly you need to introduce a single variable. Templating out the one variable is pretty easy, so you do it, and it's still mostly for humans to edit.

Well, now you have a yaml file and template engine already in place. So when one more thing pops up, you template it out.

8 features later, you wonder what you've done. Only, if we go back in time, each step was actually the most efficient. Introducing anything else at step 1 would be over-engineering. Introducing it anywhere else would lead to a large refactor and possible regressions.

To top it off, this is not business logic. Your devs are not touching this yaml all that much. So is it worth "fixing", probably not.
Git uses its own ini-style conf format which diverges from TOML.
And for almost everyone who doesn't live in an older apartment complex or or rely on street parking, they're fine.

This is like arguing that nobody anywhere can buy anything but a large 4WD SUV because some day somebody somewhere might want to take a dog to a beach.
They are to portion noodles
I don't disagree with any of this, though it might be worth mentioning that async can be useful on platforms that don't support threads, e.g. embedded or WASM.

I doubt it would have been added to the language if it was just for those use cases though.
The purpose of an Operator is to realize the resources desired/requested in a (custom) resource manifest, often as YAML or JSON.

You give the apiserver a document describing what resources you need. The Operator actually does the work of provisioning those resources in the "real world" and (should) update the status field on the API object to indicate if those resources are ready.
> [was] being able to decompile the enterprise version of the GitHub binary.

> It makes you think that distributing a binary of your app is either a good idea or bad idea,

> If your app is important though then it’s definitely a good idea.

I don’t follow. What are you saying would have been the good idea here?

It also isn’t clear to me that they required the code except to answer why it works, certainly this parsing defect could be discovered simply by testing the endpoint.
If the cited level of incompetence checks out as true then that borders on criminally negligent and some Boeing exec probably needs to go to jail.
Is Kubernetes using YAML 1.1 still? Because some of the complaints I hear shouldn’t be an issue with 1.2.

Moreover the YAML spec allows for specifying the tags recognized per application.

So on two counts, if “on”, “true”, “false”, as well as “yes”, “no”, “y”, “n”, “off”, and all capitalized and uppercase variants, are all boolean literals, it is not YAML’s fault.
You're wrong. Its the best office I've ever worked in with some of the happiest workers and a wonderful culture. I actually work there. You are getting very vitriolic about an extremely skewed hypothetical idea of my workplace that you've made up in your head. Meanwhile, I'm here, seeing happy workers all around me. And I'm not a manager. People like you sound grumpy and horrible and no wonder you don't like being around people. They probably don't like being around someone like you.

I know people with 1.5 hour commutes at my office. They come in twice a week. I ask them about it. They like coming in twice a week because everyone is really nice and friendly to be around. It's refreshing and fun. The only person management reprimanded about how often he came in was a young guy who lives less than 30 minutes away and didn't come in for 4 months. He doesn't really have an excuse. But everyone is allowed to skip a few weeks. It's not a punitive policy.

Let me also point out I'm not in the US. Living more than 1.5 hours away from your office is rare as hell and nobody is driving that distance. They're reading on the train. People leave early to miss rush hour. That's totally acceptable in our office. Because we're not micromanaging people. We just like people being in the office for culture. I know you can't fathom any reason to talk to other humans other than to control them, but some of us can.

And the people coming into the office are happy. We like seeing people, so we come in on similar days. Some people Mon-weds, some tues-thurs, some tues and thurs. Everyone knows noone comes in on friday and very few on monday. Most people come in on tues and thurs. So we coordinate. Because we are human beings with social skills.

Even the guy who avoided coming in for 4 months, when he came back said that he actually liked being in the office and would like to come in more he was just being lazy. I asked a girl who takes a 1.5 hour train and sometimes crashes at my house. She says she doesn't mind it at all she likes to have an excuse to come to the city and she still saves money over living here.

Not everyone is a miserable sod like you.
Bradley fighting vehicles are taking out modern tanks in Ukraine
Italian television brought coffee to the lab, and the results where not reassuring (from minute 18 onward, only Italian, I am sorry)

https://www.rai.it/programmi/report/inchieste/Un-espresso-a-...

aluminum was at around 1/6 of the EU recommended maximum safe concentration. But you could cut this in half using the stainless steel moka.
Apparently about half of the aluminum came from the coffee powder itself and half from the moka.

A lot of metals from the coffee itself, apparently because of fertilizers and insecticides.

Anyway the moka itself released around 0.3 mg per liter of aluminum
> I never understood why anyone ever used Coffeescript whereas I do think I have a solid understanding of why people use YAML.

When Coffeescript was invented, it was an advancement on top of the awful Javascript standards at the time. It never went anywhere because Javascript caught up, but Coffeescript had a good reason for existing.

Today, Coffeescript is a remnant of old frontends that nobody has bothered transpiling into Javascript yet, but back in the day it was a promising new development.
Sweden's polite war with Elon Musk
Capitalism didn’t invent child labor, but it did help end it. While socialist regimes like the Soviet Union exploited child labor extensively under the guise of equality, it was the economic growth fueled by capitalism that empowered societies to enact labor reforms. The wealth created by free markets enabled the development of laws that protect workers, proving that capitalism is a solution, not the problem.
Not to decide the outcome of fantasy combat?
It is increasingly harder to avoid async Rust if you do any form of IO. Most of the useful io based crates assume you are doing async with a very minor amount of them giving you a non async api. Out of the ones that do they are bundling an executor to power that api because they don't want to implement it twice.

I think part of what is feeding this sort of backlash against it is the way that it creates two different rust ecosystems. One of them, the non async version, being decidedly a second class citizen.
> Impossible to vendor without hitting name collisions

What problem exactly are you facing? I can change the name of the chart itself in chart.yaml and if the name of the resources collide I change them with nameOverride/fullnameOverride in the values. All charts have these because they are autogenerated by `helm create`.

I vendor all charts and never had this problem.
Didn’t have time to go through it all, but quickly scrubbing I didn’t see any mention of a UI. doesn’t SmallTalk by definition include a UI component?
Note that while SHA1 itself is broken, git specifically has a code to detect attempts at collisions and prevent them, see all the sha1dc stuff [0]

[0] https://news.ycombinator.com/item?id=17825441
The problem isn't with the small configuration files, those are just argv put into a file.

Here's an experiment actually worth doing: ask ten people to write a ini file for configuring between 3 and 6 servers where some properties are the same for several servers.
Nobody is friends with PS1.
I don't think anyone is suggesting that Go's concurrency model is perfect. However, the OP said "trying to remove the red/blue split will not work". This is a pretty strong claim, and Go seems like a reasonable counterexample to it.

Similarly, if someone said "trying to marry async to a language with lifetime analysis and no GC will not work", it would be reasonable to point to Rust as a counterexample, even though Rust async has various problems.
If yours is a massive company with resources to run separate centralised infrastructure for secrets management, sure. There are other nicer tools too - Doppler comes to mind.

I just wanted to build the simplest possible thing that would achieve the functionality.
I don’t see a single such submission in their pull requests, open or closed, in the past couple weeks.
Again, it’s not “absolute no one” - most people would. The question is whether it’s enough of priority for a much smaller group (legislators) to pass legislation and fund enforcement. Given that there are bigger evils in the world and most gym users are used to that sleaziness, the average legislator is probably not hearing that many complaints about this and almost certainly not hearing about it from donors other than the gym chains who are saying it’s great.
A lot of people don't know that JSON is valid YAML. You can mix JSON into your YAML wherever you need it.

So if you have issues expressing something complex in YAML (like nested arrays) just write JSON instead.
Search, Ads, Analytics, Gmail, Docs, Drive, Youtube, Maps, Android, Calendar..

All 10 are category defining (but at least top 3) products. I'd like to have a 1-trick pony like that one day!
Staying at an AirBnb, I once had a Moka Pot explode, spraying boiling coffee across the room. Luckily, I was shielded by my laptop. That was a funny conversation to have with the host.

I'm not sure what exactly caused it, probably an issue with the pressure...but I've stuck to my trusty French Press ever since.
of course. i was only talking about preventing or overriding rules that don't allow foster parents to take away a childs phone.

for some issues like this appropriate laws are helpful, for others more flexibility is needed.
How often are you communicating IP addresses? Is that not the point of domains, because humans are rather terrible at remembering sequences of numbers?
Basically you're saying YAML is unreadable without an IDE or a text editor with advanced highlighting functionality.
We should ask them instead to modify the existing INI file. I bet most would do just fine.
> it should be possible to implement functions that can be called in both sync and async contexts, removing the need for function coloring.

It is possible! They're called blue (sync) functions.
My favorite thing about archaeology is that if they have no idea whatever about the things they find. . .

>were used for ritualistic or religious purposes

Don't know what it is? Religion baby.
Such things are matters of degrees, and humans use all sorts of intonations, gestures, tags, emoticons, and such, to provide similar disclaimers. Being neither young nor on-line enough to feel myself fluent in the current local dialect of those, I fall back to something that feels workable, if rather clumsy.
Was that better than running the teacher model on the distorted images directly?
At OpenStatus we also provide a self hosted status page on Cloudflare Pages

https://github.com/openstatusHQ/astro-status-page
I get where you are coming at and find some value in it but I do often like to create these "maybe someday" tickets for a few reasons.

- It provides an obvious place to put some ideas about then that can be collected over time. Often thoughts from significantly different points in time can provide valuable perspective. Even if most of the time they are just out of date.

- It allows tracking value over time. For example adding a quick note that this would have been helpful to customer 123. If you only file tickets when you are ready to implement them it is easy to miss the common friction problems.

So basically it is a way to log interest over time. But they are also easy to filter out so low cost to keep them around.

But I'm sure that you could also manage these "feature requests" in a separate system. But that often adds friction.
Then this job is not for you, simple as. Sounds like a win-win.
You could always release and license under BUSL or AGPL or some other business non friendly and relicense if you got the job.
> Is it possible for me, or worse, a normal person, to claim or request an ipv6 address that they can keep and use like a phone number?

Yes. You also have to get an ASN though, and an ISP which which will advertise both over BGP.
One theory (albeit contested) is that they were used as a jig to knit gloves: https://www.youtube.com/watch?v=76AvV601yJ0
There is a valve that should prevent this from happening, it's that hexagonal thing on the side you can see in the picture.
Change my mind: Moka pots are no different than Nespresso but exchange water waste for some fractions of a gram of aluminum.
I disagree about ergonomics. Switching to rust allowed us to focus on the real application/business logics rather than spending time worrying about GC lag, performance, exceptions, null references, memory leak etc. plus the toolchain is much nicer than most other languages.
That doesn’t matter to them anywhere near as much as losing a job does to the people who were laid off, and it’s certainly not the case that prices won’t go up anyway.
Nice build with useful links, here are some additional links for anyone interested...

https://openbuildspartstore.com/

OpenBuilds makes and sells it's own controller and related electronics.

https://ratrig.com/

EU based reseller of OpenBuilds stuff plus others
What I worry about in a fully adopted IPv6 world, are the old Games that run on IPv4 p2p. (like C&C3)

Sure, you can do a IPv4 VPN with your friends, but that means no more games with strangers over the internet.
Helm would probably benefit from something like JSX for YAML/JSON. Just being able to script a chart instead of this templating hell.
It's kind of a running joke amongst archeologists themselves.
We are for a few projects. We've been using them for over a year and have been impressed. We have 10s millions of items in there with lots of daily inserts/deletions etc. There's been a couple of gotchas but generally it is quite predictable and scalable.

We use 768 dimensional vectors for our items with several other payload filters (e.g. language). Performance has been good and I think the qdrant team focus on the right features without creeping into other areas.
Trite but true: it's so much easier to tear down than to build, to find fault than to invent.
Even something as basic finding all references to a variable or function doesn't work very well in most IDEs.

Shoutout to the folks behind Sorbet for making an awesome LSP for VSCode [1].
It comes close to the tooling expected nowadays, bit is still very far behind even popular dynamic languages like JS or Python.

[1] https://sorbet.org/docs/vscode
For JSON I'd stick with Typescript to be honest. You end up executing Javascript and producing Javascript-native objects, but the typing in Typescript to ensure the objects you produce are actually valid will save a lot of debugging.
Which platform is the best for launching a product?
We are currently building a product and deciding on the ideal platform for its launch. Please share your experience.
Does it mean that Lisps 'code is data' is the right idea in the end?
So long as it's not a BBJ!
AI Chatbot Swears at Customer
Please, enlighten us
I mean, PLATO Notes was up and running at that time. I'm not sure what else was, but online discussion boards did exist. I can't speak to the culture of the community or what they talked about as that was before my time. The University of Illinois has archives of some of it, though, if you want to go see:

https://digital.library.illinois.edu/collections/7bfaf980-07...
> And forbidding it makes a one-keystroke action a two or four one.

The majority of editors can be configured to use tab to insert the appropriate number of spaces. Many will automatically detect the correct configuration.
Honestly, fair enough. I probably misread your tone!
You just made a copy of a chart. You modified your chart. What I’m missing is helm having some notion of an org in the chart name, like docker does: repo/name:tag, helm only has name and version. Hence you modify your chart.yaml and it should be preferable without having to modify anything.

This is really problematic when a chart pulls dependencies in.
As a general rule of thumb, random series A startups are in much lower demand for top-tier talent than top-tier talent is in demand for these companies. That would mean that the good engineers should set the rules of engagement, and that any startup that thinks they set the rules is attracting worse talent.
Not to knock Qdrsnt, but generally the whole “vector search database” rush is insane.

I’ve been working with vectors for over a decade; particularly with embeddings used in AI. We’re talking projects from 100k to 100B+ records, used for AI applications

Postgres, particularly with pgvector and derivatives, can handle to millions of records very rapidly no problem. It’s very cheap, scales great, and is accurate.

I’m sure some of these open source solutions are improvements. That said, weigh vendor lock in, cost, risk and in the end it usually makes very little sense.
It’s not just Boeing. Their supplier Spirit is a private equity holding.