simultsop

I believe everyone starts a thing with ambition: "I will fix the world".

They get fixed instead!

Unfortunately, "things" begin nicely until it gains major attention. Then it loses most of the nice things.

The idea of a unified computer, resembles also with the idea when iPhone merged, calculator, mp3 player and phone.

With ubuntu's try a decade ago, https://www.indiegogo.com/projects/ubuntu-edge#/ it was obvious there is a market for this. But the ecosystem chain beats it all. Everyone will wait for their favorite OS to catchup.

In a utopic scenario, yes, you fix type-checking and you can live happily ever after.

In an interoperable environment, when additional programming languages/teams are in play, which is very frequent nowadays. You have the problem of centralizing types/entities/schemas, reused types, partial types, and union types, and you can keep the story on.

At some point, instead of typing being an invisible tool, it becomes the tool. Then you superset the tool to other languages, because they are in an immutable state. Another language will emerge with dynamic typing in decades then people will take the same spiral and spend more time to reason wages.

We have to do what's best for our benefit.

In a world where everything means everything, fighting ambiguity is not an easy task. Hence the refactoring.

> When there's a bug, there's no going back to an older version.

This practice is developed by the industry for a reason. It would be really silly to hear people running AI in Windows XP.

> Most users are giving up.

Rust is pretty new, users shouldn't rush to switch a stack because of hype. It takes time for languages to mature, even more for the ecosystem.

Leaking bugs, I believe, do not relate to static typing or dynamic typing; it mostly involves deployment. Your types might match, but you would still leak bugs in dependencies :/

From a CI/CD perspective, you should make sure that on updates, things won't break. As others suggest, a maintainable project would have test suites.

Except if you aim to have a program that you will never update again. Write the code once, compile it, and archive it. When you decide to keep that program available to potential clients, be prepared to back up dependencies, the OS it runs on, and everything that makes it operable. If there is a breaking change in the ecosystem of that program, it will break it.

TLDR.

The outcome is the same, statically typed or dynamically. In both cases one need to perform refactoring in case of breaking changes.

The branding looks quiet strange and very conflicting with voidzero.dev

Bad. We thought that something would be fixed when they brought them to justice. Everything is on the same pace or even accelerated.

In the virtual world, I do not believe these meme accounts will ever vanish, nor will platforms give you the magic button to not see them.

He's just using a weight for another round of marketing. If someone needs friends, they probably find some.

No, we used a tool, and we've got addicted. Some fought that addiction, others are not figuring out what is going on yet. Free market and shiny gadget.

It's a pity, of all web resources advancements, js, css, runtimes, web engines. HTML was the most stagnant aspect of it, despite the "HTML5" effing hype. My guess is they did not want to empower HTML and threaten SSR's, or solutions. I believe the bigest concern of not making a step is the damned backward compatibility. Some just wont budge to move.

there are underlying differences between C++, Rust, JS. The aim of libraries are re-usability. To call a small library shallow, its your choice. If you want to drag a helpers folder with you anywhere its your choice. JS does not have the fate to have language updates as C, Rust. Code lives in many envoirements and is in many cases polyfilled/transpiled.

You are welcome to shape your point of view in this free world.

Checkout slidevjs, that may also look shallow to you. The eco-system is very open. It will never be as C++ or Rust. I believe everyone is happy where they are.

As far as I understand, this might be is the best tool for the guy who acquires a SaaS and have no clue how to develop/tweak stuff. Again still have no clue how you enable this or do you still have tilt in production. Marketing is not a big deal for tilt as far as I understand.

It is a re-presentation of the same collection. These are marvels of collaboration.

Anthony Fu (https://antfu.me/projects).

Should to be known widely.

The guy is a living legend.

To every SE out there: “Insanity is doing the same thing over and over and expecting different results.”

These practices have been an ongoing matter since 1975.

or decided to increase consistency at some point. It will be interesting to see other generations approach to changes.

I don't believe any platform will be able to gain massive trust anymore. After facebook had all possibilities and resources and yet failed to provide. All niche solutions end up on the giant whale's stomach after awhile.

In my opinion it is decentralized startup spring rather. Just because all do not go mainstream and some can't notice, it does not mean they do not exist. Next 20 years there'll be thousands tiktoks potentially.

Interesting. Nowdays people put more money to lure devs to their platforms.

Imagine Apple even got paid by developers and not pay them

I think so. But I meant no work contracts and lots of employees.

In the very end. It all boils down to who got the developers on platform for free. ( From Apple's context, while devs cost a lot, they just marketed well and even made them pay something to list apps )

Bet everyone has a different prespective. And thats what makes this world amazing. One is really free to pick any.

Also looks like, Nokia worked on this archive intensively starting 2023. Seems like a whole retrospective project. Amazingly inspiring.

I wonder if the software empowering this data is an open source project?

I was wondering if he's a new startup founder :/