投稿時間:2023-01-04 20:29:01 RSSフィード2023-01-04 20:00 分まとめ(34件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
TECH	Techable（テッカブル）	デスクワークの腰痛を予防。高さ調節できるPCテーブル「Ergon-Apex」販売開始	https://techable.jp/archives/187974	ergonapex	2023-01-04 10:05:27
TECH	Techable（テッカブル）	町工場の部品見積もりをDX、東大発ベンチャー匠技研工業	https://techable.jp/archives/188415	leadx	2023-01-04 10:00:12
python	Pythonタグが付けられた新着投稿 - Qiita	Pythonでjson.dumpsのsepatatorsオプションを使ってファイルサイズを軽量化する	https://qiita.com/nasuvitz/items/0dc594d92ffb68d3fb90	jsondumps	2023-01-04 19:30:34
Docker	dockerタグが付けられた新着投稿 - Qiita	【連載】Dockerコンテナ内からリモートサーバーにrsyncでデプロイ【その１：sshコマンドでリモートサーバーにログイン】	https://qiita.com/yoshiki_13/items/fab62235fc18e101572a	docker	2023-01-04 19:39:03
技術ブログ	Developers.IO	AWS Amazon Transcribe คืออะไร? การแนะนำฟังก์ชันล่าสุดของ AWS ในปี 2023	https://dev.classmethod.jp/articles/what-is-amazon-transcribe-2023-th/	AWS Amazon Transcribe คืออะไร การแนะนำฟังก์ชันล่าสุดของAWS ในปีเริ่มต้นสวัสดีครับLIGHT จากบริษัทClassmethod Thailand ครับครั้งนี้อยากจะมาแนะนำให้ทุกคนได้รู้จักกับอีกหน	2023-01-04 10:32:47
海外TECH	DEV Community	So, why Server Components?	https://dev.to/jankoritak/so-why-server-components-2nk3	So why Server Components Let s talk components but on the server But why would you want something like that Are good old client components not good enough Of course they are Client components are a perfect match for rich interactive UIs that implement immediate feedback loops However as it usually goes each concept implies a certain set of advantages as well as a certain set of limitations Till late the only option to render a component was doing it client side in the browser Let s discuss some of the major disadvantages of this approach and explore how the concept of React Server Components helps us push the entire ecosystem forwards by addressing these limitations PrerequisityAs most of the images in this article are created as black content on white background please switch from dark mode to white mode in order to be able to read the images properly Thanks Client Components limitations Long TTI Time to Interactive Let s recap how client side rendering with the help of SSR works The client requests a page from the server The server builds the JS bundle and hopefully also some basic HTML to give the user a fast static response The server returns the JS assets to the client The client renders the HTML The client loads parses and executes the JS The client hydrates the JS into HTML to achieve the desired interactive page The red horizontal line in the image indicates where TTI would sit The heavier the JS bundle the longer loading parsing executing and hydrating the JS take Dependencies bloat the JS bundleThe logic is somewhat linear The heavier the bundle the longer will it take to transfer it over the network barrier to the browser and the longer will it take to render it However an example speakrs a thousand words so let s bring in some code I borrowed this piece of code from the React Server Components demo Notes application import format isToday from date fns import excerpts from excerpts import marked from marked import ClientSidebarNote from SidebarNote client export default function SidebarNote note const updatedAt new Date note updated at const lastUpdatedAt isToday updatedAt format updatedAt h mm bb format updatedAt M d yy const summary excerpts marked note body words return lt ClientSidebarNote id note id title note title expandedChildren lt p className sidebar note excerpt gt summary lt i gt No content lt i gt lt p gt gt lt header className sidebar note header gt lt strong gt note title lt strong gt lt small gt lastUpdatedAt lt small gt lt header gt lt ClientSidebarNote gt The code above describes quite a straightforward component Most notably the component formats and renders a date time value and formats and renders a piece of markdown that is a summary of a note To achieve this the component uses dependencies date fns excerpts and marked When we examine the dependencies closer we can immediately see they sum to KB gZipped Keep in mind this is only one client component and consider yourself how large can the entire application get Susceptible to request waterfallsLet s start with a quote Rendered JS does not guarantee an useful UI If we do all the work we discussed in Long time to interactive to only present the user with something like this We probably can agree we didn t do the best job in the initial user experience Now imagine the spinner is rendered by a component tree similar to this import React from react import Spinner from components Spinner import Something from components Something const ChildComponentA gt lt Something gt const ChildComponentB gt const dataC useDataC return dataC lt Something gt lt Spinner gt const Root gt const dataA useDataA const dataB useDataB skip dataA if dataA dataB return lt Spinner gt return lt gt lt ChildComponentA data dataB gt lt Something gt lt ChildComponentB data dataB gt lt gt From the code above we can derive the fact that to present the user with a full user experience we ll need to fire and wait for three sequential queries All this in sequence after we fetched the JS bundle from the server and rendered the initial UI on the client It should be pretty obvious that the diagram is far from optimal With the current set up we re firing three requests to the same server for each request have to wait for the server to resolve the request by e g talking to DB a close micro service or maybe an FS and then returning the result Three requests equal three round trips from client to server and back The browser has only one threadThe browser still has only one thread reserved for JS runtime This means all the operations we ve mentioned so far have to run with a single call stack The browser can t access server APIsQuite obviously the browser can access browser APIs like DOM manipulation APIs fetch API or Canvas WebGL while the server can work with e g environment variables access local file system and can directly reach out to databases or services which the client can only reach out via a controlled proxy This is all for the better as it allows us to securely work only with exposed REST GraphQL API to talk to the BE resources However there are use cases where a little more control would result in a more comfortable development experience For E g developers tend to struggle to realize they only can access environment variables in Next js in server side code as process env differs on the client You can definitely work around this by making the variable of the choice public by prepending its name with the PUBLIC prefix but you always need to pay attention not to leak a private variable this way It would be great if we could access process env directly in a component without limitations though right Server components to the rescueWe managed to explore the intrinsic limitations of React s client components These limitations are implied by the concept of rendering the component in the browser environment or on the client if you will Let s now turn the list around and look into each of the limitations one by one again and discuss how Server Component help us counter the limitations by unlocking a completely new set of possibilities by rendering them in the server environment Long Shorter TTI Time to Interactive One of the amazing benefits of rendering components on the server is that we don t have to transfer as large JS bundles to the client anymore If our application tree consists of components and we manage to pre render of them server side we can be certain that the JS bundle will be dramatically thinner The less JS we need to transfer and then load parse and execute on the client the quicker will the initial experience be The rendered Server Components are not included in the JS bundle they are rendered on the server and serialized into a special notation designed by the React js team This notation not only helps React Next js transfer the code over the network barrier but also helps client side React reconcile the component tree update without losing the application state To expand the context let s pull up an example of a batch component update coming from the server to update the UI The data are again taken from the React Server Components demo Notes application M id src SearchField client js chunks client name M id src EditButton client js chunks client name S react suspense J div null className main children section null className col sidebar children section null className sidebar header children img null className logo src logo svg width px height px alt role presentation strong null children React Notes section null className sidebar menu role menubar children null null noteId null children New nav null children null fallback div null children ul null className notes list skeleton container children li null className v stack children div null className sidebar note list item skeleton style height em li null className v stack children div null className sidebar note list item skeleton style height em li null className v stack children div null className sidebar note list item skeleton style height em children section null className col note viewer children null fallback div null className note skeleton container role progressbar aria busy true children div null className note header children div null className note title skeleton style height rem width marginInline px em div null className skeleton skeleton button style width em height em div null className note preview children div null className skeleton v stack style height em div null className skeleton v stack style height em div null className skeleton v stack style height em div null className skeleton v stack style height em div null className skeleton v stack style height em children div null className note empty state children span null className note text empty state children Click a note on the left to view something M id src SidebarNote client js chunks client name J ul null className notes list children li children null id title Meeting Notes expandedChildren p null className sidebar note excerpt children This is an example note It contains Markdown children header null className sidebar note header children strong null children Meeting Notes small null children li children null id title A note with a very long title because sometimes you need more words expandedChildren p null className sidebar note excerpt children You can write all kinds of amazing notes in this app These note live on the server in the notes children header null className sidebar note header children strong null children A note with a very long title because sometimes you need more words small null children li children null id title I wrote this note today expandedChildren p null className sidebar note excerpt children It was an excellent note children header null className sidebar note header children strong null children I wrote this note today small null children li children null id title Make a thing expandedChildren p null className sidebar note excerpt children It s very easy to make some words bold and other words italic with Markdown You can even link to React s children header null className sidebar note header children strong null children Make a thing small null children li children null id title Test Noteeeeeeeasd expandedChildren p null className sidebar note excerpt children Test note s text children header null className sidebar note header children strong null children Test Noteeeeeeeasd small null children li children null id title asdasdasd expandedChildren p null className sidebar note excerpt children asdasdasd children header null className sidebar note header children strong null children asdasdasd small null children That s a JSON y looking mess At least it sure feels like that to the human eye After all it s a set of instructions for React runtime on how to update the application as a result of e g a user s action These instructions are likely therefore not designed with human readability in mind However it s still pretty close to a JSON so on a second glance we can see some patterns there right We can identify a bunch of shorter lines e g M id src SearchField client js chunks client name M id src EditButton client js chunks client name M id src SidebarNote client js chunks client name The first line is actually instructing React runtime to render a SearchField component that is located in a file called client In other words it s a pointer to the Client Component which is located in a JS bundle chunk called client Since it s a Client Component it s yet to be rendered We can also clearly identify a line marking a suspense boundary which is not that interesting S react suspense But there are also two more lines starting with J and J that look pretty expressive J div null className main children section null className col sidebar children section null className sidebar header children img null className logo src logo svg width px height px alt role presentation strong null children React Notes section null className sidebar menu role menubar children null null noteId null children New nav null children null fallback div null children ul null className notes list skeleton container children li null className v stack children div null className sidebar note list item skeleton style height em li null className v stack children div null className sidebar note list item skeleton style height em li null className v stack children div null className sidebar note list item skeleton style height em children section null className col note viewer children null fallback div null className note skeleton container role progressbar aria busy true children div null className note header children div null className note title skeleton style height rem width marginInline px em div null className skeleton skeleton button style width em height em div null className note preview children div null className skeleton v stack style height em div null className skeleton v stack style height em div null className skeleton v stack style height em div null className skeleton v stack style height em div null className skeleton v stack style height em children div null className note empty state children span null className note text empty state children Click a note on the left to view something J ul null className notes list children li children null id title Meeting Notes expandedChildren p null className sidebar note excerpt children This is an example note It contains Markdown children header null className sidebar note header children strong null children Meeting Notes small null children li children null id title A note with a very long title because sometimes you need more words expandedChildren p null className sidebar note excerpt children You can write all kinds of amazing notes in this app These note live on the server in the notes children header null className sidebar note header children strong null children A note with a very long title because sometimes you need more words small null children li children null id title I wrote this note today expandedChildren p null className sidebar note excerpt children It was an excellent note children header null className sidebar note header children strong null children I wrote this note today small null children li children null id title Make a thing expandedChildren p null className sidebar note excerpt children It s very easy to make some words bold and other words italic with Markdown You can even link to React s children header null className sidebar note header children strong null children Make a thing small null children li children null id title Test Noteeeeeeeasd expandedChildren p null className sidebar note excerpt children Test note s text children header null className sidebar note header children strong null children Test Noteeeeeeeasd small null children li children null id title asdasdasd expandedChildren p null className sidebar note excerpt children asdasdasd children header null className sidebar note header children strong null children asdasdasd small null children The lines J and J are in fact two atomic components div and unordered list that were rendered on the server and completely serialized to be dumped into the view on the client The browser does not have to perform any work to render these Of course apart from the reconciliation and the update itself Very cool right From the client server communication point of view the diagram would now look something like this The green rectangles mark differences from the pre React Next js we mentioned in Long TTI To sum it up notable facts are Server bundles only the Client Component to the JS bundleServer renders Server Component into instructions for React runtime not HTMLThe updates are streamed to the clientThe client can reconcile the changes while keeping the client s stateThe bottom line is less JS shorter TTI Dependencies no longer bloat the bundle bundle size components are another great argument for Server Components Since the components are compiled on the server There is no need for us to include the component dependencies inside of the JS bundle From the implementation point of view when server side React encounters a Server Component in the component tree it compiles the component into atoms For E g in case your component uses date fns format to format a date it ll happen on the server and the result of the operation will be transferred to the client without the dependency itself Say farewell to bundling heavy dependencies to execute on the client To update the image we used above we can just scratch the gZipped KBs and replace it with straight Request waterfalls with zero round tripsA Server Component is always closer to the hardware than a Client Component Every request that would go from client to server and back now lives fully on the server side To put this thought into a diagram let s update the request waterfall we discussed in to reflect that The clear difference to the Client Components architecture is that we only need to really do one round trip Notice the colorful arrows that denote the actual requests on the component level that stay server side If the waterfall exists it s way faster The server has more than one threadThis one is pretty obvious While browsers still reserve only one thread for JS runtime servers usually feature more than a single thread for Node js More bandwidth for Server Components The server obviously can access the server APIsWhen rendering components on the server we can directly access e g process env variables therefore we can seamlessly integrate corresponding logic directly into our components That s quite slick right Moreover we can directly access local databases file systems or micro services I m not implying accessing a DB directly from a component is the best idea but you get the point However there is a great use case for accessing an FS directly in the component e g when implementing a static blog by just mapping the fs into blog pages which would not be possible on the component level before React SummaryWe explored pre React pain points that Client Components do suffer from Server Components allow us to view components in a different light meaning environment which turns out to provide implicit solutions for all of the pain points we explored Hopefully the article gave you a better idea of why React pivoted towards Server Components why Next js treats a component as a server one by default unless told not to and overall how will the ecosystem look in the near future	2023-01-04 10:11:22
Apple	AppleInsider - Frontpage News	Nanoleaf rolls out new Matter home automation products at CES 2023	https://appleinsider.com/articles/23/01/04/nanoleaf-rolls-out-new-matter-home-automation-products-at-ces-2023?utm_medium=rss	Nanoleaf rolls out new Matter home automation products at CES During the Consumer Electronics Show Nanoleaf debuted several new Matter compatible products that includes a screen mirroring camera modular skylight fixture and more Nanoleaf TV syncingMatter is once more the central theme for smart home products here at CES All of Nanoleaf s new gear works with Matter as well as Apple Home Read more	2023-01-04 10:03:36
海外TECH	Engadget	Tesla's Model Y could fall foul of new EV tax credit eligibility rules	https://www.engadget.com/teslas-long-range-model-y-may-not-qualify-for-the-ev-tax-credit-101229812.html?src=rss	Tesla x s Model Y could fall foul of new EV tax credit eligibility rulesCertain variants of Tesla s Model Y may not qualify for the federal EV tax credit based on the IRS s latest guidelines a situation that Elon Musk has called quot messed up quot It looks as though the five seat Long Range version of the hatchback is too expensive as a car and not considered an SUV so it falls outside the current guidelines That could change though as the rules won t be finalized until March The IRS has divided vehicles into two categories vans SUVs and pickup trucks under and other vehicles under For the first category the vehicle must have wheel drive or be rated at more than pounds of gross weight It also has to meet four of five other characteristics most notably front and rear axle clearances of centimeters or higher and a running clearance of at least centimeters no Model Y meets these specs Internal Revenue ServiceAccording to the IRS only the seat variants of the Model Y qualify as SUVs in the category up to while the seat vehicles Long Range AWD and Performance are in the section The seaters comfortably fall under the limit but all the seaters exceed the price so they don t qualify nbsp Tesla doesn t have a specific AWD variant of the Model Y in the US both the Long Range and Performance models are AWD so it s not clear which model the IRS is referring to The and seat versions cost the same starting at for the Long Range version before destination and order charges nbsp nbsp Critics are pointing out that far more polluting hybrid vehicles qualify for the tax credits including two Jeeps the Audi Q e Quattro BMW X xDrivee and Ford s Escape PHEV However if someone buys a Jeep Wrangler with MPGe MPG after the battery is depleted instead of a Tesla Model Y with MPGe then the government clearly isn t doing the most it can to reduce carbon emissions The IRS has invited consumers to comment on the matter and Musk encouraged people to do so in a tweet nbsp	2023-01-04 10:12:29
ラズパイ	Raspberry Pi	Building community with our global clubs partners	https://www.raspberrypi.org/blog/building-community-global-clubs-partners-code-club-coderdojo/	Building community with our global clubs partnersAs part of our mission to enable young people to realise their full potential through the power of computing and digital technologies we work in partnership with organisations around the globe to grow and sustain the Code Club and CoderDojo networks of coding clubs for young people These organisations are our global clubs partners and The post Building community with our global clubs partners appeared first on Raspberry Pi	2023-01-04 10:46:29
海外科学	NYT > Science	How Climate Change Is Shaping California’s Winter Storms	https://www.nytimes.com/2023/01/03/climate/california-flood-atmospheric-river.html	How Climate Change Is Shaping California s Winter StormsSo far the downpours are largely in line with past storms an official said But their quick pace is testing the limits of the state s infrastructure	2023-01-04 10:19:42
医療系	医療介護 CBnews	医療法人経営情報、23 年度中に閲覧400件-政府目標、政策決定に活用へ	https://www.cbnews.jp/news/entry/20230104184232	医療法人	2023-01-04 19:35:00
ニュース	BBC News - Home	Romeo and Juliet: Olivia Hussey and Leonard Whiting sue over 1968 film's 'sexual abuse'	https://www.bbc.co.uk/news/entertainment-arts-64160726?at_medium=RSS&at_campaign=KARANGA	oscar	2023-01-04 10:29:07
GCP	Google Cloud Platform Japan 公式ブログ	IT 業界の予測: マルチクラウドは 1 つの段階であって、最終ゴールではない	https://cloud.google.com/blog/ja/topics/hybrid-cloud/predicting-the-future-of-multicloud/	予測パブリッククラウドを使用している組織の半数以上が、マルチクラウド機能を利用できるようになった結果、プライマリクラウドプロバイダを自由に切り替えるようになる今後数年間で企業は、リスクを分散させる手段としてだけでなく、最初のクラウドから次のクラウドに切り替える方法としても、マルチクラウド戦略を利用するようになるでしょう。	2023-01-04 11:30:00
GCP	Google Cloud Platform Japan 公式ブログ	IT 業界の予測: 統合されたデータ パイプラインでリアルタイムの分析情報がより充実	https://cloud.google.com/blog/ja/products/data-analytics/the-future-of-unified-batch-and-real-time-pipelines/	IT業界の予測統合されたデータパイプラインでリアルタイムの分析情報がより充実※この投稿は米国時間年月日に、GoogleCloudblogに投稿されたものの抄訳です。	2023-01-04 11:00:00
北海道	北海道新聞	苫小牧市、パートナー制度始動　第１号カップルが笑顔で宣誓	https://www.hokkaido-np.co.jp/article/783520/	lgbtq	2023-01-04 19:38:00
北海道	北海道新聞	「子育てしやすい町に」　白老町長選に広地氏が出馬表明	https://www.hokkaido-np.co.jp/article/783519/	記者会見	2023-01-04 19:37:00
北海道	北海道新聞	日本のコロナ水際強化に中国反発　「科学的、適度に」	https://www.hokkaido-np.co.jp/article/783495/	中国外務省	2023-01-04 19:21:34
北海道	北海道新聞	ふるさと納税　根室市１７０億円　７年連続の最多更新	https://www.hokkaido-np.co.jp/article/783499/	連続	2023-01-04 19:08:02
北海道	北海道新聞	「受け子」容疑で２３歳男を再逮捕　旭川東署	https://www.hokkaido-np.co.jp/article/783474/	福島県白河市与惣小屋	2023-01-04 19:22:03
北海道	北海道新聞	きね下ろし「よいしょ」　室蘭で子ども餅つき盛況	https://www.hokkaido-np.co.jp/article/783515/	商業施設	2023-01-04 19:29:00
北海道	北海道新聞	「改善、提案する１年に」　西胆振　市役所や企業で仕事始め	https://www.hokkaido-np.co.jp/article/783514/	仕事始め	2023-01-04 19:28:00
北海道	北海道新聞	「女性管理職ゼロ」４３％　日商調査、中小企業２８８０社に	https://www.hokkaido-np.co.jp/article/783510/	中小企業	2023-01-04 19:21:00
北海道	北海道新聞	＜ともに生きる＞社会福祉法人あけぼの福祉会「ベーカリーサンライズ」＝岩内町　“深層水パン”人気ふわり	https://www.hokkaido-np.co.jp/article/783509/	社会福祉法人	2023-01-04 19:20:00
北海道	北海道新聞	蘭越の夜空に花火７００発　新春祝う	https://www.hokkaido-np.co.jp/article/783507/	地域住民	2023-01-04 19:18:00
北海道	北海道新聞	新年の活況祈念、札証で大発会　日本ハム上沢投手が鐘打ち	https://www.hokkaido-np.co.jp/article/783469/	北海道日本ハム	2023-01-04 19:13:34
北海道	北海道新聞	２０歳の節目、決意新たに　浜頓別で祝う会	https://www.hokkaido-np.co.jp/article/783498/	成人年齢	2023-01-04 19:07:00
北海道	北海道新聞	宗谷管内３人感染　留萌管内はゼロ　新型コロナ	https://www.hokkaido-np.co.jp/article/783497/	宗谷管内	2023-01-04 19:06:00
北海道	北海道新聞	関西互礼会、３年ぶり対面で開催　２年後の万博目標に飛躍へ	https://www.hokkaido-np.co.jp/article/783496/	経済団体	2023-01-04 19:04:00
北海道	北海道新聞	中国で米国製コロナ飲み薬が高騰　ファイザーのパキロビッド	https://www.hokkaido-np.co.jp/article/783494/	新型コロナウイルス	2023-01-04 19:03:00
ビジネス	東洋経済オンライン	米アボット､中国の粉ミルク事業から撤退の背景 一般用栄養食品､医療機器､医薬品などは継続 | 「財新」中国Biz＆Tech | 東洋経済オンライン	https://toyokeizai.net/articles/-/641990?utm_source=rss&utm_medium=http&utm_campaign=link_back	biztech	2023-01-04 20:00:00
IT	週刊アスキー	スクウェア・エニックスがニンテンドーeショップ／PS Storeで「新春到来セール」を実施	https://weekly.ascii.jp/elem/000/004/119/4119411/	playstationstore	2023-01-04 19:10:00
マーケティング	AdverTimes	カカクコム、人事部長ほか（23年1月1日付）	https://www.advertimes.com/20230104/article408273/	経営管理	2023-01-04 10:17:25
GCP	Cloud Blog JA	IT 業界の予測: マルチクラウドは 1 つの段階であって、最終ゴールではない	https://cloud.google.com/blog/ja/topics/hybrid-cloud/predicting-the-future-of-multicloud/	予測パブリッククラウドを使用している組織の半数以上が、マルチクラウド機能を利用できるようになった結果、プライマリクラウドプロバイダを自由に切り替えるようになる今後数年間で企業は、リスクを分散させる手段としてだけでなく、最初のクラウドから次のクラウドに切り替える方法としても、マルチクラウド戦略を利用するようになるでしょう。	2023-01-04 11:30:00
GCP	Cloud Blog JA	IT 業界の予測: 統合されたデータ パイプラインでリアルタイムの分析情報がより充実	https://cloud.google.com/blog/ja/products/data-analytics/the-future-of-unified-batch-and-real-time-pipelines/	IT業界の予測統合されたデータパイプラインでリアルタイムの分析情報がより充実※この投稿は米国時間年月日に、GoogleCloudblogに投稿されたものの抄訳です。	2023-01-04 11:00:00