A lot of things have happened since the 90s, you know?
2,724 karma · joined May 30, 2016
A lot of things have happened since the 90s, you know?
Type, maybe, but they are visual noise when you read code.
BEGIN and END are also not as easy to match with editors/IDE's as pairs of symbols.
for (elems) |x| {
std.debug.print("{} ", .{x});
}
Why is the .{x} necessary here? What happens if I just write "x"?Some requirements:
- Code snippets are pretty and colored, and cover multiple languages
- Posting images is easy
- There's a tool to convert my existing Wordpress articles into it (I have 20+ years of that)
- Ideally, Markdown, but I'd consider similarly intuitive mark ups (I can do HTML but would rather not)
Dave Braben is a god on the same level as Carmack.
He created a new game generation for decades, which we're still living in.
This is a very pompous, pretentious, self-serving, statement.
How about Rust? C++? Kotlin? F#?
You find people interested in these things in all languages, and people not interested in these things in all languages.
How does it compare in your mind with, say, Rust and Kotlin?
First of all, than*, not then.
Second... no, it doesn't. Gradle and Maven are the standards, and they both use the very well documented, incredibly successful, Maven Central repository. They are just two different implementations using the same, reliable, battle proven approach to dependencies. You need a library? Add it to your build file, with its version, and you're done.
And yes, whether you spell it "wat" or "what", both these words are a dumb way of participating into a discussion that do nothing but expose your ignorance of the topic you are trying to debate. Voice your concern, question, challenge, in plain English, or you'll just come out as childish, combative, and not educated enough to take part in the discussion.
There is a reason why all dynamically typed languages today are scrambling to add some form of static typing to their language, but never the other way around.
Static typing does everything dynamic typing does, but better, faster, allow automatic refactoring, faster programs, better navigation, better documentation, better maintenance.
You're doing it wrong.
The point of monorepo is that if someone breaks something, it breaks right away, at build time, not at deployment time.
You're not really using a monorepo.
One person who worked on Titanic explains where these shots came from and how they landed there (they were for True Lies, and he and a bunch of friends were Amiga fans who convinced the team to use Amigas instead of the $60k equipment they were using).
- It's fast. - It's safe. Or more specifically, memory safe, which implies that it will be harder to compromise than similar products written in a different language.
Also, these two points are not hype.
Eng managers, directors, and VP's make tons more money than engineers.
"If your tasks spend most of their time waiting, use async. If they spend most of their time running, use threads"
?
These are not mutually exclusive and they describe actually two very different concepts.
If your objects will end up in a hashing container, you absolutely need to serialize what makes their identity. If not, you can serialize whatever you need from the object. It can be more fields than its identity, or fewer.
I'm not sure what your following point about serialization vulnerability (however correct) has to do with the current discussion.
You see that as a strength, I see it as a restriction because sometimes, I do like the extra flexibility of adding mutable state to my value objects.
And I know better than altering the value of hashcode after creation, although this only matters if you've put these objects in a hashing container, so it's not even a universal risk.
Either a state is part of the object's identity, and it's serialized, or it's not, and it's not. This observation has nothing to do with data classes, records, Java, or Kotlin.
> The result will be equal in the `equals` sense, but the resulting object will not be substitutable for the original.
This doesn't make sense either. You are describing someone who implemented flawed serialization. It's a programmer error, not a language or semantic one.
I see very little difference of practical importance between Java's records and Kotlin's value classe, and as much as I value your technical writings, I am concerned that your employer is tainting your objectivity when trying to compare Java and Kotlin. You can do better.
There will always be poor examples, but they don't invalidate the concept.
Smart web pages, when done right, are an incredible time saver, and if you're not convinced, go visit, for example, the web page of your bank from 15 years ago on the Wayback machine.
The difference between you and him is that you (rightfully) doubt your memory while he doesn't doubt his.
I think you are more likely to be correct than him.
[1] https://www.theregister.com/2022/12/02/android_google_rust/
And based on Google's track record, Dart is at risk of being cancelled any day without any notice.
Take a look at job boards and see how many job postings you find for React compared to Flutter.
It doesn't help Dart that Kotlin and Swift have been null safe languages for a decade now.
The billion dollar mistake was not null, it's languages that have a null value but don't support nullability in their type system.
Kotlin and Swift get this right.
a = b.wrapping_add(c);