Java has hadoop, spark, swing, spring, jaxb, jta, jdbc, atomikos, quartz, velocity, beanshell, ...
iOS has a ton of weird names as well in frameworks. Knowing the lay of the land is part of taking part of any ecosystem. I actually like the names. As of VW you tell me what AppeX and SiouX are without knowing upfront. Phil Le 6 févr. 2015 12:48, "Sean P. DeNigris" <[email protected]> a écrit : > Markus Fritsche-4 wrote > > +1 to that one. > > Yes, I also find it difficult - much more so when I was new to the > community, but even still a bit now. Coral, Zinc, Seaside, Opal - may be > catchy, but when I'm browsing the system, I just want to see where the darn > WebClient is, not mine for minerals or go to the beach!! ;) j/k. But > seriously, it's one thing to have "sexy" names at the top level - Pharo, > Squeak, Ruby, Python; but inside the system, it definitely creates > confusion. It's perhaps extra difficult for us because some of these > projects have both an outside and inside identity. It's an interesting open > problem... maybe some metadata at the MetaC/package level could help? Like > some standard tags like #WebClient, #Compiler, etc to say logically what > role a project fills... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Switching-to-Pharo-from-Visualworks-tp4803811p4804142.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >
