frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Plasma Bigscreen – 10-foot interface for KDE plasma

https://plasma-bigscreen.org
112•PaulHoule•1h ago•36 comments

this css proves me human

https://will-keleher.com/posts/this-css-makes-me-human/
149•todsacerdoti•3h ago•53 comments

C# strings silently kill your SQL Server indexes in Dapper

https://consultwithgriff.com/dapper-nvarchar-implicit-conversion-performance-trap
47•PretzelFisch•2h ago•31 comments

Show HN: The Roman Industrial Revolution that could have been (Vol 2)

https://thelydianstone.com/volume-2
28•miki_tyler•2h ago•15 comments

The Shady World of IP Leasing

https://acid.vegas/blog/the-shady-world-of-ip-leasing/
55•alibarber•4h ago•27 comments

Galileo's handwritten notes found in ancient astronomy text

https://www.science.org/content/article/galileo-s-handwritten-notes-found-ancient-astronomy-text
28•tzury•1d ago•1 comments

Hardening Firefox with Anthropic's Red Team

https://www.anthropic.com/news/mozilla-firefox-security
477•todsacerdoti•13h ago•137 comments

I'm 60 years old. Claude Code has ignited a passion again

78•shannoncc•1h ago•35 comments

Show HN: Moongate – Ultima Online server emulator in .NET 10 with Lua scripting

https://github.com/moongate-community/moongatev2
225•squidleon•11h ago•130 comments

Launch HN: Palus Finance (YC W26): Better yields on idle cash for startups, SMBs

37•sam_palus•7h ago•61 comments

Show HN: Kula – Lightweight, self-contained Linux server monitoring tool

https://github.com/c0m4r/kula
7•c0m4r•1h ago•1 comments

Tech employment now significantly worse than the 2008 or 2020 recessions

https://twitter.com/JosephPolitano/status/2029916364664611242
713•enraged_camel•7h ago•485 comments

CT Scans of Health Wearables

https://www.lumafield.com/scan-of-the-month/health-wearables
185•radeeyate•11h ago•39 comments

What canceled my Go context?

https://rednafi.com/go/context-cancellation-cause/
8•mweibel•2d ago•2 comments

Ada 2022

https://www.adaic.org/ada-resources/standards/ada22/
108•tosh•5h ago•19 comments

Entomologists use a particle accelerator to image ants at scale

https://spectrum.ieee.org/3d-scanning-particle-accelerator-antscan
100•gmays•9h ago•17 comments

Astra: An open-source observatory control software

https://github.com/ppp-one/astra
80•pppone•9h ago•20 comments

LibreSprite – open-source pixel art editor

https://libresprite.github.io/
256•nicoloren•16h ago•84 comments

Art Bits from HyperCard

https://archives.somnolescent.net/web/mari_v2/junk/hypercard/
53•TigerUniversity•3h ago•14 comments

Polar Factor Beyond Newton-Schulz – Fast Matrix Inverse Square Root

https://jiha-kim.github.io/posts/polar-factor-beyond-newton-schulz-fast-matrix-inverse-square-root/
5•ibobev•2d ago•0 comments

A tool that removes censorship from open-weight LLMs

https://github.com/elder-plinius/OBLITERATUS
117•mvdwoord•11h ago•49 comments

Workers who love ‘synergizing paradigms’ might be bad at their jobs

https://news.cornell.edu/stories/2026/03/workers-who-love-synergizing-paradigms-might-be-bad-thei...
508•Anon84•12h ago•288 comments

Multifactor (YC F25) Is Hiring an Engineering Lead

https://www.ycombinator.com/companies/multifactor/jobs/lcpd60A-engineering-lead
1•multifactor•8h ago

We might all be AI engineers now

https://yasint.dev/we-might-all-be-ai-engineers-now/
167•sn0wflak3s•16h ago•273 comments

Anthropic, please make a new Slack

https://www.fivetran.com/blog/anthropic-please-make-a-new-slack
190•georgewfraser•5h ago•170 comments

Analytic Fog Rendering with Volumetric Primitives (2025)

https://matejlou.blog/2025/02/11/analytic-fog-rendering-with-volumetric-primitives/
81•surprisetalk•1d ago•7 comments

Good Bad ISPs

https://community.torproject.org/relay/community-resources/good-bad-isps/
96•rzk•11h ago•29 comments

The disappearing Form D (2018)

https://techcrunch.com/2018/11/07/the-disappearing-form-d/
11•eatonphil•2d ago•1 comments

Global warming has accelerated significantly

https://www.researchsquare.com/article/rs-6079807/v1
962•morsch•11h ago•949 comments

Show HN: Claude-replay – A video-like player for Claude Code sessions

https://github.com/es617/claude-replay
64•es617•9h ago•25 comments
Open in hackernews

TypeScript 6.0 RC

https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/
81•johnz•5h ago

Comments

culi•4h ago
For anyone who isn't aware, TypeScript does not use semantic versioning.

Though TypeScript 7.0 will be significant in that it will use the new Go compiler

tshaddox•1h ago
Semantic versioning seems slightly weird to even apply to something like TypeScript. You could have patch releases that fix actual compiler crashes, sure, but what is a minor release?

Surely any new feature that causes code to fail to type check when it previously would pass (or vice versa) would have to be considered a breaking change.

A similar thing applies to code formatting tools like Prettier, or any linter.

spankalee•1h ago
Semantic versions would at least be playing nice with how npm manages version ranges. If every release of TypeScript is breaking, then you should use major versions so that `npm update` doesn't break your project.

Yes, typescript would be at version 60 now. No, that's not a problem at all. Numbers are free.

ukuina•24m ago
> Numbers are free.

Someone please tell the LLM naming committee.

joshkel•1h ago
Appreciate the reminder (the lack of SemVer has thrown me in the past). In this case, 6.0 is a bigger change than normal:

> TypeScript 6.0 arrives as a significant transition release, designed to prepare developers for TypeScript 7.0, the upcoming native port of the TypeScript compiler. While TypeScript 6.0 maintains full compatibility with your existing TypeScript knowledge and continues to be API compatible with TypeScript 5.9, this release introduces a number of breaking changes and deprecations that reflect the evolving JavaScript ecosystem and set the stage for TypeScript 7.0.

pscanf•4h ago
As a user, I'm of course very excited about v7. As a developer of an app that _integrates_ TypeScript, however, I feel a bit uneasy seeing the API feature still marked as "not ready" on the roadmap.

On the other hand, I can understand leaving it as the last thing to do, after the foundation has set. Also, the TypeScript team has really done an amazing job all these years with backward compatibility, so that is extremely reassuring.

Maybe my uneasiness is just impatience to get to use the sped-up version in my app as well! :)

tanepiper•3h ago
FWIW I tried it with the VSCode preview in two monorepos we have - one frontend and one backend GraphQL servers with complex types - absolutely no issues (except one breaking change in tsconfig with baseUrl being removed) and fast compile times.
silverstream•3h ago
Same experience here with a pnpm workspace monorepo. The baseUrl removal was the only real friction — we were using it as a path alias root, had to move everything to subpath imports.

  The moduleResolution: node deprecation is the one I'd flag for anyone not paying attention yet. Switching to nodenext forced us to add .js extensions to all      
  relative imports, which was a bigger migration than expected.

  Compilation speed improvement is real though. Noticeably faster on incremental builds.
spankalee•1h ago
As a developer that integrates typescript into client-side web pages and writes lots of custom plugins, I'm extremely nervous about the port to Go.

I think the last estimate I saw was the the Go port compiled to WASM was going to be about triple the size of the minified JS bundle.

tmaly•4h ago
I had no idea they were using Go to write a compiler.
alembic_fumes•4h ago
> strict is now true by default

I would still have a full head of hair if this had been the case since the beginning. Nonetheless I am glad that we got here in the end.

steve_adams_86•3h ago
I came to point that out too. What an awesome development. I think this will have a meaningful impact on the general quality of TS projects over the coming years.
369548684892826•3h ago
Just use deno
Analemma_•2h ago
TypeScript never would’ve taken off if it had been strict from the beginning, it would’ve been just another forgotten gravestone next to Dart and CoffeeScript. I’m not saying those are bad languages, they’re not, but anything other than a very slow and gradual opt-in transition was just a non-starter. It was painful, but TypeScript played the long game.
chrysoprace•1h ago
If it had been, maybe I wouldn't have had to spend years getting buy in for turning on that setting in my team's codebase.
mdtrooper•2h ago
What has always bothered me about TypeScript are union types. If you have a function that receives a parameter such as ‘Dog | Cat’, you cannot separate it. For example:

type Dog = { bark: () => void }

type Cat = { meow: () => void }

function speak(animal: Dog | Cat) {

    if (‘bark’ in animal) {

        animal.bark();

    } else {
        animal.meow();
    }
}

Okay, okay, I know you can filter using ‘in’ to see if it has methods, but in real life, in a company where you have a colleague (who is a golden boy) who writes over-engineered code with hundreds of interfaces of interfaces, you don’t want to spend time searching through the files to find every element that is in the union type.

Whereas in Rust it does:

struct Dog { name: String, }

struct Cat { name: String, }

enum Animal {

    Dog(Dog),

    Cat(Cat),
}

fn process_animal(animal: Animal) {

    match animal {

        Animal::Dog(dog) => {

            println!(‘It is a dog named {}’, dog.name);

        }

        Animal::Cat(cat) => {

            println!(‘It is a cat named {}’, cat.name);

        }
    }
}

I think TypeScript should add a couple of lines of code to the generated JavaScript to do something like:

type Dog = { bark: () => void }

type Cat = { meow: () => void }

function speak(animal: Dog | Cat) {

    if (animal is Dog) {

        animal.bark();

    } else {

        animal.meow();

    }
}
tshaddox•2h ago
The idiomatic way to do this in TypeScript is with discriminated unions. You’re basically just giving the type system an extra property that makes it trivial to infer a type guard (while also making the runtime check in the compiled JavaScript foolproof).
culi•1h ago
This does act exactly as a discriminated union. The code works exactly as written.
zem•1h ago
this post on union types versus sum types is worth a read (the tl;dr is that they both have their uses and one is not strictly better) https://viralinstruction.com/posts/uniontypes/
epolanski•1h ago
You need a tagged union for this in typescript.
spankalee•1h ago
You're talking about adding a runtime feature. TypeScript doesn't do that anymore. It can't control what properties are on objects or add new ones - you do that yourself in the standard JavaScript portion of the language. TypeScript only lets you describe what's there.

As a sibling said, discriminated unions are they way to go here. You can also add custom type guard functions if you can't control the objects but you want to centralize the detection of the types, but it's better to let TypeScript do it itself so that you don't mess something up with a cast.

littlecranky67•1h ago
Typeguard is what you are looking for: function isDog(animal: Dog | Cat): animal is Dog { return "bark" in Dog }

Then: isDog(animal) ? animal.bark() : animal.meow() You get full type narrowing inside conditionals using typeguards.

culi•1h ago
You don't even need that. The code exactly as presented acts as a discriminator. TypeScript is smart enough to handle that logic in the if block and know whether animal has been validated as Dog vs Cat. GP is complaining about a feature that already exists in TypeScript
littlecranky67•1h ago
It depends how you construct Dog and Cat. With Javascripts dynamic prototype chain, you could never know for sure.
culi•1h ago
Try it

https://www.typescriptlang.org/play/?#code/C4TwDgpgBAIg9gcyg...

reitzensteinm•25m ago
type Mutt = Dog & Cat

const imposter: Mutt = { bark: () => console.log("woof"), meow: () => console.log("meow"), }

You're both misunderstanding parent's point as well as the original point. Nobody ever claimed your link wouldn't compile.

castral•1h ago
You can literally do what your generated example does using a type guard. You can also use method overloaded signatures if you dont want to expose your API consumers to union types.
culi•1h ago
Your first code block works exactly as you would expect and has been working like that for many years

https://www.typescriptlang.org/play/?#code/C4TwDgpgBAIg9gcyg...

paulddraper•1h ago
You're looking for a discriminated union [1], which idiomatically:

  type Dog = { bark(): void; type: 'dog' }

  type Cat = { meow(): void; type: 'cat' }

  function speak(animal: Dog | Cat) {
    if (animal.type === 'dog') {
      animal.bark()
    } else {
      animal.meow()
    }
  }
Generally speaking, TypeScript does not add runtime features.

TypeScript checks your use of JavaScript runtime features.

[1] https://www.convex.dev/typescript/advanced/type-operators-ma...

jauntywundrkind•2h ago
My deepest thanks to one @AlCalzone for stepping up to Opus port Decorators to tsgo. https://github.com/microsoft/typescript-go/pull/2926

It would have been an affront to have a 6.0 that shipped without the means to work for so so many javascript frameworks/libraries. AlCalzone utterly saving the day.

I also am so so so thankful that maybe perhaps after what felt like a never ending dolldrums, we may finally be getting decorator support in some browsers. What a colossal relief it will be to see the progress of the language become manifest.

ukuina•20m ago
> Disclaimer: This is an entire day worth of Claude Opus tokens. I don't claim I understand how it works, but I did my best to direct Claude to minimize the baseline diffs, of which it removed quite a few.

TypeScript allows entirely LLM-coded PRs?

CuriousRose•1h ago
I am hoping that eventually there will be some agnosticism with the language server. Currently they all seem to rely on Node which in my opinion is rapidly being outclassed by Bun in terms of resource usage. It would be great to eventually be able to pick what runtime they use in VS Code/Cursor to reduce energy drain on my laptop when working on the go.
djrenren•1h ago
The typescript language server (along with the rest of the compiler) is being rewritten in go for Typescript 7. This work has been going on in parallel with the work on 6.0. The go port has most features of 6.0 already and you can follow its progress and read more about it here:

https://github.com/microsoft/typescript-go

CuriousRose•1h ago
Sure, but instead of waiting another year for this to be launched - with a beta version precaution and inevitable bugs - why not remove the limited hard-coded Node paths and references now and ship something 80:20?
djrenren•56m ago
If it’s a simple change, they might accept a PR. If it isn’t, well that’s your answer. Not worth allocating engineers for it.
ianberdin•16m ago
No way I turn it on. Not a joke.