1,714 karma · joined June 4, 2018
Python developer for web systems with interests in concurrent programming.
-----BEGIN RSA PRIVATE KEY-----
4
-----END RSA PRIVATE KEY-----There's an ocean of difference between e.g. preventing the model from routing to something at the firewall level and just updating the prompt (especially given models' historically poor understanding of negative prompts, relatively speaking).
That's true. But if America is so bad, why are you still in it?
I am not. I have never lived in the US. I live in Canada, and I've had my country's sovereignty threatened by the US in the past 18 months.As someone with a passing interest in infosec and cryptography, I'm sceptical of the long-term viability of this kind of product; it only takes one person successfully extracting a signing key to undermine the entire project.
[0] https://leica-camera.com/en-int/news/partnership-greater-trust-digital-photography-leica-and-content-authenticity-initiativeWe're also in a place where a lot of the usage guidance around these tools is still nascent. People are cowboying a lot of stuff, even as larger companies start to organize AI policy/safety/responsible use working groups to try and policy around the shortfalls of the technology.
IMO: if this technology persists, and if we figure out a way to use it in a broadly safe way, the value proposition will probably trend down rather than up, at least on the code generation front.
As a research tool, it shows some promise, though I still find the ethics of the technology disgusting.
Many of us are either openly having our performance reviews tied to AI use, especially at larger enterprises. Whether that's measured by sheer token count or just "how many of your tasks are you using AI for these days" (combined with the implication that question carries at many orgs which are heavily invested in AI).
If you want to give it a fair shot, it does take some time to get used to, coming from something like Python or Ruby. I won't deny that. I've found that using LSP-assissted semantic syntax highlighting helps, for me, on the typographic front.
I don't think typographic design is a key consideration in most languages' designs, though, and I don't think it should be. The main thing I look for is consistent, relatively predictable rules around the syntax, as far as that layer of language choice goes.
> So .clone() significantly reduces the mental overhead of using rust with a small performance impact? I'm intrigued :)
No, the performance impact will depend on `impl Clone` for the underlying type, the hotness of the code path, and how sensitive to those two variables your code's domain is. It may be extremely expensive. > Maybe it's harder to reason about the lifetime semantics while also writing code, and works better as a second phase (the de-cloning).
There are cases where assuming `clone` is possible allows for significant architectural and API simplifications at the expense of performance. In those cases, de-cloning will be involved and may produce significant changes. > The demand for AI is currently overwhelming. As in, can't build data centers and GPUs melting overwhelming, companies growing 3x in a month while already at multi-billion revenues.
This isn't a sign of a successful, sustainable business; it's what a bubble looks like. Between the aggressive marketing (including astroturfing!) that LLM companies are engaged in, the perceived stock market advantage companies can gain by shoving LLMs into their offering, and the missile-gap-style approach that many businesses are taking around this, this centre cannot possibly hold. > The models get better and better, Chinese open source is falling further and further behind American companies
American companies are, to be fair, flaunting safety and ignoring the wider social impacts of this technology, and both the US federal and state governments seem to be more than willing to go with the flow on that, probably at least partly because of a recognition that the LLM industry is propping up a significant part of the US economy. > The productivity gains are, at this point, obvious
They are, emphatically, not. For me and my peers (most of us, individual contributors in software -- and emphatically, those of us working at companies who haven't fully leaned into vibe coding), our jobs have become babysitting claude agents and spending most of our time cleaning up its messes and doing code review. Short-term, sure, this might lead to some productivity gains, but long-term, this is going to lead to mass burnout. > The best talent works (or wants to work) in America and get compensated obscene amounts, the most capital flows through America, this is still by far the best place to start a technology business in the world
Unfortunately, the US is in the midst of cracking down on immigration, and the international perception of the country is increasingly that it is an unsafe one. > I think American technology was on the decline for the past few years before LLMs, but for the foreseeable future as long as American companies control the talent flywheel I think the new world of tech is going to be much more American than before.
What I see in the US's LLM-backed economy is what I see in many businesses in this same economy, increasingly: the blanket of AI is being used to paper over serious, systemic issues in the organization, but this clearly won't hold. In a world where we have an ounce of responsibility for what we produce, and where customers care about the quality (notably, quality as in correctness) of what's being delivered, this will eventually collapse.Out of the three big geographic players, the US and China are jockeying for "most performant" models (whatever that means) with two separate approaches; the EU is trying to develop models that work best within their privacy, human rights and labour rights frameworks and laws.
All of these have have merits, though arguably the US's (de-facto) strategy of market dominance at any cost with as few restraints as possible will be the worst for society at large. The prudent thing to do would be to first determine if this is something that will actually live up to the hype (which IMO is still very much in the air), and then if it does, turns this into an international collaboration rather than a competitive enterprise.
It's not lost on me that this is a terminally naive point of view.
I come from a heavily Python background, professionally. I spent the entire first decade-and-change of my career using almost exclusively Python; I know it about as well as a person reasonably can (outside of scientific and ML Python, which I just never got interested in, but that's beside the point).
A year and a half ago I got a job doing Rust. At a surface level, it's about as far as you can get from Python in terms of ease of readability, but after 18 months I'm really reconsidering some of my points of view on the matter.
"Explicit is better than implicit," for example, is something I still strongly agree with, but my definition of "explicit" has shifted a lot in the past year. Seeing which guarantees are provided through mandatory, explicit, strong typing saves a lot of time over tracking down guarantees in MRs while reviewing Python code. If I see a signature as an `Arc<dyn AudioInterface>`, for example, I immediately know that:
- It's thread-safe and memory-managed using reference counting (because `Arc` provides those guarantees);
- It's a type-erased object but is guaranteed to provide all the functionality from the `AudioInterface` trait (which, let's say, could be a supertrait of `AudioInput` and `AudioOutput` -- so it provides both of those);
- It uses runtime dispatching (since it's a `dyn` rather than a generic/`impl T` where `T: AudioInterface`)
I can choose to operate on it by reference with all the caveats that entails, or decide to either `Copy` or `Clone` it, depending on whether that's available for that type and if I can stomach the runtime cost.
All that to say -- Rust doesn't suck to review, relative to Python, in the long run. At first, yes, holy crap, it's such a huge cliff, and I can appreciate your point of view... but there's something to be said about having all this information surfaced as part of the language's syntax and semantics.
Python still has a special place in my heart, and I'd still use it over anything else if Rust isn't an option, but to echo a popular sentiment from other people who've made this migration, I don't know if I can go back to handwaving away whether or not something'll cause an allocation :)
Human languages are mostly very bad at this, and in particular bad at mapping low-level abstraction to the human written word unambiguously in a way that is as expressive as programming languages.
Inference closes that specific gap significantly (which is why anyone at all sees LLMs as a useful option to explore), but it will never be as good as a purpose-built language designed to map to a reasonable corresponding assembly language implementation.
LSP is one of those things, or at least it has been, for a while.
LSP is also something that's not necessary to writing quality code; it's absolutely a major quality-of-life boost, but before rewriting my configs after switching to Rust, my LSP usage was limited to being a slightly faster autocomplete engine more than anything. I didn't have keybinds set up for going to definitions, implementations, or references of symbols. I still put out what I think was decent code. I'm also better off now that I've adopted a more useful config.
IMO it's an important part of this industry (among others) to let developers have whatever workflow they want, within reason. If someone decides they want to invest the time into setting up LSP with their editor, that's their prerogative. If not, that's fine too. I don't know who among my present or past coworkers use LSP outside of occasionally chatting about editor configs with one or two of them, because they've usually figured out a workflow that lets them produce respectable code, and I've never had to question their tooling before questioning their methodology.
The landscape isn't generally intuitive, unfortunately, and while it's getting better, understanding the differences and interop places between LSP, Treesitter, DAP, your editor, and the underlying language-specific tooling can be a big, confusing time hog.
That said, and to be clear: LSP's been a huge boon for me. I used a minimal, kinda-broken configuration for a while with Python, then rebuilt the whole thing when I switched to Rust for work, and holy hell, this thing's awesome.
With closed source IP, every bit of support, from bug fixes, to feature requests, to compatibility fixes to integrate with newer mainline/foundational tooling, costs money.
With open source projects (and in particular ones like Linux where there's a huge number of contributors and interested parties), support for would-be niche facilities can keep going as long as there's someone with the knowledge and spare time to do it.
To your side note: "take" is a very common synonym for "thought"/"opinion"/"view" in the version (dialect? I guess?) of English I grew up with. If you're unfamiliar with it, that might be a regional or generational effect. I don't know. I'm not a linguist.
Though this is undermined somewhat by stories like this one[0], where an AI runs a "slow life" store catering to a lifestyle that specifically tries to disconnect from technology.
It's incredibly perverse.
[0] https://andonlabs.com/blog/andon-market-launchLike... yeah, no shit; I didn't build it for your regex. It's not the target audience.
Plus, isn't the appeal of LLMs broadly that they can do somewhat-useful things with mostly-arbitrary input (if you ignore the risk of prompt injection)?
I have reduced my online presence to much less than it once was partly because I don't want to feed this machine training data that I've worked hard to make for a human audience.
- None of these are as flexible as writing. They're more expressive, more engaging (arguably, at least to some), and might even be good at succinctly saving certain specific types of knowledge.
Knot systems typically parallel the abacus, having been used for accounting and to keep a record of tax levies. Certainly this isn't the *only* thing they were used for, but this was the case in a number of indigenous civilizations in the Americas, as well as in some Asian civilizations. Certain dances might be good at representing the motions you have to go to while working fields or performing other societal tasks, sure. But a good writing system, in its relative blandness, is incredibly versatile, and can encode not just a wide breadth of information, but also include information about *why* the information is what it is, to the extent that the authors knew.
- Many of these systems tend to either disappear or change over time while relying on largely-unwritten rules, implied social context, and other informational artifacts that themselves don't have a very long shelf life in the event of significant social change. Where destroying the written word (especially in the wake of the invention of the printing press) is a long-term, conscious, coordinated action; dances, songs, and stories can fall victim to everything from fashion, to counterculture, to human migrations, to hostile invasions.- I don't understand what you mean by things like "stories with self-correction." In many cultures with an oral tradition, the stories do get distorted because of people misremembering, or through conscious changes in response to social conditions at the time of a retelling; if a 1,000-year-old story with no written record backing it is told today, it's almost certainly not the original story, but the culmination of a thousand years and dozens of generations of sometimes-subtle, sometimes not reinterpretation.