#dev 2026-09-03

2026-09-03 UTC
cotsuka, TwinAdam, jtojnar, lavandula, morganwebdev, grufwub and rMdes-bnc joined the channel
#
yanglake__ tameshitake[d] C++ and DearImgui
#
yanglake__ great learning experience so far
#
tameshitake holy based
#
tameshitake maybe i should learn C++ too, but... I'm kind of on my gamedev spree rn
#
tameshitake how was it though?
#
tameshitake i mean... why is it great?
#
yanglake__ getting the ick from react after realizing they throw in AGENTS.md into their inits now
#
yanglake__ noticed it after building a new project
#
yanglake__ tameshitake[d]: it's layout based, so alot of web UI design philosophy still sticks
#
yanglake__ despite being a game GUI library
#
yanglake__ it works really decent for building a standalone app
#
yanglake__ im following Hans De Ruiter's tutorials for binding Raylib and Dearimgui
#
yanglake__ tho looking back that mightve been a weird choice since SFML is right there in their docs
#
yanglake__ im also using sqlite tho might opt for document based storage, maybe CouchDB for refactoring
#
yanglake__ [edit] im also using sqlite tho might opt for document based storage, maybe CouchDB whenever i start refactoring
#
yanglake__ god its so great to work on C++ after an eternity of web development
#
yanglake__ (corporate)
#
tameshitake yeah, i moved to python w/ Qt instead though, it's relieving
#
tameshitake i swear i feel like there's osmething about web development that's just...
#
IWDiscord <t​ameshitake>
#
tameshitake idk
#
tameshitake wrong?
rMdes-bnc joined the channel
#
yanglake__ id say redundant
#
tameshitake also, i feel like everyone who tried to make GUI in C/C++ always end up meeting raylib and dearImGui somehow
#
tameshitake but ifi t works, it works
#
yanglake__ the greats
#
yanglake__ truly deserving its stay in that field
#
tameshitake mhmmm
#
tameshitake my paradise and always will be
#
tameshitake why did you choose C++ tho?
#
yanglake__ couldve used C, since they're both C libs
#
yanglake__ ive actually been (still am) doing competitive programming in C++ for a while
#
yanglake__ but i never got to use it for anything more
#
yanglake__ and since desktop applications came to mind, i thought of Electron/React at first
#
yanglake__ Notion and Obsidian are Electron apps
#
yanglake__ [edit] Notion and Obsidian have Electron apps
#
yanglake__ but Im still annoyed at Notion desktop's performance
#
yanglake__ so lets take a step further down
#
yanglake__ also Notion is on some weird shit rn
#
yanglake__ an update every 2 days
#
yanglake__ wdym you're on version 7.35.67
#
tameshitake yanglake__[d]: huh, i feell ike competitive programming especially in a low level language feels pretty scary
#
tameshitake yanglake__[d]: anything that's webapp will lag bad on my laptop
#
tameshitake and with the constant update notion has, yeah i can imagine it will annoy me more than arch updates
#
[snarfed] web-specific dev talk here is great, but for other dev/tech stuff, maybe #indieweb-random?
#
yanglake__ ahh ok
#
yanglake__ thanks for the not
#
yanglake__ *note
#
rnkn [snarfed]: the policing of conversation is a bit uncool
#
rnkn if it's not interrupting other conversation it's fine
#
[snarfed] we like to encourage people to stay on topic because consistent off-topic conversation gradually turns off people who are here for indieweb specifically
#
[snarfed] sorry if it feels bad! it's a pretty standard bit of moderation
#
tameshitake it's alright, i'll keep that in mind
cotsuka joined the channel
#
[artlung] Background on the space you find yourself in, and the guidelines you and all of us co-participants try to keep to is here: https://indieweb.org/discuss …. Thanks for being open to learning about the community
lavandula_, cotsuka, lavandula and [burgeonlab] joined the channel
#
[burgeonlab] theboeh: I just saw your message on a views counter, it's a bit late, but maybe something like this? https://88x31.lol/
lavandula and lavandula_ joined the channel
#
burgeonlab <theboeh> (ping with correct syntax for discord bridge)
lavandula, GuestZero, Maxpm, Guest853, Pixi`, lavandula_, bterry, cotsuka, wturrell and barnaby joined the channel
#
[capjamesg] TIL about image type=input: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/image
#
[capjamesg] Oops, I mean input type=image.
#
[capjamesg] [artlung] A fun potential topic for FrESH ^^
rMdes joined the channel
#
tameshitake oh man this is insanely convenient
ZodiacalComet joined the channel
#
yanglake__ wait when did this exist
#
yanglake__ no way
#
yanglake__ i had to fidget with file inputs for a while 2 weeks ago
#
yanglake__ oh wait i misread
#
yanglake__ its a button
#
[capjamesg] Yeah. It’s quite an odd name.
[0x3b0b], cotsuka, [Zephyr]1, [Murray]1, lavandula_ and lavandula joined the channel
#
[Murray] I'm not sure I understand the benefits over `<button><img/></button>`?
lavandula_, kal_jan, lavandula, cotsuka, barnaby and wturrell joined the channel
#
wturrell semantically - just double checking - is it still considered better to use <article> over <section> for "content" pages, even where they're not specifically blogs, news items etc. and don't, for example, have timestamps, or an RSS entry?
#
wturrell and also these days, is there a "better" HTML validator, other than W3C? (I occasionally use Lighthouse as well for performance stuff)
lavandula joined the channel
#
lesleylai Can you be a bit more specific? If it's at page-level, you can use <main>
#
wturrell mmm - I did wonder about <main>… maybe main for lists of other content (e.g. blog post excerpts) and stuff that isn't really standalone enough to be considered an <article>
lavandula, cotsuka and ax562 joined the channel
#
[mikemai2awesom] <main> for main content, which may contain <section> and <article>
cotsuka joined the channel
#
[mikemai2awesom] the difference between <section> and <article> is that <section> is a landmark. give a <section> an accessible name and it will show up in the list of landmarks when using a screen reader. <article> is not a landmark and will not show up even if you give it an accessible name (however, currently there's a chrome + mac voiceover bug that articles are showing up as landmarks).
#
[mikemai2awesom] personally, i find neither <section> or <article> that practical. as long as you have proper headings, you may do without them
#
[mikemai2awesom] i do use <article> for blog post because i find that safari reader mode picks up the blog post content properly when i do that. i see no harm in using it for a safari quirk.
#
[mikemai2awesom] this is a deep dive into <section> and <article> if you want to learn more: https://www.smashingmagazine.com/2022/07/article-section-elements-accessibility/
wturrell joined the channel
#
wturrell thanks!
cotsuka joined the channel
#
[Murray] Just to add (I'm sure its in that article from Smashing Mag, but tl;dr) that `<article>` is explicitly for content that can be understand by itself, beyond the context of the rest of the page. So it's useful for things like card grids/summary cards, as well as blog pages, but it isn't super beneficial, as already noted
#
[Murray] But basically, your `<article>`s would typically live *inside* of a `<main>` element, at some level of nesting. They could also wind up in an `<aside>` or `<footer>` or somewhere else, but typically
#
[capjamesg] https://mastodon.social/@firefoxwebdevs/117207290598485866 is cool!
TwinAdam, cotsuka and [herebox] joined the channel
#
[artlung] 1 hour to FrESH. https://events.indieweb.org/2026/09/front-end-study-hall-057-0SMwgItLWoSd
thatoddshade, cotsuka, pimeille, decipaliz, Guest3077, JoshuaMorris and [KevinMarks] joined the channel
#
[tantek] what is a silo?
#
Loqi A silo or web content hosting silo (AKA walled garden), in the context of the IndieWeb, is a centralized web site (like most social media) typically owned by a for-profit corporation that stakes some claim to content contributed to it and restricts access in some way (has walls) https://indieweb.org/silo
barnaby, wturrell, [Tabitha], cotsuka, [Mike], TwinAdam, ax562, sage_rakurai, ZodiacalComet, Guest4079 and vikanezrimaya joined the channel