投稿時間:2022-04-09 21:11:02 RSSフィード2022-04-09 21:00 分まとめ(14件)

カテゴリー等 サイト名等 記事タイトル・トレンドワード等 リンクURL 頻出ワード・要約等/検索ボリューム 登録日
python Pythonタグが付けられた新着投稿 - Qiita AutoTrainでテキスト分類 https://qiita.com/relu/items/d43f1d0c8496d81a9e96 autotrain 2022-04-09 20:21:32
python Pythonタグが付けられた新着投稿 - Qiita YOLOXでビデオ映像から人物の映っているフレームだけ抽出してみた https://qiita.com/masashi-ai/items/66684c3fd953091c819d 監視カメラ 2022-04-09 20:20:03
Ruby Railsタグが付けられた新着投稿 - Qiita ActiveSupport::Concernでモジュールを作る https://qiita.com/ttk/items/fa2e2b8c8721b490182c activesupport 2022-04-09 20:43:51
海外TECH Ars Technica The Senate bill that has Big Tech scared https://arstechnica.com/?p=1846884 platforms 2022-04-09 11:06:04
海外TECH MakeUseOf Got a New iPhone? Claim Your Free Temporary iCloud Storage to Back Up https://www.makeuseof.com/how-to-get-temporary-icloud-storage-back-up-new-iphone/ Got a New iPhone Claim Your Free Temporary iCloud Storage to Back UpIf you don t have any iCloud storage left Apple still gives you temporary iCloud storage to make a backup when you buy a new device 2022-04-09 12:00:13
海外TECH DEV Community Structured configuration in Go https://dev.to/andrewpillar/structured-configuration-in-go-4ap7 Structured configuration in GoThere comes a point in time during the development of a piece of software when a configuration language needs to be used you can only do so much via flags before it becomes too tenuous The language chosen should provide a format that is easy for a person parse as well as a computer Typically most people would reach for YAML TOML or sometimes even JSON For the development of Djinn CI none of these fitted my needs so I developed my own specifically for Go What a configuration language should beIn my opinion a configuration language should allow for a declarative way of configuring a piece of software The syntax of the language should be easy for a person to parse since they will be spending a good amount of time reading and writing said configuration A configuration language should be light on visual noise that is anything that might incur a person s ability to read the language It should also allow for comments so the person writing the configuration can explain what the configuration is for The last points visual noise and comments rules out JSON as being a configuration language It is fine for serializing data and exchanging it between programs but should be avoided as a primary configuration format This does not rule out YAML or TOML though Which are fine configuration languages depending on what is being configured I should stress that there is no singular configuration language that will meet the requirements for how every piece of software is configured The language chosen will vary depending on how you want to expose your software for configuration Note When I use the term primary configuration format I am referring to the configuration that a person would need to edit themselves JSON is fine for storing configuration that is edited by a program My main gripes with JSON as a configuration format arise when I have to edit it myself Starting with TOMLWhen starting out with the development of Djinn I initially settled on TOML It s simpler than YAML and much stricter no assumptions will be made about the string yes for example Below is an example of some of the configuration in TOML net listen net tls cert var lib ssl server crt key var lib ssl server key This was fine to start off with however Djinn requires a certain level of nested structure as part of the configuration Take provider configuration for example a provider can be configured for each rd party you want to integrate with in TOML this looked like this provider provider github client id client secret provider gitlab client id client secret this was not great The main reason being it made the configuration less readable and harder to parse at a glance There were other instances of this too throughout the configuration of Djinn such as the configuration of drivers driver driver qemu disks var lib djinn qemu cpus memory I wanted Djinn and its components to have configuration that was easy to read With TOML I was quickly running up against its limitations with regard to nested configuration structures So I started exploring other options HCLHCL is the configuration language from HashiCorp if you ve worked with Terraform then you will be familiar with it As stated in the readme for the project HCL attempts to strike a compromise between generic serialization formats such as JSON and configuration formats built around full programming languages such as Ruby HCL syntax is designed to be easily read and written by humans and allows declarative logic to permit its use in more complex applications this appears to fulfill my needs for making it easier to work with nested structures of configuration Let s take a look at how Djinn may be configured with HCL net listen tls cert var lib ssl server crt key var lib ssl server key provider github client id client sercret provider gitlab client id client sercret driver qemu disks var lib djinn qemu cpus memory this is better however the requirement for to assign a value to a parameter and the quotes around the labels irk me Furthermore it would be nice if I could use size units when specifying an amount of something in bytes Structured configurationStructured configuration is the type of configuration language I wanted for Djinn whereby parameters could be grouped together into blocks and nested within each other Hence the structure The language I came up with was heavily influenced by HCL and libucl and has support for duration and size literal values Below is what the language looks like net listen tls cert var lib ssl server crt key var lib ssl server key provider github client id client secret driver qemu disks var lib djinn qemu cpus memory KB as you can see it is very similar to HCL however there is less visual noise as I call it The library developed for this is called config which is used for decoding the configuration there is not support as of yet for encoding With this library you will be able to configured support for environment variable expansion and support for includes I have found that this strikes the balance I require of a configuration language declarative with limited visual noise and easy for people to read This is hardly a silver bullet and no doubt will demonstrate it s limitations depending on what it is you re trying to configured Nonetheless I have found it be flexible for my use cases You can see examples of this language in the djinn ci djinn repository itself in the dist directory 2022-04-09 11:25:53
海外TECH DEV Community How I started My Open-Source contribution Journey. https://dev.to/amolshelke2/how-i-started-my-open-source-contribution-journey-d8j How I started My Open Source contribution Journey first contribution I still remember my fist issue and first pull request in one of my friends project resumegen it was a react project but I m not familiar with react that time So I just create a Readme md file for that project and I think that why he will merged my pull request even I don t did anything just create a Readme md file and write some information about his project only line of markdown I contribute in that project because I was curious about contributing in open source project I did my first pull request and after a day my pull request was merged by the owner of the project And that s how I started contributing in open source projects and then after a month I get to know that there is an open source program is organized by Girl Script Summer of code it was a month long program in which we have to choose any project according to our interest and contribute to them and I join the program I was selected as an open source contributor I have contributed in many frontEnd projects and still contributing it was a great experience I highly suggest to beginner developers to contribute in open source projects it gives you an idea of real world programming how to understand others code and many more Wish you a good day️ 2022-04-09 11:24:32
海外TECH DEV Community Breaking the deadlock for low-code - Part-2 Leverage on low-code platforms and key advantages https://dev.to/swatantra/breaking-the-deadlock-for-low-code-part-2-leverage-on-low-code-platforms-and-key-advantages-bg4 Breaking the deadlock for low code Part Leverage on low code platforms and key advantagesWe read about the rise of the Low Code platforms in the earlier post in this series The race to add richness to low code applications aggressive vendor investments targeted at some of the most pressing needs and ability to quickly respond to the challenges of modern enterprise applications are making the low code platforms attractive Low code is often used in the niches of a company On a high abstraction level the use cases can be boiled down to four best fitted categories Figure where low code gets the job done Innovation Innovative apps are making solutions processes extremely exciting with impressive productivity generating business value using emerging technologies and driving innovation These could be smart and connected apps merging the physical and digital world using the Internet of Things IoT Artificial Intelligence AI and Machine Learning ML Applications under this category generally start with an idea and evolve with a high rate of change while relying on multiple integration points with external data feeds web services IoT data geodata etc Customer engagement This group of applications focus on business and customer experience The general goal is to improve customer experience keep them engaged and improve the satisfaction score The customer could be another business entity or end users Think about BB Business to Business portals BB apps BC Business to Consumer portals BC apps these are one of the largest pools of applications where low code presence can be seen These applications often connect to core digital systems and have multi channel connectivity Operational efficiency Not all of the applications need to be bulletproof or come with a slew of features oftentimes basic applications aim to improve the organization specific business processes or operations are sufficient to enable the team to become more productive and deliver more value These are principally BE Business to Employee apps workflow or case management applications compliance and quality management applications and departmental apps Such applications are often combined with BB apps This is also a large group of applications where low code is widely used Being organization specific in nature they are generally integrated with Systems of record ERP solutions CRM solutions Salesforce SAP Microsoft Dynamics Oracle NetSuite etc Legacy modernization In many organizations legacy applications serve critical roles in driving business operations There is a clear need to modernize outdated systems Often when retiring the legacy is a not an immediate solution a low code solution could be positioned to co exist to get the most out of the legacy before pulling the plug The primary focus could be on replacing the legacy or building new skins on top of it while maintaining the system itself This category could be one of the biggest markets for low code to penetrate At enterprises these applications mostly interact with but not limited to Lotus notes GL GL apps Access SharePoint Excel Core record keeping systems and core system extensions The key advantages of the low code platformsNever before in the history of software development has the complexity of technology been this huge Developers are expected to cover a vast array of areas multi cloud hybrid infrastructure security performance scalability cross platform multi device responsiveness offline availability distributed caching databases extensions APIs AI ML DevOps The complexity has increased exponentially and so has the application development time In this complex environment the low code platforms are developing themselves into a solid foundation for digitization with many advantages Rapid development enables faster time to market With low code platforms businesses can translate ideas into working prototypes in days rather than weeks or months It gives the true agility to quickly respond to change fail fast iteratively improve faster and reach the market better Rapid development enables shorter time to market with faster application development As a result of the rapid development tool it significantly shortens the development time compared to traditional development which can be better utilized for innovations Ease of use The development of the applications is simplified using the model and visual based development It is primarily a drag and drop interface a little technical knowledge is required to develop a business application This makes room for business users to understand engage and be accessible in the development journey of the applications Easy integration with external systems Low code solutions can reduce the complexity of integration with other systems making it interoperable Integrations have always been the most cumbersome and tiring process in any software development With the help of low code platforms developers significantly reduce time and effort using its out of the box REST APIs SOAP web services webhooks SAP OData and external databases connectivity In control Since the infrastructure and codes were generated by the low code platform the underlying platform takes care of many important security aspects It integrates with a wide array of identity providers and implements RBAC role based access controls Once a low code platform is connected and audited in the organization s software perimeter new uses cases can be built fast in a controlled environment Scalability The low code platforms provide the ability to scale on demand The applications can benefit from auto scaling auto provisioning auto healing out of the box to meet the enterprise needs for users volumes of data app functionality However the suitability in larger projects and for crucial enterprise applications are yet to be witnessed at large scale Privacy Low code platforms apply necessary procedures to safeguard the confidentiality of the data stored by the applications In built monitoring and logging Applications developed using low code benefit from the platforms easy to use in built monitoring solution There is a wide range of monitoring available e g performance network server usages activity technical debt monitoring Applications also leverage from the out of box logging analytics which helps in troubleshooting errors web service and API invocations access logs Maintainability Few platforms provide the service which measures key aspects of app maintainability against a set of ISO IEC parameters i e modularity reusability analyzability modifiability testability and highlights any potential issues that should be addressed As mentioned it also provides the technical debt monitor which helps perform code and runtime performance analysis before recommending solutions to help improve the system s maintainability Mobile first offline first Low code supports mobile app development with offline and native capabilities The platform provides control over offline data storage data synchronization and offline architecture Cost effective Due to the fact that the basic applications can be built with relatively less skilled staff and that the development cycle of these applications is shortened more applications can be realized in the same amount of time with less cost The applications are maintainable and significantly reduce the total cost of ownership TCO Hence gives great business value 2022-04-09 11:24:00
海外TECH DEV Community OpenTelemetry and Jaeger | Key concepts, features, and differences https://dev.to/signoz/opentelemetry-and-jaeger-key-concepts-features-and-differences-4pd8 OpenTelemetry and Jaeger Key concepts features and differencesOpenTelemetry and Jaeger are both open source projects under Cloud Native Computing Foundation In this article let us understand the key concepts involved in both projects their features and their differences OpenTelemetry is a vendor agnostic instrumentation library It provides a set of tools APIs and SDKs to create and manage telemetry data logs metrics and traces Jaeger is an open source tool focused on distributed tracing of requests in a microservice architecture Both OpenTelemetry and Jaeger enable application owners to set up monitoring and observability to measure application performance But their solutions are meant for different problems While OpenTelemetry helps generate telemetry data Jaeger is a distributed tracing tool What is Observability In control theory the term “observability states that a system is observable if the internal states of the system can be determined by looking at its inputs and outputs For distributed software systems observability means how well we are able to troubleshoot our systems for performance issues with collected data from the system What is OpenTelemetry OpenTelemetry is an open source project under the Cloud Native Computing Foundation CNCF that aims to standardize the generation and collection of telemetry data Telemetry data includes logs metrics and traces It is a collection of APIs SDKs and client libraries that is used to generate telemetry data from your application code The data you collect with OpenTelemetry is vendor agnostic and can be exported in many formats The biggest advantage of using OpenTelemetry is that you have the freedom to choose a backend of your choice You don t get locked into a vendor and engineering teams can get ramped up on a single technology to generate telemetry data To integrate OpenTelemetry with your application code you can use the OpenTelemetry client libraries of the required programming language OpenTelemetry also provides a collector known as OTel OpenTelemetry collector that can be used to process and export telemetry data in multiple formats The architecture of OpenTelemetry You can integrate OTel libraries with your application code What is Jaeger Jaeger is a popular open source distributed tracing tool that was originally built by teams at Uber and then open sourced It is used to monitor and troubleshoot applications based on microservices architecture A distributed tracing tool tracks user requests across services and gives a central overview of how different components of a microservices architecture interact to process user requests Jaeger is used to store analyze and visualize tracing data Jaeger does not support logs and metrics It provides instrumentation libraries that were built on OpenTracing standards The libraries cover popular programming languages like Go Java Node Python C and C For storing trace data it supports two storage backends CassandraElasticsearchJaeger provides a minimal UI to analyze the trace data captured Jaeger UI showing traces for selected services Comparing OpenTelemetry and JaegerWhile both OpenTelemetry and Jaeger are tools that enable setting up observability for modern day cloud native applications they are meant to solve different problems There are two major steps involved in setting up observability for your application Collecting relevant data that indicates the application healthStoring managing and visualizing the collected data to take quick actionsOpenTelemetry addresses the first step while Jaeger is meant to address the latter In the domain of observability a tool like Jaeger is called an observability backend while OpenTelemetry provides instrumentation Instrumentation is the process of enabling your application code to generate telemetry data You can use OpenTelemetry as your instrumentation layer and Jaeger for storing and visualizing trace data The key differences between OpenTelemetry and Jaeger can be summarized in the following points OpenTelemetry provides an instrumentation layer for your application code while Jaeger is a backend analysis tool used for storage and visualization of trace data Using OpenTelemetry libraries you can generate logs metrics and traces Jaeger does not support logs and metrics OpenTelemetry can only be used to generate and collect data It does not provide a storage layer Jaeger provides Cassandra and Elasticsearch as two options for storing data OpenTelemetry does not provide any web UI components Jaeger comes with a web UI component that is used for visualizing trace data Key Features of OpenTelemetry and JaegerBoth OpenTelemetry and Jaeger aim to improve the observability of cloud native applications by targeting different levels of the observability stack The main features of OpenTelemetry as an instrumentation layer include A single consistent instrumentation layer covering multiple programming languages and technologiesGeneration and collection of telemetry data that includes logs metrics and tracesSupports exporting telemetry data in multiple data formats to a backend of choiceCross language capabilities with the ability to produce telemetry data in consistent formats across all major programming languagesWhile OpenTelemetry gives you access to raw data needed to analyze application health Jaeger provides the analysis and storage layer to the end user i e the application owner The main features of Jaeger as a distributed tracing tool include Distributed transaction monitoring with tracesPerformance and latency optimizationRoot cause analysisService dependency analysisDistributed context propagation A better alternative to JaegerOpenTelemetry is the future of instrumentation for cloud native applications It is backed by a huge community of developers observability vendors and cloud vendors Modern day distributed software systems are complex to operate and troubleshoot Instrumenting every aspect of your application and infrastructure is the first critical step to keeping a check on application performance OpenTelemetry can take care of the entire instrumentation layer as it supports multiple programming languages and technologies The next step is about choosing a backend analysis tool Jaeger supports data formats of OpenTelemetry But Jaeger is limited in terms of its UI and does only distributed tracing For a robust monitoring and observability framework you need a unified UI for both metrics and traces And that s where SigNoz is far more suited than Jaeger as a distributed tracing tool SigNoz is a full stack open source application performance monitoring and observability tool which can be used in place of Jaeger SigNoz is built to support OpenTelemetry natively It also provides a fast OLAP database ClickHouse as the storage backend It comes with out of box application metrics charts Application metrics charts in SigNoz dashboardYou can analyze tracing data with powerful filters You can also analyze service level performance with aggregated trace metrics like the p latency of a specific service Filters for tracing data with capabilities for aggregated trace metricsSigNoz also provides a rich visualization of tracing data with the help of Flamegraphs and Gantt charts You can see exactly how a single event performed as part of an entire user request Flamegraphs and Gantt charts in SigNoz dashbaordCheck out SigNoz GitHub repo Frequently asked questionsDoes Jaeger use OpenTelemetry Jaeger is based on OpenTracing APIs for instrumentation But OpenTracing is now archived and it is suggested to migrate to OpenTelemetry if your project is using OpenTracing Jaeger s website mentions that future Jaeger backend components will be based on OpenTelemetry Collector Should I use OpenTracing or OpenTelemetry OpenTracing is now archived and it is suggested to migrate to OpenTelemetry Further ReadingJaeger vs SigNozOpenTelemetry Collector architecture and configuration guide 2022-04-09 11:17:01
海外TECH DEV Community Keep your JavaScript repository clean https://dev.to/strdr4605/keep-your-javascript-repository-clean-5gg0 Keep your JavaScript repository cleanAs your JavaScript project grows you start adding more tools and settings that will improve the development experience Nowadays tools like eslint husky and tests are essential for any project The problem is that most of these tools require a config file at the root of your project repo After some time the root directory is full of config files and it s a bit intimidating when you open it in the git hub One elegant solution I found in remirror repo There all config files that should stay in the root of the project are actually in the support root directory and they are locally symlinked when setting up the project Inspired by their approach I created symlink config which helps to migrate your project to this approach Here is how repo looks on Github before and after Default With symlink config This demo has only configs in the root but imagine adding more tools like tsconfig json jest config js and others When exploring the project locally all these files will be in the root but being just a symlink file they will differ from the rest of the files and you may skip them visually In the end I think this tool is useful for big open source projects with a lot of config files as it cleans up the entry point of the project the repo root and makes it more appealing to users Check out symlink config and let me know your opinion 2022-04-09 11:11:14
海外TECH DEV Community 😎 Make VS Code your home 🏠 using these awesome extensions 💻 https://dev.to/knaagar/make-vs-code-your-home-using-these-awesome-extensions--3fjk Make VS Code your home using these awesome extensions Wait VS Code my home What do you mean huh Making it your home means never wanting to leave that beautiful editor Here I show you some of the most useful extensions for VS Code that makes the editor so nice that you will code this way Let s start Live ShareThis extension is pretty pretty useful for collaborative coding I have myself used it quite a few times You just need to start a live session with that button in the image below and a link will be copied to your clipboard Other team members just need to use that link Indent RainbowThis extension makes coding so beautiful The rainbow indents as can be seen in the gif below look so pretty that I don t want to go to any other place to code Live SASS CompilerIf you are a frontend dev and have worked with SASS on VS Code you must have used this extension But if you are that Somewhere in my own world yeah human then I tell you to use it Just a click of the Watch SASS button and your SASS will be continuously watched and will get converted to CSS in no time Code Spell CheckerIf english is not your first language or you make a lot of typos or you just love those squiggly lines under text then this extension is for you Underlines the text that is not in its dictionary and suggest the closest possible words GitLensIf you use Git then you must be using this BUT if you are again that I am still in my world human this extension gives superpower to Git Wondering how watch the gif below Code RunnerYou know I know that this whole file will give a lotta errors in the console but the lines to seems perfect I just wanna run those but how Code Runner got you covered This runs the lines you select yes exactly those lines PolacodeIf you write blogs or you are I love code images human this extension is very useful See the gif below to see how it works Output ChroniclerWell if you have watched those gifs attentively then you must have noticed I am recording those with something called Chronicler This extension is pretty useful to record gifs like those Visit the extension link on more information of how to use it JavaScript ES Code SnippetsThis one I can t live without This makes writing JavaScript way fast and interesting See the gif below and visit the extension link to know more about the code letters you can use Plus of course this Emmet Cheat Sheet It is already available in VS Code and makes writing code again faster Hope this helps you See you around 2022-04-09 11:06:36
ニュース BBC News - Home British man safe but son missing after Malaysia diving trip https://www.bbc.co.uk/news/uk-61049323?at_medium=RSS&at_campaign=KARANGA malaysia 2022-04-09 11:40:59
北海道 北海道新聞 ウクライナ首都近郊で132遺体発見 ロシア軍が射殺か https://www.hokkaido-np.co.jp/article/667712/ 遺体発見 2022-04-09 20:19:24
海外TECH reddit こんにちは、トンボ鉛筆の佐藤です。改めて阪神タイガースの方は大丈夫でしたか?両リーグ最速の借金10ですが、13試合終了時点で二桁の借金があるチームは1955年のトンボユニオンズ、79年の西武のみだったそうです。 借金返済が難しい場合は…、その先は言う必要ないですよね。自分で考えてみてください。皆様にも言いたいこと、不満があるのは重々承知していました。全部ではありませんが、私も様々な心の奥にある声を見て・聞いています。 https://www.reddit.com/r/newsokunomoral/comments/tzr47c/こんにちはトンボ鉛筆の佐藤です改めて阪神タイガースの方は大丈夫でしたか両リーグ最速の借金10ですが1/ こんにちは、トンボ鉛筆の佐藤です。 2022-04-09 11:15:57

コメント

このブログの人気の投稿

投稿時間: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件)