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

Awesome! And thank you all for your projects and your hard work!

I hope the plugin directory get an overhaul too and a prominent place an the webpage. The plugin ecosystem was for me a huge benefit for Video.js

Even though some of them are outdated, they were a good source of inspiration.


Absolutely! The community has always been the strongest part of the project.

In the new version the core player itself is built as many composable components rather than one monolithic player, so we're going to invite more people to contribute their "plugins" to the core repo as more of those composable components. Versioning plugins and keeping them up to date has always been a challenge, so we're thinking this will help keep the whole ecosystem working well together.


Has any competitor copied anything from Deno?

Deno basically popularized the idea of a standalone JS runtime that primarily relies on standard Web APIs over "in-house" APIs like Node, although we can say that those standard APIs didn't exist yet when Node was created and for most of its rising period.

Not only that, but they helped push for new web APIs and language features for server runtimes, like URLPattern

I don't think I'd go as far as "copying" but Deno was the first to aggressively push for web standards in server-side runtimes and certainly helped accelerate getting them adopted in that environment.

I work at Cloudflare on Workers (but infrequently work on our runtime) and I've always been pretty impressed with Deno. Their recent-ish support for built-in OpenTelemetry is something we've been wanting to do for a while and have been working on, but Deno was able to build a good implementation of that in that time.


Cloudflare Workers was actually pushing for web standards on the server side several months before Deno was announced. :)

Though Ryan of course had a lot more clout from day 1 than I did.


(I love cloudflare workers and thanks for that), but I do think that credit is where its due and Deno's push for server side web standards also helped the general ecosystem.

I think it’s fair to say that work on the experimental-strip-types option in Node was inspired/energized by a desire to try to catch up with the DX improvements found in Deno for Typescript-first development that is now the norm.

I always thought Deno was more or less trying to copy the Cloudflare (edge) runtime, but decided incompatibility was a good idea. The ecosystem bifurcation was the mistake, which they came around on, but it was already too late by then.

Wait until a big company buy them. That seems not to happen.

Anthropic acquired Bun, so money should not be a problem for the next couple of years.

Anthropic, the company that actually has much worse revenues and likely mislead the public? [1] That Anthropic? The same Anthropic that has taken billions of gulf state money where the countries are on the verge of divesting itself from the US or fear of potentially losing their refineries + oil fields for at least 50 years? That same Anthropic?

This house of cards is about to collapse and lot of "smart" devs are going to act shocked when the water recedes.

The same thing always happens: companies "adopt" open source then, unless you have monopoly, money problems eventually appear and leadership sees this lovely team with "bloated budget" in the bylines.

[1] https://www.reuters.com/commentary/breakingviews/anthropic-g...


I hate it when people use commentary articles as fake sources for their points. It's even more aggravating when the "journalists" are making points that play to the ignorance and outrage of the reader, as they know those readers are the easiest to bait for clicks and mislead. For instance, how is Anthropic claiming that its total revenue since January 2025 as $5 billion contradict that its expected run-rate revenue for the year 2026 is $19 billion?

> Anthropic claiming that its total revenue since January 2025 as $5 billion contradict that its expected run-rate revenue for the year 2026 is $19 billion?

Isn’t the “exceeding $5BN” comment a lifetime revenue? … on $30BN (edit: previously said spent) raised (or something ridiculous.)

A lot of the commentary on the frontier model companies is based on how much money they’ve spent to the relatively small amount they’ve made in return, and the skepticism, especially given almost continuous reporting, that deploying AI in a variety of situations doesn’t seem to yield favorable business outcomes. OpenAI shifting to enterprise / coding type stuff this week seems, also, potentially informative. Is Gen AI actually useful for anything but code? Signs keep pointing to no… and even then, we’re in the early stages of figuring out how to build without destroying everything… something Amazon just recognized as possible with their recent shopping outage.


> on $30BN spent (or something ridiculous.)

Where did you get that figure? The filing says 10 billion has been spent on training and serving customers.


Whoops! Not spent, raised.

the sky is falling...

It also means the Bun team is no longer in control. Acquisition has a similar time frame and we've seen numerous projects chart a similar path to irrelevance.

LibreOffice ?


Yes, that is one of the major offenders. It is very awkward to pronounce in many languages.


I speak two languages (English and Russian) and have never found their name to be awkward. This is the first time, actually, that I've seen somebody say they don't like their name.


A good indicator is that the Wikipedia page even has pronounciation information: https://en.wikipedia.org/wiki/LibreOffice

What other major software has that?


> What other major software has that?

Linux?

EDIT: Also Qt, MySQL, SQLite, GIMP (rather unnecessarily), ...


Somewhat disappointingly, it’s just pronounced exactly the way it’s spelled: LEE-bruh-OFF-iss

Ref: https://youtu.be/YHBve8v13VY?si=Bql2vH6C4goZN_kX

From your comment somehow I was expecting something a bit more exotic


TIL it's 'bruh'. Until today I thought it was 'bray'


Curious on what languages have a hard time saying Libre.

Every latin-derived language (which are most of the western languages) can pronounce it naturally, and even English speakers can approximate it well enough to be understood (even though they're incapable of pronouncing the non-retroflex `r`).


> even English speakers can approximate it well enough to be understood

I'd go for "LEE-broffis" which I don't think is all that hideously far away?


Wait, it's not leeb-er?


The "bre" in "libre" is pronounced similarly to "zebra". Kinda. It'll get you in the ballpark, which is good enough for an Anglo.

"This Hour has 22 Minutes" had a great sketch where both a Francophone (Gavin Crawford impersonating Chantal Hebert) and an Anglo (I forget who) were stumbling over proper nouns from the opposite language. The joke was that both were trying too hard to pronounce things "properly". It came off as inauthentic and awkward.


And than you fix the produces shit, got high blood pressure and think "damn it,how I would love to yell at that employee"


You say that, but it's been better than most employees for a year or so ( *for specific tasks, of course. It's still not better than "an employee" )


Not true at all with frontier models in last ~6 months or so. The frontier models today produce code better than 90% of junior to mid-level human developers.


Just like a real employee!


And just like a real employee, this makes it work worse.

(Old study, I wonder if it holds up on newer models? https://arxiv.org/pdf/2402.14531)


Interesting, I've actually found swearing at the dumbass bots to give better results, might just be the catharsis of telling it it's a dumbass though.


There's certainly catharsis, but I'm taking the opportunity to train myself to be less frustrated by apparently stupid responses in the hope it makes me a more effective communicator towards humans.

My worst experience of co-workers (and in contract work, customers) is when they treat me the way I used to treat ChatGPT. If I can make sure I myself am never like that, just by training myself to different behaviour through my use of the infinitely patient LLMs, all the better. :)


Nothing, that is why it change his life ;-)


Not people, that post is from OpenClaw... 100% ;-)


100% a precursor to a follow up post like "I asked OpenClaw to write me a blog post about how it's changing my life and it hit the top of HackerNews"


I wait for frenchhub, in french only, no english translation, nothing. Typical french. Greetings from you EU neighbor.


A lot of the documentation in La Suite seems to be available in English.


> frenchhub

*Lieu de Rencontre Français Pour le Contrôle de Version


That is what the AI said:

1. Classic Coding (Traditional Development) In the classic model, developers are the primary authors of every line.

    Production Volume: A senior developer typically writes between 10,000 and 20,000 lines of code (LOC) per year.
    Workflow: Manual logic construction, syntax memorization, and human-led debugging using tools like VS Code or JetBrains IDEs.
    Focus: Writing the implementation details. Success is measured by the quality and maintainability of the hand-written code. 
2. AI-Supported Coding (The Modern Workflow) AI tools like GitHub Copilot and Cursor act as a "pair programmer," shifting the human role to a reviewer and architect.

    Production Volume: Developers using full AI integration have seen a 14x increase in code output (e.g., from ~24k lines to over 810k lines in a single year).
    Work Distribution: Major tech leaders like AWS report that AI now generates up to 75% of their production code.
    The New Bottleneck: Developers now spend roughly 70% of their time reviewing AI-generated code rather than writing it.

I think realistic 5x to 10x is possible. 50.000 - 200.000 LOC per YEAR !!!! Would it be good code? We will see.


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

Search: