I take the opposite approach - bundling is a non-starter for me. But it really depends on what you're building. Bundling can be great for web apps, but for content-driven websites where SEO optimization is key, I prefer the "90s-style" approach and Fullsoak's philosophy.
Also, separate HTTP requests allow for granular caching, and with HTTP/2 the overhead is minimal.
You're doing the opposite of SEO optimization if page speed score is of any value to your SEO (and it's important to Google's SEO ranking, so yeah). I work on a "content-driven website" - actually a few thousand of them - and our clients definitely want their SEO to be top-notch and page speed score factors into that. Any http requests for external resources will bring page speed down, and that can affect SEO. I don't have to worry about caching at all when the pages are scoring perfect 100% on Lighthouse.
Ortholinear is what you are referring to and it is absolutely worth it to learn. Staggered keyboards don’t make sense anymore - the originally reason keys were staggered was because the bars could not physically overlap - and it is far more natural to type only moving each finger along two axis
With the UHK I am already having difficulty typing directly on my MacBook. With the ortholinear this might only make switching back and forth harder. But it is intriguing.
Or easier. I have switched to column stagger pretty quickly after going to ergo keyboards and I don't have trouble typing on my MacBook. I only dread it now :).
Tried this as well but the difficulty is that Postgres is a relational database whereas ElasticSearch stores schema-less documents.
Your record in ES might include data from many different tables, and figuring out what to (efficiently) update when there is a change in Postgres is not a simple task.
For me, a shotgun approach seemed the least likely to break.
Anything that is a dependency in the elastisearch index should trigger a job to export to it. And since it is idempotent it doesn't matter if it accidentally exports two or ten times the same index in a bg job. Just make sure before writing that you do a quick check that you're not overriding a fresher one. So just have a freshness timestamp which is the latest timestamp of any record used in the indexing data.
Furthermore you can do a daily job to just re export a critical part of the index. Doesn't matter if it is or isn't fresh. So let's say you query all records that were modified in the last day, and trigger the export job thatnmaynincludebthat record. Even if it causes duicate work. Idempotency saves you there.
Perhaps include a "last modified" timestamp w/ timezone in tables of interest, PG can update this on a trigger so no app code has to change. Index this field. Then build a view on top of the relevant tables that assembles the document for ES. Include in the view a field which contains the most recent of all the "last modified" dates, and filter the view on that timestamp?
I don't think any KVM supports Bluetooth. You either need to use software like Barrier or get devices that can switch between multiple. The other option is wireless peripherals that use a USB dongle can work fine with KVMs like the ones Logitech sells.
That's the story of my life, unless you speak French you will probably pronounce my name wrong, no matter how many times I repeat it and help people pronounce it, I don't get mad nor think it's rude, it's kind of amusing actually. Once I realize they can't handle it I just tell people to call me by my last name which is very easy to say in English. There are too many interesting things in life to get hung up on a petty detail like a name.
Hey if you write your name out as LAST First (which I see many French people do) then you might not even have to ask people to call you by your first name.
Most of the time (and all of the time with gendered pronouns), you don't use it to address me. You're using it to talk about me. And then, it's really between you two what you call me, isn't it? Of course I would be happier knowing you didn't refer to me in a rude manner, or as something I'm not, but I believe in privacy too, so it's really your business.
Turkey isn't rude, and it's usually understood from context that we don't refer to the bird (the Turkish government also push Türkiye on countries where the native word has no bird connotation). We used to translate all names, and that's understandable because names are often unpronounceable or otherwise violate grammatical rules if you just blindly drop them in a different language. I think it should be fine to use "Turkey" when talking to another English-speaker.
It's a bit more complicated than that. It is also quite rude of you, where you not to not accept that other people write using other letters have have other abilities in terms of what phonemes they can pronounce.
I see a distinction between mapping a name more or less faithfully to the sounds and spelling of a language and coming up with a completely different name. For example Brazil in English is not the same as Brasil but is fairly close and fits the language. Whereas IDK where Germany came from.
I'm not a fan of this modern idea that you should get to dictate how others refer to you. E.g. I don't think it makes sense to refer to China as Middle Country for anyone not from China.
Sometimes, sometimes not. Everybody changed Peking to Beijing when China requested that. But living in Netherland, I shake my head at all the languages insisting on pluralising the name of my country. And that's not even addressing "Dutch".
I'm 100% opposed to telling people how to speak their language. I don't even like telling people who use English as a lingua franca how to use it in a culturally "correct" way.
Normally, I'm outspoken against most "domestic" proposals to change words, since the rationale and implementation are usually very poor.
But as an American, I've decided that Turkiye without the ü is more desirable than Turkey. It resolves an annoyingly ambiguous search term, doesn't change anything about how it's pronounced, reads the exact same way, and it's trivial to switch how I write it. It really is a superior design with a painless transition.
While I agree that static typing provides some of the benefits of unit tests, I think it provides much more than that: compiler-assisted renames, code completion, extra code documentation...
I like solving problems that I encounter, with the assumption that others may have similar issues. When I moved to Bulgaria, I wanted to learn Bulgarian online, but I couldn't find any good resources for it (since it's a relatively niche language). So, I built my own learning platform [0]. I created an MVP and ran a few Facebook ads, and it was quickly confirmed that many other people were interested in a resource like mine.
Currently, I'm exploring opportunities in the video editing space, based on pain points I experience with existing software.
Also, separate HTTP requests allow for granular caching, and with HTTP/2 the overhead is minimal.