投稿時間:2023-01-11 02:25:08 RSSフィード2023-01-11 02:00 分まとめ(29件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	AWS DevOps Blog	Secure CDK deployments with IAM permission boundaries	https://aws.amazon.com/blogs/devops/secure-cdk-deployments-with-iam-permission-boundaries/	Secure CDK deployments with IAM permission boundariesThe AWS Cloud Development Kit CDK accelerates cloud development by allowing developers to use common programming languages when modelling their applications To take advantage of this speed developers need to operate in an environment where permissions and security controls don t slow things down and in a tightly controlled environment this is not always the case …	2023-01-10 16:46:20
Ruby	Rubyタグが付けられた新着投稿 - Qiita	RubyでPythonみたいな文字列スライスがしたい	https://qiita.com/ss8/items/c764c6ae1b5f65a603c3	abcdefg	2023-01-11 01:07:13
技術ブログ	Developers.IO	[WTFutil]CmdRunnerを利用してTCPとUDPの送受信サイズをターミナルに定期表示する	https://dev.classmethod.jp/articles/wtf-tcp-udp/	cmdrunner	2023-01-10 16:15:50
海外TECH	Ars Technica	Closing time: Windows 7 and Windows 8.1 have received their last updates	https://arstechnica.com/?p=1908680	browsers	2023-01-10 16:01:31
海外TECH	MakeUseOf	What Is a Crypto Lockdrop? How Does It Differ From an Airdrop?	https://www.makeuseof.com/what-is-crypto-lockdrop/	differences	2023-01-10 16:45:15
海外TECH	MakeUseOf	What Are Tesla Driver Profiles? 4 Things You Should Know	https://www.makeuseof.com/things-to-know-tesla-driver-profiles/	profile	2023-01-10 16:30:16
海外TECH	MakeUseOf	PC Operating Temperatures: How Hot Is Too Hot?	https://www.makeuseof.com/tag/pc-operating-temperatures-hot-hot/	computer	2023-01-10 16:15:15
海外TECH	MakeUseOf	Is Your Ethernet Connection Slower Than Your Wi-Fi on Windows? Here's How to Fix It	https://www.makeuseof.com/ethernet-connection-slower-wi-fi-windows/	windows	2023-01-10 16:15:15
海外TECH	DEV Community	4 signs you’re over-engineering ⚓️	https://dev.to/christopherkade/4-signs-youre-over-engineering-1g8l	signs you re over engineering ️During my first years as a Software Engineer I consulted for firms of different sizes from to people and it exposed me to various levels of over engineering This can happen for a lot of reasons and is usually a collective issue that tends to get worse as time goes on This short list goes into some concrete ish examples of pitfalls and how to avoid them Of course this list in non exhaustive and can be improved upon so feel free to let me know if I ve missed any glaring signs of this issue You always go for test coverage The Pareto Principle states that of the consequences come from of causes In our case the majority of our coverage will be done with a limited amount of tests and the remaining percentage might take a lot of effort for little reward I recommend reading about the ISTQB testing principles the second of which states that exhaustive testing is impossible One of the most important skills a testing expert possesses is the ability to identify the most important functions to test You have excessive indirection and abstraction in your code Have you ever been confronted with a bug in production felt the rush of adrenaline while trying to fix it as quickly as possible and not being able to pin point where the exact source of the problem is Did you have to go through layers upon layers of files wondering why previous authors yourself included hid away details by placing them in some external function four layers deep This is not as much of a problem when building a feature as you re focused on creating code that is clean and reusable but it requires a lot more mental gymnastics when trying to understand it when you re not the original author Over abstraction can create unmaintainable amp untestable monoliths that s why I believe writing concrete code first and then abstracting is important If you ever review code and can t understand the underlying business logic within that should already raise a red flag Always remember the Rule of Threes an abstraction without at least three usages isn t an abstraction Good abstraction are extracted and not designed You use micro frontends wherever whenever Micro frontends dividing parts of your application into smaller self contained units can be beneficial in terms of DX amp performance as it Allows you to only build the relevant part of your application in your CI making it fasterAllows you to ship parts of your app using different tech stacksAllows to load only the relevant files to your client making your application more performantAllows teams to work independently in a standalone version and iterate faster on featuresAnd many more advantages I won t get into I recommend this article if you want to dive deeper With all these benefits why would it be a bad idea to use this architecture too quickly Can add complexity and little reward Ask yourself what are the concrete benefits to using them for our project specifically Does your project have a lot of independent moving parts Can add little to no benefits for a lot of work Setting up an MFE takes a lot of configuration amp work side by side with your infrastructure team Can increase the size of your payloads if you have a diversity of technology stacks used it may end up slowing down your user s experience This can manifest through duplication of common dependencies let s say two of your MFEs use React you d then have to download the dependency twice A solution to that issue would be to use the same version of that dependency across your MFE but that would introduce a form of build time coupling of our MFEs which goes against a huge benefit mentioned above Makes it harder to test your features Here s an example say a banner on your homepage appears only when the user navigates to it from their profile if both of these pages are individual MFEs then you d have a hard time reproducing that behavior locally as you d probably be working on a standalone version of any given page The general ideas here also apply to micro services but I recommend this article if you want more information on the subject Ignoring the YAGNI principle You Aren t Gonna Need It The YAGNI principle created as part of Extreme Programming by Ron Jeffries states that a feature should only be developed when required and not by anticipation The main point being that developers should not waste time on creating extraneous elements that may not be necessary and can hinder or slow the development process If you try to future proof your code all the time you ll end up more often than not with unused code gathering dust in your repository Let s say you need to declare a class User that has a method getAllUsers you might start thinking that you ll eventually need getUserById and getUserByEmail and code them right away But that s when YAGNI comes in you should probably reconsider it and only code it when a feature requires it and for a couple of reasons The requirements might change in the future and make you update already unused methodsThe methods might simply never be used and take up space for no reasonJust like other programming principle KISS DRY etc YAGNI is pretty straight forwardThis list was inspired by this tweet from Cory House I recommend going through it as it ll show you some other mistakes that can cause over engineering Have you every been faced with obvious over engineering in a previous project or jobs I d love to hear some of your stories Thanks for reading I hope you got something out of this list And feel free to follow me on Twitter I m always happy seeing my circle of dev friends grow	2023-01-10 16:52:40
海外TECH	DEV Community	Past Informs the Present: Begin’s Approach to CSS	https://dev.to/begin/past-informs-the-present-begins-approach-to-css-17io	Past Informs the Present Begin s Approach to CSSCSS occupies an interesting position among web technologies while it can appear almost quaint in its simplicity it s also been interpreted by some as the most vexing language in web development Despite its approachability CSS sometimes gets a bad rap ーone that I believe derives from a fundamental misunderstanding of CSS history evolution and function as an API for styling on the web In this article we re going to review some of that history and evolution We ll then use that information to inform a focus on several methodologies ーsome battle tested some more recent ーfor making the process of styling web apps and components both enjoyable and effective The origins of CSSIn order to gain a deep understanding of CSS it s important to first understand the ecosystem from which it emerged that is the early days of the World Wide Web Getting familiar with this context is essential to understanding why CSS works the way it does ーand also provides some insight into just how far it has come since its inception In contrast to the dynamic and interactive nature of the Web of today the Web started out as a comparatively simple medium that is one for publishing documents This intent was clearly stated on the first ever website authored by Tim Berners Lee The WorldWideWeb W is a wide area hypermedia information retrieval initiative aiming to give universal access to a large universe of documents This first website was launched on August but the world would have to wait until December of for the official arrival of CSS at the hands of Håkon Wium Lie and Bert Bos At the risk of oversimplifying things at its highest level this first draft of CSS could be reduced to three fundamental tenets CSS is a language for authoring style sheets for HTML documents CSS encourages the independence of markup from style sheets thereby preserving content fidelity and structure while allowing for the application of reusable styles CSS style sheets cascade ーthat is styling rules declared by the user agent may be overruled by styles declared by the document author which themselves may be overruled by the end user This third tenet ーthe cascading nature of CSS ーwas a source of great debate at the time and traces of this debate even carry on amongst web practitioners today And yet CSS cascade is perhaps one of its most defining attributes it underscores the web as a medium where content and its presentation is informed not only by browser makers but also by content authors end users and those users devices and their capabilities Even from the Web s earliest days as a platform for static documents CSS was in its own way declaring in no uncertain terms that the presentation of content on the Web must be approached not dictatorially but democratically ーor to use a more modern and technical term responsively The second tenet referencing CSS global scope and its independence from HTML will of course be a familiar topic to anyone who has touched frontend development over the past two decades We ll get deeper into this later in the article The first tenet I ve proposed above however is perhaps the most impactful yet also the easiest to overlook In fact I believe the nature of this principle is one that a great many web developers to this day tend to forget or never learn in the first place and this in turn has become a source of some of the deepest struggles in frontend web development over the years And so let us spell it out clearly CSS as game changing as it was was not created as an application or component styling API ーit was designed as a means of styling static documents authored in HTML Documents and applications and components however present drastically different contexts for design The nature of the standardized Web meanwhile as one of perhaps the most backwards compatible software platforms has in turn meant that CSS origin story was always going to be inescapable Unlike so many technology stacks of today turning CSS into an application styling API would never be a matter of simply shipping a breaking change and letting end users deal with the fallout As the web matured into a platform not just for documents but rather one for the multidirectional flow of information CSS as its UI layer would have to evolve gradually along with it This then establishes what I consider the grain of CSS ーa grain that many web developers continue to struggle with With and against the grainPhoto by Lucas Davies on UnsplashWith the transition away from documents and toward applications and components web developers began devising methodologies to execute increasingly complex user interfaces with a styling API that was still heavily targeted towards static documents Some of these methodologies were successful ーeven essential ーin pushing both CSS and styling on the web more broadly into the future others were less so In my experience the most important developments in CSS methodologies were those that were designed with the grain of CSS in mind the least successful candidates meanwhile tended to push quite hard against it Perhaps the most important CSS methodology to emerge during the web s transition towards application like websites was Object Oriented CSS OOCSS devised by Nicole Sullivan in Nicole s now legendary article The Media Object Saves Hundreds of Lines of Code represented a fundamental rethinking on the composition of CSS rulesets and their relationship to HTML content Instead of writing CSS styles around specific HTML content or basing styles on the location of content within the DOM OOCSS prioritized writing reusable styling rules based on design patterns in the case of the media object a fixed size media element e g image or video along with other variable size content e g text As perhaps the first instance of a CSS methodology systematically informed by a visual pattern language OOCSS was also a critical step towards a more modular reusable approach to writing CSS As style sheets became the responsibility of larger and larger teams CSS global scope and specificity were often at odds with team dynamics Style collisions became increasingly common where changes introduced by one developer would inadvertently affect styles elsewhere on the website As the old joke goes two CSS properties walk into a bar a bar stool in a completely different bar falls over As these issues and the number of people experiencing them multiplied so too did new CSS methodologies particularly those focused on style sheet architectures Before long we had SMACSS SUIT CSS BEM ITCSS and more Third party supersets of CSS also appeared during this time such as Sass and LESS which gave style sheet authors access to scripting features like variables and loops The extent to which CSS supersets benefitted or hindered the progress of styling on the web is debatable Sass for example should be credited for introducing variables to CSS which in turn inspired CSS own custom properties which improved upon Sass implementation in several ways In the same breath however I personally believe techniques such as nesting mixins loops and extends introduced by Sass and LESS were less beneficial These techniques resulted in excessively bloated and complex CSS being shipped to the browser To add insult to injury due to inherent differences between authored code and generated code CSS written in these supersets became much harder to debug a task which due to increases in complexity became increasingly necessary Similarly and despite the best of intentions some CSS methodologies could be considered more beneficial than others For example let s take the ruleset format proposed by the likes of BEM where classes are constructed with multifaceted declaration blocks bound to context aware class names The context aware part here is important ーBEM s Block Element Modifier construct declares that classes should be named based on a hierarchy derived from both markup and state This strategy introduces a dependency between the structure of a page s markup and its styles a strategy CSS itself had attempted to avoid BEM is not the only methodology to use this kind of ruleset format ーmany other methodologies rely on markup context or content context to inform the construction of classes Herein lies the problem though while this approach could be said to encourage pleasant developer ergonomics the results are inherently brittle due to the tight coupling between markup and styles On top of that the prioritization of selector nomenclature above the actual styles being applied to those selectors often results in style sheets that are bloated with repeating property declarations ーsee for example these styles from the Financial Times website o ads label left o ads inner before content Advertisement display block font size px text align left o ads label right o ads inner before content Advertisement display block font size px text align right o ads label center o ads inner before content Advertisement display block font size px text align center o ads label with borders font size px text align left In these ways and others many of the aforementioned methodologies could be said to work against the grain of CSS despite their intent to make styling easier and more robust As such the process of writing and maintaining CSS in the mid s had become increasingly complex but it also set the stage for a radical rethinking and a move towards simpler more efficient and more resilient methods of styling content on the web The atomization of CSSImage by Pawel Czerwinski on UnsplashFor many years the semantic nature of HTML led many to proclaim that CSS should also be written semantically However this tight coupling between HTML semantics and CSS selectors despite being recommended even by the WC as a best practice does not have a basis in reality Content semantics in HTML are expressed through the use of meaningful elements like h nav footer ul etc and the way in which these elements are structured to create a document tree CSS meanwhile ーbeing a presentational language ーhas no notion of content semantics there is no way for a machine to glean information about HTML content from a style sheet Nicolas Gallagher in an article I still consider to be of foundational importance spelled this out quite clearly in The primary purpose of a class name is to be a hook for CSS and JavaScript If you don t need to add presentation and behavior to your web documents then you probably don t need classes in your HTML In the absence of a mandate to describe particular nodes of content or ontological relationships between them CSS authors were free to consider other approaches to authoring CSS ーand by the early s many were doing just that The first article I recall reading that suggested a fundamental shift was underway was one written in by Thierry Koblentz appropriately entitled Challenging CSS Best Practices At the heart of Koblentz s article was a well argued overview of how so called best practices in CSS at the time often lead to multiple rewrites of both CSS and HTML whenever UI requirements change that hardly ever happens right leading to ever growing append only style sheets that become more brittle over time His proposal worked out in practice during his time at Yahoo was simple but nigh on heretical to many at the time The smaller the unit in a larger system the more reusable it is To break down styles into irreducible units we can map classes to a single style rather than many This will result in a more granular palette of rules which in turn improves reusability This Lego like approach to CSS can arguably be traced back to Nicole Sullivan s OOCSS and it could be argued early utility classes like clearfix but what Koblentz and others were proposing ーgenerally referred to as atomic CSS ーtook this approach to the logical extreme To illustrate the drastic difference in approaches consider the following two implementations of the media object for simplicity implemented with flexbox lt Best practices media object gt lt style gt media display flex media img flex shrink padding right px width px height px media content flex grow lt style gt lt div class media gt lt img class media img src … alt … gt lt div class media content gt Here s a traditional media object lt div gt lt div gt lt Atomic media object gt lt style gt flex display flex flex shrink flex shrink flex grow flex grow padding right padding right px width width px height height px lt style gt lt div class flex gt lt img class flex shrink padding right width height src … alt … gt lt div class flex grow gt Here s an atomic media object lt div gt lt div gt Note how each class in the atomic version maps to just a single CSS property and value In fact if I hadn t included the second lt style gt block I bet you d have had no problem determining each class effect from the markup alone This is a hallmark of atomic CSS ーthe effect of a class is typically self evident from its name alone whereas the specifics of a class name like media are more ambiguous For anyone familiar with atomic CSS today the example above will likely appear unremarkable The transition towards this approach was anything but however ーand on some corners of the web today debate still rages about whether atomic CSS has been the best or worst thing to happen to styling on the web since CSS There was however clearly an appetite for this approach amongst a non trivial swath of web developers the year saw the release of both Adam Morse s Tachyons and Brent Jackson s Basscss the first two frameworks to go all in on atomic CSS These frameworks were instrumental in writing the blueprints for the atomic CSS methodology and turning the status quo on its head ーand indeed the shift was so monumental that within a number of years utility first CSS frameworks started becoming multimillion dollar businesses The atomization of CSS had officially begun Atomic CSS successes and perceived failuresIn order to understand the success of atomic CSS even if that success remains a point of debate in some circles we should first examine its principles and the goals those principles seek to achieve Many of these principles are derived from functional programming hence the alternative name functional CSS Additional inspiration came from the Unix philosophy The most fundamental principles of atomic CSS are Classes should have a single purpose Classes should do one thing and they should do it well This makes each class more reusable A class that applies a margin and only a margin is more reusable than a class that applies and margin and a text colour A class effect should be self evident There should be no mystery about the effect of using a class ーclarity should always trump cleverness The effect of a class named flex which sets the display property to flex is self evident The effect of a class named media which may set any number of property values is ambiguous Classes should be composable Complex styles should be achieved by composing multiple single purpose classes together rather than by writing new complex and less reusable classes Classes should be immutable and free of side effects For example the underline class should only ever apply an underline style It should never not apply the underline or apply another style or change any other property of any other element Under no circumstances should it change the effect of another class It s important to note that these principles were not devised for their own sake ーeach plays an important role in authoring performant maintainable robust styles Single purpose classes are more reusable and composable than multipurpose classes Thus single purpose classes provide greater flexibility as well as reduced CSS file sizes both at the outset of new projects and throughout their lifecycle as fewer styles need to be added to deliver iterations and additions to UI Classes with singular self evident effects reduce cognitive overhead for developers the resultant styling systems are thus easier to learn and this in turn helps frontend teams scale their efforts across people and time Classes which are immutable and free of side effects result in fewer bugs ーand where bugs occur easier debugging and resolution follows In these ways and in others I have always felt that the nature of atomic CSS flows very much with the grain of CSS itself Remember that CSS was designed to be independent of markup and atomic CSS is by design untethered to any particular markup structure or content based semantics Atomic CSS also honors CSS specificity algorithm rather than attempting to game it ーit does not concern itself with optimized selector ranking or scope since every class is of single purpose and equal specificity This also means CSS inheritance model becomes an advantage as it was originally intended compositions can be built up with inheritance in mind over several layers of markup There are however many common objections raised against the atomic CSS methodology In general these tend to be It s not semantic We ve touched on this already but it s worth repeating semantics accessibility and clarity do matter but with all due respect to Zeldman there is nothing inherently unsemantic inaccessible or unclear about visual class names nor is there a reason for CSS to map to the same semantics as HTML This is inline styles all over again Nope Inline styles are defined in HTML atomic classes are defined in a style sheet Inline styles do not permit media queries pseudo elements or pseudo classes atomic classes do Inline styles have a specificity ranking of which can only be outranked by important atomic classes have a specificity of the same as any single class An inline style s source of truth is its own singular invocation on a given element an atomic class source of truth is a style sheet There is a lexical resemblance between class red and style color red this is where the similarities end Putting so many classes on my elements looks ugly is hard to read Admittedly lt section class max width post layout m auto pt pr pb pl gt doesn t read like poetry and yes that snippet is taken from this very page as of this writing However something that is a delight is being able to rapidly iterate on this composition ーfrom the logical origin of that composition the markup whether in the browser or my editor ーto explore different combinatorial spaces within the bounds of a design system Iterating in this fashion simply cannot be matched when using other methodologies This is so not DRY It s true atomic CSS can lead to repeating declarations of various styling rules ーbut I vastly prefer repeating declarations to repeating definitions which in my experience are much harder to maintain Also remember that every time you repeat a class name that s one more addition you didn t have to make to your style sheet Ultimately this is a matter of choosing what kind of repetition you want not one of avoiding repetition altogether Atomic CSS is at odds with modern component modeling Thinking in React is one of those articles that changed the way I thought about web development when it was published and there s no denying that building frontends on the web has become a component centric process However it s important to differentiate the process of thinking in components and the process of styling components A conceptual abstraction does not require an equivalent material abstraction and the fact of a component s existence does not necessitate a dedicated CSS class This still doesn t solve the problem of global scope or one off styles It doesn t and in fact atomic CSS is not designed for this For scoped or one off styles a different approach is absolutely required Atomic CSS can provide a fantastic foundation that covers the vast majority of styling needs for a given website and its constituent components and it can deliver those styles in a fraction of the file size and complexity of other methodologies To be clear these claims are not theoretical this has been my experience both as a contributor and leader of frontend teams over the past years and the same has been true for many others both within and outside of my professional circle But as we ve noted atomic CSS doesn t cover every use case scoped and one off styles are not part of its wheelhouse So what s to be done when a need for these sorts of styles emerges Going bespokePhoto by Chris Ralston on UnsplashWhere one off styles are needed or where we want to ensure certain styles are scoped to a given component additional measures beyond an atomic CSS methodology will be required There are several techniques that can be used to address these concerns with a few notable examples having become more popular in recent years CSS in JS The obvious contender in this list I used CSS in JS for many years myself and have to say the developer ergonomics are pretty impressive as is the ability to leverage both repeatable and bespoke scoped styles especially when using libraries like Styled System or Theme UI Unfortunately great developer ergonomics and scoping are not enough CSS in JS can add significant weight to client side bundles along with increased setup complexity especially when server side rendering is involved Some solutions can also lock you in to certain frontend frameworks limiting the portability of your styles There are some solutions emerging to address these concerns e g Vanilla Extract but at the end of the day I admit I m growing tired of learning abstractions of CSS ーthere are so many more valuable things I could be doing with my time This isn t necessarily a popular opinion but I think CSS is actually pretty amazing on its own and the closer to the metal I can stay the happier I am CSS Modules The name may suggest that CSS Modules are part of the CSS spec but this is not the case CSS Modules allow authors to extract styles from a vanilla css file and into a JavaScript file containing markup at build time these extracted styles are then regenerated as locally scoped styles wherever they are used This seems to offer some of the benefits of CSS in JS but without the ergonomics of colocating styles content and behavior within a given component Shadow DOM Shadow DOM is a web standards specification which is designed to provide encapsulation of content styles and behavior ーbut it has a number of hard to swallow caveats For one Shadow DOM roots need to be initialized in JavaScript though Declarative Shadow DOM should address this in the future Further styling encapsulation doesn t work quite like you think it does and this can cause some headaches I believe the Shadow DOM holds promise but for many use cases it can end up being more trouble than it s worth Fortunately a compelling solution for dealing with scoped and one off styles exists in the form of HTML custom elements which are part of the web components spec along with Shadow DOM and HTML templates I may be biased but I think the best way to work with custom elements right now is with Enhance though to be fair I got a sneak peak at Enhance before joining Begin in and was just as enthusiastic at that time Using Enhance to author custom elements in the form of Single File Components SFCs has a number of huge benefits Custom elements are expanded on the server providing great performance and an excellent baseline for progressive enhancement on the client Locally scoped one off styles can be authored simply by including a lt style gt block in your SFC When your component is expanded on the server these style blocks will be hoisted into the document head with all of that style block s selectors scoped to your custom element This allows for one off styles to be encapsulated and scoped to the component they re authored in without needing to touch the Shadow DOM Scoped styles written within an SFC are also a great place to leverage strategies like intrinsic design which can happily coexist alongside a global atomic class system If you don t need to write client side behavior you never have to interface with JavaScript classes or the Custom Elements Registry This is particularly handy for engineers or designers who might excel at HTML and CSS but lack experience in JavaScript Although SFCs are authored as JavaScript functions the bulk of the authored code is written in HTML and CSS as seen below my button mjsexport default function MyButton html return html lt style gt One off styles applied only to button elements rendered by MyButton Any button outside this component will not be affected button appearance none box shadow px px rgba lt style gt lt Atomic classes used for repeating styles gt lt button class p radius pill cursor pointer gt lt slot gt lt slot gt lt button gt index html lt my button gt Click Me lt my button gt Of course one need not use Enhance to gain the benefits of using custom elements Being a web platform standard you could author the above component and scoped styles without the use of Enhance ーit would simply involve writing more boilerplate although server rendering would be harder to implement from scratch My personal experience however is that the current implementation of custom elements and web components as a whole leaves a fair bit to be desired influenced as it is by the JavaScript framework wars of years past Perhaps one day we ll have a more HTML centric spec for web components as hinted at by specs like Declarative Shadow DOM but for now I find the abstractions provided by Enhance to be incredibly useful and pleasant to use Enhance also comes with an atomic CSS system out of the box which can be easily customized to integrate with design systems or brand guidelines Enhance thus presents an end to end styling solution that offers all the benefits of atomic CSS as well as the power to easily create one off locally scoped styles on a per component basis You may have also realized that since SFC styles are authored within a JavaScript file those style blocks can also take advantage of some CSS in JS niceties ーsuch as leveraging JS variables or functions ーwithout authors having to worry about client side performance While I ve yet to find much of a need for this the possibility is there Summing upWe ve covered a lot of ground in this article ーsome of it historical some of it subjective Although I ve used a lot of words to describe the benefits that I and many others have encountered with atomic CSS in comparison to other methodologies I do want to assert that as with so much on the web your mileage may vary Technical methodologies of all kinds inherently attract certain folks and repel others and as Jeremy Keith has said this is about matching the right tool to the right mindset though with the deepest respect to Jeremy I look forward to rebutting some other aspects of his article in the near future With that said I ve found that a great deal of misinformation has been shared over the years concerning atomic CSS and I think this has helped to create a mindset that may have kept many web professionals from giving this methodology a fair shake As a thorough foundation for styling ーespecially when configured to align with a team s design system ーatomic CSS is tough to beat in terms of its performance flexibility and robustness across scales of complexity and time In combination with a tight strategy for dealing with one off or scoped styles as with Enhance SFCs atomic CSS can act as a powerful styling API for documents applications and components which will serve individuals and teams and thus end users well for a long time to come Further ReadingA Brief History of CSS Until What Are Classes For CSS and ScalabilityDesigning in the Browser FasterOn the Growing Popularity of Atomic CSSLet s Talk About Web Components	2023-01-10 16:03:09
Apple	AppleInsider - Frontpage News	Apple names broadcasters for MLS Season Pass on Apple TV+	https://appleinsider.com/articles/23/01/10/apple-names-broadcasters-for-mls-season-pass-on-apple-tv?utm_medium=rss	Apple names broadcasters for MLS Season Pass on Apple TV Apple and Major League Soccer have released a list of broadcasters for MLS Season Pass on Apple TV which starts on February MLS Season PassMLS Season Pass will launch in the Apple TV app in over countries and regions Major League Soccer will announce the complete production plan for the service before the MLS season starts on February Read more	2023-01-10 16:42:24
Apple	AppleInsider - Frontpage News	Future of MagSafe, and the new Qi2 wireless charging spec	https://appleinsider.com/articles/23/01/10/future-of-magsafe-and-the-new-qi2-wireless-charging-spec?utm_medium=rss	Future of MagSafe and the new Qi wireless charging specAn update to the Qi wireless charging standard has been announced complete with a MagSafe magnet ring Here s why this is a big deal for both the accessory market and Apple s future iPhone designs MagSafe enables a secure connection for wireless charging On Tuesday the Wireless Power Consortium revealed that an update to Qi the dominant wireless charging standard used throughout the mobile industry is on the way Qi pronounced Chee Two not Cheeto will be a replacement for Qi and one that actually takes after Apple s MagSafe Read more	2023-01-10 16:00:36
海外TECH	Engadget	NASA is funding ideas for a Titan seaplane and faster deep space travel	https://www.engadget.com/nasa-titan-seaplane-pellet-beam-propulsion-163726530.html?src=rss	NASA is funding ideas for a Titan seaplane and faster deep space travelNASA is still willing to fund unusual concepts in its bid to advance space exploration The agency is handing out initial study grants to projects that could be useful for missions in and beyond the Solar System The highlight may be TitanAir a seaplane from Planet Enterprises Quinn Morley that could both fly through the nitrogen and methane atmosphere of Saturn s moon Titan and sail its oceans The quot flying boat quot would collect methane and complex organic material for study by sucking it in through a porous leading edge A project from UCLA s Artur Davoyan meanwhile could speed up missions to the outer edge of the Solar System and even interstellar space His design shown at middle would propel spacecraft by producing a quot pellet beam quot of microscopic particles travelling at very high speed over miles per second using laser blasts The concept could dramatically shorten the time it takes to explore deep space Where Voyager took years to reach interstellar space the heliopause roughly AU from the Sun a one ton spacecraft could reach AU in just three years It could travel AU in years Artur DavoyanOther efforts are sometimes similarly ambitious MIT s Mary Knapp has proposed a deep space observatory that would use a swarm of thousands of tiny satellites to detect low frequency radio emissions from the early universe not to mention the magnetic fields of Earth like exoplanets Congrui Jin from the University of Nebraska in Lincoln has envisioned self growing habitat building blocks that could save space on missions to Mars while Lunar Resources Peter Curreri has devised pipelines that could shuttle oxygen between Moon bases These are all very early initiatives that aren t guaranteed to lead to real world tests let alone missions However they illustrate NASA s thinking The administration is funding the projects now in hopes that at least one will eventually pay off If there s even partial success NASA could make discoveries that aren t practical using existing technology	2023-01-10 16:37:26
Cisco	Cisco Blog	Reduce Public Cloud Spend with Intersight Workload Optimizer	https://blogs.cisco.com/cloud/reduce-public-cloud-spend-with-intersight-workload-optimizer	Reduce Public Cloud Spend with Intersight Workload OptimizerYou can prevent surprise bills for over spending in the cloud and you can be smart about optimizing your cloud resources on an ongoing basis to truly take advantage of cloud elasticity Getting visibility into workload optimization across your entire infrastructure can potentially uncover additional cost savings in your data center	2023-01-10 16:00:39
海外TECH	CodeProject Latest Articles	Typed mxGraph with Angular 15	https://www.codeproject.com/Tips/5351700/Typed-mxGraph-with-Angular-15	angular	2023-01-10 16:23:00
海外科学	NYT > Science	AI Is Becoming More Conversant. But Will It Get More Honest?	https://www.nytimes.com/2023/01/10/science/character-ai-chatbot-intelligence.html	AI Is Becoming More Conversant But Will It Get More Honest At a new website called Character AI you can chat with a reasonable facsimile of almost anyone live or dead real or especially imagined	2023-01-10 16:02:35
海外科学	NYT > Science	Where the Bison Could Roam	https://www.nytimes.com/2023/01/10/science/bison-prairie-grassland.html	Where the Bison Could RoamBison once numbered in the tens of millions in the United States Now a nonprofit is working to restore the shortgrass prairie where the American icons and their ecosystem can thrive again	2023-01-10 16:42:29
海外科学	NYT > Science	U.S. Carbon Emissions Grew in 2022, Even As Renewables Surpassed Coal	https://www.nytimes.com/2023/01/10/climate/us-carbon-emissions-2022.html	coalemissions	2023-01-10 16:09:15
海外科学	BBC News - Science & Environment	Biodiversity: Rising tide of extinctions on Madagascar	https://www.bbc.co.uk/news/science-environment-64210787?at_medium=RSS&at_campaign=KARANGA	extinctions	2023-01-10 16:03:58
金融	金融庁ホームページ	非常勤職員（専門研究員）を募集しています。	https://www.fsa.go.jp/common/recruit/r4/kenkyu-05/kenkyu-05.html	非常勤職員	2023-01-10 17:30:00
金融	金融庁ホームページ	EDINETの稼働状況に関するお知らせについて更新しました。	https://www.fsa.go.jp/search/edinet-Information/information-01.html	edinet	2023-01-10 17:00:00
ニュース	BBC News - Home	Strikes bill: Unions criticise plans as unworkable	https://www.bbc.co.uk/news/uk-64219016?at_medium=RSS&at_campaign=KARANGA	public	2023-01-10 16:01:45
ニュース	BBC News - Home	Spare review: The weirdest book ever written by a royal	https://www.bbc.co.uk/news/uk-64223264?at_medium=RSS&at_campaign=KARANGA	memoir	2023-01-10 16:15:11
ニュース	BBC News - Home	Newcastle City Council fined after decaying tree collapsed on girl	https://www.bbc.co.uk/news/uk-england-tyne-64222170?at_medium=RSS&at_campaign=KARANGA	henderson	2023-01-10 16:19:59
ニュース	BBC News - Home	Rishi Sunak's use of jet for hospital trip defended by No 10	https://www.bbc.co.uk/news/uk-politics-64225730?at_medium=RSS&at_campaign=KARANGA	climate	2023-01-10 16:41:42
ニュース	BBC News - Home	Masters 2023: Barry Hawkins whitewashes UK champion Mark Allen to reach quarter-finals	https://www.bbc.co.uk/sport/snooker/64226296?at_medium=RSS&at_campaign=KARANGA	alexandra	2023-01-10 16:44:33
ニュース	BBC News - Home	What you might have missed in Spare	https://www.bbc.co.uk/news/uk-64220688?at_medium=RSS&at_campaign=KARANGA	donald	2023-01-10 16:06:28
Azure	Azure の更新情報	Public preview: Azure Synapse Runtime for Apache Spark 3.3	https://azure.microsoft.com/ja-jp/updates/public-preview-azure-synapse-runtime-for-apache-spark-33/	Public preview Azure Synapse Runtime for Apache Spark You can now create Azure Synapse Runtime for Apache Spark The essential changes include features which come from upgrading Apache Spark to version and upgrading Delta Lake	2023-01-10 17:00:23
GCP	Cloud Blog	Sparse Features Support in BigQuery	https://cloud.google.com/blog/topics/developers-practitioners/sparse-features-support-in-bigquery/	Sparse Features Support in BigQueryIntroductionMost machine learning models require the input features to be in numerical format and if the features are in categorial format pre processing steps such as one hot encoding are needed to convert them into numerical format Converting a large number of categorical values may lead to creating sparse features a set of features that contains mostly zero or empty values As zero values also occupy storage space and sparse features contain mostly zeros or empty values the effective way of storing them becomes a necessity We are happy to announce a new functionality that supports sparse features in BigQuery This new feature efficiently stores and processes sparse features in BigQuery using Array Struct lt int numerical gt data type What are sparse features If you have been working with machine learning systems for a while you may come across the term sparse features As most machine learning algorithms require numerical features as input if the features are in categorical format pre processing steps such as one hot encoding are usually applied to convert them before using them as input features Applying one hot encoding to a categorical data column with a large number of categorical values creates a set of features that contains mostly zero or empty values also known as sparse features  Given two sentences “Hello World and “BigQuery supports sparse features now If we are to create a vector representation of those sentences using bag of words approach we will get a result like thisTake a look at how “Hello World is represented with There are only two instances of ones and the rest of the values in the vector are all zeros As you can imagine if we have a large corpus of text suddenly we end up with a very large NxM dimension of mostly zeros So due to its unpredictable nature sparse features may span from a few columns to tens of thousands or even more of columns Having tens of thousands of zero valued columns isn t a particularly good idea especially at scale Not only are the zeros taking up the space they are also adding additional computation for operations such as lookup Hence it is essential to store and process the sparse features efficiently when working with them  To achieve that goal we can store only the index of non zero elements in a vector since the rest of the values will be zeros anyway Once we have the indices of all the non zero elements we can reconstruct the sparse vector by knowing the highest index With this approach we can represent “Hello World with just instead of like before If you are familiar with SparseTensor from TensorFlow this new feature in BigQuery is similar to that Working with sparse features in BigQueryThis newly released feature enables efficient storage and processing of sparse features in BigQuery In this blog post we will demonstrate how to create sparse features with an example First things first let s create a dataset with the two sentences “Hello World and “BigQuery ML supports sparse features now We will also split the sentences into words using the REGEXP EXTRACT ALL function code block StructValue u code u Create a dataset if does not exist r nCREATE SCHEMA IF NOT EXISTS sparse features demo r n r n Create a table with example sentences and sentences split by a REGEX r nCREATE OR REPLACE TABLE sparse features demo sentences AS r n SELECT r n sentence r n REGEXP EXTRACT ALL LOWER sentence a z AS words r n FROM r n SELECT Hello World AS sentence r n UNION ALL r n SELECT BigQuery supports sparse features now AS sentence r n r n u language u u caption lt wagtail wagtailcore rich text RichText object at xedbde gt The result table sentences should look like thisTo be able to represent the sentence in vector format we will create a table to store the vocabulary using all the words from the sentences It can be done by executing following commandscode block StructValue u code u Create a table with word frequency and assign their respective index r nCREATE OR REPLACE TABLE sparse features demo vocabulary AS r n SELECT r n ROW NUMBER OVER ORDER BY word AS word index r n COUNT word AS word freq r n word r n FROM r n sparse features demo sentences r n UNNEST words AS word r n GROUP BY r n word r n ORDER BY r n word index r n u language u u caption lt wagtail wagtailcore rich text RichText object at xeceed gt The vocabulary table will be populated with these informationOnce we have the vocabulary table we can create a sparse feature using the new functionality To create a sparse feature in BigQuery we just need to define a column with Array Struct lt int numerical gt type as followscode block StructValue u code u Generate a sparse feature by aggregating word index and word freq for each sentence r nCREATE OR REPLACE TABLE sparse features demo sparse feature AS r n SELECT r n word list sentence r n ARRAY AGG STRUCT vocabulary word index vocabulary word freq AS feature r n FROM r n SELECT r n sentence r n word r n FROM r n sparse features demo sentences r n UNNEST words AS word r n AS word list r n LEFT JOIN r n sparse features demo vocabulary AS vocabulary r n ON word list word vocabulary word r n GROUP BY r n word list sentence r n u language u u caption lt wagtail wagtailcore rich text RichText object at xedac gt You should see this result And that s it We just created a sparse feature using BigQuery You can then use this feature to train models with BigQuery ML which would not have been possible without the use of sparse feature functionality	2023-01-10 16:21:00