skysight-inc/HackerNews huggingface dataset:
Looks pretty good! Even though I've written far too many JSON parsers already in my career, it's really nice to have a reference for how to think about making a reasonable, fast JSON parser, going through each step individually.

That said, I will say one thing: you don't really need to have an explicit tokenizer for JSON. You can get rid of the concept of tokens and integrate parsing and tokenization entirely. This is what I usually do since it makes everything simpler. This is a lot harder to do with something like the rest of ECMAscript since in something like ECMAscript you wind up needing look-ahead (sometimes arbitrarily large look-ahead... consider arrow functions: it's mostly a subset of the grammar of a parenthesized expression. Comma is an operator, and for default values, equal is an operator. It isn't until the => does or does not appear that you know for sure!)
MSDN is enough to get several.
If performance is important why would you keep large datasets in JSON format?
Someone's social credit score went negative, for no comprehensible reason.
White vinegar does a better job deglazing than hot water.
Thanks for this, quite useful.

There's also more discussion in [1], linked from there, which contains perspective from real memory model experts. I think it's fair to say they're skeptical of the proposal. In particular, they've debunked the SC-DRF claim, which seemed fishy to me, but I didn't want to say anything before gathering more evidence.

[1]: https://discourse.llvm.org/t/rfc-strengthen-relaxed-atomics-...
Interesting. I'd never used an android before, and recently got a Pixel 7a on which I am running lineageos. Haven't found any rough edges other than that the home screen sometimes hangs fixed by turning the screen off and on again which takes less than 5s. What rough edges did you encounter?
Undo in assets:clobber What You Do in assets:precompile
And yet total residential usage of water is only 10% California’s residential / agricultural / industrial water usage. Agriculture is 80%.
No, because they're not loaded.

Firefox doesn't load tabs after a restart until you click on them, and I use a tab unloader so tabs also get unloaded after a few hours (mentioned in my original comment that started this chain).

It's currently only using about 3% CPU.
No reason to avoid adding to the scope and complexity of that planning, then?
The list of things that become toxic once you burn them is a very long one
Accesibility is certainly not where it needs to be for our metro, and elevators at every station is long overdue.

That said, the STM _has_ been installing elevators, and currently 25 stations have elevators, which is a lot more than even a few years ago [0]. Five additional stations are under construction [1].

[0] https://www.stm.info/en/elevatoraccess

[1] https://www.stm.info/en/about/major_projects/major-metro-pro...
It looks like a PHP tool: https://plugins.jetbrains.com/plugin/7622-php-inspections-ea...
> Once a file (and its size + hash) is tagged for deletion, that file has lost the war.

While I do deduplication with a Perl script and hashes, I don't use a DB, which is a nice idea to add.

But: how do you make sure that the last remaining original doesn't "loose the war" ...?
>if you just made it for everybody, it would no longer be a club with an underground image.

It is clearly not underground because everybody knows about it. It only achieves the "image" through arbitrary discrimination. That is the least punk as you can get.

None of what you said makes Berghain great goes away by letting more people experience it. The sound system and DJs will still be there.

I guarantee if Berghain stopped trying to be techno Mecca, the riff raff would lose interest, and you wouldn't need the picky bouncers. There's a particular club I go to in London that this works perfectly well for.
Your blog is deeply moving, thank you for posting the link. When my time comes, I hope I accept it with the equanimity and grace you display.
You might like <https://www.frontiersin.org/articles/10.3389/frspt.2023.1197...>. Same thruster, but scaled down for a trip to Mars and back. Still not very detailed, but not nearly as vague.
Starfield companions would've frown upon this solution.

More seriously though: 10 years is a long time, this is super interesting but one would wonder if in such time other limiting dengue factors might've arose.
Would they do the same if it didn't involve a delicious and commercially-interesting fish?
Yes, it is. First, how would you know that LazyVim is the fast and easy one?

Second, it's not fast and easy even with LazyVim, let's start with the basics like keymap:

map({ "n", "x" }, "j", "v:count == 0 ? 'gj' : 'j'", { expr = true, silent = true })

map("n", "<C-h>", "<C-w>h", { desc = "Go to left window", remap = true })

To understand this (and to adjust to your liking) you kind of have to learn the language you're not going to use ('gj' or <C-w>h) instead of using something easily readable like ["go","window","left"], or instead of actually pressing C-w to insert <C-w> like many (mostly GUI) apps allow

Then the time consuming part: it doesn't make it easy to resolve conlficts which inevitably arise when doing many rebinds. Also, it'd be very time consuming to learn and reference that unused binding language

Then the help is rather verbose and not intuitive (see my parent comment) (don't remember if help uses default keybinds or actual ones

Then it relies on a very barebones and not very popular language (though miles better than vimscript)

Then there are a gazillion of other things which make the perception reflect the reality pretty well
Ah, good to know! Hadn't really looked too far into component render batching, but I'm glad there are efforts underway!

I just meant that once I was rendering out each component without having to have it's parent know about its sub-components, I didn't have much use for global contexts or passing state to a component, itself. Auto-re-rendering isn't as compelling as just setting whatever data on the attribute change, or via a child element insertion/removal. Child element maintenance requires a lookup, instead of just re-rendering with the new state, but the DOM is really good at querying, so you can just look them up.

And so, once you remove auto-re-rendering (first render is still arcane, but it's still a pretty simple code snippet to accommodate templating), and state-based re-render triggering, there's not a lot that is added to the web component that isn't just a "different" way to do it, instead of demonstrably "better".

Of course, everyone's mileage may vary! Just my two cents after working with them for a few years. And my work has pushed me toward a "simpler is better" approach, which isn't universal. For people trying to make very complex web components that can benefit from batching tree renders, no amount of breakup will help (and my assumption is that it will actually hurt a lot? Web Components don't feel "cheap" as far as instantiation goes). So it's nice to have people working on these kinds of things so that we can one day get a drop in DAW web-component, or a performant "spread-sheet" component.
I know many people (as I understand it most of asia who use rice cookers) keep rice in the rice cooker "warm" but for me, that wasn't a requirement so I didn't feel like I was losing out. It's also been great to cook many other things in, which a rice cooker can do also, but thats more a "hack" than designed to.

I take the rice out, immediately put it in a container to trap the any moisture. When I reheat, it's great.
Or just don't. Lockless algorithms are hard enough with explicit and clear barrier operations. The idea that somehow empowering optimizers to further confuse things is a feature and not a bug is just completely bewildering to me. Leave the clever optimization to the sequential code and leave the lockless work explicit. Please.
I would avoid any rice grown in the United States if you’re concerned about arsenic levels.

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1892142/
Recruiter perspective - kill 2 birds with 1 stone:

1. Of course, education that you find useful, interesting, and fun.

2. Education that also best "signals" knowledge useful for future employment.

As the past year+ has shown us, you never know when you'll suddenly find yourself in need of a job. So keep in mind your future and consider education that "sells" well.

For example: fill in "perceived" gaps that future employers might miss in this world of impersonal resume keyword scans or LinkedIn talent searches.

A. Based on the background you shared, it sounds like a lack of CS degree hasn't hampered your career. But it'd be great to not only beef up your CS knowledge, but show it. So one day an employer is comparing you to another Engineer with similar skills, but lack of CS degree... except you have a CS-related Udemy "Nanodegree" or Coursera courses under your belt. Your knowledge plus interest in relevant continuing ed will give you an edge.

B. If you like startups, knowledge to make you more well-rounded (aka generalist/full stack) would be useful. Consider courses in areas like Frontend development, Orchestration, Big Data.

C. "Hot topics" that have staying power. Between 2019 - 2021, it seems like everybody and their mother had the Self-Driving Nanodegree. Looking back, maybe a broader pursuit like Computer Vision courses (which still touch upon areas like SLAM) would have been more beneficial. Nowadays, maybe learning more about NLP (which will touch upon LLM) would be a good option.

And be sure to make this visible, e.g. LinkedIn profile.
That sounds stressful. Just an FYI for your next trip, every metro map has a little symbol indicating whether a station has an elevator.
This isn't what Fossil does.

Fossil lets you synchronize artifacts both ways, so you can clone a repo, participate in discussions when on a plane, write some replies, connect back to the internet and sync them back up to the server.

When your server goes down, you don't lose anything. There's no need to remember to back up your issues every day, every time you clone the repo, you also clone its tickets, forum, wiki etc.
This brought to mind a cute way to think about the Foucault Pendulum.

The idea is to select a given latitude on Earth, and then imagine a cone that "just fits" that latitude, in the sense that it is tangent to the earth all the way around at that latitude. Draw a line all the way around the cone at the given latitude. Then imagine using a pair of scissors to cut the cone vertically up to its apex, and flattening it out to make a circle that is missing a pie slice.

A single full rotation of the earth would be equivalent to "driving a car" from one edge of the pie slice all the way around the latitude line to the other edge of the pie slice. At the end of the trip, the car will be pointing in a different direction from the one it started, for every latitude except the poles and the equator.

The angular rotation of the car from the start to the end of its trip is the amount a Foucault pendulum would rotate in 24 celestial hours at a given latitude on Earth.
Japan is the model because they don't rely on continual immigration.
Most Western countries react to young people saying they cannot afford to have kids by bringing in immigrants. Not reducing the cost of housing or raising a family. Japan doesn't just import people to solve the affordability problem and that's why they're the model. Unlike Britain, Canada, Sweden or the US
Locking up SBF was a step in the right direction. Now do the rest of the energy wasting Bitcoin shills!
That is nice and often gives more than one month's notice.

What is really not nice is the obession with pruning the versions for each package. For a specific package, there is no serious issue with keeping several old versions hanging around in the package tree. By default the package manager understands that and the user doesn't see them. But where there is some compatibility or build issue, the user would have the option of masking the latest and keep going on an earlier version: it would still build, usually with no extra effort. It would rebuild fast if you have a build cache. You could downgrade easily if you discover an issue weeks later.

But no: most maintainers where that matters delete the previous version as soon as the new one is half in. Not a helpful obsession.
I wonder how that C$119M per Km compares to other country's. Anyone know?
You could do the same with credit card and earn miles or reward points on top
Thank you! I had the "How to Build..." book as a kid and never could remember enough about it to find it again.
I used jQuery in a few personal projects and it was very useful. It was 10 - 15 years ago, so I am sure there are better tools now, but for a hobbyist it was great.
> Why doesn't it know when it's so consistent every time?

They had a feature (that I believe it's just integrated into every model now) labeled as "neuro fuzzy", decades before the neutral networks boom. I believe it's really just describing hysteresis. So it's doing things based on feedback from whatever sensors they have, but there's no learning from run to run (based on how you actually use the thing).

I also hate its lack of estimated times.
DC banned gas blowers. There is one dude left in the neighborhood but everyone else has converted in the neighborhood. It's fantastic.

Especially working from home, it just felt like there were only brief intermissions of relative quiet. It's wild how you can hear that 2 stroke whine from blocks and blocks away.

Now, it's just nice out. (Also a lot less air pollution to boot!) Your city can do it to! We also recently banned right turn on red, another recent submission; https://news.ycombinator.com/item?id=38147864
That’s still not as bad as having to spell referrer wrong in http headers where it’s spelled “referer”... which is incorrect for every flavo(u)r of English.
See the History of a Method with Git log -L
"Renewable" isn't the best word for wind and solar, better would be "use-it-or-lose-it", either you harvest it or it dissipates into useless low grade heat. Using more of it doesn't deplete the supply of it.

Solar energy (and thus wind assuming otherwise constant environmental conditions) is only going to get more plentiful for next 5 billion years...
5 big travel lessons and one 'mistake' from 50 years of Lonely Planet
Thanks for the advice!
I wanted to buy a Zojirushi, but teflon is a big no-no for me.
What are the options for a rice cooker without teflon/aluminum?
> we know it is carcinogenic

Do we? PFOA is "possibly carcinogenic" but they've stopped using it when making teflon.
Sorry to hear that happened to you.

But surely that that's not something that generally happens in any frequency that companies should take measures for, any more so than any other freak occurence.
https://archive.ph/W2Q43
The keyword everyone's thinking of is "all-metal hotend" - not "Bowden tube".
Right now I'm building a vscode plugin that renders a webpage directly in the editor. I'm absolutely sure that the vim/neovim proponents are right about how much faster you can be with vim motions, but it'll never match the versatility of vscode primarily because it's built on top of web technologies.
What is Glamorous Toolkit v1.0?
My native language (and I imagine many others) didn't have any localized version of Word until the late 90s and I (and I imagine many others, even people who didn't speak English at all) got used to using English words like "Save", "Italic", "bullets" etc.
While they are aggressive, it is optional and you are trying to avoid their revenue source. So there's reason to be so picky.

I just fast-forward or the the sponsorship segments out if they are too annoying.
The project has been donated - there are some leftover references to the enterprise offering, but all features have been open sourced
One thing I didn't appreciate until recently is how big Britain's EEZ is. If floating wind turbines can be made practical, there is huge opportunity not just for energy self-sufficiency, but for export too.

P.S. even if the numbers have been superseded, MacKay's original book is still worth reading because it's so fantastically clear in how it lays out the basis for estimation.
> I'm starting to wonder if there's an unconscious death cult in the developed world that fetishizes planetary doom

No. It is just plain propaganda. People who are afraid are much easier to manipulate. That's all.
Yeah, this is nice. I bet something like this could easily be brought to systems like Arch/Pacman and NixOS/Nix if someone wanted to champion coming up with an implementation for those systems.

(Actually, this is definitely doable on Nix, since there are mechanisms like "insecure" packages, but 1. I dunno if there's any for this situation (block package without explicit confirmation because it's not maintained) 2. I don't think there's any policy for this, but it would be nice if there was at least a procedure for people who wanted this kind of deprecation. It's also a bit different on Nix since it is not a rolling release distribution.)
gradtree is cool! thanks for the share!
Yes, I'm aware. I suspect the users who contribute tend to fall into the category of "The host saying 'and now a word from our sponsor' or explaining that 'today we are using product X so don't be surprised when the video is different' is part of the sponsorship" because I expect that people who contribute self select into people who are very anti-anything sponsor related ... I prefer having that left in, so that the sudden cut is at least expected.

My issue is less with the tool and more with the user contributions. But until there are alternative sources for sponsorblock that fit my preferences, it seems like the options are "don't use it at all" or "use it and be frustrated from time to time". I don't really care who is at fault, I'm not trying to point fingers, I'm just saying that I understand where NewPipe is coming from. Not everyone has to agree on whether all sponsor spots are good or bad.
Placenta proteins are apparently a left over from ancient viruses. They aren't killing machines, they are a data sharing feature in a very complex system. I love viruses.
The only requirement is TPM. If you burn the ISO to USB using Rufus, it disables the requirement and it works just fine.
Show HN: RAGTheDocs, one-click deploy RAG for any readthedocs website
To deploy your own, go to the huggingface space and point to your own library: https://huggingface.co/spaces/jerpint/RAGTheDocs

It uses OpenAI embeddings and ChatGPT under the hood. Source code can be found here: https://github.com/jerpint/RAGTheDocs
Thanks for the link. I don’t agree that the statements you linked amount to a real option, since the offer seems to have been informal and quite encumbered compared with the alternative of using an actual standard. But it’s fair to say that the history is not as clear cut as I implied.
Left all backups at a remote storage facility. Remote storage facility called me one day and said all of your hardware and media has been lost, except for this one [insert oldest most worthless computer of the bunch]. Cue me raging, cursing out this storage facility, threatening to never communicate with them ever again. Finally accepted the fault lied within me. Up until yesterday, I only had redundant storage but no true backups. So I purchased an LTO-5 and now I have two backup sets onsite and a third offsite at my colocation facility.

In this story the remote storage facility was my mom's house shortly before the GFC. The hardware were varying PS/2 computers from 286 to 486s with hard drives of zip files of my QBASIC, TurboPascal, Delphi, and VisualBasic code. The only hardware saved was our first computer, an 8088. All because she didn't want the clutter in the house anymore. No contact, no chance to retrieve said wares.. just poof gone. Gone were the Z80 ASM files of my rendition of PunchOut for the Ti-83+. Can't reference my old writings that I saved in various TXT files on the gazillion 3.5" floppy disks I kept in an old laundry basket. 5.25" floppies of DOS installs, random games, and an ancient version of SCO Unix. Gone.

Everyone learns the hard way.
Word is a tool, and any tool we use changes the way we see the world and interact with it. Hammer –> nails and all that.

I'd say the article missed the mark by focusing on features, especially spellcheck/autocorrect.

It's like some sort of cognitive blindness: I mean, the article has a photo with typists at the office and yet it competely ignores the transformation that an engine/platform – a computer – with a tool – a word processor – had on the way language is used in business, leisure, creative and, of course, language work (anything from print or editing to business memos).

A hammer can have a flavor, but it's still a hammer. This article focuses on the objectionable and weak flavor of MS Word while ignoring the wider implications of a digital word processor.
The primary constraint limiting the speed at which we move away from fossil fuels is cost. Investing in more expensive alternatives like nuclear increases the risk of the threat becoming existential, and the damage it does if it doesn't become existential, compared to investing in cheaper alternatives like solar and wind.

It is not a case of "we should do everything" because we can't afford to do everything. If we could afford to do everything we could easily do a small subset of everything and solve the problem.
I think this sort of condescending attitude is what makes products hard to use. I did in fact look all of this up, but that doesn't make the rice maker easy to use.

(Edit)

Believe it or not, yes, I can RTFM too (and did -- it still wasn't very clear, and neither were the online videos). But that's not really the point. I was more curious about why a company that clearly values the design behind its products would make these design tradeoffs. Is it the result of careful user research? Japanese cultural traditions? Thoughtlessness (unlikely?). Etc.

I find Japanese automobile dashboards easier to use than most American ones, for example. Japanese watches hellish to use. Sony anything pretty complicated. Is it a model/product/company/cultural/other factor?

IMO the more interesting question here isn't "How to teach HN dumbass to use a rice cooker" but "Why does this famous Japanese rice cooker company design its interface this particular way?"
I wonder if it is cheaper to buy every disabled person an Uber pass than refit large subway systems to make them accessible.
>If so, it's the sign you have a low trust society in a more general sense.

Isn't that kind of orthogonal to the question? I can envision both high or low trust societies that could have problems with required 3rd parties attached to personal property.

Even the most well intentioned and highly trusted 3rd party is still susceptible to malicious attacks, or just incompetence or plain old accidents.
> Who is the enemy? Who is the worst generation and who is the best?

You don't watch the news ? Don't you ? /s
I guess you don't have what it takes to be a climate activist!
That's not relevant since it's too small a use case when it comes to learning, but still there are options:

1. by using a serial image protocol

2. by drawing the picture in text
„Computers will understand sarcasm before Americans do.“

- Geoffrey Hinton

https://www.brainyquote.com/quotes/geoffrey_hinton_875276
If you haven’t read the book “Sustainability without the hot air” by David MacKay then I strongly recommend it. He makes some assumptions that may not stand the test of time but overall it’s well reasoned and he explains the maths and logic well.

His passing is a real loss to UK science.

I got to see him speak once, very engaging and his passion was clear.
The only requirement on Windows 11 is TPM. You just burn your ISO to USB using Rufus, and it disables the check.