POPULARITY
What are @Layers in CSS, when and where should you be using them, how do you write them, and who's using them already? Show Notes 00:23 Welcome 01:49 Syntax Brought to you by Sentry 02:55 Where is this supported? 07:21 How do we write layers? 10:47 How do you write your CSS? 16:20 Nesting 20:35 Who else is using @Layer? Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads
https://codingcat.dev/podcast/1-29-using-css-in-js-with-stitches --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/purrfect-dev/message Support this podcast: https://anchor.fm/purrfect-dev/support
Key Points From This Episode: - Introducing Cassidy, her favorite frameworks, and her road into tech. - Understanding more about React and how Next.js fits into it. - Discussing other JS frameworks like Nuxt and Vite. - Making a counter and a to-do list in Vue; Cassidy’s experience with this new framework. - How making a counter in Vue would compare to doing it in React. - Loops, event bubbling, and deleting things from lists in Vue. - Setting up a new Vue app versus a new React one. - Using CSS modules versus styles in the component in Vue. - Different shortcuts in Vue such as the dollar, pound, and v-bind. - Issues around interpolation using string quotation marks rather than curly braces. - Highs and lows of Cassidy’s experience with the Vue docs. - How to find Cassidy online and read her newsletter too. - The week’s picks: Albanese gummy bears and more! Tweetables: - “I admit some of Vue, I was just like, it works and it felt magical to the point where I was just like, ‘It almost feels wrong. I need to suffer a little more to make this work.’” — @cassidoo [0:08:43] - “Luckily, I know enough React that I don't have to go to the docs anymore because I don't like them. So, in comparison, the Vue docs are great.” — @cassidoo [0:34:55] - “I enjoyed the Vue.” — @cassidoo [0:36:19] Links Mentioned in Today’s Episode: - Cassidy Williams (https://cassidoo.co/) - Cassidy Williams on LinkedIn (https://www.linkedin.com/in/cassidoo/) - Cassidy Williams on GitHub (https://github.com/cassidoo) - Cassidy’s Newsletter (https://cassidoo.co/newsletter/) - Netlify (https://www.netlify.com/) - Ionic (https://ionicframework.com/vue) - Enjoy the Vue on Twitter (https://twitter.com/enjoythevuecast?lang=en) - Enjoy the Vue (https://enjoythevue.io/) Special Guest: Cassidy Williams.
Verdict on CSS Grid…it is awesome! This episode is about what I learned after digging in to the syntax and how you can learn it as well. CSS Grid is a new display method that is part of the native CSS3 syntax, and is supported in the majority of modern web browsers. The primary advantage of using grid is that you can create a web page layout by placing your content anywhere you like on a grid that you define yourself. No more floats, clears, or adapting to someone else's grid system—just build what you need and it works. Using CSS grid also make is incredibly simple to make layouts responsive with not very much code at all. Below is a list of the CSS Grid resources I've found to be the most helpful as I learned. Top Recommendations: Start Here! CSS Grid Changes Everything - YouTube video Learn Here! Wes Bos' CSS Grid Video Course - highly recommended! Talks & Demos (video content) Start Using CSS Grid Layouts Today (conference talk) Build a Mosaic Portfolio Layout with CSS Grid Creating a nice layout CSS Grid layout using grid template areas How to Create Website Layouts Using CSS Grid CSS Grid Layout Crash Course Flexibility & The Fold – new possibilities with CSS Grid Web Demos & Documentation CSS Tricks Complete Guide to Grid Grid By Example - Rachel Andrew demos Jen Simmons Labs Learn CSS Grid MDN Documentation This episode was originally published 2 February, 2018.
Using CSS grid to make a grid, is, well, the whole point. But what if you want all those grid items to maintain an aspect ratio, like a 1:1 square? It’s possible, but it involves a little trickery. In this video, we’ll look at doing that because we want to put a logo, centered, in each square. One of the final demos: CodePen Embed Fallback… Read article “#179: A Grid of Squares”
The special guest for this episode of Sustain our Software is Kevin Owocki. Kevin is the founder of Gitcoin, a service that links up freelance developers with people who need them and pays these developers in crypto currency. Gitcoin is a blockchain forward brand that is built on open source software and currently uses Ethereum as its crypto currency of choice rather than creating their own. They like Ethereum because of its relevance as the 2nd most popular cryptocurrency at the time of this episode. By incentivizing open source contributions, Gitcoin has become an important contributor to the funding of open source software. Pia begins the discussion by asking Kevin how the bounty system is governed for Gitcoin and Kevin shares some of their structure, process, and philosophy on the subject as well as Gitcoin’s desire to make it easy for developers to find work on their platform. The panelists then discuss how they think the future of the job market will change with the emergence of blockchain. The discussion starts with stating that bounties are the current popular system but Eric says he would look to see a blockchain based paycheck network among other ideas. Pia questions how Eric’s ideas can scale to the larger open source ecosystems and how to have a conversation with a company to open a wallet with Ethereum. Eric responds with some of his ideas on how to make this work as well as some roadblocks they might face. One of the biggest challenges is that the technologies involved are newly emerging and this brings along some skepticism with it. Richard then asks what Kevin’s long term view is that goes beyond the current system even though things are working really well right now. Kevin shares his aspiration that Gitcoin becomes a network that is owned, built by, and built for coders. This means that they find a way to distribute Gitcoin’s equity to the community and sustain open source through those means. Kevin shares that he does wish to go beyond the bounty system and some of his thoughts on how he hopes to accomplish that. The conversation then moves to networks and peer communications. Pia raises a concern that some people who don’t have an aptitude for communication often get left behind. She asks Kevin how Gitcoin helps to overcome challenges for those who struggle to get involved. Kevin shares some thoughts on why certain demographics struggle and makes the point that a difference could be made in how those in the field prioritize diversity. Kevin talks about the sustain conference and some of the great opportunities he had when he attended the prior year. He had the opportunity to talk to other professionals and share ideas on web3, blockchain and sustaining open source. The final topic covered by the panelists is who the big contributors are that are making a big difference to sustain open source. Kevin names a few companies that he feels has made a difference and a high level view of what they have done. Panelists Pia Mancini Eric Berry Richard Littauer Guest Kevin Owocki Sponsors Adventures in .NET React Round Up Adventures in Blockchain Links Gitcoin Ethereum Web3 Sustain OSS Conference Codefund Oscoin Moloch DAO Picks Richard Refined github chrome extension Using CSS to hide the github notification icon Four Tet Eric Berry Pipedrive Oss fund Pia Woop recovery tracker Open collective climate strike Octobox Kevin Advantage kinesis 2 keyboard Gratitude journaling Deep Chord by Echo Space
The special guest for this episode of Sustain our Software is Kevin Owocki. Kevin is the founder of Gitcoin, a service that links up freelance developers with people who need them and pays these developers in crypto currency. Gitcoin is a blockchain forward brand that is built on open source software and currently uses Ethereum as its crypto currency of choice rather than creating their own. They like Ethereum because of its relevance as the 2nd most popular cryptocurrency at the time of this episode. By incentivizing open source contributions, Gitcoin has become an important contributor to the funding of open source software. Pia begins the discussion by asking Kevin how the bounty system is governed for Gitcoin and Kevin shares some of their structure, process, and philosophy on the subject as well as Gitcoin’s desire to make it easy for developers to find work on their platform. The panelists then discuss how they think the future of the job market will change with the emergence of blockchain. The discussion starts with stating that bounties are the current popular system but Eric says he would look to see a blockchain based paycheck network among other ideas. Pia questions how Eric’s ideas can scale to the larger open source ecosystems and how to have a conversation with a company to open a wallet with Ethereum. Eric responds with some of his ideas on how to make this work as well as some roadblocks they might face. One of the biggest challenges is that the technologies involved are newly emerging and this brings along some skepticism with it. Richard then asks what Kevin’s long term view is that goes beyond the current system even though things are working really well right now. Kevin shares his aspiration that Gitcoin becomes a network that is owned, built by, and built for coders. This means that they find a way to distribute Gitcoin’s equity to the community and sustain open source through those means. Kevin shares that he does wish to go beyond the bounty system and some of his thoughts on how he hopes to accomplish that. The conversation then moves to networks and peer communications. Pia raises a concern that some people who don’t have an aptitude for communication often get left behind. She asks Kevin how Gitcoin helps to overcome challenges for those who struggle to get involved. Kevin shares some thoughts on why certain demographics struggle and makes the point that a difference could be made in how those in the field prioritize diversity. Kevin talks about the sustain conference and some of the great opportunities he had when he attended the prior year. He had the opportunity to talk to other professionals and share ideas on web3, blockchain and sustaining open source. The final topic covered by the panelists is who the big contributors are that are making a big difference to sustain open source. Kevin names a few companies that he feels has made a difference and a high level view of what they have done. Panelists Pia Mancini Eric Berry Richard Littauer Guest Kevin Owocki Sponsors Adventures in .NET React Round Up Adventures in Blockchain Links Gitcoin Ethereum Web3 Sustain OSS Conference Codefund Oscoin Moloch DAO Picks Richard Refined github chrome extension Using CSS to hide the github notification icon Four Tet Eric Berry Pipedrive Oss fund Pia Woop recovery tracker Open collective climate strike Octobox Kevin Advantage kinesis 2 keyboard Gratitude journaling Deep Chord by Echo Space
The special guest for this episode of Sustain our Software is Kevin Owocki. Kevin is the founder of Gitcoin, a service that links up freelance developers with people who need them and pays these developers in crypto currency. Gitcoin is a blockchain forward brand that is built on open source software and currently uses Ethereum as its crypto currency of choice rather than creating their own. They like Ethereum because of its relevance as the 2nd most popular cryptocurrency at the time of this episode. By incentivizing open source contributions, Gitcoin has become an important contributor to the funding of open source software. Pia begins the discussion by asking Kevin how the bounty system is governed for Gitcoin and Kevin shares some of their structure, process, and philosophy on the subject as well as Gitcoin’s desire to make it easy for developers to find work on their platform. The panelists then discuss how they think the future of the job market will change with the emergence of blockchain. The discussion starts with stating that bounties are the current popular system but Eric says he would look to see a blockchain based paycheck network among other ideas. Pia questions how Eric’s ideas can scale to the larger open source ecosystems and how to have a conversation with a company to open a wallet with Ethereum. Eric responds with some of his ideas on how to make this work as well as some roadblocks they might face. One of the biggest challenges is that the technologies involved are newly emerging and this brings along some skepticism with it. Richard then asks what Kevin’s long term view is that goes beyond the current system even though things are working really well right now. Kevin shares his aspiration that Gitcoin becomes a network that is owned, built by, and built for coders. This means that they find a way to distribute Gitcoin’s equity to the community and sustain open source through those means. Kevin shares that he does wish to go beyond the bounty system and some of his thoughts on how he hopes to accomplish that. The conversation then moves to networks and peer communications. Pia raises a concern that some people who don’t have an aptitude for communication often get left behind. She asks Kevin how Gitcoin helps to overcome challenges for those who struggle to get involved. Kevin shares some thoughts on why certain demographics struggle and makes the point that a difference could be made in how those in the field prioritize diversity. Kevin talks about the sustain conference and some of the great opportunities he had when he attended the prior year. He had the opportunity to talk to other professionals and share ideas on web3, blockchain and sustaining open source. The final topic covered by the panelists is who the big contributors are that are making a big difference to sustain open source. Kevin names a few companies that he feels has made a difference and a high level view of what they have done. Panelists Pia Mancini Eric Berry Richard Littauer Guest Kevin Owocki Sponsors Adventures in .NET React Round Up Adventures in Blockchain Links Gitcoin Ethereum Web3 Sustain OSS Conference Codefund Oscoin Moloch DAO Picks Richard Refined github chrome extension Using CSS to hide the github notification icon Four Tet Eric Berry Pipedrive Oss fund Pia Woop recovery tracker Open collective climate strike Octobox Kevin Advantage kinesis 2 keyboard Gratitude journaling Deep Chord by Echo Space Special Guest: Kevin Owocki.
It’s 2019. Current year. How do you style your elements? When you’re using a framework, you’ll have to dig through a maze of JSX and other unholy combinations of code to squat down with your sad and pathetic non-classed selectors. Do you hide down in the crypts or do you go out and die with honor and dignity? I don't know. Web components. Watch this episode on YouTube: https://youtu.be/l3-fLhzKkI4 Error: Code Coffee is a weekly podcast about tech, web, food and life. A new episode is released every Friday at 12PM EDT / 18:00 CEST.
I wanna build a website what do I need to learn? To build a website from scratch you don't need to have any special knowledge or education. You can simply go ahead start learning. Tooling wise you don't need much, a text editor and a web browser. There are a few components that make up a website. HTML which stands for Hypertext markup language and CSS, Cascading style sheet. Think of HTML as the blueprint for your website. You define the page structure. Using CSS you can style the HTML element to define the look and feel, like color fonts etc.. What are the applications that I need to have? To get a simple website up and running you need a lot of tools, a text editor, and a browser is your friend. The code is simply some text so you can edit it in any text editor. The reason we use a special text editor like vs code is that we can code faster with it. It provides syntax coloring and autocomplete. In how
Backlinko has done an extensive analysis of “voice search ranking factors” and identified 11 variables tied to appearing in Google Home results. The company examined 10,000 results delivered over the smart speaker. What Backlinko found was consistent with what many others have been saying but there were also a few surprises. For example, the study discounts the impact of Schema to some degree and page authority. Eric Bidelman from Google posted a PSA, public service announcement, that since GoogleBot is based on Chrome 41, Google is unable to crawl CSS Custom Properties. Using CSS custom properties (variables) CSS variables are entities defined by CSS authors that contain specific values to be reused throughout a document. They are set using custom property notation (e.g. --main-color: black; ) and are accessed using the var() function (e.g., color: var(--main-color); Eric said he ran into the issue himself when he was deploying a layout or design that relies on vars. He said make sure you are compiling CSS so your page renders properly. As you know, the mobile first index is getting ready to expand in the upcoming weeks and some webmasters that still have desktop only sites are a bit nervous. If you still haven't read the official Google tips or the what you need to know you might not understand that desktop sites will be fine.
Backlinko has done an extensive analysis of “voice search ranking factors” and identified 11 variables tied to appearing in Google Home results. The company examined 10,000 results delivered over the smart speaker. What Backlinko found was consistent with what many others have been saying but there were also a few surprises. For example, the study discounts the impact of Schema to some degree and page authority. Eric Bidelman from Google posted a PSA, public service announcement, that since GoogleBot is based on Chrome 41, Google is unable to crawl CSS Custom Properties. Using CSS custom properties (variables) CSS variables are entities defined by CSS authors that contain specific values to be reused throughout a document. They are set using custom property notation (e.g. --main-color: black; ) and are accessed using the var() function (e.g., color: var(--main-color); Eric said he ran into the issue himself when he was deploying a layout or design that relies on vars. He said make sure you are compiling CSS so your page renders properly. As you know, the mobile first index is getting ready to expand in the upcoming weeks and some webmasters that still have desktop only sites are a bit nervous. If you still haven't read the official Google tips or the what you need to know you might not understand that desktop sites will be fine.
Public service announcement: Script'18 is happening. We have just a couple of tickets left. Check out https://scriptconf.org for more information. I had the pleasure of meeting the one and only Mathias Bynens (https://twitter.com/mathias) in Munich at JSKongress (https://twitter.com/JSkongress). We had a little chat over tea and Club Mate and spoke about Mathias' career and life. How he started as a developer, came to Opera and ended up with Google's V8 team (https://twitter.com/v8js). We also spoke about regular expressions and recent advancements in that area. They are evolving, and Mathias is actively contributing to the standards. I had a ton of fun, and I'm sure Mathias will cross paths with the ScriptConf crowd sometime in the future! Links: - Mathias' blog: https://mathiasbynens.be/ - Regular expression proposals: https://mathiasbynens.be/notes/es-regexp-proposals - Using CSS without HTML: https://mathiasbynens.be/notes/css-without-html - Parsing HTML with regex: https://stackoverflow.com/a/1732454/96656 - Script'18: https://scriptconf.org
Background. Evidence is accumulating that circulating tumor cells (CTC) out of peripheral blood can serve as prognostic marker not only in metastatic but also in early breast cancer (BC). Various methods are available to detect CTC. Comparisons between the different techniques, however, are rare. Material and Methods. We evaluate two different methods for CTC enrichment and detection in primary BC patients: the FDA-approved Cell Search System (CSS; Veridex, Warren, USA) and a manual immunocytochemistry (MICC). The cut-off value for positivity was = 1 CTC. Results. The two different non over lapping patient cohorts evaluated with one or the other method were well balanced regarding common clinical parameters. Before adjuvant CHT 21.1% (416 out of 1972) and 20.6% (247 out of 1198) of the patients were CTC-positive, while after CHT 22.5% (359 out of 1598) and 16.6% (177 out of 1066) of the patients were CTC-positive using CSS or MICC, respectively. CTC positivity rate before CHT was thus similar and not significantly different (P = 0.749), while CTC positivity rate immediately after CHT was significantly lower usingMICC compared to CSS (P < 0.001). Conclusion. Using CSS or MICC for CTC detection, we found comparable prevalence of CTC before but not after adjuvant CHT.
New post by Boagworld
© 2020-2025 Ivy Podcast Discovery LLC
