投稿時間:2022-04-12 13:20:53 RSSフィード2022-04-12 13:00 分まとめ(31件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	「モンスターファーム」シリーズ完全新作の『LINE：モンスターファーム』が年内リリースへ	https://taisy0.com/2022/04/12/155651.html	育成ゲーム	2022-04-12 03:30:35
IT	気になる、記になる…	Appleの｢Dual USB-C Port 35W 電源アダプタ｣の製品画像が流出	https://taisy0.com/2022/04/12/155647.html	apple	2022-04-12 03:13:19
IT	ITmedia 総合記事一覧	[ITmedia News] 「note」に19の新機能　小見出し、箇条書き、画像一斉アップ、Markdownショートカットなどを追加	https://www.itmedia.co.jp/news/articles/2204/12/news108.html	itmedia	2022-04-12 12:45:00
IT	ITmedia 総合記事一覧	[ITmedia News] 「練馬のものは練馬に」時代が終わった　シェアサイクル通勤してみて分かったこと	https://www.itmedia.co.jp/news/articles/2204/12/news091.html	itmedia	2022-04-12 12:34:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] ミドル世代にちょうどいい！　iiyamaの湾曲ディスプレイ「G-MASTER GB2766HSU-1A」を満喫した	https://www.itmedia.co.jp/pcuser/articles/2204/12/news096.html	gmastergbhsua	2022-04-12 12:30:00
IT	ITmedia 総合記事一覧	[ITmedia News] データセンター新設に前向きな土地リスト、経産省が公開　地方のDC誘致を支援	https://www.itmedia.co.jp/news/articles/2204/12/news105.html	itmedia	2022-04-12 12:22:00
IT	ITmedia 総合記事一覧	[ITmedia Mobile] ドコモで通信障害　一部地域とiPhone 13で通信しづらく　約6時間後に回復	https://www.itmedia.co.jp/mobile/articles/2204/12/news103.html	iphone	2022-04-12 12:20:00
IT	ITmedia 総合記事一覧	[ITmedia News] 任天堂、新たな研究開発施設を本社隣に建設　約1万平方メートルの市有地を50億円で取得	https://www.itmedia.co.jp/news/articles/2204/12/news101.html	itmedia	2022-04-12 12:19:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] Meta Quest用最新アップデート“v39”を告知	https://www.itmedia.co.jp/pcuser/articles/2204/12/news099.html	facebook	2022-04-12 12:09:00
TECH	Techable（テッカブル）	スマホで瞬時に体温測定！？電池不要のポート差し込み型小型デバイス「TempBuddy」	https://techable.jp/archives/176870	kickstarter	2022-04-12 03:00:42
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	日立、Linuxで稼働する勘定系パッケージ「OpenStage」を発表、静岡銀行のシステムがベース | IT Leaders	https://it.impress.co.jp/articles/-/22997	itleaders	2022-04-12 12:26:00
AWS	AWS Japan Blog	ドキュメントの要約を Hugging Face on Amazon SageMaker で民主化する	https://aws.amazon.com/jp/blogs/news/democratize-documentation-summarization-with-hugging-face-on-amazon-sagemaker/	記事の見出しの作成からプッシュ通知用の短文要約の作成まで、自動化された文書要約ソリューションは、コンテンツプロバイダーが消費者とより効果的にエンゲージメントを築くのに役立ちます。	2022-04-12 03:30:49
golang	Goタグが付けられた新着投稿 - Qiita	Go言語 チャネル	https://qiita.com/GL-Kageyama/items/ede938064f57a3c9ac6a	ncprimeroutinetargetlinei	2022-04-12 12:01:22
技術ブログ	Developers.IO	ESP32をAWSに接続してみた(4) Lambdaでデータ変換	https://dev.classmethod.jp/articles/connect-esp32-to-iot-core-4-lambda/	kinesisdatafirehose	2022-04-12 03:47:39
海外TECH	DEV Community	Things to become a better developer	https://dev.to/anamdiazs/things-to-become-a-better-developer-37bo	Things to become a better developerHave you ever thought what exactly is the formula to become a better developer The thing is that there is no formula book or even a methodology Everything is about building a mindset and identifying those things that you need to start doing in order to became a better developer Also keep in mind that everyone who works in the tech field is constantly learning because every single day things change I ll give you some advices that help me grow as a developer Improve your communication skillsFirst things first as software engineers we don t work alone most of the times there s a development team where everyone has their own tasks Having more confidence and start asking for help is one of the most important things to have a better communication with your team solve problems and find better solutions But everything is up to you the way you act and the words you use to express yourself can make the difference Practice algorithms and DSWe all got that class at college of learning algorithms and data structures but sometimes when we get more focused on a specific area meaning Web development Mobile development etc We forget about the basics starting with data structures such as stacks and queues would help us identify when and where to use it algorithms allow us to write an optimal solution based on time and space complexity Remember It s always a good idea keep practicing your programming logic Learn how to use your terminalAs a Frontend developer I used to think that I would never open a terminal I didn t even know that a shell and the terminal are actually different But I was totally wrong as developers we need to have as a minimum basic knowledge of terminal because sometimes there are no UI and we also need to install libraries or packages that are based on commands Rest and take care of yourself not everything it s about codingLast but not least there are many times that we forgot that we are humans and we started living in autopilot The importance of resting at weekends and enjoying the things you like to do is part of the process So this weekend why don t you start watching that tv show Go to your favorite cafeteria and spend your time with the people you love friends family boyfriend girlfriend	2022-04-12 03:29:20
海外TECH	DEV Community	React components composition: how to get it right	https://dev.to/adevnadia/react-components-composition-how-to-get-it-right-4mgn	React components composition how to get it rightOne of the most interesting and challenging things in React is not mastering some advanced techniques for state management or how to use Context properly More complicated to get right is how and when we should separate our code into independent components and how to compose them properly I often see developers falling into two traps either they are not extracting them soon enough and end up with huge components “monoliths that do way too many things at the same time and that are a nightmare to maintain Or especially after they have been burned a few times by the previous pattern they extract components way too early which results in a complicated combination of multiple abstractions over engineered code and again a nightmare to maintain What I want to do today is to offer a few techniques and rules that could help identify when and how to extract components on time and how not to fall into an over engineering trap But first let s refresh some basics what is composition and which compositions patterns are available to us React components composition patterns Simple componentsSimple components are a basic building block of React They can accept props have some state and can be quite complicated despite their name A Button component that accepts title and onClick properties and renders a button tag is a simple component const Button title onClick gt lt button onClick onClick gt title lt button gt Any component can render other components that s composition A Navigation component that renders that Button also a simple component that composes other components const Navigation gt return lt gt Rendering out Button component in Navigation component Composition lt Button title Create onClick onClickHandler gt some other navigation code lt gt With those components and their composition we can implement as complicated UI as we want Technically we don t even need any other patterns and techniques all of them are just nice to haves that just improve code reuse or solve only specific use cases Container componentsContainer components is a more advanced composition technique The only difference from simple components is that they among other props allow passing special prop children for which React has its own syntax If our Button from the previous example accepted not title but children it would be written like this the code is exactly the same just replace title with children const Button children onClick gt lt button onClick onClick gt children lt button gt Which is no different from title from Button perspective The difference is on the consumer side children syntax is special and looks like your normal HTML tags const Navigation gt return lt gt lt Button onClick onClickHandler gt Create lt Button gt some other navigation code lt gt Anything can go into children We can for example add an Icon component there in addition to text and then Navigation has a composition of Button and Icon components const Navigation gt return lt gt lt Button onClick onClickHandler gt lt Icon component is rendered inside button but button doesn t know gt lt Icon gt lt span gt Create lt span gt lt Button gt some other navigation code lt gt Navigation controls what goes into children from Button s perspective it just renders whatever the consumer wants We re going to look more into practical examples of this technique further in the article There are other composition patterns like higher order components passing components as props or context but those should be used only for very specific use cases Simple components and container components are the two major pillars of React development and it s better to perfect the use of those before trying to introduce more advanced techniques Now that you know them you re ready to implement as complicated UI as you can possibly need Okay I m joking I m not going to do a “how to draw an owl type of article here It s time for some rules and guidelines so that we can actually draw that owl build complicated React apps with ease When is it a good time to extract components The core React development and decomposition rules that I like to follow and the more I code the more strongly I feel about them are always start implementation from the topextract components only when there is an actual need for italways start from “simple components introduce other composition techniques only when there is an actual need for themAny attempt to think “in advance or start “bottom up“from small re usable components always ends up either in over complicated components API or in components that are missing half of the necessary functionality And the very first rule for when a component needs to be decomposed into smaller ones is when a component is too big A good size for a component for me is when it can fit on the screen of my laptop entirely If I need to scroll to read through the component s code it s a clear sign that it s too big Let s start coding now to see how can this looks in practice We are going to implement a typical Jira page from scratch today no less well sort of at least we re going to start This is a screen of an issue page from my personal project where I keep my favourite recipes found online In there we need to implement as you can see top bar with logo some menus “create button and a search barsidebar on the left with the project name collapsable “planning and “development sections with items inside also divided into groups with an unnamed section with menu items underneatha big “page content section where all the information about the current issue is shownSo let s start coding all of this in just one big component to start with It s probably going to look something like this export const JiraIssuePage gt return lt div className app gt lt div className top bar gt lt div className logo gt logo lt div gt lt ul className main menu gt lt li gt lt a href gt Your work lt a gt lt li gt lt li gt lt a href gt Projects lt a gt lt li gt lt li gt lt a href gt Filters lt a gt lt li gt lt li gt lt a href gt Dashboards lt a gt lt li gt lt li gt lt a href gt People lt a gt lt li gt lt li gt lt a href gt Apps lt a gt lt li gt lt ul gt lt button className create button gt Create lt button gt more top bar items here like search bar and profile menu lt div gt lt div className main content gt lt div className sidebar gt lt div className sidebar header gt ELS project lt div gt lt div className sidebar section gt lt div className sidebar section title gt Planning lt div gt lt button className board picker gt ELS board lt button gt lt ul className section menu gt lt li gt lt a href gt Roadmap lt a gt lt li gt lt li gt lt a href gt Backlog lt a gt lt li gt lt li gt lt a href gt Kanban board lt a gt lt li gt lt li gt lt a href gt Reports lt a gt lt li gt lt li gt lt a href gt Roadmap lt a gt lt li gt lt ul gt lt ul className section menu gt lt li gt lt a href gt Issues lt a gt lt li gt lt li gt lt a href gt Components lt a gt lt li gt lt ul gt lt div gt lt div className sidebar section gt sidebar development section lt div gt other sections lt div gt lt div className page content gt here there will be a lot of code for issue view lt div gt lt div gt lt div gt Now I haven t implemented even half of the necessary items there not to mention any logic and the component is already way too big to read through it in one glance See it in codesandbox That s good and expected So before going any further it s time split it into more manageable pieces The only thing that I need to do for it is just to create a few new components and copy paste code into them I don t have any use cases for any of the advanced techniques yet so everything is going to be a simple component I m going to create a Topbar component which will have everything topbar related Sidebar component for everything sidebar related as you can guess and Issue component for the main part that we re not going to touch today That way our main JiraIssuePage component is left with this code export const JiraIssuePage gt return lt div className app gt lt Topbar gt lt div className main content gt lt Sidebar gt lt div className page content gt lt Issue gt lt div gt lt div gt lt div gt Now let s take a look at the new Topbar component implementation export const Topbar gt return lt div className top bar gt lt div className logo gt logo lt div gt lt ul className main menu gt lt li gt lt a href gt Your work lt a gt lt li gt lt li gt lt a href gt Projects lt a gt lt li gt lt li gt lt a href gt Filters lt a gt lt li gt lt li gt lt a href gt Dashboards lt a gt lt li gt lt li gt lt a href gt People lt a gt lt li gt lt li gt lt a href gt Apps lt a gt lt li gt lt ul gt lt button className create button gt Create lt button gt more top bar items here like search bar and profile menu lt div gt If I implemented all the items there search bar all sub menus icons on the right this component also would ve been too big so it also needs to be split And this one is arguably a more interesting case than the previous one Because technically I can just extract MainMenu component from it to make it small enough export const Topbar gt return lt div className top bar gt lt div className logo gt logo lt div gt lt MainMenu gt lt button className create button gt Create lt button gt more top bar items here like search bar and profile menu lt div gt But extracting only MainMenu made the Topbar component slightly harder to read for me Before when I looked at the Topbar I could describe it as “a component that implements various things in the topbar and focus on the details only when I need to Now the description would be “a component that implements various things in the topbar AND composes some random MainMenu component The reading flow is ruined This leads me to my second rule of components decomposition when extracting smaller components don t stop halfway A component should be described either as a “component that implements various stuff or as a “component that composes various components together not both Therefore a much better implementatioin of the Topbar component would look like this export const Topbar gt return lt div className top bar gt lt Logo gt lt MainMenu gt lt Create gt more top bar components here like SearchBar and ProfileMenu lt div gt Much easier to read now And exactly the same story with the Sidebar component way too big if I d implemented all the items so need to split it export const Sidebar gt return lt div className sidebar gt lt Header gt lt PlanningSection gt lt DevelopmentSection gt other sidebar sections lt div gt See the full example in the codesandbox And then just repeat those steps every time a component becomes too big In theory we can implement this entire Jira page using nothing more than simple components When is it time to introduce Container Components Now the fun part let s take a look at when we should introduce some advanced techniques and why Starting with Container components First let s take a look at the design again More specifically at the Planning and Development sections in the sidebar menu Those not only share the same design for the title but also the same behaviour click on the title collapses the section and in “collapsed mode the mini arrow icon appears And we implemented it as two different components PlanningSection and DevelopmentSection I could of course just implement the “collapse logic in both of them it s just a matter of a simple state after all const PlanningSection gt const isCollapsed setIsCollapsed useState false return lt div className sidebar section gt lt div onClick gt setIsCollapsed isCollapsed className sidebar section title gt Planning lt div gt isCollapsed amp amp lt gt all the rest of the code lt gt lt div gt But it s quite a lot of repetition even between those two componentscontent of those sections is actually different for every project type or page type so even more repetition in the nearest futureIdeally I want to encapsulate the logic of collapsed expanded behavior and the design for the title while leaving different sections full control over the items that go inside This is a perfect use case for the Container components I can just extract everything from the code example above into a component and pass menu items as children We ll have a CollapsableSection component const CollapsableSection children title gt const isCollapsed setIsCollapsed useState false return lt div className sidebar section gt lt div className sidebar section title onClick gt setIsCollapsed isCollapsed gt title lt div gt isCollapsed amp amp lt gt children lt gt lt div gt and PlanningSection and DevelopmentSection and all other future sections will become just this const PlanningSection gt return lt CollapsableSection title Planning gt lt button className board picker gt ELS board lt button gt lt ul className section menu gt all the menu items here lt ul gt lt CollapsableSection gt A very similar story is going to be with our root JiraIssuePage component Right now it looks like this export const JiraIssuePage gt return lt div className app gt lt Topbar gt lt div className main content gt lt Sidebar gt lt div className page content gt lt Issue gt lt div gt lt div gt lt div gt But as soon as we start implementing other pages that are accessible from the sidebar we ll see that they all follow exactly the same pattern sidebar and topbar stay the same and only the “page content area changes Thanks to the decomposition work we did before we can just copy paste that layout on every single page it s not that much code after all But since all of them are exactly the same it would be good to just extract the code that implements all the common parts and leave only components that change to the specific pages Yet again a perfect case for the “container component const JiraPageLayout children gt return lt div className app gt lt Topbar gt lt div className main content gt lt Sidebar gt lt div className page content gt children lt div gt lt div gt lt div gt And our JiraIssuePage and future JiraProjectPage JiraComponentsPage etc all the future pages accessible from the sidebar becomes just this export const JiraIssuePage gt return lt JiraPageLayout gt lt Issue gt lt JiraPageLayout gt If I wanted to summarise the rule in just one sentence it could be this extract Container components when there is a need to share some visual or behavioural logic that wraps elements that still need to be under “consumer control Container components performance use caseAnother very important use case for Container components is improving the performance of components Technically performance is off topic a bit for the conversation about composition but it would be a crime not to mention it here In actual Jira the Sidebar component is draggable you can resize it by dragging it left and right by its edge How would we implement something like this Probably we d introduce a Handle component some state for the width of the sidebar and then listen to the “mousemove event A rudimentary implementation would look something like this export const Sidebar gt const width setWidth useState const startMoving setStartMoving useState false const ref useRef lt HTMLDivElement gt null useEffect gt if ref current return const changeWidth e MouseEvent gt if startMoving return if ref current return const left ref current getBoundingClientRect left const wi e clientX left setWidth wi ref current addEventListener mousemove changeWidth return gt ref current removeEventListener mousemove changeWidth startMoving ref const onStartMoving gt setStartMoving true const onEndMoving gt setStartMoving false return lt div className sidebar ref ref onMouseLeave onEndMoving style width width px gt lt Handle onMouseDown onStartMoving onMouseUp onEndMoving gt the rest of the code lt div gt There is however a problem here every time we move the mouse we trigger a state update which in turn will trigger re rendering of the entire Sidebar component While on our rudimentary sidebar it s not noticeable it could make the “dragging of it visibly laggy when the component becomes more complicated Container components are a perfect solution for it all we need is to extract all the heavy state operations in a Container component and pass everything else through children const DraggableSidebar children children ReactNode gt all the state management code as before return lt div className sidebar ref ref onMouseLeave onEndMoving style width width px gt lt Handle onMouseDown onStartMoving onMouseUp onEndMoving gt lt children will not be affected by this component s re renders gt children lt div gt And our Sidebar component will turn into this export const Sidebar gt return lt DraggableSidebar gt lt Header gt lt PlanningSection gt lt DevelopmentSection gt other Sections lt DraggableSidebar gt That way DraggableSidebar component will still re render on every state change but it will be super cheap since it s just one div And everything that is coming in children will not be affected by this component s state updates See all the examples of container components in this codesandbox And to compare the bad re renders use case see this codesandbox Pay attention to the console output while dragging the sidebar in those examples PlanningSection component logs constantly in the “bad implementation and only once in the “good one And if you want to know more about various patterns and how they influence react performance you might find those articles interesting How to write performant React code rules patterns do s and don ts Why custom react hooks could destroy your app performance How to write performant React apps with Context Does this state belong to this component Another thing other than size that can signal that a component should be extracted is state management Or to be precise state management that is irrelevant to the component s functionality Let me show you what I mean One of the items in the sidebar in real Jira is “Add shortcut item which opens a modal dialog when you click on it How would you implement it in our app The modal dialog itself is obviously going to be its own component but where you d introduce the state that opens it Something like this const SomeSection gt const showAddShortcuts setShowAddShortcuts useState false return lt div className sidebar section gt lt ul className section menu gt lt li gt lt span onClick gt setShowAddShortcuts true gt Add shortcuts lt span gt lt li gt lt ul gt showAddShortcuts amp amp lt ModalDialog onClose gt setShowAddShortcuts false gt lt div gt You can see something like this everywhere and there is nothing criminal in this implementation But if I was implementing it and if I wanted to make this component perfect from the composition perspective I would extract this state and components related to it outside And the reason is simple this state has nothing to do with the SomeSection component This state controls a modal dialog that appears when you click on shortcuts item This makes the reading of this component slightly harder for me I see a component that is “section and next line some random state that has nothing to do with “section So instead of the implementation above I would extract the item and the state that actually belongs to this item into its own component const AddShortcutItem gt const showAddShortcuts setShowAddShortcuts useState false return lt gt lt span onClick gt setShowAddShortcuts true gt Add shortcuts lt span gt showAddShortcuts amp amp lt ModalDialog onClose gt setShowAddShortcuts false gt lt gt And the section component becomes much simpler as a bonus const OtherSection gt return lt div className sidebar section gt lt ul className section menu gt lt li gt lt AddShortcutItem gt lt li gt lt ul gt lt div gt See it in the codesandbox By the same logic in the Topbar component I would move the future state that controls menus to a SomeDropdownMenu component all search related state to Search component and everything related to opening “create issue dialog to the CreateIssue component What makes a good component One last thing before closing for today In the summary I want to write “the secret of writing scalable apps in React is to extract good components at the right time We covered the “right time already but what exactly is a “good component After everything that we covered about composition by now I think I m ready to write a definition and a few rules here A “good component is a component that I can easily read and understand what it does from the first glance A “good component should have a good self describing name Sidebar for a component that renders sidebar is a good name CreateIssue for a component that handles issue creation is a good name SidebarController for a component that renders sidebar items specific for “Issues page is not a good name the name indicates that the component is of some generic purpose not specific to a particular page A “good component doesn t do things that are irrelevant to its declared purpose Topbar component that only renders items in the top bar and controls only topbar behaviour is a good component Sidebar component that controls the state of various modal dialogs is not the best component Closing bullet pointsNow I can write it The secret of writing scalable apps in React is to extract good components at the right time nothing more What makes a good component size that allows reading it without scrollingname that indicates what it doesno irrelevant state managementeasy to read implementationWhen is it time to split a component into smaller ones when a component is too bigwhen a component performs heavy state management operations that might affect performancewhen a component manages an irrelevant stateWhat are the general components composition rules always start implementation from the very topextract components only when you have an actual usecase for it not in advancealways start with the Simple components introduce advanced techniques only when they are actually needed not in advanceThat is all for today hope you enjoyed the reading and found it useful See ya next time Originally published at The website has more articles like this Subscribe to the newsletter connect on LinkedIn or follow on Twitter to get notified as soon as the next article comes out	2022-04-12 03:26:36
海外TECH	DEV Community	Vue2 vs Vue3	https://dev.to/krowemoh/vue2-vs-vue3-32g2	Vue vs VueFor a simple table of k items with search sorting and filtering vue was significantly more responsive during the filtering step Typing in the textbox was smooth whereas in vue it was quite janky Very unexpected I ll need to dig deeper at some point The code was almost identical as I compared the two in the same project Even the page render was faster with vue which was also surprising I think it might have to do with the way that every array object now needs to get proxied It could be vue is more powerful but at a cost though I imagine it will go down over time It s also likely that I m simply doing something wrong For now vue works so I ll continue using that	2022-04-12 03:10:12
海外TECH	DEV Community	I want to integrate twitter api	https://dev.to/trektohimalaya/i-want-to-integrate-twitter-api-a86	I want to integrate twitter apiWe are trying to integrate twitter api for our page Annapurna base camp trekking we could not able to integrate this apican you look at our page and give feedback what might be the exact solution for it	2022-04-12 03:06:58
ニュース	@日本経済新聞 電子版	16歳女子高生社長、規格外果物で大福や飲料　ロス削減 https://t.co/S6HotZUCb2	https://twitter.com/nikkei/statuses/1513719614496141312	女子高生	2022-04-12 03:24:14
ニュース	@日本経済新聞 電子版	鉄道駅で国内初となるバナメイエビの養殖実験。JR東日本水戸支社などが常磐線浪江駅で始めました。3000尾を育て、地元の飲食店や首都圏の駅ナカ店などへ夏ごろの出荷を見込みます。 https://t.co/HL2r90511S	https://twitter.com/nikkei/statuses/1513717497933012993		2022-04-12 03:15:49
ニュース	@日本経済新聞 電子版	日経平均続落、午前終値365円安の2万6455円 https://t.co/O4fVcrIet7	https://twitter.com/nikkei/statuses/1513714353237037059	日経平均	2022-04-12 03:03:19
海外ニュース	Japan Times latest articles	Honda to spend ¥8 trillion on EV push	https://www.japantimes.co.jp/news/2022/04/12/business/corporate-business/honda-ev/	electric	2022-04-12 12:05:29
ニュース	BBC News - Home	Tropical Storm Megi: 25 killed in Philippines tropical storm	https://www.bbc.co.uk/news/world-asia-61076079?at_medium=RSS&at_campaign=KARANGA	philippines	2022-04-12 03:17:10
北海道	北海道新聞	新ひだか町長選　現職が届け出　無投票の公算	https://www.hokkaido-np.co.jp/article/668406/	任期満了	2022-04-12 12:19:07
北海道	北海道新聞	東証、午前終値は２万６４５５円　大幅続落、一時４００円超安	https://www.hokkaido-np.co.jp/article/668462/	大幅続落	2022-04-12 12:12:00
北海道	北海道新聞	＜宇野沢デジタル委員が読み解く＞札幌も平均以下　道内小中学生の「塾代」が少ないワケ	https://www.hokkaido-np.co.jp/article/668104/	小中学生	2022-04-12 12:12:03
北海道	北海道新聞	避難学生６４人が入学式出席　福岡・日本経済大で１年間生活	https://www.hokkaido-np.co.jp/article/668461/	日本経済	2022-04-12 12:01:00
北海道	北海道新聞	感染拡大の沖縄に政府連絡要員　１５日まで「機動的な対応」	https://www.hokkaido-np.co.jp/article/668460/	官房長官	2022-04-12 12:01:00
IT	週刊アスキー	新たに2人のプレイアブルキャラクターを追加！2D対戦格闘ゲーム『MELTY BLOOD: TL』で追加DLC第2弾を4月14日に無料配信	https://weekly.ascii.jp/elem/000/004/088/4088977/	新たに人のプレイアブルキャラクターを追加D対戦格闘ゲーム『MELTYBLOODTL』で追加DLC第弾を月日に無料配信年月日、ProjectLUMINAノーツアニプレックスラセングルは、D対戦格闘ゲーム『MELTYBLOODTYPELUMINA』の追加ダウンロードコンテンツ第弾を月日に無料で配信すると発表。	2022-04-12 12:45:00
IT	週刊アスキー	レノボやデルなど、スマートトラッカー「Tile」搭載製品がぞくぞく発売	https://weekly.ascii.jp/elem/000/004/089/4089002/	製品	2022-04-12 12:30:00
IT	週刊アスキー	萌える戦国ゲーム「戦乱プリンセス」、6.5周年御礼キャンペーンを開催！ 復刻将姫が登場する11連ガチャも毎日無料！	https://weekly.ascii.jp/elem/000/004/088/4088950/	exnoa	2022-04-12 12:10:00