Market share wise, Groq is perhaps "tiny"? Nvidia may be paying a premium for Groq [0] since it eliminates competition (at least on the inference side).
> economically, it is still much better to buy a lower spec't laptop and to pay a monthly subscription for AI
Uber is economical, too; but folks prefer to own cars, sometimes multiple.
And how there's market for all kinds of vanity cars, fast sportscars, expensive supercars... I imagine PCs & Laptops will have such a market, too: In probably less than a decade, may be a £20k laptop running a 671b+ LLM locally will be the norm among pros.
a big part of the whole "hack" of Uber in the first place is that people are using their personal vehicles. So the depreciation and many of the running costs are sunk costs already. Once you paid those already it becomes a super good deal to make money from the "free" asset you already own.
The depreciation would be amortized to cover more than one person. I only travel once or twice per week, it cost me less to use an Uber than to own a car.
When LLM use approaches this number, running one locally would be, yes. What you and other commentator seem to miss is, "Uber" is a stand-in for Cloud-based LLMs: Someone else builds and owns those servers, runs the LLMs, pays the electricity bills... while its users find it "economical" to rent it.
(btw, taxis are considered economical in parts of the world where owning cars is a luxury)
One time I took an Uber to work because my car broke down and was in the shop and the Uber driver (somewhat pointedly) made a comment that I must be really rich to commute to work via Uber because Ubers are so expensive
> The problem is, especially in a hot loop ... The proper way to do something like this in java is either log.trace(..., ...) or if (log.traceEnabled()) log.trace(...)
The former still creates strings, for the garbage collector to mop up even when log.traceEnabled() is false, no?
Also, even if the former or latter is implemented as:
GotaTun is specific to Mullvad and the features they usually add make sense for a public VPN provider. Unlikely projects such as Tailscale adopt it.
Besides, engineers at Tailscale, I don't think, strike me as startled by any hurdle too tall to debug, improve Go-based libraries. In fact, they pushed wireguard-go past 10gbps on Linux-based platforms back in April 2023! https://tailscale.com/blog/more-throughput
> you were still not fully in control and someone else exploits the economic value without investing
O'Sassy came up recently in one of the forums I lurk in [0], and as discussed there, I tend to agree with Adam Jacob (SystemInit) and others that FSL is definitely one way out but doesn't totally solve the commercialization aspect, because the code & all that IP is still readily available.
Adam, in this talk [1], argues that like RedHat (and unlike Canonical), Open Source businesses must learn to separate source license from distribution license and if they do so, the money is there to be made (in a b2b setting, at least).
> What I have found interesting in the years since is that many companies are wrestling with the same problem, but feel that the two year head start the FSL gives is too aggressive.
... if the companies conflate Open Source and business models, rather it being merely a Go-To-Market (like open core).
Especially true for dev/infra upstarts competing with incumbents (PostHog v Amplitude; GitLab v GitHub [2]), and lately for AI labs (DeepSeek/Qwen/Llama v GPT/Gemini/Claude). In a role reversal, BigTech also uses Open Source to commodotize its competition's advantages (Android v iOS; k8s v Swarm; Firefox/Chrome v IE) [3].
> So people can argue it doesn’t work, but so far we only have evidence to the contrary and Sentry is quite successful
So, RedHat has also been successful?
GP says that some companies don't find FSL aggressive enough, despite it having worked nicely for Sentry. And that's similar to the point Adam makes: That Open Source (per OSI not FSF) is a development model not a business model. Companies that don't want/need to prioritize collaboration tend to use FSL / BUSL / etc; but those licenses aren't really going to significantly change their development or business (other than prevent competition from using it as-is, but now the code is out there anyway [0][1]), and so they might as well go close source (and Lockdown the code, too).
> issue is these are mostly academic points of view
Both, commodotizing competition (through OSS) and using OSS as Go-To-Market aren't academic PoVs, I don't think.
I'm not talking about RedHat, I'm talking about the perspective that "FSL / BUSL aren't effective enough". They solve the problem. O'saasy is just freeware at the end of the day, FSL creates more open source, and BUSL often has (though unfortunately the license doesnt require it).
The idea that FSL ~= Closed Source is entirely wrong and misunderstands the value that an open distribution gives. We have 10s of thousands of customers that run Sentry self-hosted. We regularly get contributations back to our core service - both in code and (what we prefer) other artifacts like feedback.
We were "Single Origin Open Source", which is extremely common whether people like to believe it or not. Its the entire premise of the sustainability issue in the industry. Thats not just an issue for commercial entities, its also most of the big open source software people rely on. In our case though we have a great business model that makes it entirely sustainable, and now have built a solid licensing mechanism around it that protects that, while ensuring our community is still successful.
These same issues around single origin open source are why we started the no-strings-attached funding mechanism via Open Source Pledge (https://opensourcepledge.com), why we push Fair Source (https://fair.io).
Maybe others will find defensible models, but I'm skeptical. I also respect Adam, but last I understood it the model they were going after sounded pretty similar to trademark protection (which doesnt work).
Thanks for the links. I read those and some more from your blog. I've also been to a Chad Whitacre talk about Sentry's OSS approach at a conference this year.
I don't think we're disagreeing at all. I quoted Adam to drive the point that tech shops that value collaboration will tend to prefer OSI-approved licenses. That doesn't seem to be the case for Sentry:
[Sentry is] single-source. That is, [the Company behind it] are the authors and maintainers of the software, and [does] not expect the community to provide us with contributions. We still allow it, and are thankful, but we consider it our duty to develop our software.
At the other end of the "single-source" spectrum is SQLite which is closed to collaboration but is dedicated to public domain and requests a fee for "Warranty": https://sqlite.org/copyright.html
It does seem like Sentry wants control over distribution, but by the way of license? Adam proposes something similar (and I guess that's the reason he's okay with "Fair Source", like a few others too who want to unchain the idea and go beyond OSI / Open Source [0]):
[Sentry wants] to allow people to self-host our software.
> I also respect Adam, but last I understood it the model they were going after sounded pretty similar to trademark protection (which doesnt work).
A counter example: The Android Open Source Project is OSS, and is firmly gate-kept by Google via trademark and other collaborative arrangements like the Open Handset Alliance and Linaro. That said, this is the happy case. Sentry clearly had a different experience with bigger tech shops (GitLab?) trying to monetize its offering without contributing anything back, which (tbh) sounds super terrible.
To me, there seem to be pathways to both succeed & fail with OSI-approved licenses (probably you'd argue... one'd fail more than succeed), and these licenses on their own are neither the only condition nor a sufficient one for business build around them to stumble and falter. That said, I get your point that "Fair Source" gives "single-source" projects a fighting chance, like it did for Sentry. I'd also have thought that the OSI-approved AGPLv3 (your reservations about copyleft notwithstanding) is enough to keep big shops from leeching from other high-quality mostly single-source projects... but may be I was mistaken (given MongoDB / Elastic / Redis / CockroachDB didn't think so; even if, Elastic & Redis switched back to including OSI-approved license, specifically the AGPLv3).
> Mullvad ... security and privacy _very_ seriously. Not surprised to see them shine here.
? TFA reflects on dishonest marketing on part of public VPN providers more than privacy / security.
That said, VPNs don't add much security, though, they are useful for geo unblocking content and (at some level) anti-censorship. In my experience, the mainstream public VPNs don't really match up to dedicated censorship-resistant networks run by Psiphon, Lantern, Tor (and possibly others).
Advertising a VPN endpoint in country A which in reality is in country B is a security concern for users trying to reduce their visibility to country B’s authorities. You’re right about the more fit to purpose tools, of course, but they’re more of an impediment to normal internet usage.
> Advertising a VPN endpoint in country A which in reality is in country B is a security concern for users trying to reduce their visibility to country B’s authorities.
Mullvad in their Terms of Service say they'll abide by Swedish and EU laws. This, among other things, means a VPN is in no way going to save your bacon from "authorities".
[IPinfo] pings an IP address from multiple servers across the world and identify the location of the IP address through a process called multilateration. Pinging an IP address from one server gives us one dimension of location information meaning that based on certain parameters the IP address could be in any place within a certain radius on the globe. Then as we ping that IP from our other servers, the location information becomes more precise. After enough pings, we have a very precise IP location information that almost reaches zip code level precision with a high degree of accuracy. Currently, we have more than 600 probe servers across the world and it is expanding.
[0] valued ~£6.5bn 2mo ago https://www.reuters.com/business/groq-more-than-doubles-valu...
reply