manuhabitela's comments

I used big blue button and jitsi a lot in the past and this is a really good contender. Using Meet basically every day at work and it's really great. And the project gets new useful features regularly.

(I'm obviously a tiny bit biased since a made a few commits to the project a while ago, but pinky promise, you should try it!)

I'm impressed how pleasant and easy to read this pretty technical explanation was. Good job on the writing.

I agree that Laravel models rub the wrong way, but that shouldn't instantly remove Laravel from the equation when thinking about what tools to use for building a website.

Laravel is great for shipping things fast. Sometimes, that's what you want, even if that means a less maintainable app in the long run. Because sometimes there is no long run; you know it will just be an app made by you only as a rather one shot thing.

Same goes for wordpress. Lots of devs like to shit on it by default. But its like people shitting on PHP because of the PHP 5 days. You'd be surprised how quickly you can build really complex content websites with Wordpress. Way quicker than with barebones laravel or symfony. And with not that ugly code ;)

vscode is noticeably slow compared to sublime text or zed, even without any extension. You instantly notice it when switching files or typing things that trigger auto-completions.

In the end the feeling is drastically different. It weirdly makes for a more peaceful experience to have such a snappy editor.

vscode wins thanks to all its extensions, where basically every language is supported and most features you can think of are there. But it's kinda like modern react. You know better alternatives exist, like solid or svelte, but the community is so big, it stays the easier choice in the end.

Yeah, nowadays the trackpoint is just a bad pointing device. As laptops get slimmer, trackpoints get less precise and less usable. And they hurt our wrists.

We just have to let go. A haptic trackpad is miles better now.

haha, so, all of this for… nothing in the end?

Used this in the past and it's my favorite tool to make presentations now. It's really the most dev friendly tool I managed to try, and I guess I tried a few.

The most interesting thing for me is that you can write your own Vue components for your most specific use cases. Makes it easy to write some rather interactive slides. And it saves you from having to learn some presentation-specific software, some motion design or video making tool. Just quickly code your way through everything.

Quite refreshing to build slides that way.

Great job :)

cool stuff :)

I got some warnings like "this is not a best practice and I don't like bad practices". Like hey, who are you to judge me like that? I'm offended.

> There is no secret incentive to make Sentry hard to operate

It's frustrating when half the comments on a company that dares to open their product is always about how they are obviously intentionally very evil to not do it perfectly/for totally free/with 0 friction/etc.

How entitled have we become lol?

It's not only considered, it's a an actual goal to be 100% usable by everyone. It's already the case for some of La Suite projects. Not quite there yet right now for some others, but it will be.

And I agree, lots of popular, proprietary solutions should do better in terms of accessibility. I believe open-source helps in that regard, as in many others.

Here in La Suite we have some wcag-geeks in the team and regularly include some of our users with disabilities for feedback.

All the projects are already open sourced actually, but admittedly all don't have documentation as good as docs or meet. Still a wip :)

I'd say the Chrome devtools are a tiny bit better, usually with more features or a bit better UX. But there are also things where I find Firefox devtools better. And the features missing are not a deal breaker for me.

Overall it's a pretty similar experience. Most difficult part is the habit changing of getting used to a different UI.

Great to see such a tool not tied to a hosting formula, page views and everything.

I see the value in helping me (the dev) quickly setting up landing pages and including them in my existing website that I host where I want.

Super useful, great job.

Kinda harsh to see it that way. You could remove the last four 4 sentences of the post and don't see it as an ad at all. The post does actually explain the most important part and the guy just tells us we can hire him if we need help.

- compare the tailwind example and yours, they don't have the same behavior. The tailwind one has a specific mobile menu for example. And that is just one example.

- sure, but since the tailwind page does more things, it's logical it has more code. Your base for comparison is production used code, sold to people. So of course it's polished, it must handle browser bugs and other things you might not expect in a quickly implemented alternative for a tech article. So I'm not surprised the code is bigger. That doesn't say at all that tailwind == more HTML tags :)

it's just CSS yes, with the focus on naming your classes depending on the content you style instead of their looks. "article-excerpt" instead of "bg-white padding-2 shadow rounded".

The article is interesting but really feels unfair sometimes, it doesn't help:

- The whole "amount of CSS" part is unfair when the Semantic CSS implementation isn't responsive at all, so of course it will be lighter, it does less.

- The part about the big number of HTML elements is a bit frustrating too; tailwind doesn't require you to use more HTML tags at all. It's totally possible to redo the Semantic CSS example with tailwind by not adding any HTML tags.

Besides that, it's still interesting to try and compare what is the best between big HTML (atomic, tailwind) vs big CSS (semantic).

Tailwind is not perfect, and sure, sometimes, you can get more performant code by writing it the semantic way. Sometimes.

But tailwind sure is a great way to easily write maintainable CSS in a team with different skill sets, producing really performant code by default, on large web apps.

I wonder how these "visual story telling" articles are created, they are really great.

Like, what tools do the authors have. Are the content authors super tech savvy or not. How much specific code must be created for each article. How long does everything take compared to a normal, mostly-text page. How many people work on one article. etc. Must be pretty interesting.