I think the problem of the Finns was that they really wanted energy independence and tge inly ones that were on the market were the french. No doubt the frenched used much diplomatic muscle to attract them as a first experiment.
2,109 karma · joined December 29, 2022
I think the problem of the Finns was that they really wanted energy independence and tge inly ones that were on the market were the french. No doubt the frenched used much diplomatic muscle to attract them as a first experiment.
And if I am not mistaken then for a long time energy prices in France were smaller than that of neighbouring countries.
But to be fair, it is difficult to tell what "profitable" means because a primary motivation has always been the development of nuclear weapons, so the true amortization is across industry and national security.
I am not going to study a whole book just so I can find the answer to a couple things I might never need. I like to focus on a few areas, learn everything I need to understand it, know if there are any dependencies and see what is there to discover and then move on.
I know many people get joy from learning knowledge that is not directly applicable and might never be applicable. And I know that the academic spirit would be to learn these things. But my time is seriously finite and I am not using math in my life in any fashion whatsoever other than occasional curiosity.
I loved mathematics when I was young and wanted to be good at it, but I got burnt so many times by teachers who could not explain even if their life depended on it.
Asking an LLM and discovering how different theories belong together and what are genuinely open questions, along with different philosophical interpretations has been a wonderful gift.
I have long accepted that Mathematics is a language where you must go "all in" because for the most parts institutions are fundamentally unable to explain it in an intuitive way. There are people who "just get it" and are blind to the struggle of people who need a different approach in learning it. There's something about the field where a generational survivorship bias has created an environment where math is mostly taught to likeminded people, who then don't see why anybody could not see the difficulties learning it.
I know this is not true everywhere, but the only reason I could finish my studies was because there are some genuinely excellent online lectures on youtube, along with massive support from friends who have already been through the ordeal.
If I had had access to an LLM, I could have actually taught myself from scratch and be more playful in learning it. And no, I am not willing to learn lots of math "for fun", I can think of better "for fun" things that actually help my profession and cater to my actual interests and not just some academic ideal.
Sorry, but this reads like a mouthpiece exactly from those companies that benefit the most from having no copyright and I doubt your have thought this actually through.
Flattening has been the goal from the start, but it's simply not something that's delivered in this JEP. But even so, people should not overestimate the effect of values and flattening.
The biggest advantage will come from specialized libraries (stuff like OpenCV), and overall library enhancements (Tuples not requiring a dedicated indirection).
But whether your data’s integrity can be broken by such must be decided by the class author.
And looking at all the edge-cases and possible data-races via tearing, declaring something as a value must be an explicit design decision that cannot be inferred by a compiler or optimizer alone.
``` Declaring a value class is first and foremost a semantic decision. It tells our fellow programmers that its instances are defined entirely by their state and do not need identity. That clearer model is valuable in itself! The JVM’s additional freedom to optimize how those values are represented is a welcome bonus. ```
Many developers seem to think that "go value go broom", but the truth is much more nuanced and the idea should not be to think about "but performance" but to think about the nature of your underlying data. At the very least this integrates some core DDD lessons directly into language. I'm glad tearing isn't turned on by default exactly for this reason.
Java was always a language that geared itself towards making libraries easy to use, putting much faith in the library author and strong encapsulation. Now, experts can gain significantly more performance from the JVM, while more humble programmers are avoided from creating bugs they will not expect.
The free influx of money, and particularly investor money that gave the US an evergreen advantage will seize. Slow at first, then more and more as time moves on.
The problem is systemic and blaming other people for their lifestyle choices is neither effective nor helpful and just leads to further division. It's exactly this sort of division that helps fossil companies to destroy the planet and keep making money.
For methane produced by farming all components remain in a cycle. Everything released by animals eventually finds its way back to plants, which get eaten, which become exhaust of animals, etc.
This sounds to me more like a spin by big oil to finger point at another industry.
And the more you see an abstraction as a "wad of API calls and functionality", the more leaky the story gets.
Some systems are notoriously difficult to get this statement right because they are volatile and prone to changes. But I think as in live or in academia, our aspirations should be to strive for a better abstract understanding and keep building better abstractions.
For private projects, being able to code things quickly is a godsent. Also for professional environments with clear rules and mutual respect, this can be solved. But on the internet, with people you don't know? You must have some hard barriers.
We did do that and that's why our queries ended up being several lines long. But if you missed just one model? You openly walk a knife again.
It's a mess and it only gets longer and longer. I ended the project with having some proper aggregates, only for that to be thrown out of the window by the guy after me.
Never in my life did I have a problem with lazy loading causing unbearable performance until I joined a Python Django team. I really tried to find sympathy for the "dynamically typed" folks (please spare me saying Python is technically statically typed), but coming from writing apps and backends in Java, Swift, C#, Objective-C and PHP, Python with Django was the worst experience bar none.
I worked on the project for 10 months, could at least refactor the project to something semi-sane where obvious mistakes (which would not be possible in other languages) could not happen. Then along comes a "good Python dev" and threw it all out of the window and start doing SQL queries all over the place (typically 3-6 lines long), remove the domain objects and cause the same problems I started with to begin with. But his approach was saying that the other developers were "not good enough".
Yeah, have fun with schema changes going forward. Good riddance.
Mistral is playing the smart money on vertical products rather than horizontal ones. The former requires finesse, the latter brute strength.