skysight-inc/HackerNews huggingface dataset:
inb4 it was ancient fidget spinner
Not strange at all. This is largely how biology operates. These things are simpler than bio and more complex than programs
The usual reason for that is DNS load balancing.
Oh we share secrets using a password manager. But it's a long laundry list of secrets that you have to manually load into your system somehow. There's also an env file there somewhere but it's not up to date.

Eliminating the cognitive load of looking up the relevant secret, writing it manually into the RC file, testing whether it works (and starting over if it doesn't, because it's possible the secret is outdated) was one of the goals of creating this.
Lightweight branching is coming "soon" and will help this exact issue. Contact me for more info.
Ive had that multiple times. I usually quit HN when this happens.

I'll comment on a dead thread from the previous friday, rss feeds ftw. Say nothing particularly controversial or anything, a positive message.

Then I'll hit an active thread and say something thought invoking. I'll end up -10 on the dead thread comment.

Basically there are groups here which curate content using downvotes.

Luckily it only works against the last couple days. So HN is incentivizing you to only make 1-2 comments per day and no discussions are allowed. Which makes it easier for those curating content to do what they do.

Worse yet, when you get targeted like this a few times, you end up shadow banned on HN for 'low quality posting' but it's really just people curating content.
If you would make a switch and give Ukrainians the T-90's and Russians Bradley, T-90's would be hunting Bradleys.

Without well trained and high morale crew the tank is just heavily armored tractor.
Cloudy weather is harder, not easier when using concentrators (because it concentrates parallel rays of sunlight, not ambient light). Restricted space would still need to be covered with something and here you'll find that covering it directly with photovoltaic panels is more cost effective and will get you more power for a given area. As far as I'm aware concentrators are pretty much dead except for when you need lots of localized heat, for instance a solar oven. There they definitely work better than anything that is based off photovoltaics and because they tend to be totally passive probably more rugged and reliable too.
Ah, the Ship of State
we use Atlassian. My engineering team works on a Jira Kanban that only contains tickets that are soon to be worked on (read: within the next days, tops), there is no backlog at all, and engineers are encouraged to put technical findings there and pull them if the team considers it important enough to act on it. In addition, our product team works with the "Product Discovery" tool from atlassian, where they collect Ideas/Features/..., determines the RICE score for each, and does the back-and-forth with people, until they are reasonably sure what to put into the engineering kanban next, always having the "WIP limit" in mind.

Therefore the giant "icebox" is out-of-sight but the social factor of "there is a ticket for my idea" across the company is also fulfilled. works pretty well so far!
> So that vast address space might not last as long as it would seem...

Have you done the math?

* math property: x^y = x^(a+b) = (x^a )x(x^b )

* IPv4 addresses are 32 bits (2^32 )

* 2^32 ~ 4.3 billion

* So the IPv4 Internet has ~4.3B devices on it

* IPv6 subnets are 64 bits, /64 (2^64 )

So, a IPv6 2^64 subnet is the same as (2^32 )x(2^32 ), which means (4.3B)x(IPv4 Internet). I.e., a single IPv6 subnet can hold the equivalent of four billion (IPv4) Internets.

A second way of thinking about it:

* Stars in the Milky Way: 400 Billion

* Galaxies in the universe: 2 Trillion

So (4x10^11 )x(2x10^12 )=8x10^23 stars in the universe.

* Size of IPv6 address space: 3.4x10^38

Find the ratio between addresses and stars:

* 3.4x10^38 / 8x10^23

IPv6 offers about 430 trillion times more addresses than estimated stars in the universe.

A third way: On the surface of the Earth (land+water), there are 8.4 IPv4 addresses per km2. Not counting the oceans, that would be 28 IPv4 addresses per km2 of land.

IPv6 gives 10^17 addresses per mm2 (yes, square millimeter).

In terms of volume, 10^8 IPv6 addresses per mm3 throughout the Earth.
The first arg to your program is a path to the binary that's being executed. No /proc required.
Painting over the defects was just a figure of speech right ?
Ask HN: How much of your life can be automated?
I guess many of you enjoy automating stuff and so do I.

As in title, how far can we go with automating things with our lives?

Starting from simple and maybe obvious things like:

- floor cleaning robots

- food preparation robots (think thermomix and similar)

- setting up reminders and notifications so you don't have to remember meetings, deadlines, birthdays and check on your scheduled things manually

What else did you build or purchase to make life easier?
I didn't realize HN is a German forum now.
I totally agree with you on LLM usage. I have recently switched from JSON to YAML for requests and replies from LLMs (GPT-4 specifically) and I find it much better:
fewer tokens used, more readable if you are looking at the http requests and responses and you can parse it on the fly in streaming responses. The last point lets you do visual updates for the user, which is pretty important if you need to wait 1+ minutes for the full response
These reactionary waves have been so unsuccessful, I wonder if it makes more sense to model them as ways to extract money from confused old rich people?

The story you tell to some aging billionaire about their grandkids being brainwashed on campus can be successful in getting them to hand over money to found a "think-tank" campaign while being counterproductive when the messaging meets a population who has actually been to a campus and/or been born in the last few decades.
I thought everyone enjoyed being forced to watch an Apple Music advert when they just want to play a song stored on device!
But that's not true though, it isn't complete trash. Some of it is trash, some of it is nothing short of amazing. And the bit that is amazing, when applied at scale and properly weaponized already has the potential to transform our world in many ways.
If "IPv6 addresses are harder to type or remember" is the worst thing that happens during the transition to IPv6 then I'd call the whole thing an unquestionable success, given that there were numerous far more important things that could have gone wrong or ended up worse but didn't.

DNS exists to solve the problem of people not having to remember or type IP addresses. This is true regardless of whether you are talking about IPv4 or IPv6.
no need for the death penalty. Life imprisonment without parole will do just as well. It doesn't even seem unlikely to me that lines could be drawn for manslaughter (of course expensive lawyers would find ways to muddy the water but lets be real, our society relies on the fact that the buck stops at the top. Where else could it?)
Genuine question: What is category defining about Google Calender? Or even good? In my experience it lacks a lot of features and is kind of clunky.
That totally depends on where you put value. We're a fraction of other companies licenses for comparison. Also, we have new pricing for our new Helix Core Cloud SaaS product!
YAML is an amazing config language for simple to mildly complex configs. It's easier to read and write than JSON, and it only really breaks apart when you're heavily deviating from nested lists/dictionaries with string values. People use it everywhere because by the time it becomes painful you're already so invested it's not really worth the hassle of switching.
The vast majority of tickets that haven't had any interaction for some length of time are irrelevant, it's an excellent proxy.

But it's worth reading the comment in context. If your problem is that old tickets are a nuisance because they're almost always irrelevant, just have them auto cancel and when you get that notification rescue the 2 per year that you truly want to keep.

If you don't have that problem, keep them.

> Why search through cancelled tickets which are resolved to find and unresolved issue?

Why would resolved tickets be cancelled?

Also, why search through two different systems?
Normally they do, but some implementations (notably GNU SmallTalk) are so afraid of the SmallTalk way of doing things that they use source files instead, which IMO removes a large part of the attraction of using SmallTalk at all.
One angle that I almost never see career-related posts talk about is what your daily life is like for various positions. Everyone tends to focus on the intellectual content of work, but rarely what the work environment is like, where you have to live, etc.

For example – the vast majority of tech jobs require one to sit at a desk in an office. There are ways around it, including remote jobs, standing desks, and walk pads, but basically if you're a tech worker, you're in a room staring at a screen for 6+ hours a day.

So, from this perspective, I would suggest thinking about what kind of day makes you happy and fulfilled. Is it one that involves talking to a lot of people? Walking around an urban area? Being alone in the forest? Put the intellectual content of what you're doing aside.

Personally, as much as I love tech stuff, I have grown to really dislike the default work environment. Being a bike messenger or a sailor, while having nearly zero relation to technology, seem like much more enjoyable professions on a day-to-day basis. This has led me to experimenting with various work "formats" that combine physical activity with computer work, ranging from take my laptop to a cafe to use a standing desk and exercise bicycle.
Obligatory reference to Rubynetes - using Ruby and rspec to generate the YAML files that k8s loves.

[0]: https://www.brightbox.com/blog/2020/02/24/rubynetes-getting-...

[1]: https://www.brightbox.com/blog/2020/02/12/rubynetes-kubernet...

[2]: https://www.brightbox.com/blog/2020/02/17/using-openapi-to-v...
because he spent years - since the Perseverance landing - covering this mission and all status updates

I trust dedicated journalist more than generalist run-by ones that clickbait another working moment like it's the end of the world
Restricting config to static values removes quite a bit of the value of config, in my opinion.

Yes, logic should live in code, but very often that logic needs to behave differently depending on some piece of (inherently variable, not static) configuration.

Random examples (written from the perspective of personified code):
- How many threads should I use?
- On which port should I serve metrics?
- Which retry strategy should I use?
Though if you compared the efficiency of a heap pump for cooling and a resistive heater for heating, you might be surprised that cooling is more efficient.

The intuition is that the heat pump is moving heat, as opposed to just generating it.
Back in the day people pirated miracles because mp3s didn't exist yet.
I usually hate such comments but this made me chuckle, thanks.
Capitalism isn’t about claiming scientists like Tesla or Pasteur were capitalists, but about creating a system where their innovations reach and benefit the masses. For instance, the widespread use of penicillin, a monumental scientific breakthrough, was massively scaled up and distributed thanks to capitalist structures. It’s about turning breakthroughs into real-world solutions that improve lives.

Fleming’s invention of penicillin wasn’t about capitalism or socialism, but how capitalism effectively used his discovery to save millions of lives globally. It’s not about claiming credit, but recognizing the system that best harnesses such innovations for widespread benefit. Regarding corporate responsibility, capitalism doesn’t excuse unethical behavior, as seen in public and legal backlash against such incidents. True capitalism demands accountability, not sheltering the guilty.

Consider the printing press, invented not just for knowledge’s sake, but also driven by Gutenberg’s vision for profit. This invention revolutionized the spread of knowledge, paving the way for scientific progress and the Enlightenment. Just like with penicillin, it’s a prime example of how the pursuit of profit under capitalism can fuel advancements that benefit all of humanity.

The real moral outrage would be ignoring how capitalism has lifted billions out of poverty. It’s not self-congratulatory to acknowledge facts. Capitalism, unlike any other system, has consistently turned innovations into tangible benefits for the masses. Using emotive language like ‘shameless’ or ‘morally corrupt’ doesn’t change these historical truths. It’s about progress and real-world results, not ideological rhetoric.
So choose a technique and language that least limits your design freedom.

Choosing performance as your #1 priority is often a bad idea as it gets you into a straight-jacket from the start, making everything else much more difficult and slows down development to a crawl. Unless you're developing an OS kernel perhaps. Computers are fast enough these days, let them do part of the work for you! And you can always write a faster version of your software when there is a demand for it.
> I don't understand why getting rid of DHCP is desirable.

It's less infrastructure to run, especially with embedded networks.

> DHCP provides a nice central place where you can map MAC addresses to IP addresses instead of configuring it ad-hoc on every device which needs a static IP address (if you're lucky and the device even supports static IP!).

You are limiting your thinking to macro-scale 'user-managed' devices, as opposed to things like embedded things:

* https://en.wikipedia.org/wiki/Matter_(standard)
For IPv6 you need to implement NDP, RA, and a bunch of changes to the DHCP server. You also need to start paying attention to ICMP.

The documentation for ESP-IDF (https://docs.espressif.com/projects/esp-idf/en/latest/esp32/...) says:

> Disabling CONFIG_LWIP_IPV6 can save about 39 KB for firmware size and 2 KB RAM when the system is powered up and 7 KB RAM when the TCP/IP stack is running. If there is no requirement for supporting IPV6, it can be disabled to save flash and RAM footprint.

> Disabling CONFIG_LWIP_IPV4 can save about 26 KB of firmware size and 600 B RAM on power up and 6 KB RAM when the TCP/IP stack is running. If the local network supports IPv6-only configuration, IPv4 can be disabled to save flash and RAM footprint.

IPv6 takes up more ROM than IPv4, and as far as I know ESP-IDF doesn't actually fully support IPv6 either.

At this point we're talking microcents of storage, but unfortunately the 13KB of size difference can make the difference between "the code fits" and "we need to spend a dollar more per unit".
I have The Great Texas Eclipses featuring a crossover of two separate solar eclipses that concides over Waco, TX.

They do not sell them anymore but the same postermaker is selling this:

https://www.greatamericaneclipse.com/texas-2024-eclipse
There was a BBC special on the Titan submarine before it imploded, and on one of the dives with the camera crew, it got stuck going in circles on the sea floor because the direction buttons on the gamepad used to steer it were incorrectly mapped.
See: "Motel of the Mysteries" by David Macaulay

> "that the toilet seat is a sacred collar one must wear before shouting, down the hole, to the gods below"

https://scifi.stackexchange.com/questions/162247/humorous-st...
I believe Java virtual threads/project Loom fits what you are describing. No separate async APIs, everything is coded using a thread based model. The user decides between using platform/OS threads (thus delegating scheduling to the kernel), or using virtual threads and letting the JVM take over scheduling.
I've always been partial to Von Neumann's middle square method myself.

https://en.wikipedia.org/wiki/Middle-square_method
Unfortunately, almost everyone is still using YAML 1.1

PyYAML still doesn't support 1.2
> …smaller teams where the people on the teams actually work…

there’s that same vc recipe of the moment.

once you have been tricked back into the office, the next ruse will be that less is more. less headcount, more productivity.
That's a great article, you should post it separately.
Yeah I still have spores (ofc nothing legal ... :P) and will try the Uncle Ben's tek. Looks real easy. Thanks for the discussion! Would love to discuss more, but not on HN with my clear name attached to the profile haha.
Mystery Search – Google, but you get the last person's search
Intro to Jax
Indeed, XML is a decent document language because of the quality of tools available and its power/flexibility. I hate when people use it for config files and other things that are usually human edited where readability is paramount though.
> And forbidding it makes a one-keystroke action a two or four one.

You can’t be serious
It'd generate same set of problems in INI, YAML, TOML, XML, JSON, BICF (bayindirh's imaginary configuration format).

Because these are not related to how you write the file, but how your software operates in your mind.
We have a lot of issues (nearing 1000) in a public repo[0] that anyone can view and vote on.

This gives us a natural filtering mechanism for community input. We regularly sort this by number of upvotes. It also lets our users submit some off the wall ideas, and gives a way for low friction community feedback to be captured. Finally, it lets community members easily be notified when a feature is delivered by subscribing to the issue.

We also have a separate, private list of commits to customers. (The commit is public and is added to a milestone, but the customer is private.)

We also group issues by theme[1]. It's not perfect but it's an attempt to make sure we don't run into the duplicates issue you mention. It allows the eng team to address multiple issues in the same area of the code at once.

I understand what you are saying about clutter, but the low cost public feedback and tight loop between issue and code is worth some issue creep, IMO.

0: https://github.com/FusionAuth/fusionauth-issues/issues

1: https://github.com/FusionAuth/fusionauth-issues/issues?q=is%...
Yeah I'm sure it's a rare occurrence, but it just turned me off from using Moka pots in favor of a Turkish coffee cezve or French press, neither of which can explode.
No, not necessarily. Various Smalltalks have a wide range of different approaches to UI and IO more generally. This (their "operating system aspect" https://eighty-twenty.org/2019/01/13/why-learn-smalltalk) is the area in which they're most diverse, in fact. For instance, GNU Smalltalk has, by default, only a REPL, while Smalltalk 80 has a bitmapped GUI.
I worked at roughly 10 companies in my life. Most either used Outlook/Office or Gmail/Calendar/Drive. Personally I hate the Microsoft office productivity stack, and on the other hand, I love using the Google stack, including Calendar.
If the article is accurate, it seems like it's a specific type of outsourcing causing problems here. Namely, that the thing they outsourced wasn't a commodity. Spirit is selling them shit but they have to suck it up and try to patch the things together, because there is no one else to buy from.
I would expect most budget Android tablets to provide a significantly more smooth experience than a Surface Go. While it was almost serviceable at launch, these days it can barely keep up with Windows.
> shout in the ether that this engineer will have a job at your organization.

This. Or crowdfund a mega million dollar bounty for evidence of certain types of malfeasance.

The market seems to generally punish whistleblowers, and understandably so. I have never worked for a company that wasn't violating some contract, regulation, or law. In my first job we were forging stuff for PCI compliance. The next job stored medical records in a Git repo.

So most people have something to lose if there is a whistleblower personality around, as much as we might admire them when they reveal the secrets of others.

I wouldn't want to work with one. I am not a manager and even as a low level individual contributor I cut regulatory and security corners to keep bosses happy.

You would get far more whistleblowers if it didn't essentially mean wrecking your livelihood, even if you are willing to sacrifice your career.
Sounds like a job for a cheap Bluetooth OBDII dongle.
Ditto. Added atuin.
Quality issues started waaaaaaaaay longer.

DEI is just a scapegoat that is more palatable than truth to certain portions of public.
Fascism and Communism. Two sides of the same coin. In fact, they are so similar even in their base, they ended up as mortal enemy of each other.
I’m not mocking it. I’m just applying the argument I see many people on HN make in discussions about rust to this case, where I suspect many will lean much more on the side of using regexes to reimplement parsers. Don’t know if that’ll be the same people. Either way, I didn’t want to have a discussion about rust.
I could be wrong, but I do not think it's easier to remember 45465465464938259 then it is to remember the lyrics to a popular song. Now I assume there is some sort of brain difference playing here. But while looking it up most popular memorization strategies are either ram it into your head with repetition or converting it to songs, rhymes, poems, or other word phrases.

It's quite easy to remember things like "Mmm-mmm, went the little green frog one day".
I, on the other hand, find it much harder to read and write even in very simple configs. I never know what the indent is supposed to be, I just press my spacebar until my editor stops complaining. I find it really hard to tell if a line is a new entry or a subset of the parent entry.

I'm sure if I used it more it'd become easier, but my whole team doesn't understand it either. Luckily we only need it for GitHub configurations.
Everything is art then and we are all artists. Happy? Also consensus != correct.
If your concern is datamining, then you should be far more concerned about the billing info (which can't be faked) than the email.
Right Side Up (2008)
Outsourcing makes QA harder, more expensive, less reliable.
> Wait SLAACs aren't globally routable?

It is not the host-component of IPv6 that determines routability, it is the prefix.

If you have a link-local prefix (fe80::/10) then it is not global, if it is a private prefix (fc00::/7) then it also may not be global; if it is part of IANA's unicast allocation (2000::/3) it is global (firewall permitting).
In case it wasn't clear from my comment: I'm European...
> Boeing's a weapons company that makes airplanes on the side.

I don't think this is an honest assessment. From your own source, Boeing's "Defense, Space, and Security" segment draw 39% of the company's revenue, while it's "Commercial Airplanes" segment accounted for 32% of its revenue.

I don't think that there is a single company on earth that would describe the source of a third of its whole revenue as something they do "on the side". Moreso when the top segment is barely over 5% larger, and is comprised of a coarse agglomeration of activities that may or may not be all related.
Just because a measuring device is not standards referenced does not mean it can not be used to measure.

If I need a peg to match the size of a drill bit, any collection of 12 holes is likely to have one the size of the drill bit that lets me tell my peg maker to "make the pegs this size."

Handymen are just cussed enough* to not label any of them, and to expect the FNG (new guy) to remember which of the 12 unlabeled holes was the one.

* Cussed enough is a slang adjective that describes someone who does things that annoy people. We say it in Texas, but I do not expect everyone uses that phrase. I can not think of a standard term that carries the same connotations.
Considering 99% of existing software is pure crap - we need a lot more.
That’s not evidence, that’s someone who thinks everything is a leftist boogeyman and who needs to spend less time on the internet.