skysight-inc/HackerNews huggingface dataset:
Show HN: I made TV Sort, a web-based game for ranking TV show episodes
Over this Christmas break, while discussing the best episodes of Frasier with my mother (as we tend to do when I get to see her), I thought about coming up with something that's less arbitrary than 1-10 ratings.

The result is TV Sort. It just uses a sorting algorithm, but... it's human powered. When the algorithm needs to compare two items, it asks you to compare them, and with that you end up with a full, thoroughly sorted episode list.

It uses TMDB, IMDB, and Wikipedia to extract episode information for any show, to help jog your memory when making episode comparisons.

It was a fun little experiment. And finally, I know -exactly- what I think the best and worst episodes are.[0]

Would love to hear your feedback, this is my first Show HN. ;)

Edit: I wrote a whole blog post about what went into making it, if anyone wants to read more of the technical detail behind it.[1]

[0]: https://tvsort.com/show/3452/matrix_01hjtxz2e1ewkrh44ja3mz0s...

[1]: https://pocketarc.com/posts/tv-sort-engineering-the-ultimate...
Ok but who is actually saying the content/product result isn’t important? Seems like a strawman.
Asian American Officials Cite Unfair Scrutiny, Lost Jobs in China Spy Tensions
https://archive.is/z76oF
Awesome! Appreciate that. The Teespring story is a good episode of the new podcast coming out in February: https://www.youtube.com/watch?v=nTPTBDQGPSQ
Any articles about it? From what I can tell it's not very far from a fault line, so I guess earth quakes will happen in that area at some point in time.

Genuinely keen to find out more about it.
I think the idea that almost everything is a “group project” in life and that the things learned from school group projects carry over beyond to the rest of life holds true. It’s a simplification but has more than an ounce of truth.
Yep this "system" falls apart without being linked inherently to the system it claims to be dropping out of. If a large number of people tried this they'd all starve.
ok so why does it matter for borders?

the location of the border seems important, but not the length.
It's tricky though. I think a lot of people think they want raw keyword search, but what they really want is a search experience that makes intuitive sense.

If you lean too much into embeddings and so on, it's easy to get errors that don't make sense to a human being. It's extremely frustrating when you experience "I typed X, why am I getting results about Y?!"

That said, I think there's a sweet spot with some magic, where it genuinely just makes search better. But it's like perfume, if it's immediately obvious that it's there, it's probably a fair bit too much.
> I think the authors point is that some changes are so minor that elaboration is not required, like changing indentation.

Is the change _just_ changing indentation or is it changing something else which is hidden by a bunch of indentation changes?

The difference between a commit message like "reindent" and "." is that the former makes it clear that the change is intended to be completely superficial and (unless you're writing python) should have no impact on anything.

Now the person who wrote that commit message may be lying, or may have made a mistake, but, with even a commit message such as "reindent", it's much easier/faster to approach the issue if your bisect lands on such a commit message as you can go straight for "well let's normalize both versions to see if there's an accidental change hidden in here" rather than getting frustrated trying to figure out what the commit was about.

> But most people also tend to squash several changes together, because it's easier.

Don't.

I also disagree with the author of the article about having an unclean history, it's not that hard to keep a clean history and, combined with actually properly splitting and isolating changes, makes it much easier to review the code. Proper use of git isn't solely centred around making bisect work.
Yes, you cannot reasonably run these high-power devices on low-voltage DC (12-48V), this is also said in the article. But the reason is not that these devices cannot run on DC in principle, the problem is cable loss. For running devices which need >1kW on low-voltage DC, we are talking at least 20-80A, depending on the voltage. So you need thick cables, which are expensive and hard to deal with (amount of space needed, securing connections, avoiding bending, everything becomes problematic with these cables). Any little mistake done with cabling is immediately a fire hazard.

So in the end, the article says: say good bye to your washing machine, dish washer, electric kettle, electric stove, etc. I mean, the site is called "low tech magazine" for a reason...
I was somewhat reminded of Larry Wall's newsreader, 'rn', as I read the description of Orange Site Hit. I invested a lot of hours on Nutnews back in the day.
Yeah, it's pretty cool. I wish I had more time to polish it up a bit. A least make the mobile experience work a bit better.
> Instead, adjust the asserts such that they lock down the current (wrong) behavior, and add a clear // TODO: comment explaining what would be the correct result. This prevents such tests from rotting and also catches cases where the behavior is fixed by an unrelated change.

Yuck! Tests asserting wrong behavior?! Then you might as well not have the thing. Just remove it entirely.
But what if we can better methods that have lower cost of legitimate users?
A Boltzmann brain requires a similar underlying reality except with no evolution traceability for the brain's origin.

Not requiring a world around the brain does not make it more likely, but less, as the probability of brains given that worlds exist multiplied by the probability of worlds is still much higher than the probability of brains regardless of the existence of worlds
Your friend is correct. I call it the Cardinality Barrier - Cantor showed that there are incomprehensibly more real numbers than natural (whole) numbers. Any digital system can therefore be only an approximation. It is likely that the secret of intelligence lies beyond any approximation we might make in silicon.

Of course AGI advocates won't like this idea, as it dooms their entire project from the off. It may be that the only realistic way to make a human like brain, is to make a human (which is quite easy actually).
bun-lib-starter: Effortless Node.js Library Development Powered by Bun
Common Lisp is not a Lisp which 'relies on' recursion. It has various loop statements (DO, DOTIMES, DOLIST, ...), various mapping functions (map, mapcar, mapc, maphash, ...) and a complex LOOP. To prevent stack overflows those can all be built on top of a goto operator (tagbody + go). One of the reason was that compilation targets (cpus, virtual machines, other languages, ...) don't have native TCO support. For example the various Lisp Machines had no TCO support, and many C compilers did not support TCO for quite some time. C is a popular compilation target (KCL, AKCL, ECL, CLASP, CLICC, ... were (some are) all Lisp to C compilers).

> With that said, at least in the case of Common Lisp, it is true that many compilers will implement TCO, even though it is not required at all to conform to the specification.

The specification does not require it, it actually says nothing about it. TCO isn't even mentioned. Means, it also says nothing how a compiler should support it, if it wanted to. The language supports recursion, but something like tail recursion support is entirely an implementation specific optimization. Since TCO has some advantages (less stack space needed, possibly some faster loops, ...), many compilers implement it, but mostly no interpreter does it.

Also, most of them support GC, even though exactly nothing is said about it in the specification. ;-)
More 2023 Book Recommendations
I would comment on this issue, but I am still thinking about what the best comment would be....
What society thinks it is can be understood through the filters, "guard-rails" and boundaries some want to erect around that raw image.

Never looked at it like that. In the same sense one could look at law and see which ones protect us against ourselves.
> people who grew up differently than you

I've been working in this industry for almost four decades. Who grew up differently from me?

You need to go back and fix all your wrong assumptions. There are lots of them.
Yes, but they are more complex, thus more expensive.
Same, I'll get back to it though
I don't think it would be significant.
I love the ‘merge commit for my feature branch with 100 commits, but squash for merging release branch to master’ type.

It’s as if a thousand commits cried out in anguish and were suddenly silenced.
The State of Garnet, 2023
Ok, the captain kicking his own ass was funny!

Hadn't seen this before. Welcome to the public domain.
A CAP Tradeoff in the Wild
https://hyperboria.net, formerly Project Meshnet
Sprints, Daily Scrums...(cough...cough...)
> the west seems like it is decades ahead with this sort of stuff

"The west"?

Ok, so when is the US going to become part of the west?

The previous elected president of the United States believes that because he's privileged - by virtue of being a nepobaby - he can "grab women by the pussy", with no consequences.

So you tell me, what do "people like [us] want"? Do you really have no idea?
Perhaps I could have chosen to put you in your place, but why would I want to? It makes no difference to me what you think. You have clearly not thought this through.

By avoiding going down that pointless road to nowhere, you offered me some wonderful creative writing that I have been quite amused by. Had I put you in your place instead, all I would have gotten in the end is something to the effect of "Oh, yeah." How boring. That would have been the biggest waste of time ever. The outcome here has been much more beneficial.

And with that, I thank you for the amusement you provided. It has been fun.
Most stuff is switched mode nowadays anyway, so this becoming less and less relevant. Not sure if there really are any transformer based appliances in my house anymore.
You are putting words in my mouth.

I didn't say "analogue system," I said "physical system." The uncomputable reals don't have any known physical application, but the computable reals like sqrt(2) and pi, which do have physical application, can be perfectly well simulated to arbitrary precision by a Turing machine (edit: in particular, the computable reals form a countable set, though there isn't an algorithm to find the bijection). And when I said "simulate any physical system." I very specifically did not say "perfectly simulate," I meant "to arbitrarily high accuracy."

What I said is undeniably true according to modern science, and not especially deep:

- the human brain can be described as a massive system of Schrodinger equations. I strongly doubt you actually need the full machinery of quantum mechanics to describe it, but certainly quantum mechanics is sufficient.

- a Turing machine can solve any arbitrarily large system of Schrodinger equations

- therefore a Turing machine can emulate a human brain
Also: it works much better in English than in other languages I know. English grammar is simple, and many of the function words carry a strong prediction for the next tokens.
Radioactive Water Spills over at Kashiwazaki-Kariwa Nuclear Power Plant
> you do need to use the app, because I disabled transcoding

You can use Plex as a DLNA server together with a DLNA client (like players built into most TVs), so Direct Play and Direct Streaming should work just the same.
They exist, but are much more complex. they do things like pair with an air compressor to blow the arc out.
In-sync AC grids are an engineering marvel; high-voltage AC lines are comparatively lossy due to the skin effect among other things; a frequency of 50 or 60Hz yields what are, by modern standards, comically huge step-down transformers; etc. It's worth considering whether the relative ease of running AC motors makes all the difficulties of AC supply worth it.

(It's worth remembering that the "modern", i.e. 1930s, three-phase power grid is built primarily to power motors on factory floors. I don't know if these are the highest load these days, but wouldn't be surprised if not.)
I don't see any future in 12V systems, even in cars (with rather short cable lengths) there are discussions to switch to 48V, like Tesla is doing it in the Cybertruck.

I was thinking more like 200-400V DC systems, that could power most devices, but comes with a lot of challenges.
Why is it that manufacturers go for blue or bright white LED indicators? I assume that they are cheap enough that it doesn't matter, but green would probably still be slightly cheaper.

We have a USB charger that cannot be used in a bedroom, not that you should, but it can light up an entire room. Why not just have a tiny green LED? Apple is really good about not using bright LEDs in their product, or really any LED indicators (there might still be one in the magsafe). So why is it that every cheap random fly by night Chinese manufacturer feel the need to add a tiny blue torch to their products?
God the worst is bluetooth headphones. Oh people would never use these in the dark and especially not with other people trying to sleep directly next to them.
Yeah it made sense for old monitors and then a lot of people got into their minds that it was some kind of rule that could never be changed.

The limits you should observe today are more like:

* Code line length: ~120-140 characters. Longer than that and it gets unwieldy especially in side-by-side views. But you don't need to be strict about it. It doesn't matter if the occasional line overflows. The best code formatting algorithm I know (the Prettier algorithm) doesn't have a strict limit.

* Commit subject length: 72, because Github will overflow anything longer into an ellipsis.

* Commit body line lines: No limit (unless you are developing the Linux kernel). I don't know of an interface other than email that doesn't wrap them.

(You're going to get a lot of old farts disagreeing with this advice, but don't listen to them.)
I echo this sentiment. For the space this project is in, it's amazing the amount of support and coverage it gets from Buster & all the maintainers. This a good example of an open-source community done very well.
> 40 metres to 12 metres

So they sacrificed the freedom of design to save €100?
By the time I was born Mickey Mouse was so embedded in popular culture that it would be unreasonable to expect me to avoid the character. I certainly won't be telling my daughter to choose which characters to like depending on the state of so-called intellectual property laws, that would be absurd.

All this adds up to the fact that established characters are already effectively part of the public domain. A perpetual monopoly on children's culture is both unnatural and unjust.

Disney still benefits from trademark law on their characters along with a generous monopoly on new creations. I would argue that extending this further would reduce the incentive to innovate.

I don't know what the parent poster had in mind, but in my view losing most control by now is absolutely right and proper.
Does the Audi driver monitoring system let you take your hands off of the wheel or look away for extended periods of time? Can it be fooled by a smiley-face sticker?
Usually not for JS people, because they don't get to use recursion much, due to decisions by browser makers. More likely that people from other, usually FP languages think of the actual meaning it has in the article or in the computer programming world.
More than 2x. The people that quit Russia should be included in this count. They are unavailable as soldiers, and having seen the video carnage from the other side and the meat wave tactics will not return voluntarily. For army purposes they are not much different than wounded soldiers lying in an hospital.

Ukraine lost millions of people also, but some of the people that quit Ukraine returned later to fight. At some point both countries will just pivot to start recruiting volunteers overseas.
There's a whole menu of stereotypical HN commenters I could imagine someone having had enough of.
I used the ‘(correct)’ there to notate a little bit of pedantry :) You can of course write interesting things about monads in languages without HKTs, and use them as a bridge to explain the operations of real monads — but those things will not, strictly speaking, _be_ monads, which are a sort of type constructor (map on objects) with some extra operations.

You can of course also always implement a language with HKTs in a language without HKTs, deciding which parts of the language should be read as types and which as terms, but it's unclear to me once you start doing that exactly where we should say you're no longer expressing the concept in the meta-language.
Not a good idea. He explained why in the bit you quoted.
> If a change is really minor, I would say minor is an okay commit message!

This has got to be the author fishing for reactions, right? My reaction, were I on his team, would be to revoke commit privileges.
It's not running locally, sadly, but the Plex app somehow also supports more codecs, so I've found it's generally better.
TLDR for anybody who reads the comments before the article, or who does not have time to follow up Reddit threads: No app, or agent, or special automated tracking was used here. Just manual recording on a google sheet of what the user remembered doing that day... I suspect a lot of data cleaning was done. No human is so consistent, no Netflix binge anomalies etc....
There are multiple things that we really need to make it viable. A standard for the plug that separates it from any AC standard, a standard voltage and current and then standard DC to DC convertors for adjusting the voltage. I guess also we need a completely different light bulb fitting socket too that only fits DC light bulbs. Lots of different commercial DC convertors of varying sizes to replace the AC convertors in all sorts of devices.

I do wonder how much in practice would be gained given the DC to DC conversions are guaranteed for every device.
I’ve actually been doing that in my routine, but for rock climbing instead of ballet! I can finally climb without hurting my toes because they are strong enough to not completely flex back when I put weight on them now.
Delete or hide life-wasting apps
Cool to see someone created this finally, have been manually calculating start times for syncing a drop for a long time. Hope you get it back online soon!
> If you look at the rest of the world, the west seems like it is decades ahead with this sort of stuff than anyone else in the world.

Well that's alright then.

> And social change on national scales don't happen overnight.

Doesn't happen without a motive force, either. People being annoying, that kind of thing.
I think it could make a difference. A lot of devices have power factor correction (pfc) now. To draw a current without harmonics from the grid. You wouldn’t need a pfc stage anymore.
I agree that the mathematics motivating neural networks are well understood. We understand the heuristics behind them; obviously, we created them and they work. I more just mean at the most fundamental level, do we understand intelligence; could we reconstruct it without just ‘optimizing’ towards it. If we understand intelligence then we should be able to deterministically explain all behaviour of neural networks/LLM’s, instead of just poking them from the outside and seeing how they react.
Yeah it sounds nice in theory but the number of edge cases and complications it adds are crazy.

* You need to add `git cp`.

* You'll mess things up if you accidentally `mv` instead of `git mv`.

* All IDEs have to add support for this.

* Have fun resolving metadata merge conflicts!

That's just the things I thought if in a few seconds.

IMO the sensible way to improve this is to have a place for Git to add hints, so that it's automatic rename detection algorithms work better.
Good intentions leading to issues? That’s new… /s
I'd agree if we were talking about learning the full language, but a little lightweight notation often pays for its cognitive cost quite quickly. It's a trade-off, of course, but I can see why an author would choose this point on the spectrum, especially for an audience like advanced (probably polyglot) programmers who are likely to be skilled in quickly picking up new notations.
Prove your claims
As a public open source (yep, open source can be private) programmer (currently x86_64 assembly), and I am very aware of this pitfall.

It is very important to move forward in code, because you cannot predict how will actually end up a complex program: you need to have all the (sane) features in to actually know. Since code is all about trade-offs, there is "no perfect".

You have to be carefull at avoiding falling into a mental spinning loop about this.

Once you have a reasonable minimum of usable features in, publish it. It help breaking such mental loop.

For instance, currently writing a printf implementation, and printf specs are already brain damaged by themselves, so I am not looking for perfection, far from it. I did set myself a minimal set of features (full format decoding, hexadecimal and byte strings) before publishing it. Until it does not require the complexity of a compiler, does a good enough job, I'll be happy.

Sometimes it is not about perfectionism, but a question of resourses required to achieve something reasonably working: you have a montain to deal with just to get something minimaly working, and you are given a spoon... when you are lucky.
a research done by a Portuguese university on "Preparing Students for the Software Industry New Demands" and as documented in

https://www.i-programmer.info/professional-programmer/103-i-...

found that "
that low code platforms, while allowing for fast learning development processes, enabling a more systemic view of software projects and providing easy integration with other application endpoints, can't escape good Software Engineering, as low code's inherent abstraction requires following good development practices"

So no matter,you have to a developer and not just citizen developer
> "I suppose it may help improve overall performance, you're still just blindly predicting the next word based on the previous one like a first order Markov chain would."

Instead of only taking in the last "token" as context to the function that generates the next token - take the last 15 tokens (ie. the last 2-3 sentences), and predict based on that. And that's your "attention" mechanism.
You should check out YunoHost, it's like Sandstorm, better maintained and 90% there imo.
The sensible alternative is squashing the commit, not doing a rebase merge.
If you are going to comment, then you should read the article. But most things posted here (especially by science and tech journalists) are not worth reading and you can get right to the actual information by looking at the comments. No need to read all that extra fluff from some content mill. If it still sounds interesting, then go read it.
100 tiny changes to transform your life
Duff-Man strikes back
I've honestly had people say this to me within the last year!
I really like:

[diff]
colormoved = "default"
colormovedws = "allow-indentation-change"

That is great for understanding the actual code changes wish it was on by default.
When your property is representative of so many as Disney’s are due to shared exposure, it is hard to defend centralized control.
And also this assumes base models. The breakthrough where the instruct/chat models which again are much more code than 500 lines of plain training.