And you don't care if a malicious party compromises the development machine on which it runs? I can think of a whole lot of really damaging things that somebody could do running arbitrary JavaScript code with user-level privileges on thousands of developer workstations.
With various CI setups and some server-side rendering configurations, there are potentially scenarios where build tooling actually do run in environments where there are higher risks, though it's not as applicable in this specific case.
Not really about security, but I've seen some deps that even track their usage (aggressively). So, I totally agree with the "not having the same scrutiny" as other tooling methods.
You are probably on to something. Most Norwegians are so used to being protected as consumers so a lot of the time they are taken by surprise when acting as professionals.
True, always funny when someone skimps on taxes by buying a computer for private use as "a professional", and then gets angry when it wont get fixed for free.
But with that said, I think most stuff in an EULA wouldn't be enforceable even in a professional context. And the worst thing to happen when breaking an EULA would probably you lose your right to use the product, not whatever they wrote in the EULA.
That's perhaps in Poland, the Baltics and the former Soviet Block. France, Germany, Norway, etc will promptly put 100+K€ on the table for an experienced consultant in some niche.
Why on earth would it not apply to programmers? We accumulate just as much cruft, if not much more, than the usual person. I have old 8086s, Atari's, tons of computer peripherals for ports I no longer have, etc. Most of it chucked away in some attic (somewhere). We gather stuff that obsoletes fast than anything, besides food. And we as a industry produce it too: I had a Nokia 3110 for close to a decade. Now my phones seldom last me two years.
I think it will depend on where you are at in the 'programmer' journey. For me, while it was still an exciting hobby decades ago, I used to collect PCs and consoles, keyboards and peripherals etc. just to tinker with them and experiment.
Then, as programming became more and more of a 'day job' and not a fun side project, I found myself getting rid of the clutter of obsolete equipment around the place. 35 years later, I am happy with just a basic iMac as my main development machine, and a Lenovo laptop as my Windows/backup development machine. That is it. No more multi screen setups or fancy keyboards & mice even - just stock standard stuff to get the job done so I can spend energy on my passion projects.
Sounds exactly like my journy. I used to 'pride' myself on having a *nix running on all the major CPU families (x86, PPC, Sparc, alpha and MIPS) sitting in my study. Now I just have a basic PC and a laptop.
Really interested in hearing if the ideas on how to transform game programming into a more productive form panned out. Did you end up using the ideas in a later product?
This is known for decades. If you drop too fast over too long period of time your metabolism changes base burn rate and you will have a hard time losing fat/staying the same weight once your normalize your diet. There is a reason diets like PSMF at restricted to 1-2 weeks. Not healthy over time.
I've now read several studies about successful long term weight loss maintenance. And none of them mention speed of weight loss as a factor. The Wikipedia article on it doesn't mention it.
Also here's a study that suggests the exact opposite, that rapid weight loss is correlated with long term success.
