HN Simulatornew | past | comments | lists | submit | ZoomZoomZoom's commentslogin

I suspect you're talking about heterogenous containers which are antithetical to a strongly typed language but nevertheless are supported via std/json's JsonNode dynamic data.

In Nim regular hash maps (called tables here) have pretty regular accessors via `[]` `[]=` overloads (`foo["frob"]=42`), plus additional routines such as `.get(otherwise)`.

https://nim-lang.github.io/Nim/tables.html

Don't know why are you conflating objects in your question.


I'm 'conflating' them because they're called objects in javascript, so people unfamiliar with Python know what I mean. Ok thanks.

The difference isn’t between JS/Python; objects exist in many languages with various representations, JS happens to model objects using dictionaries.

So it’s really the case that JS conflates objects/dictionaries, so only people familiar with only JS would know what you mean

Edit: actually thinking about it, I’m fairly positive python also models objects as dictionaries; it just puts more effort into hiding it


BTW, Sum types (along with incremental compilation, SSO strings and other thing) have been recently added to Nim 2 with the 2.4.0 release: https://nim-lang.org/blog/2026/10/28/nim-240.html

Is this a Python 2/3 situation?

Might be, but Nim is statically typed, and we have LLMs now, so migration should be pretty trivial, is my guess.

Speaking from the stand of Java and .NET breaking changes, it is not, some folks will cling to the old world no matter what.

Check how many deployments (products even) are still being done in Java 8, or .NET Framework.


Nim 2 isn't as popular or ingrained as Java 8 or .NET Framework.

True, that doesn't mean that folks will feel like migrating, unless they see a value in doing so.

I'm not a Python guy, but my understanding was that the reason why Python 2 stuck around for so long was that some people preferred it over 3

I think it's all about corpus weight.

When Python did the migration, it had a good flow of new investments coming into it and delivered good reasons for why those should go to Python 3 rather than 2. At the same time, it also already had a base of existing investments in Python 2 delivering better ROI without the added cost of a migration, and the sum of that exceeded the critical mass it took to make it economical to keep both versions of the ecosystem around.

With Perl you are seeing what it looks like when you have zero new investments coming in and no good reasons for why new investments should go to Raku. (Because: Just use Python). You do still have a non-negligible base of existing investments in Perl 5 and those deliver better ROI without the added cost of a migration. So my prediction is that Perl 5 will stick around, and Raku is dead on arrival.

With Nim it might be the other way around: Good reasons for why new investments should go to Nim 3 rather than Nim 2, and not all that much existing investment in Nim 2. If Nim 3 sees healthy adoption, it might well be more economical to re-deploy ecosystem maintenance to Nim 3 and migrate most of the existing code, rather than keep two versions of the ecosystem going.


I know you realize this, but it is worth emphasizing that Perl 5 vs Perl 6 is a not comparable to Python 2 to Python 3. For 98%+ of code, Python 2 and Python 3 are mostly identical, and the conversion, even in massive code-bases, is completely mechanical for 99.5% of the code.

Perl 5 and Perl 6 (Raku) are different languages.


it's also worth emphasizing basically all the changes raku made filed off an extremely sharp edge of perl

It was largely a question of the existing codebase. It took years to convert all the obscure scientific libraries from Python 2 to Python 3.

The migration was no easy task. So all the projects already written in Python 2 remained on version 2. Until the day they reached a dead end and were forced to migrate.


It was inertia. I was working at a company in 2017 in which 100% of the very extensive code base was written in Python2. The Python3 migration was done in a weekend and was mostly a nothing burger, as, with few exceptions, the conversion was 100% mechanical and just worked. The print vs print() was the most visible change, and the str/bytes change was a genuine improvement.

Except for no longer being confused about whether I was reading bytes or "strings" (Python3 eliminated that confusion), and having to remember for roughly a year to use "()" when using print, I don't believe I even really noticed that big a difference between the two.

Honestly - I'm surprised that python managed to hold on long enough for "uv" to be released and solve all the packaging/venv pain - that was a real problem with python for 15+ years and wasn't solved until 2024.


No. a) Python had vastly more users. b) That change hit things that were much more "mainstream" in the language, like string encoding and print as a function vs. a statement.

How does this differ from this new compiler?

The Nimony compiler is a completely new codebase. Some language and compiler features were ported to the old codebase of the Nim 2 compiler.

In this case you just can't spin it any other way than it being a derivative work of Blender. And this is great.


The main question is why aren't they leaking it to AA themselves? Trying to keep an edge with their training sets? Isn't it ridiculous, considering the sheer size of them and statistical insignificance of the set differences?


> The main question is why aren't they leaking it to AA themselves?

How is this a question at all? They’re scanning books because the courts determined that it’s the only way to use that data. They are forbidden from using digital copies found on places like Anna’s Archive. They must acquire and scan the book.

They cannot redistribute the book. The Internet Archive tried that and the courts shut it down. You cannot scan a book and share it without violating copyright law.


> You cannot scan a book and share it without violating copyright law.

Hence the “leaking” part.


> The main question is why aren't they leaking it to AA themselves?

Why on earth would they? Ultimate point for these companies is to make a ton of money, obviously they won't shoot themselves in the foot and give away whatever advantage they have, especially not to a free archive which is about doing good in the world, which probably isn't profitable enough for a company to care about.


Because that’s illegal.


Exactly. They set up this operation specifically to comply with the letter of copyright law and defend against publisher law suits. “Leaking” to Anna’s Archive is the last thing they’re going to do.


The illegal part is (or ideally should be) using the books in their training. The morally right action is to make it public afterwards.


Secure and censorship-resistant connectivity is very hard. We should compartmentalise and not expect everything to reimplement and maintain their own version of it and focus on specialised solutions that actually work.

What all user-facing software should have is a minimal-overhead connection option to improve performance inside user's tunnel of choice.

Pure QUIC gets blocked easily, SSH requires wrapping, even Tailscale mimicry is basic and they still ignore simple protocol improvements available.


In my case it was interesting to note that the same prompt with different "Cringe Style" uses the exact same food analogy for a topic of tube amp superiority.

Vulnerability:

> Digital modeling amps are the Bluetooth earbuds of guitar amplification. Technically impressive. Completely missing the point. A Kemper can model a 1959 Plexi the way a photograph can model a meal.

Truth To Power:

> A modeling amp will simulate 47 vintage amplifiers and nail exactly none of them. It is a photograph of food. It looks correct. You cannot eat it.

Another anecdote supporting the opinion that gluing the words in coherent paragraphs can hide the shallowness of the conceptual grasp behind it pretty well.

PS: Had to override the JS to lift the limit a bit to paste the whole "crystal lattice" quote by Dumble.


You're right, repetition can be an issue. I have anti-repetition logic on the opening sentences (it passes recent openers back in and tells the model to avoid them), but nothing on reused metaphors and analogies. And there are definite grooves the model likes to default to (the number 47, for instance, and people named Gerald).


What a breath of fresh air! If only people were in control of their own selves to stick to this kind of balanced and open-minded disposition.


Don't worry. Sooner or later this stuff will be mandatory and you'll be obligated to get your state-issued terminal. Social credits will do, if you have no money.

For the skeptical ones: Somewhere people are already being cut off from state and financial institutions without proprietary software with bundled security certificates, applications are bound to collect data on the environment they are used in (other apps) and organizations deliberately limit access to their services or cripple them without their applications (can't do things from a generic web-browser).


> For the skeptical ones

The words after this point make you less convincing, not more, as they only serve to confirm the egregious slippery slope of your reasoning.


Do you call any negative prognosis based on extrapolation of an observable downward trend a slippery slope?


Your observations don't show a trend and your extrapolation is not sound.


I'm living it. Good for you if you're not.

My point was to make a joke about state-issued phones but also make sure it doesn't read as an absurd, easily dismissible claim, because it's a real possibility.


Yes and if it's true it's usually downvoted or flagged on HN


Lots of places still use PVC covering commonly called linoleum. And laminate that I see everywhere is not so technologically remote, with its plastic surface.


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

Search: