greenhatman

I'm at a point now where I'm not even a little interested in new frameworks. I want tried and tested. Preferably something that has been around for 15 years.

I'm absolute putting Linux on my mother's computer when she needs a new one again.

I ran Linux Mint on my 2015 MacBook Pro for a long time.

Maybe in the near future Linux will run well on Apple silicon as well.

Less wrong is created by Eliezer Yudkowsky. Someone who is very outspoken against AI development, because of the fears around AI destroying humanity. Once went as far as calling for the bombing of AI researchers and/or data centers, if I remember correctly.

Paying 3rd parties for gold, items, or xp was a Diablo 2 thing. They specifically designed Diablo 4 to make this hard to impossible.

You can't trade legendary items. They're account bound. And if you're trading lots of gold you get banned.

There is a base alternative, which I'm going to choose, and that's just to use social media less. Not going back to Reddit even if another alternative doesn't pop up.

And their app is so bad compared to the 3rd party ones. I quite liked RIF.

My 11 year account was just banned as well. I don't remember posting anything terrible recently. So not sure what's going on, but I won't be appealing or making a new account or going to the site anymore.

> we have chosen to put the burden for paying for those losses on all of the other banks

But isn't it likely to cause more bank runs if depositors lost money? So in a real sense, many other banks were saved from going under, by assuring depositors that their money is safe, whichever bank they're at.

My understanding is that other banks have massive unrealized losses as well, due to the steep interest rate increases. So they're all kind of vulnerable.

Minesweeper open instantly.

That is still routing. Not load balancing. The load balancing is only between pods of the same service.

Just because Nginx is doing it, doesn't mean it's load balancing. It's an extra function tacked onto a load balancer.

I don't really think of route based "load balancing" as load balancing. That's routing, or a reverse proxy. Not load balancing. Load balancing is a very specific type of reverse proxy.

The point is, if a client makes a request to a server, the response should always be the same, no matter where the load balancer sends the request to. Which means it should run the same code.

Nginx doesn't even mention route based or endpoint based load balancing in their docs. Maybe they don't consider it load balancing either.

https://www.nginx.com/resources/glossary/load-balancing/

You can have more than one server per monolith.

I don't think you actually understand what microservices are. You don't put a load balancer to load balance between different services. A load balancer balances trafic between servers of the same service or monolith.

Microservices mean the servers of different services run different code. A load balancer only works together with servers running the same code.

I want to see the company where the HTML and CSS are handled by separate teams.

For me Tailwind is sort of a shortcut to learning best practices. If I had to research and figure out best practices on my own it would take ages. Instead I can just see what Tailwind does. E.g. when to use em vs px. That kind of stuff.

It's only slightly more work than creating re-usable CSS.

Some people would rather learn every CSS rule than spend 10 minutes reading the Tailwind docs.

What make it difficult to main long term for you?

Hard disagree on that one. You can learn Tailwind in an evening.

This is probably the main thing that puts people in one camp or the other.

Before Tailwind came along I very often found myself just wanting to put some inline styling in various places. It's so much easier to just add some CSS to an element than having to think of a class name, think of where the best place would be to put the class, etc.

Semantically named classes is a lot of effort to come up with, and don't really help much. One of the big selling points is that you can quickly style things without having to name every HTML element.

Being bad at CSS is certainly why I love it. But that doesn't mean it's not a great tool for experienced frontend developers as well.

Fuzzy searching generally doesn't mean exactly the same thing as typo correcting or other full text search features.

It's more like you can search using word parts. Similar to how your IDE's search work when jumping to files. E.g. you can type 'smb' to find 'Super Meat Boy'. Or type something like 'sup mea acc' to find 'Super Meat Boy Accessed Content'

So it requires you to know exactly what you're looking for, but you can find it quickly without having to type a lot.

Generally for full text search like you're describing you need to do that on the server side. It would be too heavy to have something full featured like that on the client side.

I'd love a Spotify/Netflix subscription for books, if it can get me almost every book.

I'm not sure exactly what that means. I think it means AWS can't resell it for free, but you can use it as your production database for a commercial product.

He's going to be right eventually. Now seems like a likely time for him to be right.

It sometimes completes whole functions for me, from which I just have to make minor corrections afterwards. Some of which would have required me to lookup syntax 2 or 3 times. So it saves a lot of time in that way.

I do find it's much better in some languages though. And probably especially with languages you're new in. It doesn't do much for me in PHP, but does a lot in JavaScript.

You know all the times you need to lookup syntax or how to do something on Stack Overflow or some other site? Copilot replaces about 80% of that. Speeds up that process a lot.

There is usually a 1 year cliff. So as long as you stay longer than a year, you're not losing out on any stock options.

Engineering managers aren't necessarily better than you. It's not necessarily the next step up. I personally prefer to stay closer to code.