benrutter
Most importantly though (/s), is this toit as in "roof" in French, toit as in "to it", or otherwise?
Ah yay, I appreciate it! I feel like its rare to get a look at how these decisions cone about.
What did you measure? How'd you realise there was a problem? And did you measure anything to give you confidence that Trino won't hit the same issues?
Surprised how many answers here are on "social" reasons, and ignoring that Ubuntu does provide genuine additions to Debian.
Ubuntu includes additional proprietary drivers to Debian. So there are legitimate hardware cases were Ubuntu will work out the box and Debian won't. I can't speak for how many people need those drivers, and how much of choice is down to defaults/inertia etc.
From hearing interviews with PopOS folk, I think this is also a big reason people choose Ubuntu as a base for a lot of Distros instead of Debian.
Non LLC are not unlimited liability companies. Those have existed historically, and mean that owners themselves are legally on the hook for any company debt, without limit.
Since I'm trying to repeat back something I heard elsewhere, I'll link to the original discussion. Adrian Wooldridge is a long term writer for Bloomberg and not sine random guy on a soapbox. The discussion is well thought out, and not emotionally charged. Sorry if I've accidentally given a different impression.
https://www.pushkin.fm/podcasts/business-history/how-the-com...
https://www.pushkin.fm/podcasts/business-history/how-the-com...
(Note the discussion is about the evolution a of the concept of a company generally, the point I mentioned gets made towards the end, but I'd highly recommend listening to the whole thing)
I agree that there aren't any "silver bullets", but I think there are some decent pieces of regulation like, forced splits between investment banking and commercial banking, and heavy regulation of high risk markets, especially when it comes to inclusion in retirement funds etc.
Those aren't going to single-handedly solve the boom bust cycle, but they are amongst other similar policies, a bunch of levers than governments can use if they want to in order to shield the public from risks caused by financial speculation.
Adrian Wooldridge was essentially arguing that especially with the shift towards more privately owned companies (as in, non-publicly traded) that we've seen in the US, limited-liability companies give an incentive for a large amount of risk.
Essentially there's an asymmetry, because companies going bankrupt have no liability for debts, but they gain all profits if things go well. This has always encouraged risk (and often in a good way), but publicly traded companies are ultimately owned by retirement funds etc, which is not the case for private companies. So the risk of bankruptcy is still covered by the general public, but a lot less of the benefits are felt by the public.
I think we're in fairly uncharted waters for what this risk asymmetry means for the US and global economy. It doesn't sound like something that'll end well, I expect we'll see a lot of public fall out at some stage.
I think it's an interesting thought, I'm not sure I have a hot take here or anything. The likes of Jeff Bezos and Elon Musk are clearly good at amassing wealth (and interested in amassing wealth) but I suspect a lot less is attributable to skill than many would think.
If I think about where I see python being used though, this kind of makes sense, the two big use cases are:
- Web APIs and backends, where for the most part either the network or the database is the bottleneck
- Data science work, where for the most part, work exists in libraries like polars, pytorch etc that ship the main work out to other languages.
So from that perspective, although we'd all like python do be faster, it's speed isn't the bottleneck in the use cases where its popular (that's probably also the reason why we don't see Python getting used in other speed critical places).
That's a really different story to JavaScript, which doesn't have a handy CFFI or otherwise you can just reach out to. There are a lot of cases where JavaScript speed improving would speed up the reactivity of a web app, even now.
I'm not arguing against a faster CPython - I'd love one! But I think there's a clear reason why it hasn't been prioritised historically in the way JavaScript's performance has.
Wait, how many? I'd say just this one. The other that I know of, pypy, was massively successful for a single maintainer project. And definitely showed the possibility/potential of JIT python.
I wouldn't call it a failure for not over taking mainline CPython.
What languages are you thinking of specifically when you mention better thought out ones?
One thing that isn't super obvious from the article is that a lot of it is talking about industry solar panels rather than rooftop. The overheads of installation etc get a lot smaller if you're installing a whole bunch at once.
This isn't to say that installing solar panels on your house is a bad idea - they normally pay for themselves after something like 10 years from memory, so are similar to double glazing.
[0] https://www.energy.gov/cmei/systems/overview-trade-and-polic...
In the US, FDR stood 4 terms, and he was hardly the end of democracy.
I think those are different from pure "natural langyage programming" though because there's normally code you've written that's calling out to the LLM, so it's within the context of written code.
I think this, and lots of other comments are so interesting. There are a lot of different increasingly complex ways LLM outputs and coding are being tied together by people, that I hadn't really considered.
> the preferred form of the work to making modifications to it
Implies what you point to when you want to know where to make changes.
That wouldn't be a prompt - you might use a prompt to make changes, but the thing you're making changes to, certainly at present, is your java/python/rust++ /whatever codebase.
Lots of projects, even fully vibecodes ones, don't push and include prompts in their repos. But they all push the java code (sticking with java as an example for the sake of argument).
I can't imagine that working on a project where the java code is omitted, and people make changes to the software just by editing the prompts would go well. It's an interesting thought experiment, but I think you'd find it very hard to work on any kind of team where that was the practice.
I don't think I'd want to call it "natural language programming" in the way Dijstra's implying here unless the prompt was the thing that was actively being executed/ran/whatever when someone loads your app or website.
Whether "natural-language-like syntax" is enough "count as natural language programming" is probably a question of definition. For Dijkstra's essay here, he doesn't offer a particular definition, but he certainly seems to be implying something much more fluid and ambiguous than Inform7 is.
I definitely didn't mean to imply Inform7 had achieved the holy-grail of natural language programming or anything.
I think Dijkra's main point he's driving at is here:
> I suspect that machines to be programmed in our native tongues —be it Dutch, English, American, French, German, or Swahili— are as damned difficult to make as they would be to use.
I'm inferring/assuming a bunch, but I think he's saying something along the lines of, programming is useful because it is precise, and natural language is not precise, so attempts to make programming languages more like natural language are butting up into this inherent contradiction of precision. And therefore will end up as worse programming languages (for attempting to be more naturalistic).
In the history of programming languages, I think most attempts to be "more natural language like", such as COBOL or AppleScript, do become worse for attempting to walk the tightrope between natural-language and programming. I think Inform7 is unusual in that it achieves that balance in a way that isn't just objectively terrible (you may disagree) - I think that's mostly because it offers very few programming constructs, and is a tool for writing a kind of prose (text adventure games).
Anyway, to come back around, that was my reasoning for mentioning Inform7 - I think it's an interesting deviation from other experiments in natural language programming so far.
(Construction planner has three arms)
[0] https://www.modelcompare.ai/blog/ai-models-controversial-tak...
Normally more general capacities than that evolve. We've evolved the ability to learn and adapt, and that's what we're using to create these heuristics. But I don't people evolve into individual beliefs/attitudes in that way.
Some people will push back that agent development is "natural language programming" but I don't think that's right. I think in that case the agent is the one programming, and the programming still always happens in a deterministic language like Rust/Python/Typescript/etc. Maybe that'll change, but to me at least the other way would be a disaster.
The best exception I know of though, is definitely the Inform 7 language which is for writing text adventures[0]. It has a lot of fans, and I've never gone deep with it, but seems to do a pretty elegant job or marrying up natural language and programming together in a unique way.
Either way, definitely a must-check-out for any language-geeks interested in natural language programming.
[0] Not that my expectation has any weight, I have close to zero knowledge of psychology.
WhatsApp scares me a little to be honest - I can (and have) easily switch from using Facebook, Instagram etc. But WhatsApp is used for all sorts of groups where I live (family, work, political, etc). It's a really sticky technology, and very hard to move off of without convincing a lot of others. That would be bad enough on its own, but combined with Meta's continuous shady goings on, I genuinely feel uncomfortable with how much power is in such disinterested hands.
Is the animation comically slow for anyone else?