Edgars Snepsts

Been working on visual website builder side idea, a big milestone has been to achieve buttery smooth drag and drop hover experience, which even big name builders like webflow or framer can't seem to able to make happen.

when your every line proceeds by "ts-ignore", that is how you know you are doing @typescript right

Anyone who is in Rome wants to do builders/indiechakeers weekly meetup?

Vibe coded this small Flutter and C++ app for Windows to help me learn Portuguese while playing Witcher 3 and not feeling bad about wasting time. Now I can easily spend 30-40 hours a week studying languages 😉

Is this form of mental illness I'm experiencing because of too many years of web dev, but writing Vue "h()" render functions starts to seem a more reasonable way to build components than Vue templates.

Does anybody have advice on how to handle translations in web apps? I need something that integrates with LLM but also with an option for the translator to double-check or fix it if needed. Currently, I have React, Vue apps with 12 languages. Whenever I have a new key to add, I LLM translate to all 12 languages manually as a default. But I also mark the key as dirty, meaning it was LLM translated, for later check with a proper translator. I don't want to go to a dedicated translator for every single so I only do that when I have enough batch work for them. The process I do is laborious and repetitive, and takes a lot of my time. It surely could be automated easily with a tool. A good feature would be to be able to give the ability to add translations in the context of the app itself, not just spreadsheet/list.

I'm working on an idea to handle CSS styles differently in web apps. It starts just like any other JS-in-CSS library, except you never leave an inline declaration logic; you can only declare "font-size" or any other property once. If you need any changes because of hover or media state, you create a declaration as an array that will always resolve from left to right. In an array declaration syntax, you can target states like media query match, hover state, and certain element attributes. And you don't have to worry about setting up or destroying watchers for these various changes; it is handled by the library. The idea is to treat every property value as a distinct, separate state machine, where it is easy to tell what is going to be a particular element's particular CSS property value just by looking at HTML . The screenshot below is from the solid.js implementation, where you can also use signals eg.,("boxShadow", "enableBgGreen")

@jackfriks 🔥🔥🔥🔥🔥

keeeeeeeeeeeep goingggggggggggg

Slowly getting there:

If I want to know what is going to be the font-size of particular HTML element, why do I have to go around various style sheets and fish around for font-size declarations? Also this may not be the final truth because different types of screens may have different media queries enabled? When the developer was working on this particular piece of UI, he had right information and knowledge about it, now I have to gather it again from various places to do my changes and have that information thrown away and next time around when somebody wants to do the adjustments they will have to gather the information again. Cascading style sheets makes no sense in modern web development.

I start to think that the best reusable way for CSS is only inline with the HTML, also for pseudo-states and media. If it is an FE framework, let it live inside the framework nodes; don't bundle out CSS. Every time I bundle CSS out as a separate style tag, it becomes such a pain in the ass. Now I have to think and manage to separate the entities at runtime, the bundled CSS styles, and the FE framework rendered nodes. The problem starts to become obvious when you want to do something besides the regular path, like rendering components inside the shadow dom, using them in a Chrome extension, Electron, or webview in mobile apps. At that point, everything becomes non-reusable, as it just has this crazy assumption that CSS needs to be stripped out of the components and bundled together somewhere as its own entity. Some libraries want you to style the component with Tailwind classes, and now you have to manage which Tailwind bundling will take place, whether it's version 3 or 4. If it is version 4, you may have another library or components that may have Tailwind 3, so you have to make sure the Tailwind 3 bundling is done for whoever expects version 3 bundling. If you are using PrimeVue components, it will bundle all the styles for you and append them to the document's head, and you don't even have control over it from your bundler config, but what if you want to use the components inside the shadow DOM and not leak them to the main document? Nothing is freaking reusable anymore.

FlentFeed running on my android e-ink tablet, I needed some thing I can use before going to bed that is not emitting blue light

Me trying to get users for my Chrome extension

I bought this android e-ink tablet, so I can browse X and not expose my eyes to blue light before bed. It’s like kindle but android based and you can install any android apps on it.

I have tried every web/product analytics tool on the market, and Matamo is still the best one when you really want to see every user and how far they get along your goal channel. It just makes inspecting every individual session along the route you want them to take so easy

After failing miserably at getting organic social hype for my Chrome extension, I'm trying a paid traffic route. I'm spending $10 a day on Twitter and Reddit to see if there is a market. But feels like a daily waste of money, but there seems to be some traffic coming in. However, I've yet to get even one free user who uses the extension. Not sure when the right time is to stop trying and just accept that nobody wants it

@gusevmeatrider With time, more language will be added.

@edgars_xx what about russian

Want to learn a new language while browsing X? You can become fluent in French, Spanish, Italian, or Portuguese just by scrolling on X 🤯 Check out FluentFeed, link in bio.