ndrewxie

I see, that's a cool way of looking at it! Sadly I don't have many "itches" right now, mostly cuz I've done a lot of "write it 100% from scratch for fun" type projects for the past year or two. But hey, that's a nice mindset, and ig I'll just keep my eyes open until something catches my attention.

Yeah I'm OK with asking questions, but there definitely are projects with enough domain knowledge that it would take upwards of 30 minutes to an hour to fully explain everything... And that's kinda where my comfort limit of asking questions ends :P

Like there's this mildly embarrassing occurrence where I saw an open issue and decided to tackle it. Made it to the point where a maintainer asked for multiple live zulip discussions, but it became pretty clear that I was missing lots of domain knowledge, so after a while these discussions kinda tailed off and IDK if the PR would be considered dead or not. If so, I probably just wasted 4-5 hours total of that guy's time lol. Like that's the type of situation I'd like to avoid :p

(cherry on top is I missed an obvious-in-hindsight mapping of the problem to a graph theory problem, so my PR was 1000 lines of code when it probably could've been shorter. Then again, IDK if there's that many graph automorphism libraries I can just pull off the shelf anyways, so maybe there wasn't much potential for simplification)

Well, most variables are immutable in my language (took the lazy way out). The few mutable ones are "owned" by one scope, and must operate on the same thread.

Not to bother you with this REALLY long mess, but I've been working on it for a while already, so could you please review it for me? Some flaws just won't work out correctly, and I need a pair of fresh eyes to look at it. Laziness isn't added yet, and there are a lot of flaws that make it not ready for any sort of use (recreational or otherwise).

Thanks!

Report can be found at https://gist.github.com/ndrewxie/54d3299c998569c27e281d2320b...

OK, I'll follow the chain to the end :)

I'm a C/C++ developer for 15 years. I'm planning to do this mainly for learning purposes, and to create my newest project (actually an umbrella project containing 5 different projects).

Please don't spam.

Yes, I saw that. I'm planning to make something similar, but still pretty different.

They're opposites, I know. I'm trying to put strong, static typing and laziness onto Smalltalk and clean up it's syntax a bit (it's already pretty clean, just a few things could be improved) - essentially a faster Smalltalk.

I googled about the origins of many common languages, but most of them were just based off of another language. I tried finding out how those languages were made, but it just goes on...

Yes, I've been combining features from different languages (Smalltalk and Haskell), but all I have now is this huge mess that I don't know how to fix.

There appears to be lots of enthusiasm about Rust - I'll probably learn it, but I'm trying to learn a higher level language (believe it or not, I don't know any "high level" "modern" languages, because I figuratively spent my last 10 years in a hole).

Yes, it's too similar to C++/C (I know it's not very similar, but it's still low level).