skysight-inc/HackerNews huggingface dataset:
That's not about being smart or not.. But about brevity and a bit of experience.

I'd certainly recommend the first one, there's simply less stuff to parse, it's easier and quicker to read.

x is a pair with key of type string and value of pair with key of type string and value of type string.

The other one is overly verbose to read, it takes more effort to read and understand.. But it could have merit, for instance if you need to extract status into a variable of declared type later..
If you want to try this in Python, you can use https://github.com/ezyang/expecttest which I wrote to do expect tests in PyTorch.
I don't get all the YAML hate. The article even mentions solutions, which are all better than adopting some nonstandard json variant or toml.

- for whatever language you're using, be aware of which YAML version its YAML library supports and its defaults, and how to safe load yaml in that language.

- defensively quote strings, particularly if you're on a language with an antiquated yaml library that defaults to yaml 1.1.

- defensively use true/false only, and proactively convert any other booleans in your codebase to true/false.

- Depending on your language, you can avoid any custom data types for any externally-distributed applications to mitigate the risks, even when it might make things more convenient. Use safe loading (most languages with yaml libs support it) to avoid loading any. The other major YAML alternatives that YAML haters recommend won't have custom data types either.

Features like references and folding semantics are very convenient, and you don't even have to use them. Basic yaml enjoys better readability than json. toml is only fine if you don't have much nested data.

The author's note that there are json variants that help with some json failings makes no sense. If you're going to adopt some non-standard json variant, why not just adopt yaml 1.2, make sure your language has a yaml lib that supports it, and use that? At least yaml 1.2 is standardized. It's not their fault if python's libyaml only supports yaml 1.1. It looks like pyyaml is essentially in maintenance mode and ruamel.yaml is what everyone should be using? Unfortunately nobody's gotten around to implementing safe loading natively, but that's a python problem, not a yaml 1.2 problem, and ruamel.yaml supports pure-py safe loading that's compliant with 1.2 (no integer-interpretation gotchas), which is fine in most cases where yaml is only loaded occasionally, i.e. at start-up, and performance isn't critical.

Obviously YAML has historical problems, but what's better? Using another flawed or even more limited data format, inventing your own which will begin with zero adoption, or simply ensuring your environment/app uses yaml 1.2 and best practices?
Articles like this are really annoying, it's just based on some feelings and don't really prove anything. I'm not saying this accident is terrible and shouldn't be investigated of course. And of course Tesla should do better and fix those issues.

> then I’ll see a crash like this, [...] and I realize that, no, people still don’t get it.

That's just an example. You can't make conclusions based on a single example, you need lots of data. Your feelings that this is less safe than regular drivings are not enough to justify your conclusions that L2 is less safe than regular driving. I have the feelings of the opposite (I think it reduces the number of accidents), but I don't know wether this is true. Accidents that were avoided by L2 don't make it in the news, there's a huge selection bias here.

I think this kind of article might be very dangerous, because it makes people more afraid, and if L2 is actually safer on average, then reducing its usage will just increase the number of accidents.
The shops are obviously highly profitable. Which is my point. More of that profit could be shared with the workers who generate it. And they would still be profitable. Your scary "unprofitable" is not in sight even after significant raises to workers.
Just hematite, apatite and phosphorus, which is mined there for over hundred years already. What is new that they decided to use the new other minerals than iron ore from apatite, mainly Titan, and they'd need phosporus for fertilisers. There's also lot of V (Vanadium) needed for steel.

This Per Geijer deposite (already mined since the late 1800's) is close to the old and new Kiirunavaara mine.

https://www.researchgate.net/figure/Sketch-map-of-the-geolog...
Haha yeah, like Chief White Halfoat in Catch 22
I'd never heard of it, and doubt that there's any other explanation than pandering.
I wonder why generated JSON is not used more widely, something like jsonnet[0], although I've never used it.

Most systems come with Python 3 installed, which supports working with JSON[1] without installing any dependencies. So, I'm wondering if we could use Python to generate JSON data that is then consumed by other tools. This would fix the lack of comments and trailing commas in JSON, you get functions and other abstractions from Python, and you don't need to install any third-party tools (vs. something like jsonnet).

[0]: https://jsonnet.org/

[1]: https://docs.python.org/3/library/json.html
Concerning the public key cryptography for the exchange of private encrypted messages, I would have rather represented the shared public keys by padlocks, and the private key by the key allowing to open the padlocks. This way, it is easier to understand that there is a relationship between the two keys. In his drawing, 2 different keys can open the safe door, which is not possible in the physical world...
Yes, the problem is PyYAML.
That's always been part of their business model. What they didn't do - because it's illegal - is close shops because they unionized.
Build complex CI workflows using code
Maybe not super familiar for speed/"velocity" addicted software engineers working on web apps, but things like mining, construction and other huge operations take some time to complete, and safety in modern countries is a huge factor when doing things like this, which adds a lot of time as well.
People often forget about the environment, and I feel like a lot of the simpler services and applications could be configured through it easily.

For anything that requires more complex structures, JSON5 (https://json5.org/) has been gaining traction. It's basically JSON that allows a couple of more things, including comments, trailing commas, and even unquoted keys, if you're into that.
I like CTEs, but for complicated queries I find it lot easier to make them run fast by splitting into individual queries and creating temporary tables with appropriate indexes.
More info on the VR headset:

https://www.bloomberg.com/news/newsletters/2023-01-08/when-w...

It's expected to be released before WWDC.

According to the article, an AR/VR headset has been an R&D project at Apple since at least 2015.
edn

Extensible Data Notation, it's to Clojure what json is to Javascript.
I think of Gemini less like a competitor to the web but more as ham radio.

Radio amateurs can communicate through the internet with their phones and it would be faster, simpler and easier. But radio gives them both the nostalgia feeling and a niche community to belong.

Gemini is kinda like that.
> Obviously YAML has historical problems, but what's better?

toml
I was at a place 7-8 years ago with a hand-rolled JSON parser that had been written across a few afternoons by one guy without much ceremony. It was untouched after that aside from some renaming and other minor refactors. As usual with these things, the decision to hand-roll was made by one very opinionated dev who got his way because the business depended on him.

When that article was published it started an argument among the team. The guy ended up implementing the test suite to defend his decision. To my surprise the parser passed all tests apart from 3 or 4 unicodey-ones where it was more permissive than it should have been. There were plenty of production bugs at this place but none of them were due to the parser.

IMO parsing JSON really is simple. If you read through the article you'll see that most of the test cases are dead simple and hardly landmines.
And don't forget one of the more understated benefits of TOML over INI:

> A TOML file must be a valid UTF-8 encoded Unicode document.
This is going to have a mayor impact on Swedish politics. A new government is recently installed and this is the first mayor (public) opportunity for them to make a big impact on Europe from a sustainability, financial and political perspective. Expect A LOT faster result than 10-15 years.
To keep beating the same tired old drum: despite literally hundreds of millions of dollars poured into development and promotion of Web Components... the results are at best meh. The two leading frameworks, Lit and Stencil, see very little interest, so-so retention, and barely any usage.

None of the major frameworks and barely any of the newcomers use them... well, for anything.

(Of course the person responsible for them tries to downplay it because biased etc. https://toot.cafe/@slightlyoff/109669688324474159 )
I’ve been on paperwork side of health a small bit.

1) cash pay / direct / concierge

Agreed - especially if employer plan not great. Some of these folks do house calls. I did this for a while

2) high income area

Sadly agreed. Even in a city if a hospital is more accessible etc that can be tough. I did a walk in to sf general once a long while back - took me 20 minutes to walk out. Great hospital, but waiting room was nuts. Had a finger burned being an idiot and got seen very quickly at a different sf hospital - night and day difference in waiting room

3) mixed view on this. Kaiser brings some peace of mind - grandfathered hsa plans w 2k deductible and some free base car not a bad experience - key for me is not coordinating/ dealing w multiple bills. Their issue resolution team is terrible though on billing
EDN’s my favourite config format.

+ Simple (like JSON)

+ Has comments

+ Extensible

+ Built-in sets, UUIDs & timestamps

+ Well-suited to configuration (cf. Aero)

+ Lispy (well, Clojurey)

- Lispy (well, Clojurey)

- Handwavey specs

- Not widely supported
I haven't seen Taleb offer solutions... in the one book i managed to go through he just told you endlessly to be prepared for unpredictable events.
Level 2 Driver Assist Systems: People Are Dangerously Confused
YAML with templating becomes troublesome even more so when these are Django tmeplates. That's why I do not prefer ansible for automation. It becomes so much cumbersome at certain point that it is more valuable to jump into a real programming language instead of wresteling with both YAML, Django templating and python.

That's where I am enthusiastic proponent of pyinfra.
Thanks for sharing this! I filed it late in the day and forgot to do so myself, so enjoy the karma. :-)
Agree with the final part of this article that "programmable" configuration languages like Nix and Dhall are the way forward.

I've spent a lot of time writing YAML for Ansible, Cloudformation, k8s, Helm, etc. Some of the issues this article mentions are pitfalls but once you get a bit of experience with it, you know what to look out for.

I've also spent and a lot of time writing Nix expressions, which is much more "joyful" IMO. Seemingly simple features like being able to create a function to reuse the same parameterized configuration makes life much easier.

Add in a layer of type safety and some integration with the 'parent' app (think replacements for CloudFormation's !GetAtt or Ansible's handlers), the ability to perform basic unit tests, then configuration becomes more like writing code which I consider a good thing.
On a related note: I think that deterministic generating something based on a git commit and then later diffing the results across commits is in general a very useful technique. Our builds work similarly. We build our software into (several) container/disk images, then we show the diff between these build artefacts on PRs.

It can help you spot when something changes that you didn’t expect, and vice-versa.

For this to work we store all our builds indexed by git commit sha.
That depends on the application. Most modern applications (fortunately) shun the pile of floating windows that dominated Mac application design historically. For document-centric applications, developers can implement MDI style or tabs and keep their app tidy.
> In the past years, I've grown increasingly concerned about backups. To me, it feels like whatever you back up should be validated, before it's considered "okay".

I've been trying to toot this horn at every place I've consulted/worked at, with the most common response from software engineers being: "We're using the AWS backup system of the database, of course it works, no need to test it"

People have way too much trust in systems overall, especially ones they have no inside information about. And people also seems to default to "Of course it works" without testing it, instead of "How would I know it works if I haven't tested it?" or even "I don't know".
I have a Tesla, when using just cruise control it has slammed the brakes:

because of shadows that confused it

because of concern about cars crossing the intersection ahead where there is only the need to gently slow

because of a car crossing an intersection ahead that has already crossed!

because of a steep bridge that confused it

we can’t use cruise control in the car basically, we decided it is too dangerous at worst and jarring at least

because there is so much hype around Tesla people get the impression their software is “hardcore” but a lot of it is absolute garbage.
> If we look at how other permit processes have worked within our industry, it will be at least 10-15 years...

When it takes 15 years simply to get permission to do something, you know that your country will never be competitive globally.

Either the benefits outweigh the downsides, or vice versa. A group of 10 of the right experts ought to be able to decide that in a week.

Spending 15 years paper-pushing, doing court battles, public enquiries, etc. just delays the process. At the end of the day, you will end up either doing it or not doing it, and whatever you choose is best decided quickly (with the right expertise).

Perhaps we should adopt a system like for the choosing of popes - we lock the experts in a room till they come up with a consensus conclusion.
Chiu-Jain plots are great for getting a grasp of AIMD. Another related one I like is the figure illustrating ack-clocking in Van Jacobson's original congestion control paper - Figure 1 here: https://ee.lbl.gov/papers/congavoid.pdf
Maintaining tests that only test that things haven't changed can be a nightmare if you actually want things to change (like when you're making a change to the logic of a system). They can also be a real pain to maintain since if they fail you almost never know why they failed, just that they failed. This gives you (or the future maintainer) very little help in figuring out what's going on.
This smacks of the typical Apple, "you're holding it wrong" condescension. I understand why MacOS does things the way it does most of the time. That doesn't mean that I can't still find it frustrating.
Great Question (YC W21) Is Hiring B2B Account Executives
dupe: https://news.ycombinator.com/item?id=34352040
I hacked together a free online video editor that you can use to add texts to videos, add images to videos or automatically generate subtitles for a video for free and without registration
Refreshing to see dynamic and nimble solutions from a large organization.
Why are the solutions better than adopting toml? You don’t provide any justification for that claim.
Sadly, no, it was the product of 18 months of collaboration between a committee and “stakeholder groups”. Had it been made by a single overzealous HR person, that would’ve been significantly less embarrassing for Stanford.
I’d prefer that application stay open so that I can accomplish my next task and that Command-N does “make me a new one of what I was just doing, not a new one of the thing I was doing before that”.
It's important to note that big movie gross earnings shifted significantly to favor international markets over the last ~15 years. Doctor Strange is a great example - the international gross was nearly double the domestic [1]. And international audiences tend to really like flashy SFX over memorable stories in big Hollywood movies, especially when said movies are going to be subbed or dubbed anyway.

[1] https://www.boxofficemojo.com/releasegroup/gr2284737029/
The new features and flaws of speedtest.net, ookla and Cloudflare
Booleans aren't an edge case, on is an edge case way to spell false.
That's what I was going to ask: can anyone comment as to whether this is a disruptive event? Or is Europe so ordinarily devoid of such metals that it's comparatively little versus world supply?
And it essentially is true, minor bumps aside.

Early gold mining (and tin, lead, etc) followed rich veins with good rewards for hand tools.

Throughout history gold mining has had bursts of finding new rich grounds, but the essential trajectory has been more effort (in the sense of moving more material) to extract less target material, often with more complex processing and harmful side effects (leaching trace amounts from paydirt).

Years back I did the computational backend for a mine modelling program (under ground and pit) with application here at the superpit [1].

The dimensions of this hole are .. large - the volume of material removed is large, and the energy requirements to lift that volume free and the sort it for discard, crushing, refining, etc are also large.

This is just for gold, which is mostly useless (aside from some jewellery and some actual essential use in space electronics the bulk of gold goes to bullion and is valuable because, well, it's gold (go figure)).

You can (I have, and others do) plot the per tonne increased extraction costs of target materials against deposit richness as reserves are depleted.

The entire notion of peak oil is predicated against increasing effort for diminished returns.

[1] https://www.youtube.com/watch?v=8Wykx-_RWDw
Please someone tell me again how homeschooling doesn’t properly socialize children…
Before applying, with whom could we speak to learn more about the positions/roles/company?
No. VisionFive2's RISC-V CPU does not have the B extension. I confirmed it on the actual device.

$ cat /proc/cpuinfo
processor : 0
hart : 2
isa : rv64imafdc
mmu : sv39
uarch : sifive,u74-mc
You can mine to produce nice stuff, or you can mine to produce bad stuff. But mining you do, and you will for the rest of the life of the universe
That’s a big assumption. In TDD you write the tests first, to help you achieve the results expected, this doesn’t fulfill that need. It is basically snapshot testing applied to any kind of function.
No, the test would not help to find it, but now you can write a test for that bug. Later, when you change something, related to this code or something unrelated, you can be sure it did not affect this part.

Tests are useful when you change code that is unrelated, but still somehow connected. You would never notice the issue as you don't manually try the unrelated code, but the test would catch it.

If you had unit/integration tests for all potential edgecases you came up with, you don't have to manually test that over and over.
It should be at least one, since I downloaded it, so the counter is broken or delayed.
Ever wanted to look inside of a CPU executing code?
http://visual6502.org/JSSim/index.html
$ cat /proc/cpuinfo
processor : 0
hart : 2
isa : rv64imafdc
mmu : sv39
uarch : sifive,u74-mc
Which is much more relevant than Bitcoin so.
homeschooling doesn’t properly socialize children
According to a quick google, there are approximately 120 million metric tons of rare earths in the world. So that's not a minuscule amount, but also not earth-shattering.
Going in exactly the opposite direction, the Electronicos Fantasticos have been making electronic instruments for humans to play: https://youtu.be/UB7ZyZSKLX8
> about how newbies make their code comments too verbose

I don't Yegge is trying to make this point.

Instead, he's making a similar observation to the discussion OP had about whitespace/code:

Yegge reckoned that someone who's very familiar with the program/domain will want to have very dense code, so then they can make as much use of screenspace as possible.

Whereas, for someone who's unfamiliar with a domain will benefit from seeing less code on the screen at once. It will be easier to digest.

I don't really see that as a value judgement where "comments = bad".
Indeed, we're being too kind to you.
The really great thing about xml with XSD is the ability to validate the document really well.

I.e. having content matching regexps, so you can be sure version numbers are always \d+(\.\d+)* and does not have unexpected letters or spaces in it. That date values are in ISO format.

Very useful for APIs to 3rd parties as it now is very easy to catch most errors and provide an useful error message for them without having to code every check.
They can export their electricity through industry. Exporting electricity to other countries is quite the political challenge. And El Salvador doesn’t have that rich or easy neighbors either.

Also, mining bitcoin can be considered as a form of energy export.
All the federal employees I have met are EXCELLENT. It is very difficult to get hired into one of the dwindling jobs at the agencies. A lot of the government has been contracted out. Having worked at a federal IT contractor, I can say that in my experience most of those workers are very good and dedicated to their work. HOWEVER, they don’t always understand well the mission at hand. Some of this is to be expected given that they are contractors who come and go more frequently than federal employees charged with implementing government programs.
> I can't directly speak to any particular work you're describing, but "smart" people don't usually add significant complexity and aren't hard to work with.

I feel that's really unrelated to how "smart" person is. It's more due to experience when you start to appreciate the simplest approaches to solve the problem.

Many people chase some new and cool features and want to use them just because it is more interesting that clapping out boring code day in day out and that's where you get those overly clever blocks of code. I've seen every level of competence fall into it. Hell, I suspect like 3/4 of k8s and related deployment are exactly that, devs bored and wanting to play with new toy.
I think this is from 2016? https://m.youtube.com/watch?v=p7uv4mRUNgQ
If you're curious to science and how things work, you're also curious about how things work in other sciences.

And it's beneficial. Knowing linguistics, antropology or sociology (or about Khoomei singing, which is mentioned in your username) is helpful to stop thinking like "here's how I see X, so everyone should do Y in such and such a way".
All of those systems have outages all the time, mostly isolated incidents when it comes to NYSE, CME and similar (here is the outage page for NYSE for example: https://www.nyse.com/market-status/history). Visa, Mastercard and others have nationwide outages from time to time too, they're in no way invincible like you seem to imply. Latest Visa outage I can remember must have been around 2018/2019 sometime, but probably it happened later than that too, except I didn't notice it then.
Rare earth elements aren't actually rare.
amfora passes all torture tests.
When I first discovered YAML, I loved it's apparent simplicity. Nowadays, I sigh every time I have to use it and am very happy with the Rust world having mostly adopted TOML.
The hardest thing home schooled kids have to deal with is communication with public school kids.

Therefore, it's recommended that they speak slowly, and use monosyllabic words in the hope that most public school kids will be able to keep up and understand.
How to Manage Authorizations with RBAC