What's New in Engine 3.4.4.1
by The SteelSeries Engine Team
We recently released Engine 3.4.4.1 with a hotfix for the new Dota 2 Reborn update.
We recently released Engine 3.4.4.1 with a hotfix for the new Dota 2 Reborn update.
We recently released Engine 3.4.4 with a bunch of bug fixes, and a couple of new devices. Let’s look at what’s new.
Now that GoLisp is becoming a more complete and powerful programming language, rather than a simple extension language for making DSLs, it’s time to have some real development tools for it. This post introduces the new GoLisp profiler.
We recently released Engine 3.4.3 with a bunch of bug fixes. Let’s look at what’s new.
When I started working on GoLisp I decided to write tests of the runtime/internals in Go using GoCheck, and tests of Lisp level behavior in Lisp. To that end I wrote a very simple testing framework with one function: describe
, which wrapped a sequence of predicate expressions, evaluated them and reported errors if they evaluated to something falsy. Generally, this took the form of a series of equality checks; it worked, but didn’t communicate very well.
With the impending version 1.0 release, I decided it was time to improve this.
GoLisp is maturing nicely, and I’ve recently made it a lot more like standard Scheme. This includes some breaking changes where I played fast and loose with the language earlier on. Now I’m bringing some of the more core things into line with how standard Scheme works. Because of that, I’ve decided that it’s time to slap a label on it. v1.0 is now what’s on the master
branch, and the previous master branch has been renamed legacy
.
So what’s new?
There are several improvements to the runtime, and the standard set of primitives has been expanded.
SteelSeries is happy to announce Dota 2 GameSense support in SteelSeries Engine!
We’ve worked with the team over at Valve to bring you another incredible experience.
We recently released Engine 3.4.1 with support for some new hardware and various improvements. Let’s look at what’s new.
For V1.0, I revisited the way primitive functions are handled to make them work more like regular functions (i.e. defined in Lisp using define
/lambda
). The visible change if you are writing primitives is that they now recieve evaluated arguments. I.e. they use applicative order of evaluation now. This is as it should be.