What are the current options? I've been looking but I haven't found any. I have a DS923+ and it works fine, but I can already see what you are talking about.
I have a DS 923+. These extremely old softwares you mentioned were always weird to me but everything worked fine so far. What I'm not happy about is the vendor lock in, and the abysmal virtualization / transcoding performance. I want a NAS that comes with a similar ease of use as the DSM, but can double down as a __very lightweight__ virtualization platform for my local test deployments and as a media PC that I can rely on. What would you suggest?
I'm not surprised at all. Nx is a mess, I migrated away a year ago after I got fed up with the constant struggle. The last straw was when I joined their Slack to ask a question (about a bug I wanted to report) and they quoted me for a $1000 retainer if I wanted to get help.
- Is there a LISP dialect that doesn't suffer from this problem? I can see that from time to time LISP projects start taking off just do die a year later and I'm stuck using Emacs (Lighttable comes into mind)
Depends on the program (especially the framework used) and the GC being used. I can write a java program and set it up in a way that it runs faster than almost everything else. For example in a serverless architecture where you need fast startup and small programs you can choose __not__ to use a GC and run ephemeral Java scripts. It starts and finishes running faster than you can blink.
node is a notable exception. Compared to java node is a hellhole. the standard library is non-existent, most libraries are a buggy mess, the build system is horrible...in fact there is no reliable build system that solves all your typical problems in 1 app. The list goes on.
Note that the memory problem you mentioned is not really a problem in fact. It is just how managed memory works in Java. Just run .gc() and you'll see what I'm talking about. It reserves memory which you can see on the charts but it is not necessarily used memory.
You don't have to use PHP so there is no reason to mock it. You just know it is shit and you move on. Unfortunately you __have to__ use javascript sometimes (or always) so there is reason to mock it. That's the reason why people always mock JS. It is omnipresent and you have to touch it with your bare hands.
i switched to python a while ago. it has batteries included. i feel so much better now that i dont have to debug all the quirks of a half-baked system.
this sounds like you had poor risk management...or didn't have any. I have a strike rate around 55% but all my trades are 3:1 reward:risk and i don't risk more than 1% on any one trade
> [...] free flow of information is the only safeguard against tyranny. [...] Beware of he who would deny you access to information, for in his heart he deems himself your master
Should I try Zig? I wanted to learn something that's more low level than the JVM/Node and i have been contemplating rust and go. zig never occurred to me until now.
I started building the second brain a while ago but I quickly started to feel like I was trying to dance while wearing a straitjacket so I stopped doing it.