jdellinger

5 anni fadiscuss

Looks nice and clean! Also feels very snappy in two tabs.

However, you're breaking the back button with your redirect to a unique room. Once in a room, pressing back will join a new room. History replace instead of push should be a better choice.

jdellinger

6 anni fadiscuss

The current beta uses 7 processes with a total RAM of 139MB, so not as bad as some electron apps.

Old TS3 client uses 60MB.

jdellinger

6 anni fadiscuss

  Location: Munich / Germany
  Remote: Yes (onsite preferred)
  Willing to relocate: No
  Technologies: TypeScript/C#/Elixir/C/Rust Web/Embedded/DevOps React/VueJS/NestJS/Absinthe/Postgres/Redis/Docker/Kubernetes
  Résumé/CV: https://www.dellinger.dev/resume/
  Email: jonas [that-symbol] dellinger.dev

I'm nearing the end of my CS master and I'm currently looking for a summer internship for 2021 (flexible regarding date/duration). I'm mostly interested in backend or embedded work, but in the end I'm very open for interesting projects of other fields as well.

jdellinger

6 anni fadiscuss

In .NET we have a very similar tool for creating such packed binaries, dotnet-warp. I used it in one of my projects and quite liked it, since it's also quite easy to cross compile (cross-pack?) for the 3 major operating systems.

I like the general idea, your independent of the system wide framework version and it still has this "one-click" install procedure (dropping the binary in your path). However, I guess this is also the negativ Part. Users don't expect that a single binary extracts itself to somewhere --> uninstalling the binary leaves traces on the system.

Definitely looking forward to try it out for elixir, wondering how fast the erlang/elixir startup really is.

jdellinger

6 anni fadiscuss

So I recently had the opportunity to use the new composition API, which will come in V3, in a project and want to share my two cents. The project had some limitations tho: no webpack and no typescript (so basically inline x-templates and pure browser JS).

Starting of with the composition API was great. No "this", easy reuse of logic via react-like "useXYZ" hooks and a general fast development. But two things really bugged me:

* You need to be really careful when passing around values and how you handle them. Destructure a Proxy object? You instantly lose reactivity. Not using a reference to proxy object in computed? Changes won't trigger the computed function. There is a lot of magic involved and while it may seem that it takes a lot of "thinking" from you, once it doesn't work you will have to rethink and maybe even ditch some of the underlying language's features.

* "ref" vs "reactive", where "ref" is used for primitives which need a proxy object wrapper and "reactive" is used for objects/arrays. Now, my primary problem is that you again have to use specific operations based on whether your using ref or reactive. A "ref" array can be easily set to an empty array via `arr.value = []`. If you try this with a "reactive" array, you will lose reactivity; you would have to use `arr.length = 0`.

TypeScript detects a lot of those pitfalls and, IMO, it is essential when using the composition API. Without it, there is too much invisible magic happening.

jdellinger

6 anni fadiscuss

While kube-ps1 helps, remember that the context is set session-wide. So even if your last command says "development" in one terminal, another terminal may have modified the context by now.

So make sure to spam the return key before deleting stuff :D

comments