As obvious it's possible to use local Ollama models instead of ChatGPT , it you have large amount of data. But I love using the same approach even for building linking inside internal documentation, I really helps to keep all the changes updated and related.
Small approach to use RAG for better result in similarity for related content. The best thing is the process of getting vectors are don't only once, then you can reuse them indefinitely.
My point is when you have 100 different ways to achieve result - it's always led to inconsistency. And it's very dangerous in large distributed app because resolution of those small differences means you have to support 50+ variation of the same submit button.
Personally I'd prefer to have up to 5-10 option of buttons for all possible cases. And it's not only visual simlicity, and not only easier to support but even help your own customers because they are not have to looking for 100+ different button styles.
I don’t believe the Tailwind approach is a stable, scalable, or reliable solution for large, long-living products.
It works well for fast delivery, prototypes, and teams optimizing for short-term speed, but over time it tends to spread styling decisions across markup, making the system harder to control, reason about, and maintain.
The main issue is games. Drivers and overall performance under Linux for win games run under Wine is pretty low. The good stuff they became runnable but framerate of 12 fps is nothing for my razor laptop with rtx in Cossacs 3.
Now my setup is MacBook for work, and special game laptop Razer Blade especially for games with win11 removed defender/firewall and tons on useless stuff. Personally for me win7 will be enough but I just cannot install it on my laptop due to lack to drivers.
It’s mostly list of markdowns and images in folders.
Everything else generates during deployment on GitHub:actions
It was simpler to show GitHub desktop rather than installing something like Wordpress machinery monster and spent hours to teach how to use it. Now the process is simple:
In this short study, we will analyze the Instagram pages of five world-class musicians - Michael Jackson, Amy Winehouse, Freddie Mercury, Bob Marley, Prince.
Looks like Redis is trying to promote itself as a session data storage. From my perspective:
1. There's no difference between stealing jwt or session_id with al the problems it brings
2. Session in external storage is a solution for small projects like personal blog etc. because you have almost no traffic to handle.
FOr example: 1kk session with an average size 1k = 1kk * 1k = 1Gb in memory storage. Not so big but you will meet all the issues of 10k connections problems when trying to build a service witch can handle this also it will consume at least 100Mb/s bandwidth just for getting/setting data.
3. Server side session a simple place to store all unnecessary/secure data and also can grow exponentially. I saw plenty projects when in one moment session data was grown over 1Mb. So the limits of JWT is a huge plus
4. JWT is easily scalable solution. It works great with 1k session and with 1kk - 100kk - 1000kk sessions.
5. Migration. Because of limitation of server side session - plenty projects started with DB as session store just because they already have DB. It's way of pain of migration from DB to external storage memcache/redis then to JWT.
From my point I don't see any reason to keep using server session instead of JWT.
WHAT! It's $750 bard based on upgraded raspberry pi ? For the whole controllers I don't want to pay more than $200& Otherwise it's better to purchase a mac mini and use in as rack mount.
Nope, this doesn't work at all. Early prototypes starts in 2028. Charging requires 1000A and 15kV. It's only marketing bullshit which doesn't' have any ground in reality.