投稿時間:2023-05-18 12:19:33 RSSフィード2023-05-18 12:00 分まとめ(27件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia News] Google、東京大学及びシカゴ大学の量子コンピュータ研究支援で最大5000万ドル出資	https://www.itmedia.co.jp/news/articles/2305/18/news123.html	google	2023-05-18 11:34:00
IT	ITmedia 総合記事一覧	[ITmedia News] VTuber事務所のホロライブ、サポーターガイドライン公開　「価値観の違い、認め合って」	https://www.itmedia.co.jp/news/articles/2305/18/news120.html	itmedianewsvtuber	2023-05-18 11:31:00
IT	ITmedia 総合記事一覧	[ITmedia Mobile] 「Galaxy S23 Ultra」のカメラを徹底検証　「100倍ズームで月もキレイに撮れる」は本当？	https://www.itmedia.co.jp/mobile/articles/2305/18/news037.html	ITmediaMobile「GalaxySUltra」のカメラを徹底検証「倍ズームで月もキレイに撮れる」は本当年月現在、サムスン電子のGalaxyシリーズで最もハイエンドなカメラを搭載するのが「GalaxySUltra」だ。	2023-05-18 11:30:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] よく利用するコンビニ　1位は「セブン」、2位以下は？	https://www.itmedia.co.jp/business/articles/2305/18/news114.html	itmedia	2023-05-18 11:28:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 暑くなったら売れる飲みもの、食べものランキング　それぞれ1位は？	https://www.itmedia.co.jp/business/articles/2305/18/news119.html	itmedia	2023-05-18 11:26:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] ベンキュー、右手持ち向けデザインのワイヤレスゲーミングマウス	https://www.itmedia.co.jp/pcuser/articles/2305/18/news116.html	itmediapcuser	2023-05-18 11:17:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 東岡崎駅で「商業施設」を計画、どう変わる？	https://www.itmedia.co.jp/business/articles/2305/18/news112.html	itmedia	2023-05-18 11:14:00
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	デジタルアーツ、ファイルを介した重要情報の漏洩を防ぐ製品「f-FILTER」を10月から提供 | IT Leaders	https://it.impress.co.jp/articles/-/24838	デジタルアーツ、ファイルを介した重要情報の漏洩を防ぐ製品「fFILTER」を月から提供ITLeadersデジタルアーツは年月日、DLPデータ漏洩防止ソフトウェア「fFILTERエフフィルター」を発表した。	2023-05-18 11:30:00
python	Pythonタグが付けられた新着投稿 - Qiita	pymongoを使用してPythonからOracle Database 23c Freeにアクセスし、JSON Relational Duality Viewをコレクションとして操作してみた	https://qiita.com/500InternalServerError/items/2dc8fd9bbad5892264ca	jsonrelationaldualityview	2023-05-18 11:44:53
python	Pythonタグが付けられた新着投稿 - Qiita	Pythonによる機械学習: AdaBoost、Gradient Boosting、Stochastic Gradient Boostingの解説と実装	https://qiita.com/F8LUUI5kOxLvrmuIAIPwFsUWSKNdgW5N/items/7d0d6033e24361118241	sticgradientboostingsgb	2023-05-18 11:27:20
Ruby	Rubyタグが付けられた新着投稿 - Qiita	RubyKaigi2023に参加してきました！！	https://qiita.com/pezio/items/d96f0acd9484b5620ef8	rubykaigi	2023-05-18 11:59:23
Git	Gitタグが付けられた新着投稿 - Qiita	Git スタッシュで作業を保存しておく	https://qiita.com/Kasumin0123/items/ededd03c48f596401f6a	途中	2023-05-18 11:22:11
技術ブログ	Developers.IO	毎日オフィス出社してから1ヶ月経過したので感じたことをまとめる	https://dev.classmethod.jp/articles/%e6%af%8e%e6%97%a5%e3%82%aa%e3%83%95%e3%82%a3%e3%82%b9%e5%87%ba%e7%a4%be%e3%81%97%e3%81%a6%e3%81%8b%e3%82%891%e3%83%b6%e6%9c%88%e7%b5%8c%e9%81%8e%e3%81%97%e3%81%9f%e3%81%ae%e3%81%a7%e6%84%9f%e3%81%98/	選択	2023-05-18 02:27:37
海外TECH	DEV Community	The inspiring extension systems design overview (Chrome & VSCode)	https://dev.to/jennieji/the-inspiring-extension-systems-design-overview-chrome-vscode-4bco	The inspiring extension systems design overview Chrome amp VSCode A few years ago I discovered the power of Chrome and VSCode extensions in improving productivity I created my own extension if my desired feature was not available The extension systems allow me to experiment my wild ideas with less effort thanks to their graceful design While they have similarities there are also some significant differences determined by the nature of each app In this blog post I will provide an overview of the extension systems of Chrome and VSCode and share what I have learned from them DevelopmentInitializationAPIsThe script triggersActivating extensionThe extension parts and interfacesEventsThe communication between partsUI UXTestingTesting a Chrome extensionTesting a VSCode extensionDistributionDistribution of Chrome extensionDistribution of VSCode extensionSummary of what I have learnt Development InitializationBoth extension systems have an entry point a JSON file Chrome extension starts from a manifest json file while VSCode extensions extend the package json file which can sometimes become lengthy and contain too much information I am worried about conflicts arise from the file In the JSON developer need to provide essential information such as icon for display and script to initialise with Each parts of a Chrome extension require a script file or a html file while VSCode only need an entry script Here is an example of a manifest json file for a Chrome extension name Broken Background Color version description Fix an Extension permissions activeTab scripting storage options page options html background service worker service worker js icons images icon png manifest version And here is an example of a package json file for a VSCode extension name cat coding description Cat Coding A Webview API Sample version publisher vscode samples activationEvents main out extension js contributes devDependencies In addition to these files Chrome extensions also require careful declaration of browser permissions to enable their APIs I totally understand the importance and difficulty of guarding browser security but providing excessive information that can be accessed through automation is unreasonable APIsThe extension APIs in both Chrome and VSCode are well categorized based on the functionality of the app This categorization allows developers to explore the possibilities by following the names of the app modules For example chrome cookies get url name cookie name cookie gt if cookie console log cookie value However there are possibilities that we have no clues about the name at all ‍ ️such as the text decoration in VSCode as mentioned in this blog Being a Microsoft product the coding style of VSCode extensions can sometimes be too OOP style For instance to implement a tree view we must declare a class extends the TreeDataProvider class and provides methods getTreeItem and getChildren export class DepNodeProvider implements vscode TreeDataProvider lt Dependency gt private onDidChangeTreeData vscode EventEmitter lt Dependency undefined void gt new vscode EventEmitter lt Dependency undefined void gt readonly onDidChangeTreeData vscode Event lt Dependency undefined void gt this onDidChangeTreeData event constructor private workspaceRoot string undefined refresh void this onDidChangeTreeData fire getTreeItem element Dependency vscode TreeItem return element getChildren element Dependency Thenable lt Dependency gt Plus the “traps I mentioned above in Chrome a well structured and clear document with rich example codes become vital The script triggersThere are three ways to trigger our scripts From the extension activation User interaction on the extension interface Internal events Activating extensionWhen a user enables an extension in Chrome the background script of the extension starts working immediately Chrome has migrated the extension background script to the Service Worker in manifest v making the extension work more like a web app In VSCode the whole extension initializes from one JS file and the main JS file need to export an activate function Developers shall declare the activation conditions in the package json file see the example above out extension jsexport function activate context It seems that Chrome tries to align the pattern with web development and VSCode adopts another style commonly seen in serverless development As a web developer the way of activating script in the Chrome extensions is more natural to me The extension parts and interfacesA Chrome extension may contain parts of scripts or HTML pages for different purposes a popup page for the popup activated from the menu next to the address bar panel pages in the developer tool a content script to interact with the web page content background scripts or page for more interactions They are just web pages or scripts allow to access Chrome APIs with some constrains We must declare the corresponding permissions in the manifest json Some APIs may only work in certain scope e g we can only access user tab document element from the content script VSCode defines too many parts to list in a blog see Contribution Points Some parts or we should call contribution points are so tiny that all they need are displaying texts and actions As multiple contribution points often result into the same action VSCode took a command approach Command is a scoped key name binding to a registered script We may define our own command in the package json contributes commands command myExtension sayHello title Say Hello And register the command in the activate function export function activate context const command myExtension sayHello context subscriptions push vscode commands registerCommand command gt console log Hello We may trigger either internal command or our customised command from its name vscode commands executeCommand editor action addCommentLine Or a Uri for text editor or webview const commandUri vscode Uri parse command editor action addCommentLine When everything relies on name all the problems we had debated for CSS class come across It may not cause any issue at all when the extension is small but it is hard to tell when the extension grows big In fact more names and complexities come with the command Taking one of the menu contribution point in my extension as example contributes view title command gitlabSnippets addHost when view gitlabSnippetsExplorer mine all group navigation The configuration above adds an icon button to the title of view panels VSCode requires A when clause expression mixing a bit flavor of bash and regular expressions ID like the view name “gitlabSnippetsExplorer mine above Position name like the “group above In return our design needs get minimized All we need to provide are the condition to display the icon and the description text In addition thinking in command forces developers to split part of the workflow and reuse as much as possible For example in my GitLab Snippets Explorer extension there is a addHost command showing up as a command palette menu item and an icon button in the view panels In the meantime another publishSnippet command simply jump to this adding host action if user select the “Adding new … option below EventsBoth Chrome and VSCode provide a set of events to interact with We may subscribe to a Chrome event like following chrome devtools network onNavigated addListener callback function In VSCode we may listen to an event with a slightly shorter path like this vscode workspace onDidChangeConfiguration callbackFunction We may fire some event manually For example in the VSCode TreeView it is necessary to inform data changes to with this onDidChangeTreeData fire in the TreeDataProvider export class ExampleTreeProvider implements vscode TreeDataProvider lt Dependency gt private onDidChangeTreeData vscode EventEmitter lt Dependency undefined void gt new vscode EventEmitter lt Dependency undefined void gt readonly onDidChangeTreeData vscode Event lt Dependency undefined void gt this onDidChangeTreeData event refresh void this onDidChangeTreeData fire This looks ugly and unbelievably long to me even worse in Typescript I thought the tedious method binding in the React class component was the worst thing I knew till I see this The communication between partsIn Chrome extensions communication between different parts is achieved through messaging It is similar to the messaging between browser main thread and workers Send a messagechrome runtime sendMessage message hello function response console log response Receive a messagechrome runtime onMessage addListener function request sender sendResponse if request message hello sendResponse message hello from background script Instead of messaging VSCode extension take advantage of the command design except for webview I think it may be more reasonable for webview to execute command instead of posting message if the message type is complex UI UXThe command design in VSCode also provides a convenient developer experience and a consistent user experience Developers only need to provide an icon label and description for most scenarios However this convenience can sometimes limit creativity and the overall user experience In contrast Chrome extensions offer more freedom for developers in terms of UI UX design Testing Testing a Chrome extensionTesting a Chrome extension is very similar to testing a web page There are a few differences You will need to manually load the compiled folder in chrome extensions and update a background script will bring you back there for a manual update You have to find the inspection window for a background script from the extension detail page or the service worker list You may have no idea of why things do not work due to a wrong manifest configuration such as permission missing You have to remove the developer version to revive the live installation Testing a VSCode extensionTesting a VSCode extension requires more learning efforts I confess that I am not motivated in adding automation tests in my small extensions since the VSCode APIs are everywhere The manual testing of a VSCode extension runs on the debug system of VSCode It is my favorite tool of debugging Node js Additionally the test runs on an isolated environment and the marketplace installation settings are not affected However I find it hard to trouble shoot the root cause sometimes as Details of the network requests are invisible Error messages from the message popup or the log panel are not helpful enough and very little tracing information is offered Passing the local testing does not mean the published one will work perfectly Distribution Distribution of Chrome extensionTo distribute a Chrome extension we need to Register a Google account and top up to become an eligible Chrome Web Store Developer Pack the extension to a zip manually as required Fill out a crazy long form to market the extension and declare the purpose of requesting for the permissions I mean each permission Wait for several days to pass or fail the review I was horrified by the long form at my first submission I didn t expect it would force me to bring out my design tool to get the screenshot size right and the file size small I thought we have image processing plugins for decades What made things worse was that I waited for a long review time due to a public holiday The result was an short Email of submission failure It took me some time to figure out the problem was requesting some unnecessary permission and filling in unclear information Once successfully submitting the extension we may see the basic download times and user review comments To understand more of the extension usage it is possible to integrate analytic tools like Google Analytics I forgot the details but it was not as straightforward as integrating in a normal web app Google allow to publish an extension without showing up in their search engine and the web store User may only access this kind of extension from a URL This is a perfect simple work around for internal extensions Distribution of VSCode extensionIn contrast the process of publishing a VSCode extension is incredibly simple and efficient Register an Azure account and get a personal token with marketplace access Install the latest version of CLI tool vsce vsce login with the account info Compile the code and vsce publish Usually within few hours will receive an Email of success or fail Well I took one more step to summarise the process but…No form fillings for the extension All the necessary information could be found in the package json README md just like npm do vsce does some simple review to fail fast and prevent meaningless waiting The review process was so short that I suspect it is mostly automated as well However I did meet a review failure without helpful information due to a “risky API usage And I also did find my extension not working as expected after publishing due to packing wrongly Similar to Chrome extension once successfully publishing a VSCode extension we may see the basic download times user review comments and a handy statics graph of the recent downloads Again it is far from enough to understand user behaviors and figuring out how to improve from these data Most of the Node JS monitoring tools are focusing on Node JS server not native tools with interfaces like this It seems to me that I have to setup the metrics and monitoring system by my own For the internal extensions someone had experimented and created an extension Private Extension Manager One of my brilliant teammate did fork and made some small changes to create an internal extension marketplace Summary of what I have learntFirst of all here are the essentials for an extension system based on my observation An entry point JSON is perfect for it but we need to design wisely I think it is great to reuse some information like name version description from the package json but there is conflict risk to extend the file designed for another system Super clear document about the extension concepts the APIs the configuration of extension parts the distribution guide etc Isolated runtime environment for the whole extension or even for each part of the extension A communication channel between the parts of the extension I love the command design from VSCode but it would be better to avoid trapping us in the naming battle and costing us to learn new expressions APIs categorised by feature consistent in style and similar to the existing standards to flatten the learning curve App events subscription Complete testing support It is complicated to make a good one but we may try to use the mature system from browsers A marketplace for user to discover and developer to publish analyse the extension usage A review workflow Automate as much as we can request as little information as we can The enhancement I believe is small but significantly improved developer experience is publishing tool like vsce We may fail faster with it It is also nice to have Helpful and traceable error messages Official solution for internal extensions More informative statistics And there are dark and bright sides to choose design freedom or programming efficiency and complex configuration No matter which choice we make extracting actions is a great choice for code reusability Last but not least I will try my best to keep away from Asking for declaring permission instead of finding out from the code Names a lot of names Creating new rule expressions	2023-05-18 02:04:58
Apple	AppleInsider - Frontpage News	Online Apple Store opens in Vietnam	https://appleinsider.com/articles/23/05/18/online-apple-store-opens-in-vietnam?utm_medium=rss	Online Apple Store opens in VietnamCustomers in Vietnam can now shop for Apple products via Apple s online store Hello VietnamApple s online store has been a staple of the company since Steve Jobs return in However as hard as it may be to believe it still isn t available in every country across the globe yet Read more	2023-05-18 02:22:45
海外科学	NYT > Science	Bird Flu Vaccine Authorized for Emergency Use in California Condors	https://www.nytimes.com/2023/05/16/science/condors-bird-flu-vaccines.html	months	2023-05-18 02:33:12
医療系	医療介護 CBnews	総合入院体制加算の届け出1年間で35％減-厚労省、周産期医療への影響を注視	https://www.cbnews.jp/news/entry/20230518110848	中央社会保険医療協議会	2023-05-18 12:45:00
金融	ニッセイ基礎研究所	外国人人口や外国人比率は、前回ベースの約２倍に増加する見込み－新しい将来推計人口を読む（４） 外国人人口や外国人比率への影響	https://www.nli-research.co.jp/topics_detail1/id=74837?site=nli	目次本稿の問題意識複雑な将来推計人口を読み解く推計の仮定と外国人の出入国の状況長期的に流入増の傾向だが、今回は現状横ばいと仮定今回の推計の仮定近年の高水準を反映して、直近年間の平均人数を年間適用出入国状況から見た評価コロナ禍前の入国増ペースが戻れば、今回の仮定より上振れの可能性外国人人口や外国人比率への影響人口は一定程度でピークを迎えるが、比率は上昇継続本稿での外国人人口や外国人比率の見方諸外国と同様に、とおりの仮定を比較年齢区分別の状況外国人人口は一定程度でピークを迎えるが、比率は日本人の減少で上昇継続総括外国人人口や外国人比率は、長期的には前回ベースの約倍に増加する見込み月日に公表された新しい将来推計人口は複雑な結果となった。	2023-05-18 11:15:34
ビジネス	ダイヤモンド・オンライン - 新着記事	ドイツ銀、米富豪の性被害女性らに103億円の和解金支払いへ - WSJ発	https://diamond.jp/articles/-/323141	被害女性	2023-05-18 11:18:00
GCP	Google Cloud Platform Japan 公式ブログ	OPPO によるモバイル デバイスの AI 機能を強化するための Google Vertex AI 活用法	https://cloud.google.com/blog/ja/products/ai-machine-learning/oppo-leads-with-ai-capabilities-on-mobile-devices/	これは、検索制約を自由に追加できることを意味し、この検索制約のためにAIモデルを最適化する必要があります。	2023-05-18 02:30:00
GCP	Google Cloud Platform Japan 公式ブログ	新しいアセットクエリで Security Command Center のアセット インベントリ管理を簡素化	https://cloud.google.com/blog/ja/products/identity-security/new-asset-query-simplifies-asset-inventory-management-in-security-command-center-/	GoogleCloudをご利用のお客様は、環境の拡大に合わせてクラウドのリソースとポリシーを管理する必要があります。	2023-05-18 02:10:00
IT	週刊アスキー	Apple Arcadeなぜ強い ゲーム開発者語る	https://weekly.ascii.jp/elem/000/004/136/4136932/	applearcade	2023-05-18 11:30:00
IT	週刊アスキー	【すき家】めかぶとオクラのねばつる食感でごはんが進む〜！「めかぶオクラ牛丼」23日から新登場	https://weekly.ascii.jp/elem/000/004/137/4137035/	食欲	2023-05-18 11:30:00
IT	週刊アスキー	入場無料！　ベイサイドプレイス博多にてフォークを中心とした音楽イベント「BAYSIDE FOLK JAMBOREE 2023」5月28日開催	https://weekly.ascii.jp/elem/000/004/137/4137124/	bayside	2023-05-18 11:20:00
海外TECH	reddit	Post Game Chat 5/17 Mariners @ Red Sox	https://www.reddit.com/r/Mariners/comments/13kljao/post_game_chat_517_mariners_red_sox/	Post Game Chat Mariners Red SoxPlease use this thread to discuss anything related to today s game You may post anything as long as it falls within stated posting guidelines You may also post gifs and memes as long as it is related to the game Please keep the discussion civil Discord Seattle Sports Line Score Game Over R H E LOB SEA BOS Box Score BOS AB R H RBI BB SO BA RF Verdugo RF Tapia R B Turner J B Casas LF Refsnyder B Devers B Valdez E DH Yoshida SS Hernández K B Reyes P CF Duran Ja C Wong BOS IP H R ER BB SO P S ERA Bello Rodríguez J Martin Sherriff Garza SEA AB R H RBI BB SO BA SS Crawford J B Haggerty B France T CF Rodríguez Ju LF Kelenic B Suárez E C Raleigh RF Hernández T DH Trammell SS Caballero J SEA IP H R ER BB SO P S ERA Gonzales Gott Brash Speier Flexen Scoring Plays Inning Event Score B Rafael Devers singles on a line drive to center fielder Julio Rodriguez Justin Turner scores Rob Refsnyder to nd B Pablo Reyes doubles on a sharp line drive to left fielder Jarred Kelenic Rob Refsnyder scores Rafael Devers scores Masataka Yoshida to rd B Justin Turner homers on a line drive to left field Alex Verdugo scores B Enrique Hernandez singles on a ground ball to right fielder Teoscar Hernandez Rob Refsnyder scores Masataka Yoshida to nd B Pablo Reyes doubles on a sharp line drive to center fielder Julio Rodriguez Masataka Yoshida scores Enrique Hernandez scores B Jarren Duran singles on a ground ball to center fielder Julio Rodriguez Pablo Reyes scores T Jose Caballero singles on a ground ball to second baseman Pablo Reyes Cal Raleigh scores B Rafael Devers doubles on a fly ball to right fielder Teoscar Hernandez Justin Turner scores Rob Refsnyder to rd B Masataka Yoshida grounds out second baseman Jose Caballero to first baseman Ty France Rob Refsnyder scores Rafael Devers to rd B Enrique Hernandez out on a sacrifice fly to center fielder Julio Rodriguez Rafael Devers scores T Julio Rodriguez grounds into a force out shortstop Enrique Hernandez to second baseman Pablo Reyes Jose Caballero scores Sam Haggerty scores Ty France out at nd Throwing error by second baseman Pablo Reyes Highlights Description Length Video Bullpen availability for Seattle May vs Red Sox Video Bullpen availability for Boston May vs Mariners Video Fielding alignment for Boston May vs Mariners Video Rafael Devers plates one on a single to center field Video Pablo Reyes scores two on a double to left field Video Alex Verdugo makes a running grab at the wall Video Justin Turner lifts a two run homer to left field Video KikéHernandez scores one on a single to right Video Pablo Reyes scores two on a double to center field Video Jarren Duran smokes a RBI single into center field Video Breaking down Marco Gonzales s pitches Video Justin Turner Home Run Statcast Analysis Video A deep dive into Justin Turner s home run Video The Red Sox rally for a six run nd inning Video Jose Caballero scores Raleigh on an infield single Video KikéHernández steals a hit from J P Crawford Video Rafael Devers plates one on a double to right field Video Yoshida scores Refsnyder on an RBI groundout Video KikéHernández extends the lead with a sac fly Video Julio Rodríguez s RBI forceout Video Breaking down Brayan Bello s pitches Video Brayan Bello s outing against the Mariners Video Brayan Bello fans seven over five innings Video Marco Gonzales freezes Jarren Duran for the strikeout Video Decisions Winning Pitcher Losing Pitcher Save Bello ERA Gonzales ERA Attendance Weather Wind °F Clear mph Out To RF HP B B B Mike Estabrook Andy Fletcher Erich Bacchus Laz Diaz Game ended at PM submitted by u Mariners bot to r Mariners link comments	2023-05-18 02:12:58
GCP	Cloud Blog JA	OPPO によるモバイル デバイスの AI 機能を強化するための Google Vertex AI 活用法	https://cloud.google.com/blog/ja/products/ai-machine-learning/oppo-leads-with-ai-capabilities-on-mobile-devices/	これは、検索制約を自由に追加できることを意味し、この検索制約のためにAIモデルを最適化する必要があります。	2023-05-18 02:30:00
GCP	Cloud Blog JA	新しいアセットクエリで Security Command Center のアセット インベントリ管理を簡素化	https://cloud.google.com/blog/ja/products/identity-security/new-asset-query-simplifies-asset-inventory-management-in-security-command-center-/	GoogleCloudをご利用のお客様は、環境の拡大に合わせてクラウドのリソースとポリシーを管理する必要があります。	2023-05-18 02:10:00