skysight-inc/HackerNews huggingface dataset:
Jesus fucking Christ. Every single year we have people in giant companies continue to completely misunderstand simple concepts, and YAML is probably the most egregious.

First of all. YAML is supposed to be human readable, not writeable. If you even learn the standard, you realize that it's primarily a multi-document streaming data format. That means it's intended to be written on the fly by a machine. The macros it contains are rudimentary and don't actually recursively interpolate data. The extensions are designed solely for external applications to evaluate, leaving the humans out of the loop. And its many different object types are intended for the serialization of program data structures - not for a human to write the word NO in their terminal text editor, into the data format designed for a program to deserialize arbitrary data.

Stop fucking writing shit in YAML by hand!

And while we're on the subject, please, for dick's sake, stop treating data formats like configuration formats!! An Apache or Nginx config file is a configuration format. YAML is a data serialization format that is human readable. Learn the difference.
> CST is a sloppy term;

It's not though, it means "Central Standard Time", which is UTC-06:00. It is sometimes sloppily misused to mean "Central Time", which is a sloppy term, meaning either UTC-06:00 (CST) or UTC-05:00 (CDT) depending on the time of year and where you are in the country.

> or America/Indiana/Indianapolis (for the weird one that doesn't use DST)

1. You mean `America/Indiana/Knox` or `America/Indiana/Tell_City` or historically almost any of the other `America/Indiana/…` zoneinfo files except for Indianapolis. Indianapolis has "always" (since 1961) been "Eastern" rather than "Central", it's other non-Indianapolis regions of Indiana that have been "Central, but without DST".

2. But regardless, it's outdated; all of Indiana has been doing DST since 2006; mostly Eastern (EDT/EST), but a few western parts of the state are Central (CDT/CST).

> (While researching this comment, I found that Indiana has at least 8 different time zones, so ... good luck with that.)

They only still exist for pre-2007 dates; for post-2007 dates they're all equivalent to either America/Chicago (…/Knox and …/Tell_City) or America/New_York (the other 6 of them).

> I don't know if you can type things like "CST" into Debian, but I don't think you can.

It's inconsistent. You can type in EST or MST, but not CST.
While I agree with the sentiment of this comment (there are so many aspects of modern web development that are layers of abstracted complexity to re-invent wheels long-since optimised). However...

scrolling lists are, once one gets to thinking about them in depth, a lot more tricky to implement than they are to use. In fact I can't actually think of a better example of something that seems at first glance simple, but upon closer inspection is riddled with challenges.

It basically comes down to the simple question of: how do I render as little as possible at a time, but also render everything/anything in the list "immediately" or as fast as possible. These are fundamentally oppositional requirements, and no solution, whether arrived at after 20 or 50 years, will ever not be a compromise of some sort between them.
People value things differently. There's people who bristle at the idea that the government should coerce them into getting unwanted medical procedures or restrict their movement. There's people who don't believe governments who have badly and repeatedly bungled the response to covid are a reliable or trustworthy authority on the matter.

Not everyone may take covid exactly as seriously as you would wish them to, but it doesn't mean they don't take it seriously just because they value other things more. People going out en masse to protest police brutality for example apparently understood the risks of covid but believed their cause and their right to protest it to be more important. Who are you to say they are wrong? People who understood the risks but believed border closures to be wrong or racist believed that cause was more serious than covid, again who are we to say that's wrong? Do we have some ivory tower of government experts who are there to provide us unthinking plebs with the canonical guide for ranking everything in seriousness and importance?

If we had the government telling us that driving automobiles causes a million deaths every year and the only way to solve it is for everyone to stop driving, but maybe we can start driving again after everyone's cars have been fitted with modifications to limit speed to 5mph which should be at least 90% effective at eliminating hospitalizations and deaths, then they're not exactly _wrong_, but of course people are going to protest it. If you drove anyway that does not mean you don't take automobile accidents seriously, that you're anti science, or that you're a grandma killer. You will certainly statistically increase the load on the hospital system if you drive, that choice does not make you responsible for possible deaths of other people who could not access sufficient medical treatment. Not even if you just went for a drive to the beach, up a mountain, or an aimless drive through the streets just because you enjoyed it.
Who literally saved Apple from their attempted corporate suicide? Yeah, I think he is a good example of why you need a strong founder sometimes.
That was indeed the thrust of the analogy. Basically, we try to design programming languages so that the interface is decoupled from the implementation. A function should have an intuitive, descriptive name that reflects what it achieves, free of such terrestrial concerns as who wrote it, and when, and whether a different person decided to fix a bunch of bugs in it. But commands in Unix exist in a single-layer, permanently immutable namespace. Someone wrote the canonical 'top' once upon a time and now all evolutions on the concept must use names like "htop" and "vtop" and "gtop" and "ptop". By 2121 we'll have exhausted that namespace too, and be on to "aatop", "abtop" etc.

Good interface design is stable, even as the backend tech improves. Both a go-kart and the NASA crawler-transporter have steering wheels, because the wheel is an affordance for the human, not the machine. But on a Unix system, there's huge churn in how to do things - usually for no better reason than that it would break a bunch of stuff to change how the old way works, so better to simply add a new way. Someone wrote an improved version of grep - does that mean we get grep v2? Nope, we get "ripgrep", and old grep stays permanently...

The worst of it is, that namespace doesn't even guarantee anything! It would at least be some consolation if 'ls' worked identically on every system, but alas...
Alphabet open sources low-cost device to make drinking water from air
You know, if you bring up the First Amendment in US, people usually stop listening. I haven't seen it brought up in court, though. But even in court. Unless of course there's something exceptional and sound in a strict sense about your argument (off the top of my head "I was born on the Moon. Because everybody who has ever walked on the Moon, and the only military on the Moon, were American, and the only country with a human presence on the moon, was America, therefore it is part of America, therefore I was born in America, and am therefore an American citizen." Suppose that's the truth, you were born on the Moon, and you say just what I wrote, and you believe it, and you mean it, oh man. American courts will, yeah, they'll really sympathize with you, and then yes, they will accept "freedom of speech" as an argument.
I pretty much use it every day at this point and I notice when it is disabled.

> It’s just trash

I have a hard time relating to this kind of experience considering how useful it has been for me. What language are you writing in btw? When I use it for OCaml it's not that useful, perhaps because there isn't as much OCaml code to learn from :D
Yep! We both quit FB in 2019. This has been our (full time, volunteer, spending our savings) job since ~Jan/Feb of this year.

It's taken a long time to gather people, build trust, figure out our strategy, find consensus, make our first reports, etc.
Presumably when these age check systems fail, governments will be able to justify a system which assigns each computing device a registered owner.

You'll have to initiate a video call with a government employee, hold up your photo ID and say your name, and then the app will download a digital certificate to be stored in your device's TPM chip.

From then on, you'll have to use that certificate every time you are issued an IP address by an ISP, and the ISPs will keep a log connecting each IP address (and time period) with the ID baked into the certificate (which will be a passport / driving licence / national ID card / immigrant visa number).

Perhaps the protocol between the device and the ISP will be zero-knowledge, so the ISP never sees your ID, they just know you've been issued one, and the value they store is blinded with a government public-key, so that the government can unblind it after subpoenaing it from the ISP.
I wasn’t clear at all, but I certainly agree it would be clear life was on earth from such data. I am less clear how much about our society you could meaningfully conclude from it is all, but perhaps it’d be clear from our pollution exactly what we’re manufacturing/burning
Lua is also good.
They’re already on the top end of the distribution, you can see pretty accurate numbers on Levels.fyi
Well I certainly do not agree with Ricardian equivalence. For it to hold, one must assume lump sun taxes which one cannot avoid by being poor. That's a ridiculous assumption.

> But if you do not believe in Ricardian Equivalence, then the deficit spending is an increase in net-wealth, which again shows up disproportionately on the balance sheets of the wealthy.

My whole point was that this is not necessarily true, and depends on the form the spending takes place. Did you miss that?

Even if a UBI eventually trickles up, we must not conflate solvency and liquidity. The boss has power because the worker's consumption is more time sensative than the production. A good UBI takes away that coercive power not (just) by increasing worker savings, but by making an income floor. (Stock vs flow).

That's like giving people the ability to go longer without food and water so long as their nutritional needs are still met on a (longer term) average.
OpenMetrics relates to the metrics part of OpenTelemetry, where the latter is currently in alpha/experimental phase. OpenTelemetry has a statement on being interoperable with OpenMetrics for both accepting, forwarding and generating in the OpenMetrics format [0]. So they are two separate CNCF projects where OpenMetrics has overlap with a part of OpenTelemetry.

[0] https://github.com/open-telemetry/opentelemetry-specificatio...
Exactly, I'm already laughing reading the comments here considering I've been using copilot for weeks and it's a game changer
You really think Frances is a deep cover op by Facebook? Really? Wow.
For any Kicad devs reading this thread, are multi-sheet schematics on the roadmap at all?

I work with some Orcad designers who view it as a necessary feature for the style of schematics that they draw. They feel like forced-hierarchical is arbitrary and high friction, but also don't want to throw a complex design onto one giant sheet.
Hey thanks! Photostructure seems cool I may give it a go..
How should one create kubernetes infrastructure then?
Your comment hides some truth! Imagine coding today without stackoverflow. Possible, but you'd lose so much time looking for simple answers.
I didn't think YAML was that bad until I heard about unexpectedly truncated YAML files still producing valid YAML
Why would a billionaire leave the US? There they are like gods with services to cater to their every whim. Nowhere else in the world will roll out the carpet for big money like the US does (excluding maybe Monaco and other small states). I just see 3 as a false assumption, as any country they 'flee' to will have higher taxes anyway.

I live in New Zealand and a billionaire here can have a lot of land but otherwise we just don't have the infrastructure to support that ultra high end lifestyle. They would basically be average people with nice toys and a big house here.
Almost everything is possible you manage to get the other shareholders to agree. That might happen when some early investors sometimes want the founder to have more control especially before going public. The theory is that you'd rather have a founder you invested on in the first place steering the company than let your generic wallstreet shareholder without a vision(tm) take over a unicorn still full of promise.

Sometimes the bet pays off, very very well. Take for example Musk. You can say whatever about him, but it's extremely clear he has a vision, and does pretty much anything to get there. I'm not sure tesla or spacex would've survived 2018 with someone else at the helm or if a shareholder revolt happened. Just by that metric he is already worth dozens of billions to the rest of the shareholders.

Zuck is also a good example of investors trading off votes for a more wall st. independant, steadier long term eadership.

Now keep in mind those are exceptions. Having supervoting shares orbmultiple classes of shareholders is very often not a good thing and usually leads to less value being generated.

Accountability to shareholders is usually good and very important to ensure sane corporate governance. Which is why CEOs and founders absolutely love having ever less powerful shareholders and we end up in situations like now where even the crappiest IPO has absurdly overgeared supervoting classes. Who doesn't want to buy in a deeply in debt, cash burning ipo with very questionable growth who's founder has a perpetual 80% of the votes?
Funny you should link that! I have gotten as far as getting a raspberry pi zero to be a USB audio gadget, but I haven't played with the Pico yet. The raspi zero has one i2s input and one i2s output.

> Pico itself can interface 29 microphones with no sweat.

I... had no idea. I thought that since it didn't have an i2s peripheral I was going to have to either find a micro that did, or do something bitbangy using SPI and perhaps an external buffer. I see that it might be possible to get a few I2S inputs using the PIOs. Thanks for this, will certainly give it a shot.

(though I don't see how you're getting 29 microphones :P "prove it" ;)
I didn't focus specifically on these women to imply it only applies to women, I merely responded to somebody far up the thread that singled out that demographic.

I think it's important to be precise about the group. I'm assuming a subset of women that have delayed relationships or family planning for 1-2 decades due to their full dedication to their careers. Most educated women would not fall in this group. They would have found some balance between the two, and start earlier with the social aspect of life. So the group is highly specific, to a degree extreme.

I do not believe that men and women look for the exact same qualities in each other. The thing these women optimized for (professional status) is not necessarily high on the list of all men. And even if it was, (many/most) men would settle for "less" in the meanwhile, indicating that again time is the selector. These women have desirable qualities, but they don't matter if they're not on the market when it matters.

The opposite situation is not the same. Whether it is biological or cultural, men fully dedicated to their career do tend to find partners accepting this imbalance, thus they don't wait until 40 years old to start a relationship or family. It doesn't even have to be a harmful stereotype if its fully consensual.

So I agree that this dynamic is less applicable to men. And indeed, said women have to adjust expectations.

Again I could sum it up as this: start in your twenties if you're picky.
aka "lacks namespaces"... but it isn't so. The namespaces are paths and they're "linked" by $PATH. /usr/local/bin is a namespace. Is it guaranteed to be a fully qualified namesake? No. But your sysadmin (now Docker) is in charge of that. You can plan a system that forces everyone to use fully qualified nameplates, but you can't force people to use the system. That's why unix/posix/Linux remain the lowest common denominators.. by making fewer assumptions they retain a different flexibility that makes them useful for gluing together the ornery systems designed by all you planners.
> This facilitates wealth transfer from generation to generation

Well, arguably it's the step up in basis that enables generational transfer without taxation.
Jerry (YC S17) is hiring a senior software engineer
Why don't we have comments in JSON?
And when you reimplement <select>, it won’t feel native because different platforms have different conventions (e.g. placement of dropdown, click-and-drag behaviour, whether focus is selection, keyboard shortcuts like Tab), and very few implementations try even half-baked user-agent sniffing to try to emulate the platform. And that’s just thinking about desktop platforms; on mobile platforms, the native dropdown behaviour is simply unimplementable.

I would say: if it’s just about the style of the <select>, stubbornly refuse to reimplement it, just do what you can on it with CSS and try no further. If you’re needing different functional behaviour (e.g. adding right-aligned text on each option, or making it intelligently filterable by typing—e.g. an airport picker making “CHC” match “Christchurch”), then yeah, you’ve got to reimplement <select> even though it’ll necessarily be a smidgeon worse in some ways.

<select> makes a very bad primitive.
WWV and WWVH will be sending a new test signal on minute 8 for WWV and minute 48 for WWVH.

https://www.youtube.com/watch?v=O3Q7L0TNGtk

The test signal .wav file is available here:

https://zenodo.org/record/5602094
YAML's not bad if you couple it with strong types. I used YAML _heavily_ and wasn't aware of any of the issues that the author mentioned because of the types. It doesn't let YAML automatically parse dates because the destination structure is either a date or a string or whatever, and that controls the parsing. It doesn't have the Norway problem because it knows whether a field is a boolean or not. I don't think it had the octal problem, not 100% sure though.

It's very good for non-technical people to edit because they are allergic to symbols and quotes and brackets and making sure things match. YAML's syntax let you write like you're a CEO sending agenda notes to a subordinate. You can easily switch between line-per-item and brackets-style and you do so whenever the readability is improved by doing so. It's highly intuitive somehow. You can pretty much turn someone into a config-editor just by showing them an example file, especially with syntax highlighting.
I am not so sure about that...maybe you don't run updates in the background but some of the distros do and there are random strange problems until you reboot. Windows is definitely worse at that but Linux is not 100% safe either. Also there is always a chance that your Linux update will cause things to stop working, it happened to me a lot more often than with Windows.
If you have a tablet without kb attached Linux is a major PITA as the on screen kb and touchscreen work 90% of the time and then randomly stop. If you think that 90% is good, try it and see for yourself...spoiler: try to unlock your screen when kb is not working...or try to select a menu that keeps closing as soon as you touch it without selecting the item...or try to search for application in Gnome activities with touchscreen. It is so, so close but not quite there yet...and it doesn't seem to be getting any better.
NixOS is another great idea with sub-par implementation. Two things that made me wipe it off the computer:
1) compile your own program and now try to run it on NixOS computer...good luck.
2) upstream program is marked as abandoned, I guess you don't need it until someone starts maintaining it again...W.T.F!!!!
A tax on personal unrealized capital gains will not take away any money from the company. It's privately-held, and has no effect on a company's balance sheet.
I don't hate yaml. It's a bit overcomplicated, a bit too cute, but it works. It doesn't leave a lot of room for additional complexity, though.

I've been using Ansible a lot recently. I like it a lot, most of the time. Its configuration files are YAML + Jinja2 templates + Python expressions. It works fine for the basics but when you push it quickly devolves into madness.

e.g. I had a task like this:

- set_fact:
foo_bar: >
{{ item | map(attribute="something") | rejectattr("bar", "none") | flatten | select is any }}

Can you spot the error? The block scalar header `>` was missing the hyphen `>-`. YAML helpfully added a newline to the end of the template output. Python helpfully interpreted "False\n" as `true`.

I'm starting to think I should write Python modules for anything complex.
Samsung (South Korea), TSMC (Taiwan) and Intel (US, Israel) locate their fabs in small countries that are heavily dependent on the US for ensuring their neighbors do not attack.

Two of those three (TSMC & Intel) are building fabs in Arizona due to political pressure, hefty subsidies and geological stability of the area (reducing the number of defects in chips).
I don't follow your reasoning, either. Do you really think that a new tax on several hundred billionaires will discourage the hundreds of thousands of entrepreneurs that are out there, that a significant amount of them will not bother since they can only make a few hundred million before they have an extra 15% of their money collected in taxes?

Most entrepreneurs would be overjoyed to be a billionaire and have to pay that extra 15%. Seems like they'd be the lucky ones. Seems like a billionaire or an aspiring billionaire complaining about such a thing would be pretty weird.

The parent you replied to mentioned wealth being locked up to avoid capital gains taxes. There are other pros and cons, I'm sure. Do you think this new tax on billionaires means that less people will be trying to become multi-millionaires?

Note that I'm not happy with the current tax system, and this seems like another kludge. I also don't know that we need to coddle or incentivize wealth maintenance, it's not an end in and of itself.
> How can we reduce emissions from the rich?

How can we reduce the hunger of the spider? - the fly
Unity uses a subset of YAML as its serialization format, and dear god that is one of the worst choices they’ve made. Very hard to decipher, very hard to resolve merge conflicts, and god awful slow.

YAML is good as a concise configuration description language, but using it as a serialization format for general data should be avoided at all costs.
Yesterday I tried to convert the representation of a number into another representation/type in Rust:

let coeff = BigUint::from_str(x).unwrap();
let coeff: <<G1Affine as AffineCurve>::ScalarField as PrimeField>::BigInt =
coeff.try_into().unwrap();
let x: <G1Affine as AffineCurve>::ScalarField = coeff.into();

I wrote that, then I wanted to move that code in a function so I wrote:

fn string_int_to_field_el(s: &str)

copilot suggested the following one-liner that did exactly the same thing:

fn string_int_to_field_el(s: &str) -> <G1Affine as AffineCurve>::ScalarField {
let x: <G1Affine as AffineCurve>::ScalarField = s.parse().unwrap();
x
}

I still don't understand how some heuristics could produce this code. It's mind blowing.
> There are ways around this in the UK system, however. It's probably the same case in the US. The short of it is you transfer the wealth well before (15-20 years) the death occurs, thus there is no inheritance.

So, you pay gift taxes instead.

Unless you use fake business transactions.
Shutting it down would have made every single existing radio controlled clock e-waste, overnight. And not just random wristwatches and wall clocks, but school and industrial clocks. None of these will work with GNSS signals.