lexx

He was talking to me

The flags in Live Updates are wrong

Firefox is great. Just use it and tell your friends to use it. Problem solved

Fast mail is awesome. And fast.

HoMM3 is a magical game. And the music, especially in HoMM4. It's one of my favorite soundtracks ever. I can instantly go back 20 years and feel the warmth in my heart, playing this game countless hours as a teenager.

The best thing that happened to the business the last 20 years was the end of flash. I am not sure why is this even a discussion.

I honestly wonder, for a team that is unfamiliar with both psql JSONB and mongodb, which of those two would be easier to learn? And later on, which of those two would make the team more productive? I think this is the most important.

To be fair, I use mongoDB for 8 years now compared to less that 1 year of psql JSONB, so I can't really answer objectively.

I started doing a demo rewrite of my app in Postrgres from Mongodb. The reality is that even though Portgres seems more stable etc, making queries in Mongodb is much easier and fun.

Postgres JSON operators are cryptic and made my head hurt every time I wanted to accomplish something more complex.

To express it differently, if mongo and postgres where identical operationally, I would choose mongo every day. More friendly and fun. But there are so many horror stories that I am still not sure that it is the right choice for a safe production environment.

pretty ugly

I agree with you. I did give a look at Inertiajs just because Laravel was friendly towards it. Looks sweet.

Right now the "glue" I came up with is a silly connection between the server side router and the "Entry" component of Svelte. It works, it's 10 lines of code, it's clean and the website is super fast. But, both Inertia and my solution feel somehow "hackish". Not a proper pattern.

But really, anything to avoid client side routing, state management and auto-magic code splitting.

I think there is another layer to that conversation. Frameworks become bureaucratic and boring because they are developed by large teams for large teams. Most developers are working on small projects and need more fun and less maintaining huge amount of boilerplate code that recreates the browser.

The framework that I feel makes development less ugly is svelte. But still, I really don't like the idea of heavy client side websites. It really makes everything more complicated and the user's device slower.

I love the simplicity of Turbolinks, I love how clean svelte code is and I am trying to figure out the "glue"

As a user, I really miss native apps. The difference in UI responsiveness is huge. Not to mention battery and memory usage.

As a developer I understand why the native app road can become a more expensive solution, especially for startups.

But, I have to express that I am really tired of glitchy super heavy javascript apps, online, mobile and desktop. I would choose old clanky but lightweight UIs everyday.

I really enjoy this kind of articles. The author started with small logical steps that indeed made sense and then he did a crazy leap to nowhere. The final outcome is silly.

In any case, I would like to see a follow up article, taking account of the feedback. That is how design works... iterations

We just charge hosting and a small support fee for the small sites. For startups or companies with bigger needs, we have tailor made contracts.

Imho, support has to be a significant part of a company's or freelancer's income. Otherwise, you have to constantly create new websites to avoid bankruptcy :P

This is only for subscribers...

So many paypal stories like that. Why do people still use it?

If I have to code a serious application with complex schema, ORM is out of the discussion. If I want to kick fast prototype project I would consider it. But in the end I know that I will regret it!!!!

Great article!

Grid for photos as main content, lists for texts...

I have the same problem...

I thought only dinosaurs used something different than utf-8.