投稿時間:2022-09-11 00:16:13 RSSフィード2022-09-11 00:00 分まとめ(19件)

カテゴリー等 サイト名等 記事タイトル・トレンドワード等 リンクURL 頻出ワード・要約等/検索ボリューム 登録日
AWS AWSタグが付けられた新着投稿 - Qiita AWSアカウント初期準備 https://qiita.com/wawon1111/items/0ba1eb451edc166ca6e4 無料 2022-09-10 23:43:24
技術ブログ Developers.IO Mac端末の入れ替え後にSlackアプリからのデスクトップ通知が来なくなったので対処した https://dev.classmethod.jp/articles/desktop-notifications-from-the-slack-app-stopped-coming-after-replacing-the-mac-device-so-i-dealt-with-it/ slack 2022-09-10 14:11:07
海外TECH MakeUseOf GNOME 43 Is Almost Here! Here's What You Can Expect https://www.makeuseof.com/gnome-43-new-features-to-expect/ linux 2022-09-10 14:45:13
海外TECH MakeUseOf How to Use TypeScript in React Applications https://www.makeuseof.com/typescript-react-applications/ react 2022-09-10 14:31:13
海外TECH MakeUseOf How to Disable Read or Write Access for Your Removable Storage Devices on Windows https://www.makeuseof.com/windows-disable-access-removable-devices/ windows 2022-09-10 14:16:13
海外TECH DEV Community Q&A: Who Is Responsible For Accessibility https://dev.to/yuridevat/qa-who-is-responsible-for-accessibility-3ep2 Q amp A Who Is Responsible For AccessibilityRecently in the position of a frontend developer I was invited to a Q amp A session by a UX design team of a large company in Vienna where the goal was to find out together where the responsibility for accessibility in the web development process lies I will share the questions I was asked during the session by the UX team and my answers transcribed I hope to give you a sense of how to implement accessibility into the web development process from a frontend developer s perspective Table of contentsAt what stage should we share the ay guidelines requirements What can you do as a designer to make sure the developers know how to build it What do the developers need in the briefing regarding accessibilityMake functionality available from a keyboard Where does the reading flow begin Show where your focus is How to display hover state on keyboard How to communicate with developers Ay for frontend developersConclusionThe session started with an introduction about what accessibility is and how it is implied in UX design by the UX team of the company to give the developers of the project an insight about the topic At what stage should we share the ay guidelines requirements It is very good practice to have accessibility guidelines not only for a specific project but generally within the company itself These should be shared with all employees already when they are hired so that everyone is aware of these guidelines What can you do as a designer to make sure the developers know how to build it Set constraints in Figma Will be answered together with question What do the developers need in the briefing regarding accessibility Should this be in the Figma file as a comment or a post it I would like to answer these questions together There is a difference depending on the size of the company If there is no dedicated UX Designer there the frontend developer often does the UI design and development ergo they are also responsible for ay In case of a team where there are both UX designer and frontend Developer I see the split as follows If I as a dev get a design that I now have to convert into code I don t want shouldn t have to worry about whether the color contrast is high enough about the font size and family and the button are big enough or whether the position of the popup makes sense Text should be left or right aligned no longer than characters font ch letter spacing and l ine height These are things that should be decided at the design stage with ay in mind so the UX team should take this into account that everything meets the ay criteria The implementation of the design to make the code fully ay now is up to the dev There is no reason when it comes to code that a UX designer would still have to get involved here in a big way Anyone who deals with frontend and cares about staying update should have some basic understanding of accessibility anyway e g semantic HTML etc After all this is my job as frontend developer It starts simple Semantic HTML is just the minimum that every dev has to know and understand anyway that s why they are frontend devs There are more than HTML tags and most of them already make a component accessible So when I get a design I know what the header is the main content the footer the navigation Accordingly I write these components using the intended semantic HTML tags Common bad practices or incorrect use of tags in relation to ay can often be found in e g button and links There are differences between button and a tags Do not nest interactive elements If you need a link that looks like a button design the link accordingly A click event on a graphic fires only when clicked A click event on a button fires when it is clicked and when the user presses the Enter or Space key cursor pointer automatic on link JavaScript void on a tag means that it is not a link Every img tag needs beside height and width also an alt attribute even if it is empty in case of a decoration image Best would be to insert these sort of images with CSS as background When there is no text alternative for the image screen readers may will announce the file name or the image URL When writing letters in uppercase screen reader may read each letter out loud like USA so write the word in lowercase and style it uppercase with CSS Do not set the user scalability to no People with limited vision need to zoom them If the design doesn t work the problem is in the design itself Make functionality available from a keyboard Where does the reading flow begin Does it go from H to h or top to bottom or component Everything is basically correct here The reading flow starts as the DOM order is written so it is important to use semantic HTML and not interrupt this flow e g by tabindex or other CSS attributes A page should best be divided into landmarks that can be easily displayed with semantic HTML header navigation bar main content side content sections in the main content footer The user can then navigate between these landmarks with the help of a screen reader The next selection is the headings which must appear in the correct order There can only ever be one h per page as this is effectively the title of the page and there is only ever one title An h can never be followed by an h This is also purely HTML and not styling It is perfectly okay that e g on your page here the title looks exactly like the first h heading if it is your branding as long as it is marked in the DOM as different headings This is important for people with visual impairment who use a screen reader they want to know what page it is h and then what the first section contains h They don t care about the styling Show where your focus is How to display hover state on keyboard Can keyboard only users hover There are always problems with the hover effect and it should therefore be used with caution and certainly not to display important content An equivalent to hover for keyboard users would be focus How to communicate with developers It happened to me only once that I had questions about the design and that was in relation to stages of responsiveness of the design from desktop to tablet But I didn t get a useful answer from the UX designer who was still a junior themselves so I decided on my own how to do it No one complained so it will have been fine From the current perspective now that a few months have passed since the QA my answer would be that communication is dependent on the design system If the system is prepared to provide explanations for each component the system should speak for itself In case of questions from the developers there should always be a contact person in the UX team who can give information about ideas of the functionality of the project Design tools such as Figma are so mature that you can recreate almost any interaction and send it to the developers Good and respectful communication is always key in a team Ay for frontend developersAt the end of the QA session I shared what I thought were the most important points for the frontend development team to focus on and shared useful links and tools for them to work with to get used to accessibility in the process Get an understanding ofsemantic HTMLfocus focus within focus visibleinteractive elements like buttons links and formsreading order DOM orderImportant links and toolsWC ARIA Authoring Practices GuideWAI Tutorial TutorialsMarkup Validation The WC Markup Validation ServiceAxe DevToolsWaveTabayNVDA Jaws Voice Over ConclusionI enjoyed the QA session very much It was exciting to talk with a team full of UX designers about accessibility in the web development process share views and took a lot also new from the conversation Thanks for your reading and time I really appreciate it 2022-09-10 14:09:18
海外TECH DEV Community How is serverless computing going to change the cloud landscape? https://dev.to/aviyel/how-is-serverless-computing-going-to-change-the-cloud-landscape-5ff5 How is serverless computing going to change the cloud landscape IntroductionServerless computing is a relatively new concept in cloud computing It s been around for less than a decade but it s already making waves in the world of Information Technology And it doesn t look like things are going to settle down anytime soon Serverless computing means that developers can create applications without having to worry about managing infrastructure which makes it perfect for projects that require more flexibility than traditional cloud options provide What is serverless computing Serverless computing is a cloud computing model that enables developers to build and run applications and services without having to worry about the underlying infrastructure Unlike traditional virtual machines serverless computing allows the developer to simply focus on their code and not have to worry about provisioning servers or maintaining them once they are in production In this context serverless refers to the fact that when you deploy your application it still gets loaded onto a computer somewhere but you do not need to think about how it will be runningーyou just write your code The infrastructure is managed at least partially by an external service provider which means that they take care of scaling up or down based on the demand Definition Serverless architecture and serverless computing explainedIf you are building a service or website which requires a backend as in not a static site there are only two choices you can choose from You can either build your own server and operate it yourself or use someone else s servers and go through an API to communicate with it Serverless architecture is an emerging technology in web services While it existed prior to Amazon popularized the term serverless computing with AWS Lambda their implementation of functions as a service FaaS Serverless architecture is an application type where software and its associated infrastructure are provided as a fully managed service meaning that others provision and scale the “servers used in running such applications Serverless computing is a cloud computing paradigm in which the cloud provider fully manages the operating system storage and network infrastructure that runs the application It differs from other forms of cloud computing in that it does not use virtual machines VM but instead uses containers or functions Serverless computing is not a new concept it s been around since before AWS Lambda was released However recently this technology has seen an increase in interest according to Stack Overflow surveys serverless technologies have risen to become one of their most popular developer tools today Serverless architecture computing allows you to build and run applications without having to worry about servers or infrastructure management by using pre built services called functions You can think of these functions as small units within your app that perform certain tasks when triggered by events like user actions or requests from apps The future of serverless computingHow will serverless computing evolve in the future It s hard to predict it but here are a couple of things we do know First it ll only add more complexity to cloud infrastructure and give developers even more options for building applications Secondlyーand perhaps more significantlyーthe new standard will likely cause developers to change the way they interact with their backend services as well as provide them with new ways of accessing data that is stored in the cloud Third this change will take time to implementーthere are still many challenges that need to be addressed before consumers and businesses adopt serverless computing However with all of these possibilities ahead of usーand considering how fast technology has been evolving latelyーit s impossible not to think about what could happen next Serverless computing is growing fast Serverless computingーwhich is also known as fixed resource allocation computingーis a relatively new technology that has been gaining ground in recent years As previously stated serverless computing is a critical component of next generation cloud infrastructure The ability to run applications without having to worry about the underlying hardware or software may have driven this adoption and is likely here stay for a while Although many people still associate serverless computing with AWS Lambda there are other services that also allow you to build applications without thinking about servers Google Cloud Functions and Azure Functions both offer similar functionality There are even companies like Metacallーwhich is fully open source and make it easy for developers to add serverless capabilities on top of existing application architectures e g Node js Python Ruby C and more Why do we need it AdvantagesServerless computing is a cloud based architecture that allows developers to build and run applications without worrying about the underlying infrastructure Serverless offers several benefits including Cost savings Serverless architectures provide significant cost savings especially for small and medium businesses The cost for a serverless architecture is based on the consumption of resources and it s very easy to scale up or down your application as needed without any effort In fact you can even save money by using serverless architecture because it eliminates the need for infrastructure management Better performance Serverless architectures are highly scalable and they provide better performance since they re optimized for speed not efficiency This means that your application will respond much faster than if you were using traditional managed hosting solutions such as virtual machines or containers Flexibility Serverless architectures are highly flexible because you can choose exactly when and how much computing power your application needs at any given time You can also change how much computing power is required without affecting other parts of your application or its users because each function runs in isolation from all others Reliable Serverless architectures are built on top of services from third party vendors that take care of availability and reliability for you Lightweight Serverless architecture is lightweight because you only pay for the resources that you use It also means that you don t have to maintain servers or scale them when the load increases Bare metal vs Virtualization vs Containerization vs Serverless ComputingIn this section we ll take a look at each of these options and compare their pros and cons Bare metal This is the most bare bones of all the options It doesn t require any virtualization layer which means there is no overhead from multiple layers or operating systems between your software and the hardware itself You also don t need to worry about performing upgrades on your servers or ensuring that they are properly patched with security updatesーeverything runs directly on top of physical hardware Virtualization Virtualization puts another layer between your application code and its underlying operating system but it still requires some kind of server or computer to run software on whether that s a dedicated machine in a cloud data center or an individual computer on someone s desk at home or both Containers In contrast with virtual machines VMs containers isolate processes within their own operating system so they cannot access other parts of the system outside their container ーeven though they might be running within the same physical machine as other containers This makes them easier than VMs since there s less overhead involved when creating new containers vs starting up new VMs Serverless Computing Serverless computing is a new category of cloud computing that allows developers to build and run applications and services without thinking about servers It s the natural evolution of Infrastructure as a Service IaaS which abstracted physical machines from application developers With serverless the resources are virtualized by the provider and managed in an automated way The idea behind serverless computing is that you write your code in any language or framework and run it on a platform that handles scaling availability and other challenges associated with running production workloads You pay only for the resources consumed during execution rather than having to pay for idle time or unused capacity Serverless computing is going to be very cheap Unlike traditional cloud computing serverless applications don t require you to buy or manage servers manually The application vendor provides the necessary resources and scales the application automatically as needed You don t have to worry about provisioning or managing capacityーit s all handled by the vendor Serverless computing can be used for any number of applications including APIs and web services that need to respond to requests quickly But it isn t just for developers anymoreーbusinesses are starting to realize its benefits as well The biggest benefit of serverless computing is that it drastically reduces your operating costs by eliminating infrastructure management entirely It also makes it much easier to make changes in your application because you aren t dependent on configuration files and other tools that require manual updates when you want to make changes in your code base The development process will become snappier and more efficient The development process will become snappier and more efficient When you re not running your own servers you don t have to worry about scaling or managing them If a server has a problem and goes down it can be brought back up quickly without affecting other parts of the system The developer is freed from some of the technical overhead that comes with managing these machines by themselves Disadvantages of Serverless ComputingDisadvantages of using Serverless Computing Security risks One of the biggest risks with serverless computing is that it is relatively new and not mature This means that there are still some security concerns with serverless computing especially when it comes to authentication With traditional cloud computing you can use a variety of tools like Kerberos or OAuth to authenticate a user s identity and ensure they re who they say they are before giving access to sensitive data or resources In the case of serverless computing however authentication becomes much more challenging because there s no central identity provider that controls all login requests throughout the entire stack Hence there s a chance that your cloud provider could be hacked and their data might get stolen ーnot something you d have to worry about with your own hardware Response time Your serverless application will need to wait for each function call to finish before returning a response backーto the client The number of functions being used the number of users using the application and the number of data sources being accessed are all contributing factors to response time in a serverless architecture A lot of people think that as long as they use one function their response time will be fine But if you have functions each one needs its own machineーwhich means on average your machine count has gone up by times for every function added The same applies to the user base if you have users accessing your app in parallel instead of users accessing it sequentiallyーyou ve doubled your infrastructure costs and time again This can lead to poor user experiences if not handled correctly by developers and architects who understand how these services work under pressure from lots of users trying simultaneously to access their apps using different devices With these considerations in mind it s easy to see why some companies might consider adopting serverless architectures only when they re serving huge amounts of traffic or high volume through their APIs APIs New ways of writing code With serverless computing you don t have to write complex multi threaded code for all your tasks Instead you write simple functions that are triggered by events This means that you need to think about how your application will be broken down into smaller chunks of logic You also need to make sure that these chunks can be called independently from each other without interfering with each other s execution Additional Tooling Serverless computing is still relatively new and there aren t many tools available yet to help developers get started with it easily This means that in order to take advantage of serverless computing you first need to learn how to use new tools like AWS Lambda Azure Functions Google cloud functions or even Metacall and then start developing your application using these tools instead of traditional programming languages Moreover since these tools are still evolving at a fast pace there are bound to be many bugs and issues which will require constant monitoring and maintenance while developing an application using this technology stack Will serverless computing will become more common as cloud services increase Serverless computing will become more common as cloud services increase Cloud computing is being used by more people than ever before and it s only going to get more popular as time goes on Cloud computing makes sense in some cases but not all of them In order for cloud implementation to work well you need an understanding of the technology behind it so that you can make wise decisions about which workloads are best suited for it Just like how we use our developers skillsets selectively based on their expertise levels and areas of interest experience and depending on whether they re working with us or someone else so too should we treat this new technology as something that has its own pros and consーnot just because everyone else has adopted it doesn t mean there s no room for improvement While serverless computing is still in its early stages of adoption it s likely that this trend will pick up steam as cloud based services become increasingly popularーjust like how cell phones transformed from clunky devices into sleek gadgets capable of doing many things ConclusionServerless computing is going to change the cloud landscape in a number of ways It will make application deployment and management easier it will allow applications to scale more quickly and efficiently than before and it will enable developers to focus on what they do bestーbuilding great software The fact of the matter is that serverless computing has already taken hold even if its use is still limited at this time But once it becomes more widely adopted by companies seeking to migrate to the cloud there will be a large number of serverless services available for developers and business users to choose from The implications are dramatic and we are still watching them unfold But one takeaway from this is that the cloud universe is very different than the world we live in today and that it s going to keep changing in ways no one can predictーand yet there are things we can do now to prepare ourselves for future changes 2022-09-10 14:02:16
海外TECH DEV Community Temel Rancher kurulumu https://dev.to/aciklab/temel-rancher-kurulumu-9hb Temel Rancher kurulumuRancher hakkında temel ve sözel bir dokümanı Rancher a giriş olarak Medium üzerinde paylaşmıştım Şimdi ise hedefimiz elimizi biraz daha kullanıma alıştırmak olacak Öncelikle temel olarak sanal makine üzerinde Ubuntu sunucu sürümünükullandığımısöyleyebilirim Farklıdağıtımda farklıbağımlılıklar olabileceği için yeni başlıyor iseniz aynısürümden devam etmek daha doğru olacaktır Ön hazırlıklar ve Docker kurulumuSanal makineye kendi kullanıcınızla girişyaptıktan sonra yönetici hesabına geçerek aşağıdaki paketi yüklememiz gerekiyor sudo apt install docker ioBu adımdan sonra docker kurulmuşolacak fakat docker ın sudo olmayan kullanıcıile de çalıştırılmasına önem veriyorum bunun için kendi kullanıcınızıbelirterek aşağıdaki iki komutu da yönetici yetkisi ile uygulayalım sudo usermod aG docker KULLANICIADInewgrp dockerAçılışta docker ın açılmasıiçin ise aşağıdaki komutu uygulayabilirsiniz sudo systemctl enable dockerBu adımdan sonra sanal makine yeniden başlatılmalı Bu kısım özellikle yetkisiz kullanıcının docker ıkullanmaya yetkisini görebilmek için önemli Rancher kurulumuSistem yeniden başladıktan sonra artık yönetici yetkisini kullanmayacağız Normal kullanıcımızla girdikten sonra aşağıdaki komutu kullanarak rancher server ıkuruyoruz docker run d name rancher server restart unless stopped p p privileged rancher rancher stableDocker imajlarıindirilip ayağa kaldırılmaya başladığında yaklaşık dakika filan zaman alabilir ki bundan sonra ve portlarından web arayüzünden girişyapılabilmesi sağlanacaktır Rancher web arayüzüne girişYazıyazıldığında son kararlısürüm v olarak gözükmekte olup web tarayıcınızdan sanal makinenin IP adresine girdiğinizde size parolanıza bakmanızısöyleyecektir Bunun için aşağıdaki komutu çalıştırmanız gerekmekte Eğer rancher sorunsuz ayağa kalktıysa bu da gözüküyor olmasılazım docker logs rancher server gt amp grep Bootstrap Password Parolayıgirip yeni ve zor parola ile değişimi yaptıktan sonra aşağıdaki gibi bir ekranla karşılaşacaksınız Tabi ki bende koyu modu seçili olduğu için farklılık gösterecektir Ve tabi ki buradaki kalabalıklarısağüst kısımlarında bulunan çarpılarla kapatıp asıl işi olan kümeleri listeleyecek hale getirebilirsiniz local kümeWeb arayüzüne girdiğinizde ilk olarak dikkat çekebilecek nokta ks Kubernetes provider ıile yerel bir küme oluşturulmuşolmasıolacaktır Bu şekilde kubernetes in nimetlerini kullanmaya başlayabiliyorsunuz Bu kümenin içerisinde aşağıdaki Kubernetes bileşenlerinin bulunduğunu söyleyebiliriz EtcdSchedulerController ManagerKüme içerisine girdikten sonra kaçpod kaççekirdek CPU ve kaçhafıza olduğuna dair temel bilgilere ulaşabileceksiniz Tabi ki daha sonra helm paket yöneticisi ile birlikte Prometheus ve Grafana ile de daha detaylıbilgileri alabileceğiniz bir yapıoluşturabilirsiniz Bu konularla ilgili birkaçyazıile de devam etmeyi düşünüyorum ama girişkonusunda bu adımların anlaşılmasıen önemli nokta olacaktır 2022-09-10 14:01:14
海外TECH Engadget CD Projekt Red releases an official modding tool for 'Cyberpunk 2077' https://www.engadget.com/cd-projekt-red-cyberpunk-2077-redmod-143304735.html?src=rss CD Projekt Red releases an official modding tool for x Cyberpunk x Cyberpunk now has an official modding tool CD Projekt RED has launched REDmod which provides players integrated support to easily install and load mods onto the PC version of the action RPG As the developer s official announcement notes it will also allow players to modify and personalize their game by using the custom sounds animations and scripts that come with the tool CD Projekt Red promises to update the tool alongside future patches to ensure that it remains compatible with the game It is a free DLC though and players don t have to install it at all if they don t want to Mod yourself up from the bottom to the very top REDmod is our new tool dedicated to all Cyberpunk and modding enthusiasts Learn more at and leave your own mark in the dark future world of Night City pic twitter com zyVoWKYjWkーCyberpunk CyberpunkGame September As popular mod website Nexus Mods clarifies while new mods are required to use a specific format to be compatible with REDmod old mods will continue to work just fine Older mods that aren t compatible with the tool simply won t show up in the new REDmod menu That s also were players can toggle mods that are compatible with the tool on or off nbsp The free DLC is now available for download from the official Cyberpunk website but players can get also get it from GOG Steam or Epic 2022-09-10 14:33:04
海外TECH CodeProject Latest Articles It is Better to Use devector Than std::deque https://www.codeproject.com/Articles/5339774/It-is-Better-to-Use-devector-Than-std-deque deque 2022-09-10 14:54:00
ニュース BBC News - Home Bank holiday approved for day of Queen's funeral https://www.bbc.co.uk/news/uk-62862225?at_medium=RSS&at_campaign=KARANGA funeral 2022-09-10 14:14:40
ニュース BBC News - Home Charles praises Queen's reign as he is formally confirmed as king https://www.bbc.co.uk/news/uk-62860893?at_medium=RSS&at_campaign=KARANGA selfless 2022-09-10 14:28:32
ニュース BBC News - Home Queen Elizabeth II: Royal Family meet well-wishers at Balmoral https://www.bbc.co.uk/news/uk-scotland-62862145?at_medium=RSS&at_campaign=KARANGA edward 2022-09-10 14:16:06
ニュース BBC News - Home Kharkiv offensive: Russia retreats as Ukraine attack takes key towns https://www.bbc.co.uk/news/world-europe-62860774?at_medium=RSS&at_campaign=KARANGA balaklyia 2022-09-10 14:52:35
ニュース BBC News - Home Hong Kong: Five jailed in for 'seditious' children's books https://www.bbc.co.uk/news/world-asia-china-62863622?at_medium=RSS&at_campaign=KARANGA beijing 2022-09-10 14:20:10
ニュース BBC News - Home Super League play-offs: Huddersfield Giants 0-28 Salford Red Devils - Visitors to face St Helens in semi-final https://www.bbc.co.uk/sport/rugby-league/62837226?at_medium=RSS&at_campaign=KARANGA Super League play offs Huddersfield Giants Salford Red Devils Visitors to face St Helens in semi finalSalford beat Huddersfield Giants in the Super League play off eliminator to set up a semi final at St Helens 2022-09-10 14:23:55
北海道 北海道新聞 車3台絡む事故、5人死傷 山梨・富士河口湖町 https://www.hokkaido-np.co.jp/article/729250/ 富士河口湖町 2022-09-10 23:12:40
北海道 北海道新聞 出産一時金、28都府県で不足 23年度から大幅引き上げへ https://www.hokkaido-np.co.jp/article/729308/ 医療機関 2022-09-10 23:13:00
北海道 北海道新聞 ひろびろ釧路の夜空に3尺玉 3年ぶり大漁どんぱく花火大会 https://www.hokkaido-np.co.jp/article/729267/ 北海道新聞 2022-09-10 23:13:29

コメント

このブログの人気の投稿

投稿時間:2021-06-17 05:05:34 RSSフィード2021-06-17 05:00 分まとめ(1274件)

投稿時間:2021-06-20 02:06:12 RSSフィード2021-06-20 02:00 分まとめ(3871件)

投稿時間:2020-12-01 09:41:49 RSSフィード2020-12-01 09:00 分まとめ(69件)