Notes from the language.

It's all about the beat.

I'm happy. I'm feeling glad.

The Art Of Computer Programming Volume 3. Kind of. Again. This time with hash.

LINQ? I think I've seen that one — but that was a year ago.

So meta. Much wow.

It's an anniversary. Why don't I feel like celebrating?

Never send bot to think about mans job.

I have macros and I'm not afraid to use them.

Much code. Very explain. Wow.

It was a fun little experiment while it lasted.

I feel like I've done this before. It brings back memories.

The Art Of Computer Programming Volume 3. Kind of.

Yes and No.

Why internal tools?

The lint apocalypse is coming and you are not prepared.

I like live coding. Here, I said it.

You say You are AI friendly. But how friendly are You?

Sometimes technical debt gets paid off.

Sometimes little things make big difference.

This is going to be a good one. It's an iceberg.

LINQ? But Boris, DASLANG already has high-order functions.

There are ways to die EDSL, and there are ways to die EDSL.

Its very easy to ignore reality. Ignoring effects of ignoring reality - now that's tricky.

Construction can't be finished, only stopped. 0.5 is out.

Das is not a write-only code. The idea is we read more than we write. There is "write as you speak", but there is also "read as you listen".

Updated on 2024-07-29 16:31:00

Sometimes shorthand notation arrives first.

What do a mafia boss and a garbage-collector have in common? Both make sure you'll never see unwanted things again!

The plug has been pulled. Daslang it is. Take a look at dasCHash too ( C#->DAS ).

0.4 is out. Its a big deal. Its not a big deal.

Hectic is exactly the word which comes to mind, when I look at the commit history for the month.

Its a matter of multiplication, really. Productivity factors do not just add up (thats why they are called factors).

It has to be stable. The time has come to test the damn thing.

In the world of computer programming, there is a concept known as pattern matching. This technique allows us to take a complex value, such as an array or a variant, and compare it to a set of patterns. If the value fits a certain pattern, the matching process continues and we can extract specific values from that value. This is a powerful tool for making our code more readable and efficient, and in this section we'll be exploring the different ways that pattern matching can be used in daScript.

It's stupid. It's ugly. Its also measurable performance gain.

From dascript.org "... is high-level, statically strong typed scripting language, designed to be fast ..."

With an emphasis on fast. Performance first, last, and foremost.

Whats in a name? The sheer fact that I'm writing this post implies a problem. "It's not a script" is something we had to say on numerous occasions.

• Boris ELI5 script?
• Script is a simple programming langue you write your game logic in. When it gets slow you rewrite it to C++.

daScript is none of the above.

During the last few days I took a small detour from the land of the JIT, to the land of the profiler.

In the early days of daScript development having robust JIT was never a priority. In fact during the initial planning meetings JIT was postponed until the cows came home.

Herb Sutter is right. Its the same thing year after year after year. Lifetime, Initialization, Type safety, and Bounds safety are the things which your language should do for you.

Consider the following example:

[export]
def main
    var a <- [{int 1;2;3;4}]
    for x in a
        a |> push(13)   // kaboom

It causes daScript runtime panic.