930 karma · joined March 5, 2024
They probably would've achieved enough to sustain Firefox development in perpetuity if they invested most of Google's money in a fund.
At least, if this information is public, someone can act on it and sandbox ffmpeg for their use case, if they think it's worth it.
I personally prefer to have this information be accessible to all users.
I think Qt really is 'just' missing more language bindings, and a better hot reload story for more people to use it. Lots of devs (specially Free Software devs) would prefer to use native toolkits, if the prototyping experience was similar to how Vite is for web frontend stuff, I think Qt would be used a lot more.
Are you sure about that?
I would be surprised if it was much above the US salary average, considering the global audience of HN.
I don't follow. Some of my most important friendships were built on forums and text-based communication. We never felt any need to have video calls. Some of them I met in person once, 15+ years after we started messaging each other, and we're great friends regardless.
I don't mean to say you're wrong in an absolute sense, but I can't relate to your post at all. Not a single one of my friends has video calls as their preferred method of socialization with online peers.
> I'm honestly not sure where all these hackernews commenters with low-dpi displays are coming from
I still see 1080p fairly often on new setups/laptops, basically, although 1440p and 4K are becoming more common on higher-end desktops. Then again, 1440p at 27" or 32" isn't really high dpi.
> One is hard-put to buy a developer-power laptop with a sub-2K display these days, even in the Windows world
I personally see a lot of 1080p screens on new gaming laptops too. Lots of people get those for work from what I see with my peers. When I sold my RTX 3060 laptop with a 1080p screen, most buyers wanted it for professional work, according to them.
> I'm honestly not sure where all these hackernews commenters with low-dpi displays are coming from
If anything, this is exactly the place where I'd expect a bunch of people to be rocking an older Thinkpad. :)
This is commendable, specially during times when libraries and programs aren't afraid of breaking changes and API churn.
> I think somebody who won't acknowledge that is either being intellectually dishonest, or has already had their higher cognitive functions rotted away by excessive reliance on LLMs to do their thinking for them.
This feels too aggressive for a good faith discussion on this site. Even if you do think that, there's no point in insulting the humans who could engage with you in that conversation.
> a slow-loading app isn’t just an annoyance. It’s a liability.
> the issues I was seeing with Next.js weren’t specific to Next.js. They were fundamental to React’s architecture.
> The real performance story isn’t splitting hairs over 3ms differences, it’s the massive gap between next-gen and React/Angular.
That apparently is not the case for a lot of people.
I think it's significant more convenient if your stack touches multiple programming languages. Otherwise you'd have to implement framing yourself for all of them. Not hard, but I don't see the benefit either.
> they also add a bunch of performance and complexity overhead over raw sockets
What performance overhead is there over raw sockets once you're past the protocol upgrade? It seems negligible if you connection is even slightly long-lived.
I'm not disagreeing with you per se, but those statements are subjective, not an objective truth. Lots of people fundamentally enjoy the process of coding, and would keep doing it even in a hypothetical world with no problems left to solve, or if they had UBI.
Please, there's no point in arguing like that. There's no need to mischaracterize or reword what another user is saying.
I don't think we'll get much further in this discussion if you consider yourself a fan of the FSL, a proprietary license. Your time will be better spent replying to other people.
That's exactly what my comment is addressing! People advocating for Free Software don't usually advocate that _only_ the software they use should be free; they advocate for the freedom of all users.
> I never claimed it was Free Software.
You did not, indeed. Sorry if my wording gave the impression I was trying to put claims in your post. That phrase is an answer to this question from you:
> Why do you object to FSL for this specific type of software
We object to it because it makes the software proprietary rather than free.
https://www.gnu.org/philosophy/free-software-even-more-impor...
That license restricts what you can do with the software due to a business interest of the author. Therefore, it's non-free or proprietary.
I agree it doesn't need to be called "source available"; it's just proprietary software.
My take is that you can get pretty far these days with a simple bytecode interpreter. Food for thought if your side project could benefit from a DSL!
Deno used similar wording in a tutorial for creating your own JS runtime using Rust and V8 bindings: https://deno.com/blog/roll-your-own-javascript-runtime
IMO the tutorial is still cool nonetheless, it's a fun subject.
Regarding AoS vs SoA, I'm curious about the impact in JS engines. I believe it would be a significant compute performance difference in favor of SoA if you use typed arrays.
Lots of apps are still stuck in Meteor 2.x hell because of the dependency on Fibers though.