I don't think I'm qualified to answer the question, and I also think it depends on terminology where maybe 'core' is the wrong thing to say, but regardless: my general point is that the assumptions that hold for CPUs don't hold for webservices, and that's where the design ethos between them splits.
What to expect, when Microsoft decides to do stupid things like renaming .NET Core into .NET 5, thus everyone that doesn't pay attention to Microsoft world keeps thinking .NET is Windows only, as the .NET Framework was always known as plain .NET in most circles.
Napoleon's only been gone for about two hundred years, whereas Common Law has some real classics. For example https://en.wikipedia.org/wiki/Statute_of_Merton was a set of laws promulgated in 1235, some of which remained in force (at least nominally) until the 1980s. I don't know much about Canon Law, but that surely goes back even further.
All that to say, you can just do your best to understand the law in the the context in which it was written, and replace the text every now and again.
I think there's more dimensions that also matter a bunch:
* a bad craftsman will get pedantic about the wrong things (e.g. SOLID/DRY as dogma) and will create architectures that will make development velocity plummet ("clever" code, deep inheritance chains, "magic" code with lots of reflection etc.)
* a bad practician will not care about long term maintainability either, or even correctness enough not to introduce a bunch of bad bugs or slop, even worse when they're subtle enough to ship but mess up your schema or something
So you can have both good and bad outcomes with either, just for slightly different reasons (caring about the wrong stuff vs not caring).
I think the sweet spot is to strive for code that is easy to read and understand, easy to change, and easy to eventually replace or throw out. Obviously performant enough but yadda yadda premature optimization, depends on the domain and so on...
We just live longer than back then and have way more opportunities to see these (mostly) late-life diseases. Same with cancer.
Yes, average life span was shorter back then because of child mortality. But the vast majority of surviving adults never reached age 80. Old age was 60-70 and many of these diseases only occur at 70+ in significant numbers.
My partner Elaine Gord was on VisiOn's C compiler team in 1982-1984 with two others. They experimented with having two instruction sets: the native 8088 code for best performance, and a C virtual machine bytecode for code density. The two modes were mixed at the function level, and shared the same call/return stack mechanism. This was terrible for speed, but was thought necessary because the target machines did not have enough ram for the total VisiOn functionality. I don't know if the bytecode scheme got into "production".
Tiny Core has always amazed me. The amount of functionality they fit into such a small footprint shows how far you can go when you optimize for simplicity.
A Web version is definitely planned, and Android support is in development as well.
Since the core engine is fully portable, both should come naturally once I’m done polishing the iOS launch.
Really appreciate your interest and willingness to support it on other platforms.
And yes, as you can imagine for the kind of comments I do regarding high level productive tooling and languages, I was a big Dreamwever fan back in the 2000's.
I'm not sure your characterization is all that accurate.
Originally, they thought they could build a product that worked across many languages. That necessitated a "lowest common denominator" language, which is a void that has always been strangely lacking in choice, to provide an integratabtle core. Zig had only been announced a few months earlier, so it wasn't a viable contender. For all intents and purposes, C, C++, and Rust were the only options.
Once the product made it to market, it became clear that the Typescript ecosystem was the only one buying in. Once it was understood that the original business idea was a failure, the "multi-language" core didn't make sense anymore. It was a flawed business model that forced them into using Rust (could have been C or C++ instead, but you should be able to get the drift) and once they gave up on that business model they understood that it would have been better to have written it in Typescript in the first place. Now they have the opportunity to actually do it.
I have never worked (in Prod) with Perl, but my introduction to programming was with PHP and all I know IMHO is that PHP was/is so easy to start with. One of the reasons I picked PHP over other languages.
Thank you so much for the thoughtful feedback — really appreciate it.
About the initial lag you noticed: that most likely comes from the first-time Game Center initialization.
After that first launch, everything runs at full speed, but I’m looking into smoothing out that initial moment.
The timer toggle is a great suggestion and I’ll add an option to hide it.
And the idea about using triads/chords for the sound feedback is surprisingly interesting — I’ll experiment with this.
Thanks again for taking the time to share this. Feedback like yours really helps me improve the experience.
There isn't really a path to a Russian-Germany conflict unless the Germans keep trying to pour resources into killing Russians. I mean, theory #1 for why Germany and Russia might start fighting - because for 4 years now Germans have been trying to kill Russians. The German leadership very much set any conflict up. They just made tut-tut sounds over the invasion of Iraq (and actively supported the Afghanistan invasion), they clearly have no moral qualms about what is happening in Ukraine. They just hate and fear Russia, irrationally.
And I'm no expert in German history, but my understanding is that the Russians controlled East Germany as recently as 1989 and the official language was still German.
The mix is the centrist way of populism: I large number of people affected are not allowed to vote. At the same time the current government consists of the 2 parties that were mostly backed by already retired people or baby-boomers, soon to be retired. We have state elections coming again and the government is largely unpopular and has not delivered on other things, with economic prospects not looking good either. After seeing years of partially misguided 'rational' governments, Germany is clearly shifting towards a more populist path (unclear which political direction, but we all know who are the best at this game, particularly if the generation 'never-again' won't vote anymore)
I'd love to hear people compare their system76 laptop to a Macbook, but it's really hard to find recommendations that don't just grade their non-Macbook on a curve just because it's not one.
Edit: Oh, r/system76 seems to hate these things. Bamboozled again.
people haven't explained why this is the case, it's the simple genetics we learn in biology.
the first generation has a many sets of genes with "Highly Productive Dominant (HPD, my terms for this post) genes, Not so Productive Recessive Gene (NPR)". By inbreeding 2 lines for a while, one can end up with a strain that has both genes being one and thereby when you cross it with something else, you know the offspring will get its gene (as it really only has one). Therefore the first generation, will have many sets as what I described above and will 100% express the HPD of those pairs.
The 2nd generation though of seeds will have a randomized assortment of HPD/HPD, HPD/NPR, NPR/NPR genes. Therefore while 75% of the seeds expressed genes will be HPD on average, that's obviously less than 100% that one gets from first generation.
