←back to thread

Ask HN: Abandoned/dead projects you think died before their time and why?

358 points ofalkaed | 4 comments | 11 Oct 25 22:16 UTC | HN request time: 0.289s | source

Just curious and who knows, maybe someone will adopt it or develop something new based on its ideas.
Show context
piskov ◴[12 Oct 25 03:59 UTC] No.45555096[source]▶
Microsoft Silverlight.

Full C# instead of god forbidden js.

Full vector dpi aware UI, with grid, complex animation, and all other stuff that html5/css didn’t have in 2018 but silverlight had even in 2010 (probable even earlier).

MVVM pattern, two-way bindings. Expression Blend (basically figma) that allowed designers create UI that was XAML, had sample data, and could be used be devs as is with maybe some cleanup.

Excellent tooling, static analysis, debugging, what have you.

Rendered and worked completely the same in any browser (safari, ie, chrome, opera, firefox) on mac and windows

If that thing still worked, boy would we be in a better place regarding web apps.

Unfortunately, iPhone killed adobe flash and Silverlight as an aftermath. Too slow processor, too much energy consumption.

replies(4): >>45555141 #>>45555576 #>>45555725 #>>45557264 #
drnick1 ◴[12 Oct 25 04:10 UTC] No.45555141[source]▶
I am happy this one died. It was just another attempt by Microsoft to sidestep open web standards in favor of a proprietary platform. The other notorious example is Flash, and both should be considered malware.
replies(4): >>45555236 #>>45555238 #>>45556687 #>>45558274 #
Rohansi ◴[12 Oct 25 04:30 UTC] No.45555238[source]▶
Open web standards are great but consider where we could have been if competition drove them a different way? We're still stuck with JavaScript today (wasm still needs it). Layout/styling is caught up now but where would we be if that came sooner?
replies(1): >>45555658 #
motorest ◴[12 Oct 25 06:02 UTC] No.45555658[source]▶
> Open web standards are great but consider where we could have been if competition drove them a different way? We're still stuck with JavaScript today (wasm still needs it). Layout/styling is caught up now but where would we be if that came sooner?

Why do you think JavaScript is a problem? And a big enough problem to risk destroying open web standards.

replies(3): >>45556173 #>>45556633 #>>45560043 #
piskov ◴[12 Oct 25 09:01 UTC] No.45556633[source]▶
The same reason Typescript exists
replies(1): >>45556885 #
1. motorest ◴[12 Oct 25 09:54 UTC] No.45556885[source]▶
> The same reason Typescript exists

TypeScript exists for the same reason things like mypy exists, and no one in their right mind claims that python's openness should be threatened just because static typing is convenient.

replies(1): >>45557740 #
2. nurbl ◴[12 Oct 25 12:28 UTC] No.45557740[source]▶
Though in principle they serve similar purposes there are some big differences though. Python with types is still just python. Typescript is a different language from JS (guess it a superset?) and it being controlled by a large company could be considered problematic.

I suppose JS could go in the same direction and adopt the typing syntax from TS as a non-runtime thing. Then the typescript compiler would become something like mypy, an entirely optional part of the ecosystem.

replies(2): >>45562313 #>>45574089 #
3. motorest ◴[12 Oct 25 21:55 UTC] No.45562313[source]▶
> Python with types is still just python. Typescript is a different language from JS (guess it a superset?)

No, it's the exact same thing. TypeScript adds support for type annotations, and removing these annotations leads to JavaScript. See how Node.js added support for TypeScript by implementing type stripping in v22.

https://nodejs.org/api/typescript.html#type-stripping

4. joquarky ◴[13 Oct 25 22:39 UTC] No.45574089[source]▶
If your IDE supports JSDoc, then TS isn't needed for basic type constraints.

https://jsdoc.app/