skysight-inc/HackerNews huggingface dataset:
What does it mean “they’re not meant for it?” I have money on it, some site accepts the card, it works, it worked. The limitation you’re suggesting is purely theoretical.

In my specific case, I needed cash to buy a used vehicle in a country where not everyone has a bank account, so your preconception about money may not apply here.

Wire transfers across borders are expensive and slow anyway. Remitly was available within minutes and at 0 cost (first transfer is free).
Recent? The meme basically started with this article: https://www.joelonsoftware.com/2000/04/06/things-you-should-... - note the date in the URL.
You mean I get scoped every few years and it’s not even a thing??!
That’s very dependent of your home network setup. Many consumer grade routers use dnsmasq behind the scenes which handles that for you by default. Once you get out of the consumer grade aio routers it’s much less likely to work out of the box.
There are absolute huge numbers of very tiny run magazines that simply no longer exist in any form, and the people who even knew about them may be old or dead.

Think "college-adjacent" run off the mimeograph machine late at night kind of thing. They could have run for 4 years or more, and basically be forgotten.

Now and then you hear of a famous author's work being rediscovered in one, from something they wrote in college for one of those magazines.
This makes me want to never use your service. I already don't trust the picture and name reviews on websites like this, but when you're new and your site already has this boilerplate of lies, I now know everything I need to know about it.
>> The benefit of print media is its forced-decentralization and stand-alone nature. It can survive for 100+ years on a shelf, and I don't think any digital data format could match that.

> MDisc definitely can, if its claims are to be believed. Maybe you can find some specialized tape too?

1) I don't think they actually make real M-Discs anymore (the DVDs). There are some M-Disc branded BD-Rs, but I don't think those use any different technology than standard BD-Rs.

2) They're not stand-alone, and by that I mean they need a player or they're unreadable. IMHO, it's unlikely there will be many working DVD/Blu-ray players in 100 years, and very unlikely there will be any players for "some specialized tape."

I've been working a bit with VHS recently, and it's eye opening to see a once ubiquitous format start to drift into unreadability (it's not there yet, but a lot of the specialized equipment needed to do a good job is becoming expensive, hard-to-find, and breaking down).
> The only odd thing was their phone number was GV and didn't match the location of their address.

How is that even remotely odd? Ever since cell phones became popular the phone area code no longer means anything. People tend to have the area code of wherever they were when they got that phone, which is often many location moves in the past.
If you're looking for a good read on why large scale rewrites are unlikely to succeed go read Fred Brooks "Second System Effect" essay (and go and read the whole book anyway): https://archive.org/details/mythicalmanmonth00broo/page/52/m...

Large scale rewrites are really good at promoting the people that had the idea and "delivered" the rewrite with one or two bogus metrics improved and leaving a dumpster fire that those that will have to maintain it in the long run will pay the actual price for.

Only get involved in large scale rewrites if you're the ideator that will be blessed with the laurels of the first delivery, if you're going to own the shitshow later, run away while you can.
that last sentence doesn't make sense to me - as a leader I enjoy succeeding rather than failing so if a rewrite is what's necessary then that's the fun option.

rewrites happen when changing requirements bent your code past its limit. they're natural and necessary and resisting one on principle is way less fun than the alternative.
PostgreSQL: Effective_io_concurrency benchmarked (2019)
Colonoscopies come with potential for complications.

There are actually a number of companies which have either released or plan to release non-invasive colorectal cancer screening based on blood dna sequencing.

GRAIL, Freenome, and Guardant all have tests out or coming down the pipeline.
>The kilometer was based on 1/10000 the distance between the poles and the equator.

And that measurement they got was ultimately off, which is why the meter became (until its later redefinition), for all intents and purposes, "the length of some arbitrary metal bar".

Clearly, "some fragment of roughly how large the Earth is" is a base unit designed first and foremost for human-scale measurements, and definitely not by self-fellating academics that would never seriously have to use the thing (and whose work does not, by and large, depend on the base unit used; Americans use thousandths-of-an-inch for everything under 1/64th). Fortunately, metric time was too weird even for the French.

>but by measurements everyone on the planet could reproduce using the sun and a bit of water, at least to a very acceptable approximation.

By contrast, the "foot", which is literally named after the device used to approximate it. The median human being has two of these. In fairness, you usually have to be taught which part of one's body approximates the inch and is thus harder to do.

>join the metric system

The metric system was initially imposed at gunpoint by the French upon most European nations in the first place due to the French going batshit insane just before 1800 and conquering most of the Continent. The Russians, being a nation that rather famously was not conquered by the French during that time, would retain Arshins until Communism (at which point the Soviets would impose the metric system, also at gunpoint- kind of sensing a theme here); the English would retain the Imperial system even longer than that.

It's also why people living in the only nation that really has a choice all measure distance and height in (square) feet, inches, and kilometers (per hour), human weight in pounds (and very rarely ounces), most other weight in grams and kilograms, non-cooking-related volume in liters, and non-cooking-related temperature in celsius.

It would have been objectively better from a usability to have just set '1 meter = 1 foot' and call it a day- could have even been (one of) the French foot, too. But no, just had to fuck it up for everyone who actually has to use it because "we know better".
The problem with medical interventions, especially tests, is that they sometimes work. There will always be success stories.

The big question is: are those success stories worth it, and are there other paths to those same success stories.
From reading "Quantum-Limited Atomic Receiver in the Electrically Small Regime" (PDF) [1], it seems there are 3 main advantages to Rydberg sensors, wide frequency rage (DC to Ghz), very small sampling volume, and non-interaction with the RF fields.

The wide frequency range means that you can use the same sensor for a wide variety of measurements, calibrating it down near (or at) DC, and later using it to make accurate measurements of RF or Microwave signals.

The small sampling volume means that you can probe at resolutions far smaller that the wavelength of the frequencies being measured, so you can measure the field strength in 3d (with appropriate mechanical scanning hardware) of antennas and other gear, something you can't do normally, because normal antennas are much larger than a wavelength.

The isolation means you can effectively probe almost any system and without disruption. Unlike measuring voltages with a voltmeter, there are literally no conductive elements that would reflect or refract RF signals, short out dc signals, or induce currents from present magnetic fields.

[1] https://arxiv.org/pdf/1805.09808.pdf
What you describe sounds like an immigrant, not an expat.
This made my day:

The implementation is just enough to run very small workloads:

* Full GPT2 small (124M parameters) model including byte pair encoding, embeddings, multi-headed attention, and multi-layer perceptron stages

* Inference/forward pass only (no training)

* Context is limited to 10 tokens in length

* 10 characters per word limit

* Zero temperature output only

This sheet is very big. Unfortunately, it is not unusual for Excel to lock up while using this spreadsheet. It is highly recommended to use the manual calculation mode in Excel.

from: https://spreadsheets-are-all-you-need.ai/
I’m curious what you think the ED outcome difference is between the best hospital in your city, and any random suburban one, for generally common emergencies.

Not trying to snark, honest question.
NXP and STM make NFC<->I2C EEPROM chips that are <$1 which can easily be used to transmit data from a mobile device directly into the target.

https://www.nxp.com/products/rfid-nfc/nfc-hf/connected-nfc-t...

https://www.st.com/en/nfc/st25dv-i2c-series-dynamic-nfc-tags...
> First you need to determine the requirements. All of them. In excruciating detail.

Funny, I am currently in charge of a rewrite that did exactly the opposite (start with an MVP, do agile increments), and just recently went into production with great success.

It was the third attempt to replace a 25 year old web app written in C. The previous attempts both failed exactly because they tried to "determine the requirements in excruciating detail" - they never got past that stage.
As far as I know, countries outside the USA that recommend it are Switzerland, Germany, and Austria: https://publichealthreviews.biomedcentral.com/articles/10.11...
This is actually a nice summary of how a clinical trial is more than just "did it have a positive or negative result?".

Every single trial introduces some bias through the way it's designed. Good trials try to minimize bias or at least limit it to things we know don't introduce bias.

The article does a nice job at digging into the nuances of the trial design and how it may influence (or not influence) the results.

That's why the "reference wars" you see on HN are so pointless. It's easy to just find a paper that supports your position. But trials are of varying quality.

What you see in this article is what normally happens with most major trials - results get discussed, challenged, discussed some more. After a few months doctors finally settle on the main takeaways. Sometimes it takes years.
Enabling power on after power loss is "just" writing a register value to the chipset, so it's viable to have Linux do that during boot.
I was going to post the same thing – Poland launched a nationwide campaign two years ago to get all people over 50 years old (above 40 if they had family history) in for a colonoscopy. However, the linked article is working with a European study done a decade ago (EDIT: I’m wrong about that). There may have once been greater differences between American and European approaches.
Hi. This is really cool. I tried your example, and it rendered top to bottom instead of left to right (as in the directions).

The very first example: x -> y

I rendered the svg, and then loaded ONLY the svg into a browser window.

I then looked through the whole of the document and tried to find how to align the output... and couldn't find out how.

Since the linked instructional was diverging from real life results, I stopped using it. :(

If you know how to fix it or could update the directions to ensure reliable output to the directions... that would go a long way for visitors like myself :)

Edit: did a google search for "d2lang connection left to right" and ended up here: https://d2lang.com/tour/layouts/

which may be helpful to you for the question I surfaced as it isn't linked in your overview docs :)
Yes, I was skimming up and down the article to find out why they didn't just take a photo,
Indians Are Entering the U.S. Illegally in Record Numbers
Xcode development seems to be very driven by the need to have things to demo at WWDC each year.
What a nice 169 second run of my gravity-twisting game Future Bike can look like [video]
Playable in the browser on both phones and keyboards at http://doomlaser.itch.io/bike
Data does not seem to indicate better survival odds so whats the point?
Baymard (https://baymard.com/blog) and Nielsen Norman Group (https://www.nngroup.com/articles/) might have the kind of research that you are looking for.
Funny. I liked the TypeScript being added and then removed in the TODO.

I've been working with the web since before JS and CSS existed, back in the cgi-bin days, and have somehow ended up still working with it to this day.

I used most of the pre-SPA frameworks, when everything was what is now being referred to as "SSR".

Then I was dragged (somewhat kicking, screaming, and muttering about 'kids these days') into the world of SPAs, except I ended up on the Angular side and have not really been on the React side.

I will say that I have been following along with this Next.js stuff and the other changes going on over in the React ecosystem, and I am left utterly confused while at the same time having an uneasy feeling about the whole thing.

It's not necessarily because we've seen all this before, it's more about "why now?", and then wondering about how badly this is going to be abused, because if it can be, it will be. I get it, people need SEO, FCP times need some help ... and ... well that's about what I came up with off the top of my head.

Have you ever seen a SQL statement that JOINs 20 tables in your a component, that uses a magic string to indicate that it is not your ordinary component? You will.

Naturally, almost anything can be used in ways it should not be. But when you are combining the dominant SPA framework, blurring the lines between the front and back ends, and employing a large amount of fairly complex magic behind the scenes to make it happen, I get the sense that bad things may be afoot.

I for the moment am content working with a different framework, it's been smooth sailing for a complex enterprise system. I'll see how the rest of this unfolds from afar.
Article doesn't actually answer the question? Certainly interesting information about the topic and efficacy, but it doesn't really explain how the current situation came about.

Why is my neighbor driving around on a donut? I could write 3000 words on the history of tires, the assorted trade offs of trunk storage vs spare diameter, the geographical distribution of potholes, etc., but none of that explains why the donut is there.
This looks super useful. It is a bit convoluted to setup WG/PiHole/Unbound/foo and link them all together. But, it is not tedious enough that I’d ever put in the time to make a whole UI to improve it. I’m glad someone did though, it’s these little things that you don’t realize you need :-)
> Last time I tried to setup LaTex on my mac I just gave up because it was too much work, this seems to be agreed upon a lot of other users too so I don’t feel alone on this, am I?

It seems like I am not part of those many users. On mac yoi can install the full texlive distribution with the default GUI using home brew easily.

brew install --cask mactex

Or if you just want the basic and without any applications you can install basictex

brew install --cask basictex

Then you may use tlmgr to install tools/packages that you need.

Or you can do it using tex live utility (GUI) which can be installed easily

brew install --cask tex-live-utility
Six essentials for mainstream EV adoption [pdf]
The sad thing about the article is that skirts around mentioning the possibility that the American disease industry hates this trial because it will reduce their income.

The good thing about the article is that it has a colonoscopy joke that also involves (bonus for the HN crowd) Bayesians.
The nordicc trial was published last year. This is recent results, trials with 10 year followup take a long time to run.

https://www.nejm.org/doi/full/10.1056/NEJMoa2208375
I only use Prime on free trial, mainly because I don't purchase enough to justify the price. I've noted non Prime shipping is almost as fast as shipping, maybe a day later. I can wait.
this is why it’s important to always rewrite twice in rapid succession. keep 3rd if better than 1st.
I think by everyone they meant everyone involved in the contract being signed
Yet this is exactly what the article's argument amounts to. There is simply no way to feed 8B with cozy 'holistic regenerative' approaches to farming.

We're barely capable of doing it with the current rapacious mega-conglomerate chemical-soaked system. To go beyond it, and scale back the damage, we're going to need fermented foods, indoor fish races, synthetic juices/pulps/flours, proteins/meats, etc, etc. There's still a place for 'premium' food from local farms, etc. 'Cake' as you put it.
My doctor recommended Cologuard, a test of your stool sample for cancerous DNA, instead of a colonoscopy. I can't imagine taking a colonoscopy now.
fwiw {U+1F197 SQUARED OK} is capitalized “OK” in every emoji font I’ve ever seen
It’s failed if it doesn’t accomplish its stated goal. Don’t get lost in deconstructionism then declare all goals meaningless. It failed to create a stable state. That’s all.
ARM boards consume more and more power generation after generation so its probably be going parity power performance profile in the end. Also the key problem for ARM boards is piss poor Linux support beyond release so x86 always wins there
I’m an idiot. I thought those numbers were huge. Thanks for correcting me. Wish I could delete my post now.
Comparing Scholar or any other Elixir ML component is bizarre. Elixir has been around for many years and its ML ecosystem has only existed for the last few. Obviously Python, the most used ML ecosystem in the world, is going to be way more popular than Elixir.

ML isn’t even close to the primary use case of Elixir either. This is just a bizarre comparison.

Also, Scholar would be equivalent to Sklearn, not Numpy. Nx would be the Numpy equivalent. Scholar has literally only existed for 2 years.
There’s a lot of orgs out there that will do all of:

1. Never consider a rewrite / v2.

2. Never schedule refactoring work.

3. Not accept any refactoring work as part of feature work, because the refactoring is always deemed more risky (despite tests). “Let’s split this PR into feature and refactor.”

So my question to these orgs is: when are we supposed to clean up the hacks to ship yesterday’s features?
Doubling an idle power of 5 watts is 10 watts. Even at $0.25 kWh, that's the difference between ~$11 and ~$22 per year. That's not nothing but it's not really a big deal either if the advantages of being x86 apply to your situation.
Apologies, I mistook some of the ones I responded to with being ones I posted.

Here's a video from Minnesota timestamped to them talking about exactly this scenario in detail. Namely, yielding to all lanes of cross traffic: https://youtu.be/CEhNboz5GPk?si=LxdVQZx0MHrYhl8w&t=196

> With multi-lane roundabouts, it is important to stop for vehicles in all lanes of traffic. Wait until there is a gap in all lanes of traffic and then enter slowly. Never try to enter alongside cross traffic or assume any driver's intended path. One of of the most common mistakes people make when entering a roundabout is failing to yield to all lanes of traffic. Yield doesn't mean just slow down or merge. Yield means that you must wait until all traffic in the roundabout has cleared before proceeding. Make sure that no one is in either lane of the roundabout and then proceed.

The video also has a good overhead view that is better than most at showing the scale of the roundabout. The important thing to note here is that to enter the roundabout, you have to cross the lanes that are exiting, not merge into them. So you are yielding to all exiting lanes.
I got a letter from the government last year saying they wanted some of my poo, so I sent them some. The whole thing was weird, but much better than visiting a doctor.

I'm in Australia.
Yeah, people want readymade products. No patience
People trust only Big Businesses.
They dont become that way overnight.
Dont want to build anything from scratch.
Dont trust small businesses.
If I had a dollar everytime, I would already be rich.
This is what kills most businesses not some random competition.

However, rest assured, we are building it actively.
Have a vision for it in the future.

WE all have to start somewhere. :(((
Sun and Solaris weren't around back in COBOL's heydey (well maybe they were at the tail end of it) so that makes sense. COBOL is only really still popular on mainframes because a lot of core early buisness data processing code was written there in COBOL. So much in fact that it's basically impossible to manually rewrite (not to mention the performance hit if you rewrite it in something like Java which seems to be the "new COBOL" in terms of being super vanilla and business-y, or you use an automated rewriting tool which you might imagine is going to come out pretty nasty looking).

There is a big niche of hooking all of that stuff up with modern frontends and running it remotely via browser interface and maybe a Node server on a mainframe and that sort of thing. That is how you end up with projects like this. The author jokes about it being ready for production, but I'm not joking I have really seen some stuff not dissimilar from this running in production, but with it calling the IBM Enterprise COBOL compiler instead. Doesn't look like it's supported here but it could be modified trivially to run on a real mainframe, just change the name of the executable it's calling and handle the case of a different path format when given a path outside of the Unix file system (there is a Node library already that can handle this, or you can compile C code since weird path support is provided by C libraries as well and can be made into a native node extension).

A more interesting discussion might be had about dynamic linkage and how that works in mainframe COBOL environments and how it's different from C environments. And in particular how that all fits together with transaction monitor systems, which are like very primitive containers. The closest comparison would be AWS Lambda functions and other serverless abstractions. A lot of COBOL actually looks like serverless, with lots of small very modular programs that link and load each other dynamically, which is part of why there was a tendency to reject some aspects of structured programming. I've seen apps that use too much serverless that feel a lot like classic COBOL spaghetti code.

Anyways, that's my big bunch of stuff I know about COBOL, which is quite a lot but unfortunately have never had much opportunity to write it.
Trabant was the cardboard version of Zaporozhets [0] and the little brother of Wartburg [1].

Another Bulgarian jokes about Trabant:

- It is that it's the longest car in the world... if you take the smoke trail behind it.

- A truck was heavily and couldn't climb a hill. A Trabant stops and suggests to pull it over the hill. The Trabant keeps pulling making a huge cloud of smoke. At the top of the hill, the truck driver jokes: "See how much smoke you made!" And the Trabant driver responds: "Sorry, I forgot to release the hand brake."

[0]: https://en.wikipedia.org/wiki/ZAZ_Zaporozhets

[1]: https://en.wikipedia.org/wiki/Wartburg_(marque)
I love it (gpt4) for code. At least for Python and Typescript.

It doesn’t always get it perfect, but it gets a lot right. Having enough experience in the field makes it easy to know when it’s right or not. Then you either ask again with more context and information, or do it yourself.

Overall, it’s definitely increased my productivity.
I’ve been writing Elixir for years and I can’t even think of the last time I had a language server crash…

Plus, these days there are many alternate LSP implementations besides Elixir LS:

https://github.com/lexical-lsp/lexical

https://github.com/elixir-tools/next-ls