skysight-inc/HackerNews huggingface dataset:
"Can't" vs "won't" is a huge distinction. All the examples you provided are either economically non-viable, bureaucratic landmines, or believed to be pointless. You can argue whether those arguments are justified, but the point is we didn't forget the technology.
> Where's all the good operations people at nowadays?

Still in the same place they were 20 years ago. They’ve just been lost in the swamp of their peers that know nothing.
At some point back when, I had decided that our government contract needed its documentation in hypertext. I spent a few days putting some of it into the GNU Info format, and showed it to my boss. He said something like That's interesting.

Then I installed Mosaic on my PC, and ran the Info documents through a converter to produce html. I showed my boss the documents with Mosaic, and this time he said Wow!
From Decoding to Meta-Generation: (LLMs)
[dupe]

Lots of discussion: https://news.ycombinator.com/item?id=40807032
Thanks for bringing this to our attention! Our team thoroughly reviewed and can confirm all is well; your 83(b) election (and that of your co-founder) was filed successfully and on time.

Here’s what happened:

When our third party mailing service is slow, we send a duplicate filing. The latest 83(b) election was properly filed, but a bug in the Atlas dashboard meant we showed the state of the first filing attempt. We’ve identified the root cause of that dashboard bug and are fixing it swiftly.

We’ve followed up over email with a PDF of the 83(b) letter we mailed to the IRS and your postmark confirmation from USPS. All 83(b) elections filed via Atlas are being filed successfully and on time. Sorry to cause you and your co-founder any stress.

Thank you again for letting us know,

Pooja

Product lead for Stripe Atlas
I think they can compete in all of these areas, at least in theory. Scalability has been done before with things like email and old school messenger programs, UX design doesn't really rely on a system being centralised or not, and monetisation/incentives are much the same.

Unfortunately, the issues often arise from philosophical disagreements and business logic rather than anything technical. Companies tend not to invest in decentralised systems, because it's probably easier to make money if you control the whole system rather than contributing work to something used by thousands of providers. So it often falls to the open source community to develop these systems, and well... that community often doesn't prioritise UX design all that much, nor features designed to make money/provide incentives for popular creators on them.

So the developers are often 'design peaked in the 90s goddamnit!' types, and the users are often against the idea of either mass appeal or the system being used for business purposes/monetised.
I keep saying there is no evidence that it has happened, which there isn’t.
Severance and Technofeudalism [video]
I mean, yeah there's tons of theoretical work. Predictions about lensing and structure have been done and verified. We've taken pictures of black holes. Susskind did a big fancy simulation for Interstellar that lined up great with them.
> This law changes nothing for US TikTok users.

The users who have a million followers or make money using TikTok are expecting that the sale doesn't happen. In the best light, the TikTok forced sale will be constitutional if it succeeds (i.e. results in a forced sale) and will be unconstitutional if it fails (i.e. results in a ban). But even assuming that a sale will happen (and putting aside the burden of demonstrating that "this law changes nothing"), two things would change. In the short term (i.e. during the transition), I would expect interruptions in the content moderation at best (temporary increase in posts in violation of TikTok's rules). In the long term, I expect the change in managing personnel to change the content moderation, including the recommendation algorithm. Users of post-sale TikTok will receive different information than they did from pre-sale TikTok.

Lamont v. Postmaster General confirmed a First Amendment right for a US citizen to receive foreign propaganda in the mail without needing to tell the government "I consent to receiving foreign propaganda". If such a simple burden as having to write a sentence to the federal government to receive foreign propaganda violates the First Amendment, then surely the temporary degradation of TikTok's service (of uncertain length from the average TikTok user's perspective) in the course of a forced sale would violate the First Amendment as well.

Less rigorously, I suspect that the TikTok forced sale is unconstitutional (relating to "deprived of life, liberty, or property" in the Fifth Amendment), since the US employees at TikTok's US office will have uncertain job security.

Note: When I say "unconstitutional" I mean in the context of "so long as the federal government refuses to declassify its evidence that TikTok is a national security threat".
Time doesn’t magically freeze inside of a black hole. That is a misunderstanding of what happens to light rays carrying the image of the infalling diver as they approach the event horizon. From the perspective of an outside observer, those light rays are slowed down more and more and light from the instant of crossing the event horizon never actually arrives; it appears to take an infinite amount of time to do so. The mistake is to think that the object is still there, hovering at the event horizon, for an infinite amount of time. The reality is that the diver notices nothing unusual as they cross the event horizon; they may not even be able to tell exactly when it happens. They certainly do not freeze in place forever.
> The Office of Technology Assessment was dismantled specifically because it was making it too hard for lobbyists to transparently pull the wool over lawmaker's eyes. Suddenly there was paper trail that the Legislature *knew, or should have known, that lobbyists were feeding Congress a line. OTA's entire job was to issue legislative subpoena's to collect information relative to legislative business.

> Congress can literally make itself the single most pre-eminent employer of research staff on the planet, overnight. Do not sit here, and tell me with a straight face, that that is infeasible. The issue is will to govern, and reluctance by moneyed interests to start being questioned back by motivated, competent answer seekers in D.C. they can't legally withhold info from without committing the equivalent of a felony.

And this ruling is going to change this how exactly? It isn't. It is merely going to increase the gap between what is going on in the real world and what is effectively regulated. This is a shift in power from the unelected bureaucracy to the unelected judicial. I'll take the bureaucrats.

> Federal governance is far from impossible to do; and I'd like to know your definition of Federal governance. If it's "I want to pass a controversial law once to get it to stick in all jurisdictions, damn the consequences"; then not only do your complaints fall on unsympathetic ears, but I'd say that's the system working as designed, and Chevron was a step to breaking it worse.

Federal governance includes the need to manage, iterate, and execute on regulation in a world that is far too quickly changing and far too complex for 535 people. There are more decision makers than that in a large tech company.
NetQL: Web Automation Framework
Hey HN,
We've been quietly building a powerful new way to automate much of the web in a more modern fashion. After many years of operating and using other scraping tools, what we really wanted was a "one-stop shop" to write, run and watch what was going on with the browser. Not a local one, mind-you, but the actual browser that will be responsible for running this kind of programmatic traffic.

This led us to pioneer a new way of thinking about and automating web platforms. Having had success in prior API designs with technologies like GraphQL, we began to wonder if it might be a good fit for browser automation. Having inline documentation, history, and typings built into the API was a nice leap forward. The fact that mutations are executed in series also lent itself well to a majority of the web automation use-cases. This means you're also not tied to any particular language or framework and can leverage the full capabilities of the service.

So! Today we wanted to show a bit of taste as to what this looks like. You get an amazing "batteries-included" toolset out of the box with: documentation, history, variables, tabs as well as a live debugger to see what the browser is doing when it's being ran. All while being backed and powered by well set up automation stack that has all the other pieces you might need or want. It's also stateful by design, meaning you can come back to a prior session and continue where you left off which is a great fit for things like AI agents.

This is the future of web automation as we see it, thanks for taking a look!

https://netql.dev
Bear in mind that nobody starts out being familiar with the counterpoints you raised.

You probably aren't telling this to 1 person 100x, but rather 100 persons just once.
> Am I right in understanding, that's over $100 Million worth of GPUs?

Ha! I guess most or many of the readers (who don't have that much of funding) should jump to the next HN submission
The 1984 decision only codified the status quo: federal agencies were already doing what it affirmed as lawful. The EPA didn't start functioning properly in 1984.

If the EPA currently relies on its private interpretation of ambiguous passages of federal law, that's messed up and needs fixing. Have them write a draft bill to codify how they currently interpret vague law, and let a senator introduce the bill on the floor.
and how are you going to be compensated when an AI model has been trained on it, and your code is spit out? and who will pay for the litigation?
Yep -- Eastern and Western Yiddish are mutually intelligible, but have substantially different accents and word choices. Most people speaking Yiddish today speak an Eastern dialect.
I'm not sure where you're getting your information from.

Chrome (and many other performance-critical workloads) is using instrumented PGO because it gives better performance gains, not because it's a more mature path. AutoFDO is only used in situations where collecting data with an instrumented build is difficult.
It's a great way to say "Absolutely no more fossil fuels. For things that need hydrocarbons we'll make them. They cost more but it's better than cooking the planet."

With a side bonus of not sending money to oil rich theocracies like Saudi Arabia and Texas.
Let me rephrase: The time we measure with our clocks from the outside doesn't apply inside of black holes. There is no way to say whether any singularity has ever formed or ever will form even according to the math, since time inside of them isn't the kind of time we can measure from the outside.

If you go inside of it the math says that now your clock inside of the black hole can still function, but that also means you are no longer connected to time outside of the black hole, so you can't say whether anything actually happens inside of them from our perspective, all the math says is what it would be like for someone inside.

You need to make extra assumptions about what it means to have a disconnected time reference frame to say anything.
i don't think anyone training AI models cares about any of that right now
Congress cannot divest its legislative power, nor can it vest interpretive power to executive-branch agencies. The judiciary interprets law— not Congress.
> hot garbage their Server Software was

True. I created an online product catalog thing. For reasons I can't remember, I used SuiteSpot and JRunner.

Turrible. Absolutely turrible. Truly unforgivably bad.

Ditto their LDAP thing.

And Netscape sabotaged Java and Applets. And created JavaScript. And XUL. And...

But hey, marca famously named the image tag "img". So it wasn't all bad.
Arguably the entire web is clickbait, if you consider the point of offering a link is to evoke clicks on that link.
The expectation is because sports are glamorized in media and pop culture, and people don't want to admit that talent is mostly genetic, and even the mental strength to practice every day is mostly genetic
Yes, you have to actually build them too.
i think we are a very long way from that, there is no "intelligence", just advanced interpolation
What is white hole ?
Amazon hires founders from well-funded enterprise AI startup Adept
That phenomenon is often referred to as the "Tech Support Superpower" or "Tech Support Magic." Another popular term is the "Tech Support Effect." These terms capture the idea that technical issues often resolve themselves when an IT person is present.

Your term "I.T. Person Proximity Location Rectification" is quite descriptive and amusing!
They don't believe it's unconstitutional. They believe it conflicts with the Administrative Procedure Act from 1946. Something that they apparently believe the unanimous decision in Chevron from 1984 got wrong.
the open source licenses are not provided along with the AI generated code, AFAIK
Terence McKenna would have a field day with this article
They really need to change the name to something else. I don't know a single person that has used Eclipse in the past and thought that it was a good IDE. I think most of us had no choice but to use it back when we did and just struggled through it.
I wonder what this means for SEO. If someone develops content and someone else then generates very similar content using AI, how do the search engines know who to rank higher?
Luther was a major force on the standardization of (school) German, wasn't he? It makes sense to me that his influence would have bypassed Yiddish. I take it to be mostly a variant of old regional German. I base this on transcriptions to the Latin alphabet that I have seen, for I have never learned the Hebrew alphabet.

Archaic language features: I have heard that Quebecois French was some centuries behind what is spoken in France.
Well, of course not. We have to actually build them. Just saying it does nothing.

Assuming by houses you mean the high-density housing people are actually saying would help alleviate the issue.
True, if I was a really smart sociopath and a good actor I'd just mask and act like I'm normal so I could extract friendship and true love from people by giving them the same
As a Google outsider, that's not at all the impression I got from the paragraphs.

This:

> It's not held to THAT high a standard. We absolutely commit janky MVPs and iterate.

seems to very directly address this:

> The opposite of move fast, build a shitty prototype and iterate is a deliberate problem solving approach undertaken by the highest caliber of engineers. The actual challenges to be addressed are effectively addressed right at the design stage.

If your claim is that "Well, if you look at the codebase AS A WHOLE, there's absolutely no iteration and shitty prototypes, it's all designed right from the start."... well, I can't see any way that codebase came into existence without being built up by individual projects and changesets.

So, yanno, when folks on the ground report that individual projects and changesets/PRs/whatever ARE using the "Commit something barely serviceable, test it out, and iterate." process, statements like "We always get the design right before we write even a single line of code!" definitely come off as a circlejerk.

Google's a very large software house, it has a very exclusive hiring process, and it (reportedly) has internal tooling that's very well-adapted for the problems a company of its size faces. But Google is still hiring from the same pool of programmers as everyone else, and the odds that zero of those that it hires will work best with the "Get something out there to field-test, and use the test results to make it more suited for field use." method of development are absolutely zero. Given Google's size, the odds that zero of those will never be able to negotiate to work in the way they work best are ALSO zero.

(And -frankly- I expect that this method of development gets used a lot in the company. You can burn an assload of time on simulators (and what is the "What if?" game, but a in-brain simulator?), but in the realm of software, it's not-infrequently the case that the simulator with the best ROI is real-world deployment.)
The ETA 2836 is another very common self-winding movement.
genetics, skill, ability, mindset.

sure more money translates to better coaching probably, but it seems that ceteris paribus better players can spend many years being better.

so basically rising players have an logarithmic curve with an asymptote. and sure they are getting better and higher, but they should estimate their peak. especially because even if current top players retire younger ones can easily take the spot from more experienced players.

all in all the current ranking system is very efficient (lots of data points, it's not like boxing where matches are organized after some initial success to maximize the money made, slowly take on opponents that seem beatable or otherwise lucrative, etc.)

tennis and other very athletic individual sports are mature (progress is mostly due to technology, dietary know-how, better data-driven coaching), and there's just no big chance of an underdog beating the numbers. (especially considering that the numbers are much better, again due to more and better data and compute)
> The reality is that the diver notices nothing unusual as they cross the event horizon

That doesn't mean that he actually crosses it from our reference frame. Relativity is all about understanding that time is relative, that applies here as well, except that there is no connection between the two reference frame unlike regular space, so we can't say anything about how time flows inside of a black hole from our perspective.

Basically what I am saying is, you can't say whether the singularity has actually formed, since your reference frame is just as connected to the instant anything fell into the black hole as it is connected to the end state of the singularity. That makes it just as valid to say that things freeze the instant they touch the black hole as to say that they merge with the singularity the instant they touch it, since both are equally valid viewpoints from our perspective.
Any public entertainment jobs where the people at the top are famous
There's no issue with Congress interpreting laws here. The executive branch is (was). Which they have to do because how do you enforce a law that you do not have an interpretation of? If Congress disagrees with the judiciary's interpretation they can just pass a law that makes their interpretation the literal law.
To the external observer, the black hole is perfectly spherically symmetrical.¹ The center of mass of a spherically symmetrical object is always right in the center. Right where the singularity would be, if it weren’t for the fact that to the inside observer the singularity is now in the future at the end of time.²

These types of coordinate changes are one reason why the subject is considered so hard.

¹ Except very briefly as two black holes merge. Or in the case of a rotating black hole. Or potentially during the formation of the black hole. But those are all complications and the subject is difficult enough.

² Except for the fact that the singularity might not actually exist if the interior of the black hole is growing without bound in the timelike direction. See ER=EPR.
that doesn't work at scale though. the difference between dev, staging, and prod when there's a handful of services is fine. when there's 300 of them, and 200 of them are broken in the dev environment at any given time, that means you can't actually use the dev environment to do development in because the 300 other teams are also trying to do development in that same environment so their stuff is just as broken as your stuff.

so then you either have to accept that sometimes it's broken and just wait on it, or otherwise agree that staging should always have a working copy of Kafka, except that means the Kafka team can now no longer use staging to stage Kafka changes, so then they have to setup their own separate staging environment and then plumb sufficiently representative test data into that new staging, and then and then and then.
This is just using solar heat to reform methane from biogas. I was hoping it would be using solar heat for production of the reduced chemicals from water or CO2. This latter problem is much harder, but there have been proposals, for example using heat to reduce transition metal oxides with evolution of oxygen, then reacting the oxides with steam to make hydrogen.

M2O3 --> 2 MO + 1/2 O2

2 MO + H2O --> M2O3 + H2
It also has no good definition for its semantics when presented with a NaN.
but they were paid very well at least, right? whereas tennis seems like a money pit.
After way too many years of working on several sprawling Ruby and Rails projects, I would enjoy the everloving fuck out of working on this.
> I think we will have to wait and see what happens.

What will happen is that anytime someone doesn't like a regulation, they'll now have many, many jurisdictions in which to shop for a judge that will rule in their favor.
I worked in QA for the first 4 years of my career. There was a lot of creativity in “how to make an application/feature break”. Sure, most of the time I didn’t realize that 10 scenarios I would run through were moot because of how a feature was implemented. But often, that “creativity” would expose major issues that I had no idea about their root cause, but would drive significant (or important) changes to the product.

One of my favorites in my first couple of months in my career was testing a service that accepted user uploads and returned some value based on the upload. I thought “oh, I should just test a butt-load of invalid files”. Where am I gonna get a butt-load of invalid files for our service? I’ll just write a script that iterates and uploads everything under my `C:\Windows` folder. Discovered 2 bugs. One was that some random binary files there caused the parser the service was using to segfault and another about how the service stored those temp files before validating them. The first required involvement from a totally different team in the company because of “how serious it was”. As a fresh college hire at the time I got a ton of praise for “exposing such a critical buffer overflow” that went undetected for years (lol, I had no idea what I was doing but I took the praise). The latter was because the developer of the service never cleared their /tmp directory where they wrote user uploads before validating them. I ended up filling the VM disk with junk that took down the entire service.