- in 2022 a decision was made to abolish leap seconds by 2035, by allowing UTC to drift from the time as defined by Earth's rotation (UT1)
- negative leap seconds, while established, were never actually used
- ice melting caused by climate change has a slowing down effect on rotation of the planet, delaying a need for a negative leap second until 2029, otherwise forecasted in 2026
I've tried to use macOS with case sensitive filesystem for some time (before APFS). Works mostly fine but there're applications that break (Steam and Intellij IDEA are the two I remember).
I'd be a fashion designer. Oftentimes I feel like software engineering doesn't give me an opportunity to fully realize my creative self. Mostly because of people, not because of technology. Creativity is not valued for its own sake in software development and you cannot just say "that's the way I see". I feel it narrows down my life perspective too much.
It seems to me like most of the problems of modern tech are related to quality yet everyone is rushing for new features and quantitative "improvements".
Let's take a look at GNU tar [1] and GNU social [2] webpages as examples. The first thing they tell a user is what the project is. I would say, both of them are order of magnitude better than the yarn homepage.
I went to DuckDuckGo to check out what yarn is. The front page makes no mention of JavaScript at all (at least on mobile). Accordingly to DuckDuckGo the whole site mentions "JavaScript" only three times. The same is true about the GitHub readme: no mentions of JavaScript at all. Before praising something, makes sense to tell people what it is.
/rant
Thanks for the highlight, I use npm solely for global installs, will give yarn a try.
I've been writing Java in Vim from time to time for 3 years. Rust is much more pleasant to deal with in a plain text editor. I encourage you to give it a try.
Some of this issues could be resolved while staying within plain text, well to some extent at least. There're various attempts to encode metadata into plain text source code. Loading partially incorrect code should be possible, that's what many IDEs do successfully.
Plain text is the most portable data format ever invented, any incentive to replace it should have very convincing benefits.
I like the colours and am curious if it's a known colorscheme available for other environments (Vim, Emacs, terminals) or is it designed from scratch. Thanks for pointing to the config, it could be used to replicate the colorscheme for other editors.
Why should we break compatibility with plain text based tools to achieve what Lamdu is set to achieve? AST could be an intermediate representation but source should be text. Parsing/generating source to and from AST is some work but doesn't look like an unsolvable problem. We would got all the benefits without actually throwing away all the existing tools. Am I missing something?
The quote is missing important context. Just want to clarify that author is speaking about microservices specifically. The whole point of microservices is that one could be rewritten in a matter of days without involving substantial risks and expenses.
The cost of managing microservices and whether multilingual environment pays off is a separate question. Rewriting a now much better understood solution using an appropriate technology could have dramatic effect.