skysight-inc/HackerNews huggingface dataset:
This is nonsense if it's meant to be interpreted as anything but a joke, or as a way to maximize your own personal fun.

If you send me $20k of bitcoin and a UUID, I will run 'crypto.randomUUID()', and if I get the same UUID as you I'll send back $40k.

If you don't send me any money, you have 0% chance of winning, but if you do send me $20k, you have a mere 1 in 2^122 chance of winning, an infinite increase in your chance of winning, so surely it is rational to do so.

If you truly believe what you just wrote, I'll await my $20k.
Not only does the spec say that, but it was an explicit goal of Ingy döt Net, the designer of YAML.
You are correct. I just wanted to add that regardless how the US company alters their ToS, they are still obliged to follow the law of the land where they offer service. Which is why they get all the time legal troubles in the EU. But yeah. once your photos were already processed it's a bit late to sue.
I somewhat dislike the notion of "self-explanatory code" (especially if someone has tendency to be "smart")... optimise for reading and add comments!
You're wasting so much time doing this... Nobody will ever read 99% of it. Then the comments will get out of date and it'll end up worse than having no comments.
It's really impressive !!!!

BTW, the video show him playing with and against BOTS (that are notoriously weak in CS2), not with/against other human players (where he would stand no chance - and no fun - even against beginning players)
nothing can beat the simplicity of Nextjs using the old page router. Try it, all you need for a starting point is a package.json (react, react-dom and next as dependencies), and a pages directory with a single index.tsx, no need to even install typescript or manually create tsconfig.json. And you can do multi pages or single page app or static generation. All other options can only either do web server or static generator, not both.
Sounds like they don't want to do business with you because they think you are Russian.
https://archive.ph/xoSy8
From what I learned from Podcasts, they did a massive build-out of datacenters with Joyant technology for internal use as Samsung. But I don't know if that continued. Love to hear from Bryan more on that.
Also an example of open core is https://www.quantconnect.com/
> People reading this should remember that Flight 1 was preceded by hysterics from online detractors who predicted, correctly, that the launch would make a giant mess.

Does this "giant mess" matter in any practical way?
I miss the 90s/2000s internet too, but I'm also realistic about it.

Dialup sucked, search engines sucked, it was easy for random stuff to brick your computer and it was hard for anything you published to reach an audience. If you think ads now are bad, they were even worse back then.

What people miss is the slower sense of community. Social media has removed all boundaries between smaller local communities and many people aren't interested in finding one. So a lot of people have local friends, and then the amorphous blob of people on social media that they throw posts into. But these things still exist. You can find forums with only a couple hundred users, or circles of blogs. There are IRC channels dedicated to niche interests.

I haven't engaged with proper social media in years because I realized the above and just...left.
> 81 uL of catalyst -> 81 μL of catalyst

Oh, interesting. NIST recommends "L": https://www.nist.gov/pml/special-publication-811/nist-guide-...
“Jeff Dean’s résumé lists the things he hasn’t done—it’s shorter that way.”

Just brilliant. :-)
A part of this article misses a part of the point. Imagine saying: AI art is now purer, cleaner and cheaper than man-made. Sometimes the opposite is exactly the point. One wants a bit of raw history and imperfection.
I don't think that dicotomy is quite right. bad actors can take away my freedoms (for example if they steal my bank account I'm no longer financially free as I'd have no money)

I don't know the correct balance. maybe it's just an impossible problem. I just don't think the two sides are freedom vs state protection.
We have a couple of challenges today. Hobbyists often go over 20MHz, because they put WiFi, BT or USB on their boards, giving EMC issues. Also, the speed of the modern ICs tend to be very high. If you have a 9600 Hz UART signal, that is not a 9600 Hz signal if it's a square wave with a modern IC with very short rise time on the pins. So a good old, slow serial line can with modern MCU emit noise up in the hundreds of MHz range.

So your PCB layout tips are important, even on slow circuits these days.
Advice on signals they are looking for in key behavioural interview questions
Even if the users opted in when they signed up by agreeing to some privacy policy they didn’t read, that no one ever reads, that doesn’t make it okay for facebook to do this.
I can imagine that this is helpful to some people, but when coding I ignore comments usually. Good docs and code is all I need.
one great property of the terminal is that it’s not a continuous canvas. it’s a grid of discrete cells, just as it is natural for computers to be. instead of laying interactive objects out in virtual space, you’re pushed to think in discrete states and discrete actions. so I say cli is, indeed, good in part due of its limitations.

edit: i’ll add that continuousness of guis is actually its limitation. a terminal interface is indexable, a gui is not. so what looks like freedom is actually a different structure. a gui is more general, as real numbers are more general than whole numbers. but to get to whole numbers, you have to re-constrain real numbers. this is left up to the developer to create a constraining framework. and it’s a path of less resistance to not do this.
most data we deal with is discrete. so a continuous representation of it is a mismatch of structures. terminals force you to stay in that same discrete space. so your solutions are from the getgo closer in fit to your data.

it’s important to match up the structure of your interactive surface with the structure of your domain. it’s a common principle we talk about too little.
Just playing devils advocate.
I've built GPTeasers a ChatGPT based quiz generator. You can enter any topic and get a 10 question multiple choice quiz back - which you can play in the web app.

I don't know any webdev so please forgive the jank.

https://djsaunders1997.github.io/GPTeasers/
"A computer can never be held accountable. Therefore a computer must never make a management decision." -- IBM presentation, 1979

https://constelisvoss.com/pages/a-computer-can-never-be-held...
On what basis exactly? Income is taxed where the company (Apple subsidiary) is headquartered, so they would have to prove Apple would have chosen a different country, which is not going to happen.
Really good tool, I made a very basic text one and showed a few friends and it put them off the lottery.

One suggestion I would make is allowing the random numbers selected by the user to be random for each draw. I understand in the scheme of things that it doesn't make difference to your odds but that's a strategy that some people play.

It would also be cool to track how many other people chose the same numbers that you did and then divide the jackpot winnings by that amount of people.

Another thing (I'm really just giving you a todo list of things that I had) was to organise the number selectors to mirror the pattern on the lottery tickets. People have very different approaches, picking columns, going over 31, sequences and you could track the user behaviour behind number selection.
I disagree with that rule. I get that people spell liter, gram, meter in lower case, but units based on names of historic persons like Volt, Ampere, Coulomb, Pascal and Kelvin deserve to be capitalized.
I've definitely been bitten by designs that were too simple in critical areas. Interfaces can always be added to and code can always be deduplicated later. But an accretion of kludges around an insufficient set of core functionality is absolutely worse than having a little extra functionality that you end up deleting later.

Don't try to solve speculative future problems. But if you are pretty sure you're going to need something in the future, you should probably take it into consideration in your design.
> Don't they take the amount of time they need in order to ensure safety

According to SpaceX no safety concerns have been raised in quite some time.

It's also odd how much slower this approval process is compared to the previous and much more complex ones.
I am hoping and waiting for the 80s punk equivalent anti-SoMe counterculture to appear.
I couldn't agree more. This is essentially a solved problem, we just choose not to implement the solution. To everyone's detriment.
Hey! You might be interested by what we're building at Gouach

We're engineers/designers from France, and we've built the Ultimate DIY Battery that you can repair and refill!

It works with 90% of the bikes/motor brands on the market, so I assumed that some people here might be interested, if they got a non-functional batteries but they still want to use their e-bike?

We believe that everybody should have control about stuff they own, and we should fight against planned obsolescence!

Here are a few videos about our founder on the battery itself, why we built it, and how to assemble it:

- What is the Gouach Battery: https://www.youtube.com/watch?v=NsuW1NPkvNk

- Presentation of the pack: https://www.youtube.com/watch?v=mLoCihE0eIA

- Presentation of the fireproof and waterproof casing: https://www.youtube.com/watch?v=EDJpt7RDbRM

Here are the juicy bits: https://docs.gouach.com

We'd love some feedback from the e-bike DIY builder community

Oh, and it's launching as a Kickstarter in September and there is an offer for early-backers here https://get.gouach.com/1 for a 25% discount on the battery!

You can follow us on Instagram https://www.instagram.com/gouach.batteries to get the latest news!
There are indeed those situations where a comment would not increase the clarity of the code.

But one shouls be careful not to mentally think of this as a zero sum dichtomy, where you either have well named functions XOR you have comments, because in reality choosingn both is often the golden path to success.

The danger is of course that code that is totally obvious to you now will take far more time to become as obvious later, be it to your future self or to your psychopathic lunatic co-worker who knows where you live.

So very often code can be made more readable by adding comments, even if it is just saying the same thing with other words, just by reducing ambiguity. Comments can also bridge higher level concepts in a good way, e.g. by you explaining in a few lines how a component fits into a concept that is spread out over multiple files etc.

In the end code is text and like regular prosaic text you can both make it harder to understand by not mentioning things or by mentioning too many or the wrong things. This is why it is not irrelevant for programmers to be good and empathic communicators. Sure in the end readability doesn't matter to the computer, but it certainly matters to all people involved.
If you look for software engineer or type the company name...it will show how much is paid to the person. Here is the link

https://h1binfo.org/jobs/software-engineer/2024
Windows update doesn't install a proper driver?
Also very harmless (consider how many meteorites hit the Earth every year and consider how reactive the steel is compared to the random rocks) and very normal for rockets.
> If companies avoid tax and rich people avoid tax it means more tax for normal people who work for a living.

Which is exactly what is happening, with the gap between rich and poor increasing in the western economies.
The reason why cli commands are written in C is the fact that the OS is written in C. There is a lot of inertia, because it is more efficient to have the operating system and the tools for it written in the same language. We may be entering a transitional phase with new tools written, old tools rewritten in Rust. Some of the innovation or simplification highlighted in the article remind me of the chaos of the Unix wars which led to POSIX. I wouldn't chuck out the tools we have though. Modernise them, but keep their functionality. What many critics of CLI tools do not realise is that there is a lot of power hiding in that complexity. Familiarise yourself with xargs or parallel commands to see that quite often learning them given you results faster than reimplementing them.
The EU now mandates that new cars have an interface to allow installation of devices that measure your blood alcohol.

Perhaps this is well meaning, but there are countless ways to sabotage such a system.

Another example is the break assistant and collision avoidance. It isn't a solved problem and there are quite a few cases where cars break without any reason, which presents a huge danger itself. Still, such a system is now mandatory too.

That will make cars even more expensive. I think governments around the world are quite overtaxed...
FWIW this is more of a concern if you expect the case to go to court. In the US most "criminals" accept plea bargains without a court ever seeing the case. So statistically you can likely "act on your feels" as long as the suspect does not think they can prove you wrong in a court of law (whether it's because they're guilty, because they don't fully understand the law or because they can't afford the time and money involved in a court process).
YAML 1.2.2 still isn't a superset of JSON, because it requires all keys to be unique:

> The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique
Have you tried sending the large company a quote for how much you'd want to make the changes for them? They want you to do something, you're not free. It seems like the monetisation opportunity is staring at you in the face. It might not give you the constant, passive income stream you might be hoping for, though.
It should be called Reject-O-matic or you might get the impression that it’s ever used to consent to anything…
Someone has to pay for distribution, maintenance, and integrations of the encryption on an ongoing basis. If it was legal to write encryption but illegal to distribute it, what would be the difference from a ban? Both tor and cryptography require an ongoing effort to provide their service.
You've questioned existence of such "bad policy". I pointed out that there are such policies. I neither supported nor opposed them.

I won't be surprised if there were something in US criminal code with supreme court precedents that specifically dictate the government harass in timely manners the makers of cutlery used in a mugging. There _are_ always laws. _Everything_ is regulated. Most of those regulations are reasonable.
I think the point is that naive regex are a very generic purpose tool, but it's still in the same ballpark. Having a custom optimized state machine for this specific use case could bring another 5x improvement on top, leading to 2.5x faster, potentially.
Yaml should be used as a lesson learned, not sure why people still use it as a data format. You should stop even tolerating it, refuse on sight.
Sorry but hi. It’s me, your girlfriend. Only I’m actually in an engineering role.
One issue with comments is that an engineer who struggles to write clearly will also struggle to write clear comments. And clear code. But at least the code can be deciphered by reverse engineering it, stepping through it, or in some cases rewriting it. For me, at least the comments are worth reading before trying to figure out what someone's code does, to get me into the ballpark.

I often add comments to code as I decipher it, then remove them again when I figure things out.
> public void RemoveItems(Func<Item, bool> condition)

Tangential, but remember that you can't generally push this condition over a database connection. You've just forced your code to be best-case O(n).

Using structured queries as far as possible is useful for performance. But consider what happens if you create a Predicate structure, and someone adds a field without updating the Remove function to match... Perhaps a recursive discriminated union is the way to go, for languages that fail compilation when not all branches are covered? Positional arguments in other languages?
The terminal is valuable just because it has applications that are easy to do or even only possible in it. Specifically, a full-duplex interactivity at a low data rate. I don't think any current "modernization" proposals threatened that so far, the biggest contender would be any image support but it isn't meant to be used every time anyway.
Brute force hardware locks us into the local minimum of matmul. Stella Nera demonstrated better power efficiency than GPUs, using approx matmul. Maybe the next generation of special purpose HW can help, too. But they come after 2-4 years. Who knows what we will want then? I'd rather have flexible HW.
YAML 1.2.2 is also not a JSON superset, as keys are required to be unique:

> The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique

https://yaml.org/spec/1.2.2/#representation-graph
Ensure that you’re either increasing someone’s revenue or decreasing their costs. In both cases, it should be possible to somehow convince people to pay you. How exactly is a bit of an art and requires some creativity but should be possible. For example if a company earns or saves 100k dollars per year from your software, it should not take much convincing to negotiate them giving you 1k-5k.
Can you switch the licenses? I'm assuming since no consideration is exchanged, there's no contract, so you can change to a less permissive license.
They might be rarely considering code formatting specifically, but the claim that one language is a superset of another really does imply that all valid instances of the latter are also valid instances of the former (and are similarly parsed).

The old spec of YAML 1.2 section 1.3 explicitly said:

YAML can therefore be viewed as a natural superset of JSON, offering improved human readability and a more complete information model. This is also the case in practice; every JSON file is also a valid YAML file.

The revised spec 1.2 revision 1.2.2 (2021-10-01) no longer contains that sentence; but still says, in section 1.2:

The YAML 1.2 specification was published in 2009. Its primary focus was making YAML a strict superset of JSON.

and in section 6.8.1:

Note that version 1.2 is mostly a superset of version 1.1, defined for the purpose of ensuring JSON compatibility.

Given all these claims, Patrick Stevens’ observations that YAML really isn’t a superset of JSON, because YAML can’t handle all JSON number literals, and tabs as whitespace, really is surprising. At least to me.

When previously JavaScript/ECMAScript 2018 was found not to be a JSON superset, at least it was about unescaped occurrences of little-used characters U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR in string literals. And even that got fixed (by allowing the unescaped characters) in ECMAScript 2019.

[YAML 1.2]: https://yaml.org/spec/1.2-old/spec.html#id2759572
[YAML 1.2 revision 1.2.2]: https://yaml.org/spec/1.2.2/
[ECMAScript 2019 feature Subume JSON]: https://v8.dev/features/subsume-json
tl;dr

Nevada plans to launch a generative AI system powered by Google that will analyze transcripts of unemployment appeals hearings and issue recommendations to human referees about whether or not claimants should receive benefits.

The system will use Google's Vertex AI studio to create a retrieval-augmented generation (RAG) model, which will draw on a database of Nevada unemployment law and previous appeals cases. Proponents argue that if done correctly, AI automation can address some of the problems that caused life-altering delays for unemployed Nevadans during the pandemic.
Your post's remark about YAML 1.2 being opt-in with a "%YAML 1.2" directive is true for the parser you are using (LibYAML), but is not compliant with the 1.2 spec. The spec specifies it should assume 1.2 and 1.1 should be opt-in.
Let's not exaggerate. Everything they did was already well-established in academia for decades and what they built was pretty dumbed-down rather than novel, at least conceptually.

Sure, they did good engineering to apply those techniques at Google, but they did not "lay out the foundations of large scale distributed computing".
Yaak is now open source
I acknowledge Jevon and that demand may increase. But the original point was actually that specialized HW will be outcompeted by newer algorithms on more flexible HW. I have seen this play out several times, for example with brute force Sum of Abs Difference instructions that no video codec uses anymore, because a sparse search is faster than brute force HW. Personal opinion: this will happen again.
Why should we focus on how to fill GPU cycles, rather than invent the future of how to do better?
In the end a comment should be like a shortcut that allows people to understand your code faster or a reminder why certain choices were made.

You are right in spirit to say sorry when the code cannot be self-explainatory, but consider that sometimes even if the code is self explainatory, comments can help your reader to see the grand picture faster or to avoid interpersonal ambiguity by allowing you to use two different ways of phrasing a thing.
This seems pedantic, but I suppose anyone using the term 'superset' is inviting the pedantry.

For almost all intents and purposes, if you are asked to create a YAML file then you can choose JSON as your syntax instead, because your file will be understood by the YAML parser. The benefit being that JSON has far fewer quirks and edge cases.

It's comical that when people get confused with YAML (which is often) they convert their YAML snippet to JSON to see what's really going on. YAML is horrible for humans to write. Let's just use JSON, the sane syntax, instead. A few extra parents and quotes is really no big deal, and it's far easier to read unambiguously.
A tree is a specific kind of graph.
While JSON doesn't prevent duplicate keys per se, it doesn't fully specify its semantics anyway and only states that duplicate keys are less "interoperable". And there is an explicit profile of JSON with this requirement (I-JSON [1]), so YAML 1.2.2 can be said to be a superset of some version of JSON.

[1] https://datatracker.ietf.org/doc/html/rfc7493
sqm instead of m^2 is also just a way of typing it on a mobile keyboard.
> I am not sure if you catch the point?

I definitely don't, especially pertaining to the actual question I asked:

>> participants are appraised based on the value they provide to the society

>How do you measure that? And who decides?

I wasn't talking about "pure free markets", I am not interested about philosophizing and talking politics - just concrete, real, actionable points.

LE: I live in the EU and saying Western European countries offer more economic freedom than the US is joke. The actual reality proves it: European economy has fallen badly behind the US. Reasons include overregulation, anti-business and anti-corporation climate.
the first couple of times

Times every yaml user in the multiverse.