home.social

Search

85 results for “Dazzatron”

  1. #UnusualHistory flip.it/w8FJql The Incredible Henry ‘Box’ Brown: This Black Man Mailed Himself Pennsylvania To Escape Slavery

  2. #UnusualHistory flip.it/w8FJql The Incredible Henry ‘Box’ Brown: This Black Man Mailed Himself Pennsylvania To Escape Slavery

  3. Got a chance to have another #designsystems therapy session with @brad_frost and Ian Frost on @shoptalkshow this week. This time about the intersection of AI and Design Systems.

    shoptalkshow.com/713/

  4. Got a chance to have another #designsystems therapy session with @brad_frost and Ian Frost on @shoptalkshow this week. This time about the intersection of AI and Design Systems.

    shoptalkshow.com/713/

  5. Got a chance to have another #designsystems therapy session with @brad_frost and Ian Frost on @shoptalkshow this week. This time about the intersection of AI and Design Systems.

    shoptalkshow.com/713/

  6. Got a chance to have another #designsystems therapy session with @brad_frost and Ian Frost on @shoptalkshow this week. This time about the intersection of AI and Design Systems.

    shoptalkshow.com/713/

  7. Got a chance to have another #designsystems therapy session with @brad_frost and Ian Frost on @shoptalkshow this week. This time about the intersection of AI and Design Systems.

    shoptalkshow.com/713/

  8. [Перевод] RESISTORS: как подростки из 1960-х работали с компьютерами до эпохи ПК

    В конце апреля 1968 года компьютерная конференция в Атлантик-Сити едва не сорвалась из-за забастовки телефонисток: терминалы крупных компаний стояли мёртвые. И вот посреди этой неразберихи в центре внимания оказалась небольшая группа подростков из окрестностей Принстона. Они раздобыли акустический модем, подсоединили его к ближайшему таксофону — и вышли на связь с удалённой мини-ЭВМ. Отраслевая газета Computerworld вывела их на первую полосу с заголовком в духе «Школьники украли шоу у профессионалов». Эти ребята называли себя RESISTORS — придуманная задним числом расшифровка аббревиатуры: «Radically Emphatic Students Interested in Science, Technology, Or Research Studies» — то есть «Радикально увлечённые ученики, интересующиеся наукой, техникой и исследованиями».

    habr.com/ru/companies/cloud4y/

    #RESISTORS #история_компьютеров #Тед_Нельсон #гипертекст #PDP8 #Burroughs_Datatron_205 #Клод_Каган #Project_Xanadu #Computer_Lib #история_программирования

  9. @davatron5000 [CEO on a plane]

    #riseAndGrind y'all, I GUARANTEE you can be a 100B company just like us, and live the life—

    [panel falls off; gusts of wind, engine sounds]

    —YOU ALWAYS DREAMED OF. JUST SIGN UP FOR OUR—

    [engine smokes and sputters, tailspin starts, CEO plastered on ceiling]

    —TEN WEEK, "ZERO TO HERO: CRUSHING COMPLIANCE AND SAFTEY" COURSE

  10. @davatron5000 [CEO on a plane]

    #riseAndGrind y'all, I GUARANTEE you can be a 100B company just like us, and live the life—

    [panel falls off; gusts of wind, engine sounds]

    —YOU ALWAYS DREAMED OF. JUST SIGN UP FOR OUR—

    [engine smokes and sputters, tailspin starts, CEO plastered on ceiling]

    —TEN WEEK, "ZERO TO HERO: CRUSHING COMPLIANCE AND SAFTEY" COURSE

  11. @davatron5000 [CEO on a plane]

    #riseAndGrind y'all, I GUARANTEE you can be a 100B company just like us, and live the life—

    [panel falls off; gusts of wind, engine sounds]

    —YOU ALWAYS DREAMED OF. JUST SIGN UP FOR OUR—

    [engine smokes and sputters, tailspin starts, CEO plastered on ceiling]

    —TEN WEEK, "ZERO TO HERO: CRUSHING COMPLIANCE AND SAFTEY" COURSE

  12. @davatron5000 [CEO on a plane]

    #riseAndGrind y'all, I GUARANTEE you can be a 100B company just like us, and live the life—

    [panel falls off; gusts of wind, engine sounds]

    —YOU ALWAYS DREAMED OF. JUST SIGN UP FOR OUR—

    [engine smokes and sputters, tailspin starts, CEO plastered on ceiling]

    —TEN WEEK, "ZERO TO HERO: CRUSHING COMPLIANCE AND SAFTEY" COURSE

  13. @davatron5000 [CEO on a plane]

    #riseAndGrind y'all, I GUARANTEE you can be a 100B company just like us, and live the life—

    [panel falls off; gusts of wind, engine sounds]

    —YOU ALWAYS DREAMED OF. JUST SIGN UP FOR OUR—

    [engine smokes and sputters, tailspin starts, CEO plastered on ceiling]

    —TEN WEEK, "ZERO TO HERO: CRUSHING COMPLIANCE AND SAFTEY" COURSE

  14. Issue 18 of #OwnYourWeb is out. ✨

    Curators.

    ✷ Personal site of the (more or less every other) week by @henry

    With links to posts and tools by
    @anarodrigues, @rachelandrew, @adactio, @anildash, @davatron5000, @manton, @robin, and @zeldman
    Thank you all for keeping the open web alive! ✊🎉

    newsletter.ownyourweb.site/arc

  15. @westbrook @davatron5000 @stubbornella I suspect this might overlap with existing #HtmlModules work.

    Also one more idea similar to 1.:

    5. Could we use this format to do the initial render of a component? By which I mean that #Angular compiles components to #JavaScript which looks like:

    ```
    function renderComponent() {
    if (initialRender) {
    createComponentDom();
    } else {
    updateExistingDom();
    }
    }
    ```

    This always bugged me as inefficient, because the first branch is only ever executed once per component instance. If we compiled components to this SFC format, could we just do the first render at compile time, generate the HTML directly and drop that `createComponentDom` function?

    I'm not knowledgeable enough to say that definitely makes sense, but I think it's an interesting idea at least.

    Not sure if other frameworks could benefit from similar optimizations, I suspect #React would not, but I'm less clear on non-#VDom frameworks.

  16. @westbrook @davatron5000 @stubbornella This proposal reminds me a lot of my #HtmlFragments investigation a lot while back (albeit with a very different use case in mind).

    blog.dwac.dev/posts/html-fragm

    I wonder if there is a potential path for this proposal which is less "Vue in the browser" and more "a primitive SFC format which frameworks can compile to". I wonder if this could solve multiple problems:

    1. #SSR small fragments of #HTML after page load.
    2. Vertical slice of separation of concerns for a component.
    3. Import module format (like #HtmlImports or #HtmlModules).
    4. Lazy loading a component and its styles without requiring CSS-in-JS.

    Kind of a smorgasbord of requirements but I can see value in the right primitive here.

  17. Last week I *also* showed up on the latest @shoptalkshow, which was *also* a wonderful danged time. That @davatron5000 and that @chriscoyier know how to cast a good pod, they do. 💖

    shoptalkshow.com/587/

    #YDATUbook #bookstodon #1u #podcasts

  18. @davatron5000 Is it too late to call this your "Bing Ban Theory"? #bazinga

  19. @zachleat @davatron5000

    If only the broken SPA merely flashed instead of stuck. That would be a reasonable and balanced technical design with prorities straight!

    more like Flash Of Great HTML Before Broken Single Page App.

    or... Flash Of Styled Content (FOSC) for short 🤓

    Ref fosstodon.org/@krinkle/1098075

  20. @davatron5000 I've seen it said, "bad alt text is better than no alt text", and I think in this case that's still true. still, it might help to have a short tag like "#autogenerated" at the front, so someone can recognize that it might be mangled and unmangle it. "I don't like sand" is an iconic enough line that it's possible that someone hearing that would recognize the context and understand how it got mangled

  21. @westbrook @davatron5000 @stubbornella I suspect this might overlap with existing #HtmlModules work.

    Also one more idea similar to 1.:

    5. Could we use this format to do the initial render of a component? By which I mean that #Angular compiles components to #JavaScript which looks like:

    ```
    function renderComponent() {
    if (initialRender) {
    createComponentDom();
    } else {
    updateExistingDom();
    }
    }
    ```

    This always bugged me as inefficient, because the first branch is only ever executed once per component instance. If we compiled components to this SFC format, could we just do the first render at compile time, generate the HTML directly and drop that `createComponentDom` function?

    I'm not knowledgeable enough to say that definitely makes sense, but I think it's an interesting idea at least.

    Not sure if other frameworks could benefit from similar optimizations, I suspect #React would not, but I'm less clear on non-#VDom frameworks.

  22. @westbrook @davatron5000 @stubbornella I suspect this might overlap with existing #HtmlModules work.

    Also one more idea similar to 1.:

    5. Could we use this format to do the initial render of a component? By which I mean that #Angular compiles components to #JavaScript which looks like:

    ```
    function renderComponent() {
    if (initialRender) {
    createComponentDom();
    } else {
    updateExistingDom();
    }
    }
    ```

    This always bugged me as inefficient, because the first branch is only ever executed once per component instance. If we compiled components to this SFC format, could we just do the first render at compile time, generate the HTML directly and drop that `createComponentDom` function?

    I'm not knowledgeable enough to say that definitely makes sense, but I think it's an interesting idea at least.

    Not sure if other frameworks could benefit from similar optimizations, I suspect #React would not, but I'm less clear on non-#VDom frameworks.