skysight-inc/HackerNews huggingface dataset:
Might just be to reduce the size of the index.

Not sure if they still do, but they used to map keywords to integer identifiers, instead of using the actual string value (string indices get very big). Page and Brin themselves explain it here[1]. I do the same in my search engine.

Problem is there are a lot of junk identifiers, so there's a point to reducing the scope by eliminating probable noise-keywords that are unlikely to ever be relevant to any search. UUIDs and hashes would probably fall into that scope, since they have a very large namespace that can very easily gunk up the lexicon with words that are never ever going to be relevant. You'd probably want to keep the word identifier 32 bits if you can get away with it, but maybe 64 bits for a global search engine like Google.

[1] http://infolab.stanford.edu/~backrub/google.html (section 4.2.4)
If the legacy code runs faster on modern hardware then the modern code, wouldn't that be a competitive advantage?
unlike a few years ago when everyone was trying their hardest 24/7? It's always been 80% slackers and 20% go getters.
The top Comment of [0] of the OP has a likely scenario: malware offers periodically searching for hashes of their malware to see if it's detected on the web, without having to submit it to virus scanning websites (as most online virus scan engines will automatically submit the executable for automated malware analysis).
You do. You own the disc. Or you own a copy of the virtual equivalent on a disk that you have. You also own the equipment serving as the runtime environment.

What you don’t own are the servers running the server side features or the software not on the disc you bought.
No, they were referring to trees in general. As in, this particular mountain range has existed since before the first tree evolved on earth.

Edit: My mistake, thought you were referring to the original “older than trees” comment.
> I see no harm in having history.

You want meaningful history, not unfiltered history.

The harm is that the history is no longer as useful if it's not curated -- whether that's for tracking down the origin of a bug, or just using it to remember what you did a few weeks ago.

It's easy to see the flaw in "keep everything" by taking the argument to its logical conclusion, which would be recording the history of every keystroke in your editor.

If you have false starts or alternate approaches that you gave up on but think you might still want, by all means save them, just not in "main."
Akro-Mils clear stackable 5" x 4" x 3" bins, standalone or hanging, optional dividers, https://www.amazon.com/gp/product/B01AADDBTI/

Sterilite clear stackable 13-5/8" x 8-1/4" x 4-7/8", https://www.homedepot.com/p/Sterilite-6-Qt-Storage-Box-16426...

Made in USA, both companies founded around 1940s.
A lot of things in computing are overwhelmingly stupid or assume everything will work as expected. I have experienced several data corruption events related to parity data being read incorrectly, not in ZFS, but with hardware and software raid controllers. In one case the hardware raid controller even had ECC memory, but its memory was overheating and thus introducing bad data into calculations when multi bit errors were not correctable. A similarly horrific error condition saw a controller confuse disk IDs in memory and start mirroring one drive to every other drive in the system.
Show HN: I made a cross-platform command-line music player called maestro
It is built to work on Windows, Mac, and Linux, and was tested thoroughly on my Mac and lightly on my friend's Windows. Unfortunately, no one I know uses Linux.

It works with WAV, MP3, FLAC, and Ogg Vorbis files.
Thank you for those helpful words
This is https://hackertyper.net/

I've used this site a few times to give a comically superhuman impression of my programming skills to parents, co-workers, and associate venture capitalists.

True Story: an associate VC, whom my co-founders and I were very friendly with, was touring my startup's office, and we put HackerTyper on everyone's computer, receptionist included. The look on the investor's face was worth the price of admission.
You didn't really explain anything. You waved your hands a bunch. You didn't address the fact that FreeBSD already accomplished this, then stopped maintaining it, you conveniently ignored the fact that Illumos had it even later than FreeBSD, mostly from scratch. Your tone was overly dismissive. Now you start calling me names. Grow up. I'm sorry I misunderstood your point of view, but you did sound exactly like certain FreeBSD community gatekeepers, and you're responding to a post about FreeBSD project decisions, so is it really so strange or "idiotic"?
Just saying the other services don't require $36 to be usable... but yeah its mostly free-ish.
Works on my machine, anecdotally; no Wayland, and an X window manager that hasn't been updated in a decade. Automatically resizes windows when I drag them to fit each monitor's DPI settings.
Hoo boy, there is a lot to unpack here.

- Lack of API/ABI stability in the kernel:

Chasing a moving target is no fun, exhausting even, but it would be a lot easier to just upstream the driver. The article fails to mention that AMD did just that and have vastly better UX than Nvidia.

- No GUI for multi user audio device sharing:

It sucks to have to use a terminal and read a manual so you can listen to music while your brother is on YouTube (somehow), but at least you may learn a useful skill.

- lack of support for some printers/scanners/peripherals:

Obviously things take time if the company offers no official support; volunteers only implement what they need to move on with their life. Generally if a printer is supported on macOS it should work on GNU/Linux due to sharing the underlying framework (CUPS).

- Power management:

While Linux have had its issues, things are vastly improved nowadays, to the point I suspect it's better than Windows on most hardware (but I have no personal experience).

- X.org/Wayland:

No excuses here. X.org is a hot mess of legacy garbage, and Wayland is not all it was hyped to be, with some equally brain-damaged design choices. I think once Wayland becomes the new normal transitioning to other display servers get easier due to simpler APIs than Xorg (I'm sorry for everyone who had to endure that in their lives).

- Fonts:

Still a mess, but improving rapidly.

- kernel difficult to debug:

Is Mach or NT really better in this area? At least Linux is completely open and has a gazillion knobs that you can tweak.

- Linux kernel code is low quality:

It's got some ugly interfaces and warts, like most hugely complex organically grown software projects, but that doesn't mean the code is poor quality.

- Low-memory conditions:

The kernel will still become unresponsive when running low on memory, but there are user-space workarounds for that (as mentioned in the article, I agree that earlyoom should be default).

- anti-cheat protections fail to work:

I personally do not want software making changes on my machine without my explicit consent. This is a feature IMO.

- Money, enthusiasm, motivation and responsibility:

I adore the diversity and creativity in FOSS. Many, perhaps most developers are doing it from passion instead of greedy interests. If you care about a particular project or feature, they will likely be happy to accept donations.

Hope this did not sound too condescending. I am grateful posts like these exists giving everyone a chance to straighten their priorities.
In law you assume something is innocent until proven guilty. You are suggesting guilty until proven innocent. That's the opposite of how criminal law works (in reasonable places).
Aesthetically too. If you've seen screenshots of Obra Dinn, you remember. It has such a distinctive look to it.
Two problems with it:

* Combinatorics is an unforgiving mistress. This is why we can't even brute force Go/Paduk. A combinatorial explosion of data and links between things. Works great in toy settings, but if you try to scale it up, even just to a single person's experience, it would quickly overwhelm the computing capabilities of the entire world.

* Very brittle compared to natural language, so many things that should be linked are not, even things that seem trivial to humans. If you solve this, you'll have the holy grail of knowledge management. The notorious difficulty of language translation is an example of this. It works great for the first 80% of things, but even improving that by 5% requires herculean effort.

I'm trying to do a very restricted subset of this by parsing natural languages to automatically look up words and group words by their dictionary forms. It feels like I'm already approaching the limits of what is possible, or at least what I'm capable of imagining.
Most alternatives mentioned here miss the main point of this, which is that it shows you 1 app that is equal to the size of x other apps
You literally just asserted

> For water you test for known contaminants like these forever chemicals and a host of others. Your question is insinuating that we don't know how to test for water safety, which is dishonest
Believing in God can trigger same reward regions of the brain as taking drugs
Each major advancement does not imply that more major advancements are necessarily coming.

Deep learning did turn out to be a very major advancement! And it's still bearing new fruit. But it does not at all imply that future advancement is inevitable or that advancement must continue at its present rate.

It's also worth considering that the domains where deep learning now excels are the same domains where it excelled when it first became popular (AlphaGo and AlphaFold are perhaps exceptions) and that all this advancement comes from hammering away at the same problem spaces for so many years, with huge budgets. Maybe the next area for advancement is something like combining fast on-device deep learning inference with robotics, and maybe that opens up a whole new world of possibilities. But that's a maybe.
Thank you so much for this! I used the website to generate brown noise to mask city noise like jackhammers and construction trucks.
I didn't say it's not worth paying for. I said that if you're getting something in return for your money, then you shouldn't call your payment a donation.
Wow private servers are largely reverse-engineered, not leaked Blizzard code.

That's why Blizzard has such a hard time doing anything about them. There's no violation of IP with the server.
IDE was one of many hardware issues that just took too long to be solved. For a long time, BSDs didn't seriously try to support consumer-grade hardware - be it because of lack of manpower, conservative attitudes, or "commercial" choices. OpenBSD still doesn't support Bluetooth...

On the other side, the Linux community fought hard to get everything to work, creating positive loops: the more hardware it supported, the more people could get it to work on their hobby hardware, the more they'd become familiar with it and push for adoption at work.
A bit of a tangent, but I lost quite a bit of respect for Jonathon Blow when he made comments about impostor syndrome:

https://youtu.be/ECwHZlvvVH4?t=3370
This article is kinda a mixed bag of complaints that ranges from very reasonable and important to completely nonsense, which is to say it's very representative of discussions of the relative merits of operating systems

For example, a lot of driver issues and architecture flaws (e.g. on wayland/X) it points out are really useful to consider for both maintainers of those subsystems and users of a desktop computer. But then you also get stuff where things are considered "impossible" for an average user because they involve... editing a text file? Using a shell at all? Not every difference in how you use something is a problem with it. I think having the exact same user interface for an entirely different operating system is a pretty insane expectation
I find it hilarious that 99.9999% of web3 events are not using NFTs as Tickets. Even more hilarious is that are using Ticketmaster or Eventbrite.

I decided to participate in a Polygon's hackathon and build something that is totally free, with no gas fees and more importantly doesn't alienate non-crypto folks.

The platform is called FutureTickets.xyz and you can claim a ticket here -> https://futuretickets.xyz/e/your-first-nft-ticket_91nox70YHN
to experience the flow (you don't even need a wallet!).

If you want to post a new event, I would be thrilled as I am looking for more feedback, just send me a DM to enable your account.

A walkthrough of the platform is here -> https://www.youtube.com/watch?v=21IE5Tmh-nM

I used: Python (Flask), AlpineJS (should have used Vue or React), TailwindCSS, Solidity and hardhat.
- like https://www.liquidtext.net/ for program codes ?

- or Flow-based programming ? --> https://github.com/topics/dataflow-programming
Now let the music play
Have you heard of the Unison Codebase Manager (ucm)? In Unison (https://www.unison-lang.org/) all code is stored as its AST and then you can 'chat' with ucm asking it for specific type signatures for example. Also the text you write as code really is just an intermediate representation and theoretically ucm could give you all sorts of different views on your code.
Low fat/non fat dairy is not healthy, nor is most low fat/non fat replacements because sugar is added to increase flavor.
Love Quarkus. Dependency injection is a beautiful pattern, and Quarkus is getting software development right.
Here's a generative art project I did a while back: https://github.com/maxvfischer/DIY-ai-art

It's not so much about creating the generative algorithms, but more if you wanna wrap the learning around a fun project.
> retail worker in your local grocery shop

Actually, that frequently is malice, but it's malice on the part of the grocery shop, not the individual worker.

Proposed addendum: never attribute to personal malice what can be adequately explained by institutional malice.
Toshiba TSS and Echandia work on marine H2 fuel cell systems
I've looked at that book before, and while I agree that it's probably worth reading it sure doesn't answer all the questions. It just talks about voice leading and gives scientific explanations for why the 18th century rules of part writing reliably turn out pleasing music. It doesn't account for all the music that satisfies listeners somehow even while violating some of those conventions. Nor does it cover anything aside from tonality, from what I remember.
Strongly agree. The way the roman alphabet is represented on digital computers is to treat upper- and lowercase letters as completely separate sets of characters. People are pretty used to treating these sets of letters as functionally equivalent across "cases", so there's an argument to be made that this is a weird and unnatural choice. Maybe it would have been better to treat the "case" of a letter like we treat fonts, as information separate from the plain text that's only ever used in rich text display. But since this representational convention is settled across every platform, it is a much weirder and more confusing choice to then treat these characters as equivalent when naming files, and causes more confusion than it clears up
I second these recommendations. The TS-80P has replaced my soldering station, I sold it because I don’t use it anymore.
The first author of AlphaFold paper is John Jumper. John Jumper wrote a PhD thesis on protein folding.

It is not true that AlphaFold team did not have domain expertise. I would accept that AlphaFold team had less domain expertise than expected. Could it be done with no domain expertise? Maybe, maybe not, but AlphaFold is not an evidence either way.
Regardless of our views on capitalism, unjustness, or any of those related matters, I have to read this and feel sad for the lost talent, potential, and productivity especially now that we badly need every ounce of hard work we can get for some of the bigger problems we face, climate change, global uncertainty, and such things.

Now more than ever, we as humans need to find a way engage and unite. But instead we are seeing more apathy, what feels like more division, and less interest in tackling truly difficult problems. Again, not trying to pin it on why (unchecked capitalism, etc), just trying to say that the state of affairs does not seem encouraging.
Groupthink: Modern Perspective
A "big picture" retrospective on some recent dynamics in (very) large scale group decision making.
True believers (or, at least, people who have figured out that their odds of survival are improved on playing the fool and seeming to be one) are way more than 20 percent of corporate workers. They're probably 70-80 percent (with an unknown contingent of that set being smart people who are simply good at pretending to buy in). This is counterbalanced by the fact that true believers tend to be not very smart and, therefore, incompetent. So it feels like only 20% of the company buys into the false consciousness, just because the people who really do tend to be the inherently ineffective ones: if someone who is not pulling 7 figures per year genuinely loves his corporate job--i.e., his position of having to sacrifice more than half his life to do paperwork for rich people--he is probably not very bright and it is borderline miraculous that he functions at all.
So, the most recent paper says they get a "majority" of structures right:

https://www.nature.com/articles/s41592-021-01362-6

And the January paper from this team claimed 66%:

https://www.nature.com/articles/s41592-021-01362-6

This is impressive, but not game changing.

Solving protein folding is analogous to solving the halting problem, but harder. The sequence is interpreted by squirting out a string of stuff that mutually attracts and repels itself and the environment. Different temperatures, neighboring proteins (the "program input"), etc, leads to different folds (the "program output"). As with software, there's a happy space of expected inputs where it's hopefully easy to reason about expected outputs.

The difference between folding and the halting problem is that each step of the execution trace you'd need to generate to show a particular structure is reachable is quadratic in the number of atoms in the protein and surrounding environment, and the steps are not discrete.

Alpha fold mostly just glues together previously seen folds that were produced via x-ray crystallography. This technique is called "threading" and is decades old. It has all the obvious limitations you'd expect if you extended my halting problem analogy.

Also, most of the low hanging fruit in this field was picked a long time ago, so the 33% they perform poorly on is precisely the interesting part of the problem space.

Edit: Here's an early paper from 1997: https://pubmed.ncbi.nlm.nih.gov/9237912/

For whole structure threading, they get the correct fold "45-75% of the time". "Correct fold" is a weaker criteria than Alpha Fold uses in their abstract. However, it's interesting that Alpha Fold is still stuck in that range 25 years later. (Also, the 1997 paper is nowhere near state of the art.)
No it wasn't, not sure why people keep choosing to believe that when Kiwis keep correcting them.
No idea, never needed it. At some point I decided I had no use for dedicated GPUs that justified dicking around with atrocious driver blobs. That might change in the future if I get more into ML though.
Maestro and V Pay are being discontinued as of July 2023 (existing cards will keep working but no new cards will be issued). Banks/merchants will have to start issuing/accepting MasterCard/Visa instead.
I recall Krugman, in the last week, saying, that, no, there is no recession, because jobs.
I’d definitely be a NullPointerException. I don’t want a programming language that I can’t type in ascii. Sorry, god. Limited to 255.
This probably does not only apply to software but to UI/UX in general.

The "atarimae" translates to "UI/UX that works" and "miryouteki" is "UI/UX that is pleasing to use".
Well, if you are truly wondering, I think I can give you some intuition about "why they were so pissed". Obviously, I don't know what were the facts of the situation, and if they really should've been pissed, but I can explain the typical mindset.

The main idea is that writing some code to achieve any particular effect in the system is typically easy. But writing code, that is efficient and maintainable isn't easy. So, there's a team X, which has people working on some specific system. They own the code. To them, their work isn't quite about "implementing requested features". It is about inventing proper abstractions that both reflect the logic of the requested feature and reasonably anticipate the logic of any future feature requests. They want to avoid having 2 implementations of the same thing, they want every piece of code to be idiomatic to their system, etc. And they are right thinking like that, BTW. Every new developer they get is treated with some suspicion at first, and when he learns the idioms of the system he becomes a honored member of the team X. If he fails to learn them, he gets fired or passed to another team, where he may turn out a better fit.

So, for the members of team X, they are professionals, who know how to work on the product and on the system X. Members of other back-end teams are probably not, even if they are good devs otherwise. Some frontend dev — doubly so. Some junior frontend dev coming from military or helpdesk or whatever — triply so.

So, you may think that you are a great and charitable developer, who just implemented a Feature. But to them, you are a lowly ape who made a wobbly hut out of some sticks and leaves that is going to fall down now any moment, and it's going to fall down on THEIR heads (and you will be long gone).

Worse than that, they understand, that other non-engineers (like their manager) also are prone to mistaking a wobbly hut for a Feature. And you basically humiliated them in front of these people by "solving" their problems (while in fact you created more problems). So it gets political here. In fact, because of that, even if the above is not a fair description of your work, they kind want it to be fair, they want you to fuck up, because it at least makes it easier to explain why your help wasn't a real help.

And, in all fairness, it is kinda unlikely that a guy who is new to a codebase didn't fuck up in any way, even ever so slightly. Especially if that's a kind of guy who doesn't understand why dedicated back-end and front-end teams exist.
So it's Lisp with uglier syntax?
I'm not an expert in the topic by any means, but it feels to me like goal-post moving. Previously I had the impression they were saying 'protein folding' is the key problem. Now they say, so what we can fold proteins, there is more to drug discovery than this.
I guess this is natural with any scientific advance.
Is this supposed to be funny content?
...and chronic inflammation has been linked to lack of physical exercise and poor diet.

Inflammation is helpful when rebuilding muscles and recovering from work. Inflammation is harmful when there's nothing to work on. The body goes haywire and you get all manner of problems.

The kinds of food you eat can contribute, but it is largely that we have an engine designed to work that we're perhaps letting idle in the garage, that seems to be the main problem.

Crohn's, for example, is a disease that manifests with severe inflammatory problems. One of the chief ways to keep it in check (not a cure, just one of the things that help) is significant exercise (fitness) and controlling food intake and quality.

You walk your dog... you need to "walk" your own self too.
Why the heck would you rely on solar power in Northern Europe? The North Sea has some of the most reliable winds in the world, and Northern Europe is full of mountains. Use excess winds to pump water up the mountain and use the head to turn a generator on the rare windless days.