skysight-inc/HackerNews huggingface dataset:
XML is/was hated by newbies and old farts alike.

Of course some of the hate come from the application where XML was used, more than XML itself, but it also is a deeply flawed language.

Nowadays the main issue would be that it requires a complex generator and parser libraries to be any useful (you'll never want to deal with XML parsing/escaping by yourself) yet it's not as efficient as binary formats like protobuff for instance.

That means that anything you'll want to edit by hand or be purely textual and readble will be better done in yaml or json, and anything beyond that can be done in other ways. The need for a single language trying to awkwardly span all the spectrum isn't big.
It's complicated. Unions do what their members want. But "what the members want" can be pretty different from what turns out to be a good idea in hindsight. Should children work down the coal mine? The view of somebody who wants that extra income from their 12 year old working in the mine may be quite different...

I support many union actions at my employer, for example I joined their recent strike, withholding my labour (and consequently getting paid less) because the employer and indeed their entire sector, refuses to make sensible pension and pay provisions - but I won't join the union itself because I don't agree with all their positions and I'm content with the trade off that results.
One thing that confused me was that the author talks about using "Good Boy Ninja’s method for talking to Gumroad’s API," which I thought meant that they were relying on undocumented behavior of the API. That would explain why Gumroad was so cavalier about breaking existing clients who relied on this method.

I checked Gumroad's API documentation[0] and found that the product_permalink and increment_uses_count parameters weren't documented. Then I checked the Wayback Machine for the documentation at the time the exploit was discovered[1], and those parameters were documented, so the author was relying on documented, supported behavior.

Given this, Gumroad breaking all their clients with only two weeks' notice over the holidays and offering only a $500 bounty feels pretty disrespectful.

I obviously don't know about Gumroad's internals, but nothing about the original API semantics seems inherently insecure to me. Why couldn't they have just verified that the entity that owns the license key also owns the permalink? It feels like Gumroad just chose the fix that minimized work on their end while pushing a lot of work onto their API consumers and those consumers' clients.

[0] https://app.gumroad.com/api#licenses

[1] https://web.archive.org/web/20221107215637/https://app.gumro...
> Contrary to popular belief, modern cold-climate heat pumps can heat a home efficiently even when the temperature drops below -10 degrees. At this temperature the best cold climate heat pumps are still more energy efficient than furnaces and boilers

This is maybe true if your house is insulated to Scandinavian standards. Our heat pumps here in Maryland get iffy around 20 degrees in our circa 2005 house. We have a nice oil burner heating a hydronic system that does a great job at that point.
You could just use pkgsrc. Joyent has binary packages.
There's a scene in the 1979 film Scum (https://www.imdb.com/title/tt0079871/?ref_=nv_sr_srsg_0) where one of the warders in a young offenders' institution allows a bullied inmate to be framed by his peers and punishes him.

When I saw that (not long after it was released) I thought how well that captured the spirit of many school interactions, where bullies would blame their victim and the teachers would fall for it.
Yet you still need to do it, even if it is every few months, else you will eventually hit the snag.

If you don't have an option to restore the data your backup might as well not exist.
A compromise is to just have smaller schools. I don’t know who came up with the idea to put over 1,000 teenagers together in a building everyday as so many public high schools do in the US, but there are plenty of studies that show it’s a terrible idea.
To build on your comment…I think picking simple or anti-complexity is a values call perhaps enabled by emotional intelligence and being secure in who you are.

I have met many people whose identity is wrapped up in being smart. When faced with choosing a clever solution or an understandable solution they will choose the former. This is where preserving their identity outweighs empathy for you or even for themselves. Some people also like to be the hero. If they are the only ones who get the solution then they are more likely to be the hero to fix it in some future moment of need.
Not a deep learning expert, but: it seems that without backpropagation for model updates, the communication costs should be lower. And that will enable models that are easier to parallelize?

Nvidia isn't creating new versions of its NVLink/NVSwitch products just for the sake of it, better communication must be a key enabler.

Can someone with deeper knowledge can comment on this? Is communication a bottleneck, and will this algorithm uncover a new design space for NNs?
-10F is -23.33C
Wow, you must really be forgetful. Maybe your productivity would improve with some post-it notes stuck next to your monitor, reminding you of the basics about how these formats work.
Next week, the kremlin will discover russian-speaking citizens in Kiruna, and demand the city is returned to its rightful owner — the CCCP — for everyone's safety and prosperity.
I think it probably IS the APIs that are a problem but since you usually cannot instantly get rid of such things I think you need tricks.

e.g. keeping your fixtures in separate files and naming them in such a way that the actual data doesn't appear in your test code.

You might use some fixture as a base value (in my case I had this problem with a big old structure that describes PKI certificates of may types) and have derived fixtures that are (the base plus a change to the "account" field or the base with the "accept" field set to "false"). I did this with python classes and inheritance. Each derived class copied the base class's data and applied a diff. YMMV but I mention it just in case it helps.

If these are all named and kept in separate files then your actual integration tests can look a bit simpler perhaps?
I find this take absolutely incredible.

Take any of the last 3 years, and then let’s compare that to the past, and let’s compare what came out in e.g. 2022 and 1992.

That you think things have gotten better is one of those things that makes me lose hope for the future of humanity, because clearly we are so different that we’re perceiving completely, vastly different realities - we might as well be living in parallel universes and it’s just a perversion that we can perceive each other.
What are the advantages over AutoMapper?
This would not support that suicides dropped though would it? Kids would be online more and likely face bullying continuation.

Not that I disagree with it generally being a horrible scourge on childhood experience.
Running Zola on WebAssembly
I consider code to be a liability, and Git history to be an asset. If something's in version control, there's no need to keep unused cruft around "just in case" it's useful in the future.
>You can certainly challenge the premise that humans will ever have the capability of creating a simulation as high fidelity as our reality. This is very far from certain.

I don't think it's the best formulation. Let me formulate this in IMHO a better way:

If a simulation is of an equivalent complexity level to the 'true' thing, it's essentially equivalent and might as well be true. There's an argument from quantum mechanics that this reality cannot be properly simulated with anything simpler. If true, the conclusion is that since we exist we are real.
Too late, they're virtually in Nato already.
I don’t think it’s necessary in most cases, although oddly I recently had a medical insurance claim rejected because of a gender mismatch for my wife. (USA and all the health insurance mess)

Turns out that my employer deliberately doesn’t send gender to the insurance company. This means it defaults to male. A urologist appointment for kidney stones was then rejected by the insurer when it didn’t match the provider.

If this was an Ob/Gyn appointment that makes a little more sense, but kidney stones and urology in general are non-gendered. This was not the first claim either. Plenty of others were fine with other providers.

I can see gender being used sort of generically for fraud prevention in some cases. But, it’s a stretch to say it’s broadly useful.

In general now I lie on forms about as much as I can. At Panera Bread I was asked if I’m the CEO when my account came up first name Panera, last name Bread. There’s no reason for any personal data, so I don’t give it.
I love the idea of robot vacuums. In fact I own one. In my opinion one of the most useful "smart home" device currently made. Too bad the good ones are all tied to some shitty cloud (whilst they could work locally 100%).
Fortunately projects like https://valetudo.cloud exist...
I’ve been using this for (schema + autocomplete) for at least 18(!) years.

Moreover I even got comments on xml attributes and elements, warnings if required element is missing or required count is not met.

You even got visual hierarchical collapsable UI for viewing/editing that XSD schema.

I repeat: 18 years of autocomplete, comments on hover, and validation for typos/count/order for XML in Visual Studio.
Having to watch out for footguns (by being defensive as you described) means you're just having to learn these rules. What benefit is YAML giving you then?

Why not use JSON? Conversion of types from YAML to the language's native types is a poor feature to get in return for footguns.

If you _need_ complex types - like a in RPC serialization - then i would imagine using XML is better, and forget about making it human-readable. Create a client/testbed instead.

For simple things, JSON fits really well imho.
I don't understand why anyone would be worried their heat pump isn't going to work in winter. I've never seen a heat pump installation that didn't include an emergency resistive heater.
> #13 - Early adopters are unfairly rewarded
The first users are rewarded for taking on more risk with their time and money. The capital invested in bitcoin at every stage of its life strengthened the community and helped the currency reach subsequent milestones. Argue that early adopters do not deserve to benefit from this is akin to saying that the first investors in a business, or people who buy shares in the IPO (Initial Public Offering) of a company, are rewarded unfairly.

The unfairness is in the halvings which reward early miners exponentially more than later miners on top of the large advantage they already enjoyed in having far less competition. The result is a large concentration of wealth on early miners.
Recession is mostly about market participants being fearfull. In "reality", things aren't that bleak.
> Article doesn't say why only one week per year

"That decision helped set expectations for appropriate vacation length per year."
I've never really understood the use case for these mapping generators. Every time I've seen them used (MapStruct in Java, AutoMapper in C#) the mapping configuration eventually ends up being so complex that just manually writing out the mapping would've been just as simple and arguably simpler to understand.
You don't need to drive significantly slower than others, just slightly slower so a new gap appears in front of you.
1.) welfare state
2.) some people refuse to integrate like Expats using only English.
Deep dive tutorial for learning in a forward pass [1]

[1] https://amassivek.github.io/sigprop
Why an engineer chose to build his mobile app with NoCode
You're describing the exception situation that has led to many drivers to install dashcams.
Uptime is kinda moot measure.

If it had uptime of 2 days but only went down for a minute at a time that would not be a problem
Also 249.817 K
The lack of scale on temperatures throughout is remarkably frustrating. I am assuming Fahrenheit as the graphs indicate this but the content really should as well.
Does anyone know (or can speculate) why Nepal is ranked so low (worse than North Korea)?
Check out Compressorhead! They make this look more like "An engineer has built a couple of self playing instruments". Still pretty cool though.

Compressorhead video page: https://www.youtube.com/@RobocrossMachines/videos
Obviously, the Tesla FSD Autopilot made a big mistake, but didn't the driver react? If my car slows from 40 to 0 MPH in 5 Seconds, and there is no obstacle in front of me, I must assuredly would step on the accelerator.

Not that FSD Autopilot is what it's marketed as, but this is the responsibility of the driver and not the car.
Almost all of the issues mentioned would be solved by using quoted strings.
OP must have accidentally put in 10°F, which is -12°C.
Down to -20C, and even -25C:

* https://www.mitsubishielectric.ca/en/hvac/professionals/fs-s...

More advanced unit (primarily for hydronic heating) that goes down to -20F / -29C:

* https://www.spacepak.com/solstice-inverter-extreme
From the article and comments I don't understand - are they talking about backup (copy of data) or backup system (nuke your primary system, failover to backup system and just keep working) ?

I think it is a SYSTEM

> It has a backup, which officials switched to when problems with the main system emerged, according to the source.

> Officials ultimately found a corrupt file in the main NOTAM system, the source told CNN. A corrupt file was also found in the backup system.

Perhaps the backup system is just using data from main system which currently is compatible but won't be in the near future?

Still there should be data copy somewhere, right (with corrupt data...)?
> I guess a lot of it is because the APIs I’m calling are so badly designed.

Sort of, sounds like the problem is that you have a distributed monolith. If things are this tightly coupled they should just live in same process. If you even had just a regular monolith (which I don't recommend but it is much better than distributed monolith) you wouldn't have this particular problem. Of course another alternative is to redesign the system so that services are based on independent domain capabilities so that they have high cohesion and loose coupling.
TDD not really. Having tests help, writing them first is irrelevant
> Please just stop using PyYAML.

Why?
32-bit single-core, even.
I second that. And if people need to deal with YAML in Python, they should be using ruamel.yaml, which is a far superior library on just about every level: https://pypi.org/project/ruamel.yaml/
Rare earths aren't really that rare, so probably not. Everyone has lots of rare earths, the rare thing is an environmental policy that allows them to be mined economically.
Crockford probably didn't imagine the idiocy of creating YAML to replace the lack of comments in JSON.
Language aware is definitely important. But honestly I've usually found it easier to use a "real programming language" to generate the structures. You can read and write as normal. Then you can just serialize them to YAML at the end.

Helm is so bad. It has a `| quote` function that is almost always wrong. People use it to escape strings into YAML strings but it just adds quotes around the values. It doesn't actually escape to YAML. I had a surprising hard time convincing people that they should be using `| toJson` and ideally be doing it for every interpolation.

But really working with text is just an inconvenience here. You can imagine how much better everything would work if your base template was `console.log(JSON.stringify({ /* your config here */ }))`
Case here. No it isn't.

Every headset I've tried fits over my glasses. I've had several different frames over time as well.
On the contrary, the school system groups kids from the same neighbourhoods and the same age together. Some schools also by religion. Homeschooled kids tend to mix with a broader range of ages and geographic basis.
This is the problem with all comparisons between government programs and private action. Private players can skip the hard bits. Government must be universal.
Well, you should test your backups. But TDD is entirely unrelated to the problem aside from including "test" in the name
Because if you don't interact with people you can't learn how to interact with people. And this include interacting with people you don't like or which aren't so nice (but just that, not bullies).

The problem isn't schools. It's a bad treatment of social issues at schools (and in society) in many ways.

I mean how messed up is the US that police presence at schools is normal in many areas (and I don't mean just guarding the gate but presence _in_ the schools).
If this is the case, wouldn't cyberbullying have increased during the pandemic since kids would have been on devices more often?
> We have a nice oil burner heating a hydronic system that does a great job at that point.

A primarily for hydronic heating unit that goes down to -20F / -29C:

* https://www.spacepak.com/solstice-inverter-extreme
I guess the point is you could just stick the results of each step that is currently a CTE into #table as separate queries, and you're only doing the work once to step through the stages?

From a debug point of view that feels more convenient to _me_.
If you think about it, the only scenario where that is actually useful is the corporate workplace.

Homeschooling children will interact with people in the context of their parents in all places in society their parents visit, and there are a wealth of groups and activities for the kids to join and interact with. Even better, the parents often have more direct insight into their childrens' interactions with others and can advise and support as necessary.

The whole 'needs socialising' claim is based on flawed assumptions, lest we assume all kids at school benefit socially from the environments they are in at school, which seems... optimistic.

Also, where else in society do you need to be measured in competence against other random local individuals of the exact same age?
I assume it is for economic reasons. Unless property taxes shoot up, how would you support that?
This reminds me of a certain architect at my last shop who invented a DSL on top of his Python superapp. He expected all projects to go through his superapp. The DSL was configured in YAML. The YAML was often so dense he recommended devs use Jinja to generate the YAML.

This meant debug was hell, plus it wasn't always clear if what you were trying to do was even supported / if not why & what needed to be changed. This was because you were now 3 levels of abstraction away from the Python code that was actually executing.

Every time a dev took on a new project they had to jump on a call with architect or right hand man to figure out if what they were trying to do was going to be possible.

It escalated into the architect demanding to know a sprint in advance any task devs were trying to do, in a review session, so he could explain if it was possible or not and try to triage in his DSL..
Also f'ing freezing.
This mirrors what I am seeing as well. Lazy writing that produces a reaction of “why did they even bother making this movie?” despite the good actors and videography. Is it because good writers are difficult to find or, as with the actors, are the writers being constrained as well either by the streaming business model or poor taste in story selection by the streaming execs? The emergence of generative AI might make this even worse, as it’s only a matter of time till these are used to churn out scripts; although some of these scripts are so bad, maybe it has already started?

Anyway, I find myself terminating movies earlier and more readily than in the past due to the higher frequency of disappointing dialogue and story lines along with the fear of wasting my time. My response is cancelling streaming subscriptions for a year or so and then resubscribing for a few months in hopes that a few decent new pieces of content were created.
except it's everyone else that has to maintain the code that pays the price
We ran into a problem where AutoMapper changed it's approach between versions for a way we were using it. We then got to spend the next few weeks updating our code because of it. I'm pretty sure that all the time we "saved" by using it was lost.
I find go test writing a misery because of the style golang recommends and our company has decoded is to be enforced. You have a list of data values and expected results in an array and then a test at the bottom that applies these array items to the function you're testing - sounds great right? No - because often the only way to get all the variations you need in the test is to have helper functions that are referenced in the array to setup the situations you want. i.e. it ends up being far harder to add a new and slightly different test to this array than to just write a new test - and that's not supposed to be allowed.
Automapper generates all mappings at runtime with reflection.
Mapperly in contrast uses roslyn based source generators and generates all mapping code at compile time. This leads to improved runtime performance with less allocations [1]. Since no reflection is used at runtime, the generated code is completely trimming save and AOT friendly.

[1] https://github.com/mjebrahimi/Benchmark.netCoreMappers
The real brain drain started when people were finally allowed to flee the paradise and what was left of it. It wasn't their fault your apparatchiks and yesterday's party members, the real owners of everything, started to carve up their posessions calling themselves capitalists this time. Before the fall only establishment members could flee (illegally) and jews (since the 1970s).
Please someone tell me again how they don't understand statistics. Suicide is still extremely rare even with schooling. Child abuse is actually more common in homeschool environments, which you apparently wish to ignore. It can be true that homeschooling doesn't properly socialize children AND that there's an astronomically small increased risk of suicide from school attendance.
Eh, let them live with their "smart" code:

What happens when they leave it for a few months and come back and forget how everything works?

When a client encounters an issue in the field and they have to debug it with "It doesn't work, yo." as a problem description?

When a coworker tries to modify it and breaks everything because they can't figure out how it works and there are no decent tests?

Eventually, they'll come around :) Or maybe there is no saving some people and they should stick to R&D...
I love these mechanical mechanisms animations: https://mechamechanisms.com/
It’s more that without backpropagation, you no longer need to store your forward activations across many layers to compute the backwards pass which usually is dependent on a forward pass. When a network is hundreds of layers, and batches are very large, the forwards and backwards accumulations add up in terms of memory required.

Communication across GPUs doesn’t solve this but instead allows to have either many models running in parallel on different GPUs to increase Barch size or to share many layers across GPUs to increase model size. Quick communication is critical to maintain training speeds that aren’t astronomical
Russian passport in the top 50?

Please.
For managing configs of ML experiments (where each experiment can override a base config, and "variant" configs can further override the experiment config, etc), Hydra + Yaml + OmegaConf is really nice.

https://hydra.cc/

I admit I don't fully understand all the advanced options in Hydra, but the basic usage is already very useful. A nice guide is here:

https://florianwilhelm.info/2022/01/configuration_via_yaml_a...
So. "fundamentally broken" is now code for "some aspects of it displease me"?