{"title":"前端Web开发中的障碍","authors":"David I. Samudio, Thomas D. Latoza","doi":"10.1109/vl/hcc53370.2022.9833127","DOIUrl":null,"url":null,"abstract":"—Developers building web applications constantly face challenges, particularly in working with complex APIs. In response, developers often turn to Stack Overflow, offering a window into the programming barriers developers face. We examined 301 posts on Stack Overflow related to front-end web development and systematically characterized the challenges present in these posts. We found that most challenges reflected not a request for new code or an explanation of an error message but a request about how a specific code snippet might be edited to make its behavior as desired. Many challenges also reflected an underlying need to gather information about how specific code idioms are implemented within a framework or library. We identified 28 barriers developers face in front-end web development. Our findings suggest opportunities for facilitating more effective interactions with complex APIs through new types of programming content and tools that better address barriers in working with code idioms. An idiomatic diagnostic system identifies a relevant graphical barrier and asks the developer for the desired behavior based on the visual selection (1). It then shows how to overcome the barrier, GB2. A step-by-step explanation of relevant APIs summarizes the current behavior: the style property (2) is not mutating in-between graphical setters (3, 4), as logged by the system (2, 5). A code change is suggested to achieve the desired behavior.","PeriodicalId":351709,"journal":{"name":"2022 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)","volume":"2013 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2022-09-12","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Barriers in Front-End Web Development\",\"authors\":\"David I. Samudio, Thomas D. Latoza\",\"doi\":\"10.1109/vl/hcc53370.2022.9833127\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"—Developers building web applications constantly face challenges, particularly in working with complex APIs. In response, developers often turn to Stack Overflow, offering a window into the programming barriers developers face. We examined 301 posts on Stack Overflow related to front-end web development and systematically characterized the challenges present in these posts. We found that most challenges reflected not a request for new code or an explanation of an error message but a request about how a specific code snippet might be edited to make its behavior as desired. Many challenges also reflected an underlying need to gather information about how specific code idioms are implemented within a framework or library. We identified 28 barriers developers face in front-end web development. Our findings suggest opportunities for facilitating more effective interactions with complex APIs through new types of programming content and tools that better address barriers in working with code idioms. An idiomatic diagnostic system identifies a relevant graphical barrier and asks the developer for the desired behavior based on the visual selection (1). It then shows how to overcome the barrier, GB2. A step-by-step explanation of relevant APIs summarizes the current behavior: the style property (2) is not mutating in-between graphical setters (3, 4), as logged by the system (2, 5). A code change is suggested to achieve the desired behavior.\",\"PeriodicalId\":351709,\"journal\":{\"name\":\"2022 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)\",\"volume\":\"2013 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2022-09-12\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2022 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/vl/hcc53370.2022.9833127\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2022 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/vl/hcc53370.2022.9833127","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
—Developers building web applications constantly face challenges, particularly in working with complex APIs. In response, developers often turn to Stack Overflow, offering a window into the programming barriers developers face. We examined 301 posts on Stack Overflow related to front-end web development and systematically characterized the challenges present in these posts. We found that most challenges reflected not a request for new code or an explanation of an error message but a request about how a specific code snippet might be edited to make its behavior as desired. Many challenges also reflected an underlying need to gather information about how specific code idioms are implemented within a framework or library. We identified 28 barriers developers face in front-end web development. Our findings suggest opportunities for facilitating more effective interactions with complex APIs through new types of programming content and tools that better address barriers in working with code idioms. An idiomatic diagnostic system identifies a relevant graphical barrier and asks the developer for the desired behavior based on the visual selection (1). It then shows how to overcome the barrier, GB2. A step-by-step explanation of relevant APIs summarizes the current behavior: the style property (2) is not mutating in-between graphical setters (3, 4), as logged by the system (2, 5). A code change is suggested to achieve the desired behavior.