riogordo2go

I remember not using/trying Svelte because there was no TS support and it took quite some time before TS support emerged. With that in mind it doesn't surprise me they are not doubling down on TypeScript.

I'm looking long and hard to see if Next.js is still a good fit with this new direction. The VC's want their money and the push to host will Vercel is getting louder with every new version.

At least in prior Google Analytics versions, a third party cookie was used, giving the possibility to link you to every site that implements Google Analytics. But Google explicitly states not to do this, so you are correct in calling me out here.

Because I think most people who use something like ublock don't want to see ads or have their privacy violated by being followed around the web using third party trackers.

A site owner observing some general, anonymized stats like visitor and page count, which outbound links are clicked, os, screen size, time on page and what have you is quite different. I understand a blocker must go all the way and cannot distinguish between these cases. Hence my effort to find an alternative.

That used to work but current block filters analyse js variables and url parameters and are much harder to circumvent.

I'm using the matomo self hosted version and like it overall. I love you can track all outbound clicks without having to specifically add Dom elements to outbound links to make this possible. Unfortunately matomo is blocked just like Google Analytics by every ad/tracking blocker. Doesn't matter if you host it yourself and only track global stats vs tracking users across the web like GA does. The only solution seems to be writing your own analytics.

>"Server Actions in Next.js have been designed for deep integration with the rest of the data lifecycle, including the Next.js Cache, Incremental Static Regeneration (ISR), and the client router."

I'm personally going the other way, moving as much logic as possible out of Next.js. I want to keep my frontend clean, simple and separated from the backend as much as possible as this is clearly where must of the churn happens.

It's not fake, it's a perspective. I'm not sure if "web3" is going to solve it though. The incentives are the same, so why would the outcome be different this time.

This is also my concern. If the happy path is Serverless/Edge (on Vercel) with React Server Components I'm in for a big rewrite. I'm holding off any new investments in the Next.js ecosystem until the dust settles or a more community focused and stable alternative arises.

Big Termux fan. From using my phone as a borg backup target (with Wireguard) to ssh access to remote servers, it gives you a full blown Linux environment in your pocket.

Not only expensive, the coverage is spotty too. Driving cross country, even along major highways often results in many dead spots.

Good luck with the interview!

Maybe the new generation of developers are afraid of light Sysadmin tasks like setting up nginx, PostgreSQL, Redis, iptables. And Vercel welcomes them with open arms with the promise of easy deployments and infinite scalability. In reality you probably don't need fancy edge functions and deploying isn't that hard with today's tooling.

I find it somewhat annoying to see the intense community pressure to go with third party auth providers. I see auth, user and role/permission management as a core pilar of an online business and would think long and hard before handing this over. I realize doing this yourself requires a big investment in studying proven security practices and finding well established libraries, but I think it's well worth it.

   "I don't recommend having components responsible for querying data because their responsibility is already in presenting the data. More accurately, components need only receive data from view models, format it, and output it to the screen. Instead, I advise you to follow either of the three following ways:

  Render the data on the server and pass it to components as a view model, as shown in this guide.
  Use a state management library that supports dispatching actions (e.g. Redux or MobX), deriving view models from the state, and passing them to components as properties."

This is opposite to what Next.js new React Server Components stuff is advocating for in the new app/ dir structure. It expects every component to fetch the required data, and just cache any duplicate calls. It's probably good for a Serverless / Edge deployment but I much rather use a MobX store that takes care of state, fetching and mutations.

It depends on the capabilities of the low code tool and the problem domain. Just today I created a "flow" in the Android app Automate to add "auto-sleep after 30 minutes" functionality to YouTube every time I toggle pause/play after 11pm. Dead simple with a very easy to understand ui control flow. I could have written an Android app/service to tap into the various APIs and accomplish the same, but for this use case this low code solution was clearly superior. I could see a lot of software development being replaced with low code tools.

Maybe trades will get popular again as this is less easy to swap with an ai alternative.

It's a bit of work but allows for fine grained retry logic. Some jobs should not be retried but escalated, others might need a retry in one hour, others can be retried at a lower priority. I prefer a flatter stack and total control over the queue. That being said, I have RabbitMQ running in a production project that I haven't touched in years, it's rock solid and I'm pretty sure these guys had it misconfigured.

I think the 'select for update' query is used by a worker to fetch jobs ready for pickup, then update the status to something like 'processing' and the lock is released. The article doesn't mention holding the lock for the entire duration of the job.

"Some of our customers are experiencing elevated error rates" while in reality the entire service is down.

Funny thing: I asked ChatGPT last week to write me a script to fetch the latest HN posts and notify me on Telegram when a post matches a given keyword. Keeps me updated without wading through the ChatGPT posts.