Hacker Newsnew | past | comments | ask | show | jobs | submit | Scubabear68's commentslogin

I am not surprised, but disappointed, to see something like the CHIPS Act be used for something which is still in ultra-super-unbelievably-early-research-phase. Put more candidly, something not currently useful like Quantum computing.

Looks like just a handout to IBM.


The administration fired the original CHIPs Act team and so the new team might not be up to speed.

I have been using an 8GB Macbook Air M1 for non-development work, and it has been fantastic.

Macos really excels at managing memory very well.


I used an M1 Air for developing iPhone Apps for years and it worked great. Not "wow" fast but I never had a complaint about it.

Heck, on Windows it would be 4GB if you're lucky.

I went to Holmdel High and my girlfriend's dad was an engineer at the Bell Labs Holmdel location. As it turns out he invented a little something called Adaptive Delta Modulation (aka Abate Delta Modulation) for his Doctorate Thesis in 1968.

They definitely had brain power at the Holmdel location too.


"AI coders submitting 25 PRs within an hour of an issue being filed, GitHub bears the brunt of that....".

What "brunt"? These are not large numbers.


Before AI coding, a GitHub issue might get one or two PRs after six months.

AI coding has made this orders of magnitude bigger.

The individual numbers are small, but they add up quickly.


Maybe I am really dense, but a single issue getting 2 vs 25 PRs seems to be no practical difference.


Well two in six months vs 25 in one hour. So that's a 54,000x increase.

But also, each PR kicks off a bunch of CI work, often in GitHub Actions.


Precisely.

If Microsoft can't scale something like Git 14x, then the problem is with Microsoft.


I really don't understand people saying that this is due to AI commits and it is all the volume's fault.

A volume increase that is a single order of magnitude (which 14x is) should not result in this level of failures.

When I compare what Github does and the volumes vs social media companies, payment companies, video platforms, etc, it just doesn't make sense that it is just a volume problem.

It looks a lot more like a platform that already has baseline issues that are compounded by increased volume.


What happens at your job if there's suddenly 14 times as much load?


> What happens at your job if there's suddenly 14 times as much load?

You mean like every startup ever that has been successful?

And for a service that is heavily text bound? A 14x increase would not be a big deal.


My roommate circa 1989 had a bunch of Apple II’s with multiple modem cards per machine to run a bulletin board. Not sure why an Apple II could support multiple users logging into the BBS via multiple modems but DOS based machines could not.


A function call is not necessarily an indirection. Basic premise of the blog is wrong on its face.


1. "Indirection" can be logical, or runtime.

2. Please read the blog. That's literally what is said.


Did you read the article? The author makes exactly that point.


[flagged]


Why do you mention lifetimes here? They are exclusively a compile-time pointer annotation, they have no runtime behavior, thus no overhead.

Dynamic dispatch in general is much, much faster than many people’s intuition seems to indicate. Your function doesn’t have to be going much at all for the difference to become irrelevant. Where it matters is for inlining.

Dynamic dispatch in Rust is expected to be very slightly faster than in C++ (due to one fewer indirections, because Rust uses fat pointers instead of an object prefix).


The signature check is actually not uncommon, particularly if the vote is contested or a recount done.

We had a vote thrown out of an election several years ago, the woman died right after the election, the signature on the card looked nothing like hers and was probably done by her daughter.

That said all indications are voter fraud is not any kind of wide spread problem in the United States.


Many years ago I was doing due diligence on a point of sale hardware company, I had to head up to an acquisition they had done. People bitched and moaned about the level of physical security added, and when I asked them why they were so upset, they told me to go to the loading dock in the back.

The loading dock was kept completely open "because it's hot and we don't have A/C back here!".


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: