clementmas

I'm currently self-hosting a planet OpenMapTiles mbtiles file with several styles on top of it. I've been meaning to look into Protomaps closer to see if I could use it to reduce costs. It looks like a very promising project!

I thought :has() was already supported. It's becoming very popular.

I'd also like to see FF support Scroll Driven Animations and View Transitions.

The Stripe API docs are also slow on Firefox for me. Even with a good browser, sites shouldn't use that much JS

Good job! I've been using Flowbite and building on top of it but having Alpine as a base makes it easier.

I'm glad to see more options to render content on the backend using stable backend languages (not Next.js). I've seen too many slow React websites that could have been rendered with simple PHP or else.

I can't find it on my Podcast apps

Do you support displaying comprehensive stats for wildcard subdomains? Do you have an API?

Can we use HTTP3 today? Is it widely supported?

What about for web servers? What's the default nginx version installed?

Is this mostly a US drug? I never heard about it in France. I can't believe people love it so much without thinking about the actual source of their problem.

There's also Tom's World Walk: https://tomsworldwalk.com Currently hiking through Indonesia

I have a bunch of styles based on the OpenMapTiles schema. Is it possible to swap the underlying data with PMtiles?

I've been using PdfSam to split large PDFs locally. I didn't know this could be done locally in a browser. Great work! I'll try it out next time

When using React, Vue, Svelte, etc. for large SPAs, so much of the logic has to be duplicated from the backend to the frontend. That's why it's tempting to ditch PHP and use a JS meta framework to be able to reuse code (types, utils, etc.).

So 10 years ago you wouldn't use jQuery?

People comparing Alpine to React, Vue, Svelte, etc. are missing the point. Not everything has to be a SPA.

There are so many Reacts devs out there that now blogs and landing pages are fully rendered client-side. With a backend only used for its API. Instead of simply sending HTML.

Alpine is great for the simple dropdowns, navigation drawers, etc. The things we used jQuery for before we started to do everything in JS.

I still love writing SPAs but I'll stick to boring HTML with JS sparkled whenever I can.

Seems like very short notice to delete all the data.

I feel like a dinosaur using hexadecimal colors because I'm familiar with them. This article convinced me to give other color formats a try.

I just wish Gmail would let me rename email subjects

Very happy to see this happen and be open-source. I'll probably stick to OpenStreetMap and OpenMapTiles to generate my basemaps but they'll most likely benefit from the "competition".

Isn't it too early to drop Safari 13 support by default?

I would personally keep everything mentioned but leave out the social proof (I do B2C). Instead I prefer to add more screenshots or possibly small videos

I saw the news in this tweet: https://twitter.com/shanselman/status/1595177845093183488. Says it's a big deal but I'm still not sure what the difference is.

I generated my own vector tiles using OpenMapTiles. Planetiler looks very promising too.

I serve the tiles using TileServer GL Light. It works but it requires Node.js v10.

OpenStreetMap is planning to make their own vector tiles style to convert their raster tiles. Looking forward to that! https://github.com/openstreetmap/operations

I scrolled down on mobile and closed the website because I couldn't see any example

Link to the Vue docs: https://vuejs.org/api/built-in-directives.html#v-memo

That kind of performance optimization should be applied automatically. It's a welcomed addition for advanced developers but it should be the machine's job.

I think frameworks like SolidJS or Svelte are one step ahead in that regards. As far as I understand, they can surgically update the DOM without having to re-render the whole component. I wonder if Vue 4 will still use a Virtual DOM.

Is the data shared between vector tiles, geocoding and directions? Or is each feature pulling its data from a different index?

Most users don't care but I very much prefer to have URLs with `/?page=123` instead of `?_next=xxx`. I should get over it but meanwhile I'll stick to offset pagination with deferred join (see aarondf's comment).

From a user perspective that seems like great news. Now I don't have to worry about file extensions. I just keep ePub files in my library.