Jakub Janeček
@jakubjanecek.bsky.social
It's not perfect but the timestamp is in the hover popup.
March 28, 2025 at 9:26 AM
It's not perfect but the timestamp is in the hover popup.
Reposted by Jakub Janeček
The tech industry has to stop castrating itself with such awful, hideous, complexity.
The ultimate sophistication is simplicity, and right now, the software industry is extremely unsophisticated.
The ultimate sophistication is simplicity, and right now, the software industry is extremely unsophisticated.
February 11, 2025 at 2:49 PM
The tech industry has to stop castrating itself with such awful, hideous, complexity.
The ultimate sophistication is simplicity, and right now, the software industry is extremely unsophisticated.
The ultimate sophistication is simplicity, and right now, the software industry is extremely unsophisticated.
I agree. However, in my opinion using descriptive names is very close to actually putting the definitions into named object (it's basically just one extra line like "object MyUtils:") so given the surprise with bincompat and filenames I rather do that to be explicit.
Dropped: Package Objects
docs.scala-lang.org
December 2, 2024 at 4:17 PM
I agree. However, in my opinion using descriptive names is very close to actually putting the definitions into named object (it's basically just one extra line like "object MyUtils:") so given the surprise with bincompat and filenames I rather do that to be explicit.
Exactly! Changing the filename is not binary compatible which in my view is very unexpected (though logical). It's actually described here: docs.scala-lang.org/scala3/refer...
Dropped: Package Objects
docs.scala-lang.org
December 2, 2024 at 4:15 PM
Exactly! Changing the filename is not binary compatible which in my view is very unexpected (though logical). It's actually described here: docs.scala-lang.org/scala3/refer...
How do you deal with the fact that the filename gets encoded into the FQN of the method? It's logical and not anything new but given how top-level definitions are presented I was very much surprised when I got conflicts because I had the same filename (e.g. package.scala) in main and test sources.
December 2, 2024 at 11:21 AM
How do you deal with the fact that the filename gets encoded into the FQN of the method? It's logical and not anything new but given how top-level definitions are presented I was very much surprised when I got conflicts because I had the same filename (e.g. package.scala) in main and test sources.