I’m a software engineering developer from Ottawa, Ontario, Canada.
Just the historical Russian ties, which is enough for some people/organizations to avoid them. The biggest practical reason is the dependence on tooling. Kotlin is a great language, but loses a lot of its allure when you can’t use an IDE for whatever reason. It makes sense, given that its developed by a company whose main product is IDEs; but it can still be an issue in some circumstances.
Good clarification, thank you. I guess it would still require some extra care when interfacing with plain Java libraries, but so does e.g. Kotlin. Cool implementation.
There are many valid practical reasons to avoid Kotlin in certain circumstances (not the least of which being Russian ties). More tools for Java isn’t necessarily a bad thing. However I don’t really think it works. It reminds me of this blog post: https://www.javacodegeeks.com/2017/02/elvis-not-visit-java.html which I think accurately reflects many of my thoughts about null-safety in Java.
I decided that at my scale, NixOS is easier to maintain. So for me its just a `systemctl status <thing I host>ˋ
Thats exactly what I so often find myself saying when people show off some neat thing that a code bot “wrote” for them in x minutes after only y minutes of “prompt engineering”. I’ll say, yeah I could also do that in y minutes of (bash scripting/vim macroing/system architecting/whatever), but the difference is that afterwards I have a reusable solution that: I understand, is automated, is robust, and didn’t consume a ton of resources. And as a bonus I got marginally better as a developer.
Its funny that if you stick them in an RPG and give them an ability to “kill any level 1-x enemy instantly, but don’t gain any xp for it” they’d all see it as the trap it is, but can’t see how that’s what AI so often is.
How is #6 not specific to IDEs? I’ve never had vim, np++, or any other dedicated editor freeze; and I’ve used them to edit multi-gigabyte log files before.
Out of curiosity, what is the original?
Except that AWS is (for better or for worse) a tier 1 network solutions provider, in part because of advertised uptime. Due to that, it is possible for a minor AWS outage to result in lack of 911 service in an area, for example. Hopefully they have the common sense to try out these new things on less critical nodes though.