throwaway38375

Well done to your daughter! She is clearly a smart one. I wish her the very best for her future career (possibly) in computers. :)

Looks like the average connection is somewhere between 10 and 30 Mbps?

Seems enough for browsing the internet, online banking, emails, some social media, and watching videos in standard definition.

That sounds like enough for the average person. :)

Because you can set up a rudimentary queueing system in MySQL/PostgreSQL very quickly these days. And it scales really well for small to medium sized applications!

I maintain a web application with a few hundred daily users and with the following table I have never had any problems:

CREATE TABLE `jobs` ( `id` BIGINT NOT NULL AUTO_INCREMENT, `queue` VARCHAR NOT NULL, `payload` JSON NOT NULL, `created_at` DATETIME NOT NULL, PRIMARY KEY `id`, INDEX `queue` );

Using MySQL's LOCK and UNLOCK I can ensure the same job doesn't get picked up twice.

All in all, it's a very simple solution. And simple is better!

Worked at a place where the lead engineer was adamant a graph database was the solution. After two years of trying to get it launched, the project failed spectacularly.

Another team got given the rewrite and build it in six months using MySQL.

I love SQLite, so please don't think that I'm a SQLite hater, but:

I've never seen SQLite used in a setup which multiple machines connect to the same database over a network.

For example: A web application with a web server, a worker/job server, and a database server.

In these instances MySQL or PostgreSQL seem to be much better choices.

So will SQLite ever be able to "take over" in these scenarios?

Neat! This is exactly what I'm planning to do one day.

How did you find the development experience? Anything that you would change or do differently?

Also, how does Kaboom/Kaplay hold up under load with lots of sprites? I've hit a few performance problems with my game when rending lots of sprites...

Yes! Windows got it right IMO.

Ah, I see. Thank you for explaining. This is much clearer.

Good point.

I should clarify that I see the value of encryption at rest for something like an employee laptop, which could be left at a bar (while powered off) by accident.

I just don't get the value of it for always online servers.

This might sound like a stupid question, but I'll ask anyway:

What benefit does encryption at rest solve for something which is never intended to actually rest?

For example, a MySQL database powering a web application is expected to be alive and responding to requests 24/7. It's never really intended to be at rest.

So what benefit does encryption at rest bring? Won't a hacker be attempting to take data when it's online (and therefore not resting)?

but one thing that dissuades me from getting into it is the whole monstrous npm system of components around it.

You are not alone. It is very complicated, but a lot of people seem to get off on the complexity (for some unknown reason).

Is it not possible to just like include react through CDN with `link` or `script` tags and still make good use of it?

Not with React (as far as I know). But with Vue you can use it straight off a CDN.

Follow this guide through. It take about 15 minutes but it is entirely worth it!

https://v2.vuejs.org/v2/guide/#Getting-Started

More specifically, I want to know what can I hope to achieve if I migrate from jquery to react?

You can build SPAs (which although not impossible to do in jQuery, is a lot harder). You can also be part of "The React Gang" and get more jobs.

And to begin with, is this a good idea even?

Not if jQuery is still working for you. If it ain't broke, don't fix it! :)

I don't think you can swap bits out. When I used it things seemed baked in. Yes, mainly suited to 2D side or top down view games.

Backend:

Stick with the LAMP/LEMP stack. It's not perfect, but if you're moving from WordPress (which uses the LAMP/LEMP stack) then sticking with it will make the move less painful.

In terms of a framework. Laravel is a good idea for RAD, although Symfony is a fine choice too!

---

Frontend:

Assuming is has to be a SPA: Use whatever you know best. React, Vue, or Angular are fine. Laravel seems to prefer Vue slighty?

If you can get away with SSR: Use a templating system. Assuming you're using PHP, you could use Blade (for Laravel) or Twig (for Symfony).

---

In terms of hosting and deploying, use one big VM for as long as possible. It's not better, but it's simpler... and I'd say you've got a lot on your plate!

---

But to answer your original question:

If you stick with LAMP/LEMP and a framework, there is so much documentation (and so many guides) that you will be able to figure out what to do. :)

Very excited about this, I have the best memories of using Kaboom.

Yes!

Take a Raspberry Pi Zero and connect it to these:

https://www.amazon.co.uk/Battery-Holder-150mm-Wires-Leads/dp...

https://www.amazon.co.uk/voltage-converter-Raspberry-batteri...

Allows you to run a Raspberry Pi Zero from 8 AA batteries!

I can't remember where I'm getting this figure from, but I think it accommodates for about 3 days of runtime (obviously dependant on what you're doing with your Pi!).

You could try using https://infinitemac.org/ to emulate MacOS in browser.

Then drag and drop one of these into it:

https://www.macintoshrepository.org/5953-star-wars-pit-droid...

https://www.macintoshrepository.org/4962-star-wars-droidwork...

You might need to use StuffIt to uncompress the SIT files. But when booting Infinite Mac there's an option to include common applications, of which StuffIt is one.

As many others have said, I think HTMX was around many years ago, just in different forms.

There were many jQuery plugins that did most of what HTMX did. But maybe it has risen in popularity recently because of JavaScript fatigue?

Unrelated, but my preference when working with JavaScript:

1. None

2. jQuery

3. Alpine

4. Vue

As you can see, I have JavaScript fatigue, and prefer the lighter touch frameworks.

Happy to help dude. Enjoy! :)

Something useful, submitted with good intentions, will be received well, regardless of when you submit it.

This one?

https://www.macintoshrepository.org/64891-aliens

A couple more noteworthy examples:

https://metro.co.uk/2024/05/14/big-cat-hunters-have-proof-ru...

https://www.theguardian.com/world/2024/feb/22/it-was-a-big-c...

My apologies for the abysmal UK news websites!

This is one of the most likely theories IMHO.

A lot of sightings started at the end of the 70s, which would align with the introduction of this law:

https://en.wikipedia.org/wiki/Dangerous_Wild_Animals_Act_197...

Rumour has it that lots of wealthy people simply released their "pets" into the wild rather than confirming with the laws!

Fairly certain there were documented cases of servants confirming this too.

It would appear this is not the first bit of evidence suggesting that Alien Big Cats (ABCs) are a real thing.

https://en.wikipedia.org/wiki/British_big_cats#Proven_captur...

I should add, the "Alien" in ABC denotes alien to the country they were found in. Not alien to planet Earth! :)

LAMP (or LEMP) stack, hosted on a single VM (probably Digital Ocean).

You probably want to use a framework of sorts. Laravel or Symfony are good. Not mandatory though.

Server side rendering to start off with. Bulma for CSS. Alpine for JS.

Throw in some cronjobs for scheduled stuff.

Maybe a bit of Redis for sessions and caching.

Agreed! I find XFCE to strike the best balance between simplicity, performance, and features.

You have the same person causing two different problems.

1. With regards to the CTO, treat them like an employee. Prove that their performance as an employee is not good enough, and fire them. They now have no reason to interact with the company on a day to day basis.

2. As a 5% owner, treat them like a shareholder. Put together a reasonable offer to buy them out, and do so. If they don't want to sell then that's fine, you'll only have to interact with them during shareholders meetings.

The first action will solve a lot of your problems. The second action can happen later on when you've got the money to do so.

LAMP (or LEMP) stack.

Throw in a PHP framework (probably Laravel for rapid development) and use server side rendering.

Maybe add in Redis for caching too.

All hosted on a single Digital Ocean droplet.

It's all relative. When you're in your thirties, you'll panic on hitting forty.

None of it matters really. Would you rather be 25 and unhappy or 35 and happy?

Your answer may shock you! ;)

And PHP 8.1 is a really nice language to use for web development too.

It's got enums, typed properties, named arguments, union types, and the splat operator to name but a few.

Plus between Laravel and Symfony, you've got some good frameworks too!

Yes, I'm a PHP fanboy. :)