skysight-inc/HackerNews huggingface dataset:
I've found VGA on literally on the TV's and monitors I've come across until now, regardless of which end of the price spectrum they are on. Plus these ports are durable too, you might get some glitchy tinted picture due to dust/bent pins, but it's better than nothing.

Just last week, my team had to attend a meeting where our manager was going to project a presentation on a TV, sadly the HDMI port of the TV was not working so everybody's Macbook and it's dongles were useless. My manager had to resort to transferring the presentation file to my HP Probook and using it to present, which thankfully still sports a good set of ports (the only gripe I have is the lack on DP/mini DP).
Infant surgery without anesthesia was common still in the mid 80's https://www.nytimes.com/1987/12/17/opinion/l-why-infant-surg...

> surveys of medical professionals indicate that as recently as 1986 infants as old as 15 months were receiving no anesthesia during surgery at most American hospitals.

It's unknown where the consciousness starts (the hard problem sense) is but it's not unreasonable to assume that sentience (ability to feel pain and pleasure and experience subjectively) and ability to suffer that comes with it happens long before the ability to form long term memories, object permanence, or other any other cognitive abilities.
Sounds a bit inconvenient if something low level gets changed, no? If libc changes you’re in for a day of builds…
I think the above comments are the clue that the private sector isn't interested.

Too many downsides in being a primary battery. BTW hearing aid batteries are zinc air. So the metal-air technology has certain uses, but as for EVs the highly energy intensive process of re-generating the batteries is probably what causes potential investors to pass.
I suppose I don't understand the conflation of the very real mass slaughter of nonhuman animals, with harvesting plants.
Facebook violates users privacy, yet again
I hope the CBOR tooling is better https://cbor.io/tools.html
I think it's constrained outcomes -- you can mess up and still eat the next day.

You can - for example - die in-game (most games) and re-spawn, reload, restart or whatever. The possible outcomes are known and constrained to what seems a non-damaging locus.

Meanwhile progress is designed in, immediate (relative to real life) and palpable.
It really depends on the task at hand and what the alternatives are.

For example I would much rather write 200 lines of my own code to deal with user authentication (leaning on my framework or a lower level library to deal with the gory bits of setting and deleting sessions), vs. pulling in some higher level authentication library that has 3,000 lines of code but tries to be so generic that it's a jumbled mess which is difficult to customize.

Basically the more important the feature is for my application, the more inclined I am to write my own code. Although I may at times draw inspiration from other libraries that don't quite solve my problem but helps me get closer to what I want to do.
> I don't understand the insistence of the article to place quotes around the word pain when referring to what insects feel. These are animals that can sense their surroundings and react to stimuli. How else would they be convinced to avoid dangerous situations, than by an unpleasant sensation?

If you build a robot which senses dangerous stimuli and avoids them, does it feel pain?

Equating reaction to stimuli with pain is too sinplistic.
Yes. I went:

GW-BASIC (no built-in help, incompatible with most library books, no real editor: hard for a kid to teach themselves from nothing)

-> QBasic (Help! Graphics programs that crashed didn't leave you in graphics mode! Proper editor!)

-> QuickBasic (bigger programs, compile to .exe)

-> Turbo Pascal (help, compile-time errors, programs ran fast in comparison, proper modular code, good editor (great in 6.0), advanced graphics (for the time) totally within reach, and that's where a lot of high-school lunch hours went).

Once Windows started to catch on, Visual Basic and Delphi (both had integrated help), then C++ (though I'd done some of that in DOS too, with Turbo C++).

Integrated help systems were almost essential before the internet, and Microsoft and Borland did them well.
Which open source distributed locking libraries would you recommend?
Several people have gotten well-paying jobs due to contributing to the D programming language effort.
If only websites have their data dumps for free instead of html reverse engineering.
I was one of the original leads on

https://en.wikipedia.org/wiki/Steve.museum

Did it GET me a job? Maybe not. Did it come up in every interview since? Yes.
I hadn't heard about that Nurburgring lap. That's encouraging. I look forward to hearing the specs when they eventually release them.

I am looking at the links. One of them is about a camouflaged ID3 being spotted a few days ago. Why is it camouflaged? Because the production version has not been revealed yet. Everything shown so far has been prototypes. Admittedly the prototypes have been getting a bit more realistic in styling. I like the look of it. I'm just saying, no specs yet and production version is yet to be unveiled. I hope they can come up with something better than BMW just did. And better than the e-tron they launched earlier this year.
Best to read this blog as an example of economic behaviour explained through a graph - valuable in itself, as even basic graph theory concepts rarely make it onto an economics curriculum. Which is a shame, given how neatly algorithmic thinking and complexity costs improve a standard rational agent model (e.g. a few behavioural economic concepts, such as myopic discounting, pop out naturally if you assume mental costs to imagining future states).

Conceptually, it's interesting and potentially foreign to the target reader - more formal definitions can wait for an academic paper rather than a casual blog.
I highly recommend GSoC. It is a fantastic opportunity to learn and contribute to an open-source project by having a mentor from that project that you can talk to, and get paid to do it.

I was already contributing to an open-source project (fireflier) when I applied for GSoC for the ClamAV project, and continued to contribute to the project after GSoC was over.
Shortly afterwards got invited to be part of the team, and when the project got acquired by a company the next year I got a job there to continue working on it (initially part-time because I wanted to finish my studies at the university, and after that full time).

Try to apply to 3 or 4 projects that you like, but don't get too disappointed if you don't get accepted the first time. It probably helps if you already are a contributor to an open-source project so that people can check your coding style/knowledge by looking at GitHub/Sourceforge etc.
But we don't know that insects absolutely couldn't experience pain, in the same way that we're certain a brick couldn't (unless one is a panpsychist). At least they have a nervous system.
A cinema could detect your bot and return fake data rather than blocking you outright.
This seems poorly motivated.

> What are the benefits of an immutable OS?

> One of the main benefits is security. The base operating system is mounted as read-only, and thus cannot be modified by malicious software. The only way to alter the system is through the rpm-ostree utility.

How is this different from the current experience? "Operating system" files already aren't writable by the user. The only way to alter the system is through the "sudo" utility.

> Another benefit is robustness. It’s nearly impossible for a regular user to get the OS to the state when it doesn’t boot or doesn’t work properly after accidentally or unintentionally removing some system library. Try to think about these kind of experiences from your past, and imagine how Silverblue could help you there.

How often does this happen? I've worked with complete Linux noobies who were "forced" to use Linux in a VM daily and I've never seen this happen.
How is it different than paying for any kind of entertainment? (Except maybe the dependency on a single person).
Polyfilling is also some kind of "roll-your-own X".

https://en.wikipedia.org/wiki/Polyfill_(programming)

In web programming, it might sometimes be useful to write your own polyfill when you need to add a single feature for backward-compatibility reasons. Well, a third-party polyfill library that provides that missing feature perfectly might be available. However, the library is too big (with respect to file size) or adds too much complexity during the build process (by pulling in lots of other dependencies).
How to set an ideal Thread Pool size
Well, that's terrifying. Here's a 2017 article on the history of it:

https://www.bostonglobe.com/ideas/2017/07/28/when-babies-fel...
I think VR will be more disruptive than the internet

The internet enabled new ways of doing things. There were things that were literally impossible before we were online. VR doesn't do that. It's great tech, it's very clever, it improves on whats there now but ultimately it's just a fancy monitor and a new sort of mouse. There's nothing that can be done VR that can't be done outside of VR. That is a very limiting factor for it's impact on the world.
> no specs yet

Look at the links.
The actual nice thing about those packages was the straightforward support they provided for the mostly gaming-oriented hardware features in those machines (particularly the Amiga). In this way, they were close precursors to present-day game engines like Godot. And this also creates a conundrum for anyone wanting to bring the originals back, of course - do you reimplement their actual features, even if this means basically emulating a legacy platform?
Furl: A functional React.js component library (beta release)
Scaling Graphite in a Cloud Environment
Only contributing unlikely. Happens, but rarely.
Leading a project very often.
Everything on a CPU is subject to heavy validation .. but I bet the random number generator is exempt, because by definition it's not deterministic. It's more like a peripheral "listening" to randomness.

https://www.amd.com/system/files/TechDocs/amd-random-number-...

> "The RNG uses 16 separate ring oscillator chains as a noise source. Each chain consists of a
different prime number of inverters in a free-running configuration which capture natural clock jitter"

So it's (deliberately) dependent on natural manufacturing variation in the silicon, and in any deterministic simulator won't produce random numbers. It also takes a while to start; it's possible that the startup conditions are bad such that "a while" turns out to be "forever".
Having a good aluminum-air battery would be fantastic, even if it was non-rechargeable. It makes no sense to replace the existing battery pack in BEVs, but they could be used for range extension when going on road trips.

I'd be really curious to know how many kWh you could pack in a hand-swappable unit like Gogoros batteries. Make two slots in the bottom of the trunk (in a way that it can be used for storage when you don't have batteries in there). When you go on a long trip, just go to a station, pick up two batteries, and drop them off at your destination.

The problem is, considering that this is the main use case, it's not a technology with a huge market potential like lithium-ion. It's nice-to-have, but not essential.

Could also make sense for electric air planes or boats.

"The technology development has peaked and unlike aluminum, lithium is not recyclable"

This is just false. Solid state lithium-ion batteries are arguably more mature than aluminum-air, which is a huge step forward. Lithium is also recyclable. That process is not as mature as the process for making aluminum, but I'm guessing there's a bit more to scaling up the recycling of these batteries than just handing over the spent cell to an aluminum smelter.
Package-Distribution.md
You can get it on Kindle:

https://www.amazon.com/dp/B076838QS2

Well worth the money. I don't think I'd pay the $90+ people are asking for a hardcover version...
I had a somewhat similar experience.

This, especially, is what my team also found to be true: "The only model that makes sense in cassandra is where you insert data, wait for minutes for the propagation, hope it was propagated, then read it, while knowing either the primary/clustering key or the time of the last read data."

We use Cassandra in production at my company, but only after much scope reduction to the use case.

We needed a distributed data store for real-time writes and delayed reads for a 24x7 high-throughput shared-nothing highly-parallel distributed processing plant (implemented atop Apache Storm). Cassandra fit the bill because writes could come from any of 500+ parallel processes on 30+ physical nodes (and growing), potentially across AZs in AWS. And because the writes were a form of "distributed grouping" where we'd later look up data by row key.

At first, we tried to also use Cassandra for counters, but that had loads of problems. So we cut that. We briefly looked at LWTs and determined they were a non-starter.

Then we had some reasonable cost/storage constraints, and discovered that Cassandra's storage format with its "native" map/list types left a lot to be desired. We had some client performance requirements, and found the same thing that hosed storage also hosed client performance. So then we did a lot of performance hacks and whittled down our use case to just the "grouping" one described above, and even still, hit a thorny production issue around "effective wide row limits".

I wrote up a number of these issues in this detailed blog post.

https://blog.parse.ly/post/1928/cass/

The good news about Cassandra is that it has been a rock-solid production cluster for us, given the whittled-down use case and performance enhancements. That is, operationally, it really is nice to have a system that thoughtfully and correctly handles data sharding, node zombification, and node failure. That's really Cassandra's legacy, IMO: that it is possible to build a distributed, masterless cluster system that lets your engineers and ops team sleep at night. But I think the quirky/limited data model may hold the project back long-term, when it comes to multi-decade popularity.
Interesting.

British English uses both 'spend' and 'pass'. In particular hobbies (leisure activities) are known as passtimes.

"How do you pass your time?" is not a common expression though but the concept is available, and used sometimes.

People also say things like "what do you do with your [spare] time?".
I think there's confusion of terms. It's obvious that a lot of living things can feel "pain", as in stimuli and response; it's less obvious which living things are capable of experiencing suffering, and it's even less obvious to which point we can (or should) reasonably care - e.g. it's ridiculously hard (bordering on impossible) to live a life in which you don't hurt insects.
When the total lifecycle cost to use existing solutions is higher than the cost to build and maintain, when the future direction of development is unlikely to match your requirements, when the existing solutions lack critical functionality and modification or extension are non-viable, or when you want to learn more about the implementation.
The most interesting thing about this to me is the lesson it teaches human players about bluffing.
Also with NixOS you can install a package and start using it immediately, whereas with SilverBlue you first have to reboot the system to use the new package or after installing updates (or use one of the experimental live update features that tend to break booting the system).
If you don't change the set of installed packages often, and reboot your system daily to get the updates, then SilverBlue works quite nicely. You can use containers (via podman or docker), and there is a builtin utility "toolbox" that gives you a persistent mutable container.
Yes, "the time before you" in en-gb is slightly poetic but could mean either the time in history up to the point where you existed, or it could be the time in the future that is yet to come.
I'm sceptical of the experiment claiming to show that whether Chinese-English bilinguals use the horizontal or vertical axis to order people by age is influenced by language (as cued by the ethnicity of the person in the photo).

The description makes it sound as if 上/下 [shàng/xià] (up/down) were the dominant terms to express time in Mandarin (as exemplified by 上个星期/下个星期 [shàng gè xīng qī/xià gè xīng qī] (previous week/next week)). However, there are at least two other metaphors.

One is 去/来 [qù/lái] (go/come), e.g. in 去年/来年 [qù nián/lái nián] (previous year/next year) or 过去/未来 [guò qù/wèi lái] (past/future).

The other is 前/后 [qián/hòu] (front/back) e.g. in 以前/以后 [yǐ qián/yǐ hòu] (before/after) or 前天/后天 [qián tiān/hòu tiān] (the day before yesterday/the day after tomorrow).

Now if you wanted to use one of those combinations to describe the age of two persons, you'd use 前辈/后辈 [qián bèi/hòu bèi] (elder generation/younger generation). That's not only not vertical, it also orders them by time of birth and not by age.

So I don't think you can use linguistic phenomena to explain why Chinese-English bilinguals would put a young Chinese person above an older Chinese person, if the effect is even real at all. (There were only 32 participants in the experiment.)
“VisiCalc, meanwhile, was mired in a lawsuit between its creators and its publishers—software in its early days was distributed under an author-publisher model, like books.“

It really is incredible how much the software industry has changed over the years.
As terrifying as it is, I wonder if a large part of it was because anesthesia on infants is a lot more dangerous because of the low body weight and unknown metabolism. That could lead to a lot of complications, so if there was reason to believe that it wouldn't otherwise impact the infant (no long term memory) it could be more ethical and safer to not do so. That said I'd assume they've solved those problems now if they're using it.
“Correct” here was not supposed to mean you must agree. As others have pointed out “loophole” is often in the eye of the beholder. But I mean to say that it’s not inaccurate to use the word loophole in such a way that a mod should change the title.
Pain as in stimulus to nerve endings given damage to a limb yes

But pain in humans (or other more complex animals) is more complicated than that
The Korean alphabet is a thing of beauty. It could more or less be the international phonetic alphabet.
Why don't they encrypt that kind of payload? I suppose tampering with it is easy enough that it would prevent using this data in litigation issues, right?
Wow. Lived there for years, studied Chinese, and never noticed these little variations of thickness / weight / line height.

What a cool peek into the obscure subculture of sign-crafting!
> While scraping competitor sites for pricing info etc is exactly as sleazy as it sounds

Why is it wrong to scrape your competitor's site for pricing info? If it's publically accessible, it's free game. As long as such scraping doesn't cause any undue DOS'ing or prevent anyone else from accessing such info.
Yup, all of them in fact, it's a very tangible proof you can work on the subject. Sadly, I do mostly Python and JS so I can't mentor you but as mentionned in other comments, lot of projects are looking for contributors, Firefox is good project for example.
I am a potential employer (CEO TimescaleDB).

Contributing to one of a company’s OSS projects or to a related project is great way to get that company’s attention and prove your ability even before any interviews.
FOOF[1] is still my favorite in this series. Such a wonderfully onomatopoeic chemical formula.

If you read the reference I shared you’ll see that some maniacs reacted chlorine trifluoride with dioxygen difluoride.

High energy chemistry is nifty.

[1] https://blogs.sciencemag.org/pipeline/archives/2010/02/23/th...
See also "Things I'm Glad I Don't Do" (https://blogs.sciencemag.org/pipeline/archives/category/thin...) and "How Not to Do It" (https://blogs.sciencemag.org/pipeline/archives/category/how-...) from the same blog. Slightly less alarming stuff (generally), but still a fun read.
It seems patronising to Americans. They even renamed The Philosophers’ Stone to The Sorcerors’ Stone because they thought ‘philosopher’ was too complicated.
It has Ukrainian keyboard, so yep, it from post-USSR country.
Oh yeah NIH is a problem, but "we can't invent it here" is also a problem

Person tries to find a library that does what one line of code would do (cough left pad cough and others) and then guess what, the library fails at that thing that maybe not 90% of people need but 50% need

And that even applies to some corners of famous apps or libraries big sigh
I have an open source project that absolutely got me hired to Intuit years ago.

The biggest win of doing open source work is that it’s more challenging than corporate work. You build product management skills and really learn to focus on objective quality factors and continuous improvement.

At this point in my career I have passed the tipping point and my open source work is making me less compatible to many of my corporate JavaScript peers. I am not interested in easy, dicking around with unnecessary configuration madness, and prefer to write original code. I am less interested in learning how to write code and more interested in data structures and algorithm design. Contrarily JavaScript is a low barrier of entry field where many newer developers have little or regard for automation practices compared to various other concerns.
https://www.history.com/news/the-father-of-modern-gynecology...

> While some doctors didn’t trust anesthesia, Sims’s decision to not use it—or any other numbing technique—was based on his misguided belief that black people didn’t experience pain like white people did.

See also https://www.pnas.org/content/113/16/4296.full

> These findings suggest that individuals with at least some medical training hold and may use false beliefs about biological differences between blacks and whites to inform medical judgments
Ask HN: Is “new” Reddit completely unusable for anyone else?
I notice that when browsing Reddit day-to-day I am constantly getting either "Sorry, we couldn't load posts for this page" on a subreddit page or "Cannot load comments" on a thread page. This isn't just happening occasionally, it's been happening daily over the course of weeks.

There's been a lot of hate for the "new" Reddit design but outside of the actual usability of the site, there seems to be some huge problems from a technical perspective.

I've tried multiple browsers, internet connections,VPN enabled/disabled and it's always the same. I now just use https://old.reddit.com, but I'd be interested to hear if other people have the same experience?

It boggles my mind that a redesign could be implemented so poorly on such a popular site.
It may be more complicated, but do we know the minimum complexity required of a nervous system to support 'suffering'? If not, surely we are obligated to give even the simplest nervous systems the benefit of the doubt.
Show HN: Cloud Maker – Rapidly create attractive cloud architecture diagrams
Java's Original Sin (2009)
Famous Pirate Flags
I was completely unaware this had been republished. I think it might be finally time to get myself a copy. £13.69/$20.49 (paperback) is a completely reasonable price compared to what I had seen before.
I used to visit the QBasic.com website around the early 2000s, it was also a trove of information. Was fun to dissect snippets that did raycasting or 3D wireframe animations.

Interestingly, it seems that the website was re-purposed briefly in 2002: http://web.archive.org/web/20020524053704/http://qbasic.com/

...but in 2003, it returned to its regularly scheduled content: http://web.archive.org/web/20030207131457/http://www.qbasic....
> In particular hobbies (leisure activities) are known as passtimes.

Minor nit - it's "pastime" (although it does come from "passe tyme" and "passe-temps")