156 karma · joined November 22, 2016
If you are used to api calls from a client, then this doesn't do that sort of thing.
Support couldn't seem to support me.
I would probably still be on that IDE if not for that.
VSCode seemed to handle the incremental builds in a much better sane fashion.
Well, with Linux, any number of interfaces and themes are available. There is even a 'windows' theme to reduce the migration curve. If you supply respectable hardware and GPUs, there should be zero issues with slowness or instantaneous feedback.
Make sure the hardware platform works well with the distribution and its drivers. Ensure that your artists don't deal with these issues, and that your IT team pre-tests all builds and upgrades.
I have no basis in reality for this suggestion, but I'd go with a lightweight window manager like LXDE rather than heavy weight gnome or kde. Less eye candy and straight functionality. And less drain on resources.
Someone was talking about problems building on hardware. This isn't really an issue if you builds are automated: allows machines to be rebuilt on major upgrades. This, of course, requires that data drives and directories either be on separate partitions or on the network.
Perhaps better comparisons would be: how many deaths are there in the world per day? Before and after the instigation of covid19? How many deaths due to pneumonia before and after?
Has the death rate in other categories been reduced? Are there fewer accidents? Maybe we should just lock down forever because it might save at least one death due to accident?
"On a long enough time line, the survival rate for everyone drops to zero".
Isn't "secure egress gateway" descriptive as well?
I run two HP Z32 4k monitors side by side in portrait mode. Running Debian Linux Buster. Connected to NUC8i7hvk. LXDE, sometimes KDE. Text is clear. Moving windows around is smooth as silk.
27" would be too small. 30" is about the right size for the resolution.
Plus I have five or six virtual desktops to task switch between various development projects.
VSCode with CMake, clangd, and C++ code filter seems to work for the little I've used it so far.
Havn't quite taken the leap of faith in VIM, clangd to see if that is suitable.
A subnet should only be in one vlan, but there are networks where there is more than one subnet in a vlan.
Whether that is appropriate or not, that would be a different topic.
I have bare metal servers tied together with L3 routing via Free Range Routing running BGP/VxLAN. It Just Works.
No hard coded vlans between physical machines. Just point-point L3 links. Vlans are tortuous between machines as a Layer 2 protocol, given spanning tree and all of its slow to converge madness.
Therefore a different Golden Rule:
Always. Overlay. Your. Network.
Leave a note if you'd like more details.
"And this is why I think Kubernetes will disappear. It’s so generic that there’s no reason to do it yourself. Few organisations operate on a scale where it makes sense to run datacentres. The practical friction of running Kubernetes creates a similar dynamic. Like reliable infrastructure, it’s too hard, slow or expensive to justify doing it really well yourself, but there probably is value in paying for that as a service from a cloud provider."
Basically saying: it will still exist, but just outsourced to some one else's computer.
With the server side rendering, it is able to detect browsers where javascript has been disabled and then render html-only pages.
So whether it means anything or not, server side rendering can service a wider audience than can client side renderers.