beart (u/beart) - Readit News

beart commented on U.S. government takes 10% stake in Intel cnbc.com/2025/08/22/intel... · Posted by u/givemeethekeys

andrewflnr · a day ago

You don't think $8.9B would do it?

beart · a day ago

This link contains a graph of fab costs over time. It looks like 9 billion might get you a cutting edge fab 15-20 years ago. but that's just the fab.

https://semiwiki.com/forum/threads/how-to-build-a-20-billion...

beart commented on 95% of Companies See 'Zero Return' on $30B Generative AI Spend thedailyadda.com/95-of-co... · Posted by u/speckx

amluto · 2 days ago

I’d like to see a competent AI replace the time that doctors and nurses spend tediously transcribing notes into a medical record system. More time spent doing the actual job is good for pretty much everyone.

beart · 2 days ago

But... that is the actual job. A clear medical history is very important, and I'm not ready yet to cut out my doctor from that process.

This reminds me of the way juniors tend to think about things. That is, writing code is "the actual job" and commit messages, documentation, project tracking, code review, etc. are tedious chores that get in the way. Of course, there is no end to the complaints of legacy code bases not having any of those things and being difficult to work with.

beart commented on Copilot broke audit logs, but Microsoft won't tell customers pistachioapp.com/blog/cop... · Posted by u/Sayrus

ocdtrekkie · 4 days ago

I would say "insecure by default".

I talked to some Microsoft folks around the Windows Server 2025 launch, where they claimed they would be breaking more compatibility in the name of their Secure Future Initiative.

But Server 2025 will load malicious ads on the Edge start screen[1] if you need to access a web interface of an internal thing from your domain controller, and they gleefully announced including winget, a wondeful malware delivery tool with zero vetting or accountability in Server 2025.

Their response to both points was I could disable those if I wanted to. Which I can, but was definitely not the point. You can make a secure environment based on Microsoft technologies, but it will fight you every step of the way.

[1] As a fun fact, this actually makes Internet Explorer a drastically safer browser than Edge on servers! By default, IE's ESC mode on servers basically refused to load any outside websites.

beart · 4 days ago

I've always felt that Microsoft's biggest problem is the way it manages all of the different teams, departments, features, etc. They are completely disconnected and have competing KPIs. I imagine the edge advertising team has a goal to make so much revenue, and the security team has a goal to reduce CVEs, but never the twain shall meet.

Also you probably have to go up 10 levels of management before you reach a common person.

beart commented on Node.js is able to execute TypeScript files without additional configuration nodejs.org/en/blog/releas... · Posted by u/steren

lbltavares · 7 days ago

Yes, it can't parse enums, for example.

beart · 4 days ago

I think enums are on their way out, and erasable syntax is one of the main reasons.

https://dev.to/ivanzm123/dont-use-enums-in-typescript-they-a...

They added an optional flag to disable enums (and a few other features) in 5.8

https://www.totaltypescript.com/erasable-syntax-only

beart commented on Node.js is able to execute TypeScript files without additional configuration nodejs.org/en/blog/releas... · Posted by u/steren

pjmlp · 7 days ago

jslint/tslint are an install away.

beart · 4 days ago

tslint has been deprecated for quite a long time now - from 2019: https://github.com/palantir/tslint/issues/4534

beart commented on The GPT-5 Launch Was Concerning blog.charliemeyer.co/the-... · Posted by u/csmeyer

coldpie · 15 days ago

> Only if you consider Sam Altman not serious

> Elon Musk[1], Sam Altman, or Marc Andreessen[2] ... these people are liars.

Bingo. These people are salesmen & marketers. Lying to sell a product (including gathering funding & pumping company stock) is literally the job description. If they weren't good at it, they wouldn't hold the positions they do.

beart · 15 days ago

Being a good salesperson does not require lying. It's not the job that's doing the lying, but the person lying to you.

beart commented on We shouldn't have needed lockfiles tonsky.me/blog/lockfiles/... · Posted by u/tobr

deepsun · 17 days ago

I don't understand how Maven's YOLO is different from NPM's range.

If you force a transitive dependency in Maven, then yes, some other library may get incompatible with it. But in NPM when people declare dependency as, say, ~1.2.3 the also don't know if they will be compatible with a future 1.2.4 version. They just _assume_ the next patch release won't break anything. Yes npm will try to find a version that satisfies all declarations, but library devs couldn't know the new version would be compatible because it wasn't published at that time.

And my point is that it's _exactly_ the same probability that the next patch version is incompatible in both Maven and NPM. That's why NPM users are not afraid to depend on ~x.x or even ^x.x, they basically YOLOing.

beart · 17 days ago

From my experience, this is a self-policing issue in the npm ecosystem. When major packages break semver, the maintainers take a ton of heat. When minor packages do it, they quickly fall out of the ecosystem entirely. It's not "YOLO"ing, but rather following the ecosystem conventions.

But anyway.. isn't that exactly the purpose of lock files? If you don't trust the semver range, it shouldn't matter because every `npm ci` results in the same package versions.

beart commented on We shouldn't have needed lockfiles tonsky.me/blog/lockfiles/... · Posted by u/tobr

whilenot-dev · 17 days ago

No tag other than latest has any special significance to npm itself. Tags can be republished and that's why integrity checks should be in place. Supply chain attacks are happening in open source communities, sadly.

beart · 17 days ago

I don't think you can republish to npm.

https://docs.npmjs.com/cli/v11/commands/npm-publish

> The publish will fail if the package name and version combination already exists in the specified registry.

> Once a package is published with a given name and version, that specific name and version combination can never be used again, even if it is removed with npm unpublish.

beart commented on We shouldn't have needed lockfiles tonsky.me/blog/lockfiles/... · Posted by u/tobr

Tainnor · 17 days ago

Maven artifacts are immutable, so the whole resolution is deterministic (even if hard to understand), unless you're using snapshot versions (which are mutable) or you use version ranges (which is rare in the Maven world).

beart · 17 days ago

Maven artifacts are not immutable. Some maven repositories may prevent overwriting an already published version, but this is not guaranteed. I've personally seen this cause problems where a misconfigured CI job overwrote already published versions.

npm used to allow you to unpublish (and may be overwrite?) published artifacts, but they removed that feature after a few notable events.

Edit: I was not quite correct. It looks like you can still unpublish, but with specific criteria. However, you cannot ever publish a different package using the same version as an already published package.

https://docs.npmjs.com/cli/v8/commands/npm-publish?v=true

https://docs.npmjs.com/policies/unpublish

beart commented on What will become of the CIA? newyorker.com/magazine/20... · Posted by u/Michelangelo11

pessimizer · a month ago

This seems like a very ominous-sounding way of saying that Democrats have been losing in the Supreme Court lately and Republicans have been winning.

beart · a month ago

This framing torments me. Political parties "win" and "lose"... It's the quality of life of our parents, children, neighbors, and alike that waxes and wanes by the judgment of these far-removed decision makers.