Back to the channels

#java

1. 06:17 Bombe Casting for me always means that I fucked up the data model somewhere.
2. 06:17 Bombe (Exceptions apply for basic utility/library code, or interactions with other APIs.)
3. 06:33 Para Builder hierarchies have an use for casting as well.
4. 06:39 jreicher Bombe: it's not an explicit cast. As I said the return type of the method is non-covariant. That might be a nice way of "evidencing" that it's not a screw up, but an (unusual) way of expressing a constraint I want the compiler to check.
5. 06:46 Para I document my intentional casts with Class#cast()
6. 07:02 jreicher Interesting. Not familiar with that syntax.
7. 10:07 jreicher Bombe: did you mean to write Class#cast()? I assumed it was a syntax I didn't know, but I can't find anything on that.
8. 10:07 jreicher Sorry, Para ^
9. 10:07 Para yes
10. 10:08 Para That's how methods are generally referenced in javadocs and other such :P
11. 10:08 Para Classname#methodname(Param1,Param2)
12. 10:08 Para https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/lang/Class.html#cast(java.lang.Object)
13. 10:08 nevet Class (Java SE 25 & JDK 25)
14. 10:09 Para That's also useful because it throws in place, so the wrong type doesn't go on an adventure through execution flow.
15. 10:21 jreicher Oh, that's what you mean. OK. But an upcast is not actually a cast in this sense.
16. 10:21 jreicher Nothing is done at runtime.
17. 12:49 dreamreal Lore (https://lore.org/) looks interesting but the reference implementation using dynamo means NEVERRRRRRRR
18. 12:49 nevet Learn about Lore: next-generation open source version control
19. 12:49 javabot dreamreal's title: "Lore | Next-Generation Open Source Version Control - Lore"
20. 14:09 nimaje (why do webdevs think everything has to be invisible and their html a huge mess?)
21. 14:10 Para For context, Lore is VCS for games. So excellent binary file, vendored dependencies, copyright/legally restricted parts of the whole with granular permission management etc.
22. 14:42 cheeser i think we're due for new vcs systems to vie for the crown.
23. 14:58 Para git sucks for non-text so there's space
24. 15:08 cheeser git isn't great for usability so there's space. :)
25. 15:13 ernimril you prefer sourcesafe? or subversion?
26. 15:13 cheeser bitkeeper for life!
27. 15:14 Para email!
28. 15:15 fizzie Perchance Perforce.
29. 15:15 ernimril "oh, my quota is full, lets just send a large (several MB) to new zeeland, It will bounce in a few days..." :-) Sadly it does not work that way anymore
30. 23:02 jreicher https://darcs.net/
31. 23:02 jreicher Never used it, but always wished I had
32. 23:07 NeXeN i once tried to make a version control system, and failed
33. 23:13 jreicher By the time I started using version control, subversion was becoming popular, but I decided to start with RCS. I'm very glad I did because it showed me how hard the problem is to solve, and what a good (albeit incomplete) solution looks like. It was a very "clean" introduction to the space.
34. 23:16 NeXeN i used cvs then git
35. 23:16 NeXeN i wasn't on the bandwagon at any time, i sort of had to learn it because it was becoming the standard
36. 23:18 jreicher I'd be surprised if anyone with "taste" is on the bandwagon. Git is not perfect.
37. 23:18 jreicher I particularly hate the porcelaine.
38. 23:18 jreicher porcelain
39. 23:19 jreicher If it weren't for the decent quality of the various frontends it probably wouldn't have taken off. Ironically it might be the scriptability of the command line that enabled them to emerge. I've never really checked the history.