SpacemanSpiff

The only thing I really dislike about Honda styling right now is the “underbite” look they have on the front. The previous gen had the opposite, almost a pig nosed look. Why can’t they just do normal front designs?

I love the rear this generation and how they toned the entire look down, but they can’t figure out front grills to save their life it seems.

I think the point is that it’s possible, in theory, maybe depending on your employer. But you get close to that amount of vacation time in total. The majority of Americans don’t get more than two weeks for the entire year, and many get none at all, only sick time. Many Americans can’t even take just two consecutive weeks off any time of the year.

These are all weak takes imo.

The designer of much of Hyundai’s current lineup is Luc Donckerwolke, who is famous for his Lamborghini (Diablo, Gallardo and Murcielago) and Audi designs. You may not like them but they’re not “design by committee” derivatives.

Almost no manufactures are heavily developing their ICE engines anymore, nor do all even produce their own engines (Hyundai/Kia do).

Much of the “airflow” “issues” you’re talking about are simply price point. The two most impactful areas for sound insulation on cars are undercarriage and wheel wells and door/window frames and seals. For the former, nothing about it is high-tech. Even luxury makes user sound-absorbing materials including plastic deflectors, fabrics, and lightweight low-density filler materials behind panels such as polystyrene. How much sound proofing you get is a reflection of Hyundai’s entry level lineup. You’re not going to get Mercedes-level sound insulation at half the price just because the design looks high-end. It’s not until you’re near the top of luxury car lineups or Rolls/Bentley territory that this area becomes innovative.

P.S. Hyundai/Kia also hold patents for 2-stroke supercharged engine designs as well as variable compression designs.

You’re thinking of the Space Force.

SPACECOM is a unified command that has its origins in the 1980s. It is entirely necessary and handles real things including military satellites and missile defense.

I use Kagi too, it’s surprisingly snappy! Like seriously impressive for a small org. They talk about speed optimisation being critical for them as well. I find the result to be excellent as well. A true Google replacement/feels like Google in its prime.

I believe they have their own index and bot as well?

Yes….on a technical level. But the picture is bigger than that. Personally, I have a hunch that the choice of Rust is making Lemmy’s development slower. This seemed to be evidenced by the fact that Kbin has more functionality than Lemmy while having only been around for 2 months. Vs Lemmy’s 4 years. The Kbin dev has also been much more able to fix things on the fly during the surge in users. Whereas Lemmy will supposedly move off websocket use any day now.

Adoptability isn’t something to be discounted. The fact that there any more people out there familiar with PHP may give Kbin an edge over time. And let’s be honest, in real-world test PHP can very often be faster then - less-than-mature-Rust codebase.

Really? Kbin as the name is what intrigued me initially over Lemmy. It’s actually inspired by Linux, the sbin directory to be specific.

Kind of like how Lemmy made up communities? Lol you don’t call microblogs “toots” either. Seems every fediverse software has their own terminology.

Also it’s dev, singular. Kbin has been put together by only one dev. I personally find that damn impressive considering it’s functionally on par with Lemmy being only 2 months old to Lemmy’s 4 years.

They do have their own crawler and I believe supplement from bing only when necessary. Something like 96% of results are from their own index. They actually have a breakdown for every search.

Currently using Orion on iOS. It’s made by the same people behind the Kagi search engine (which I also use now).

It’s still in alpha, so I occasionally encounter a bug, but the fact that it has built-in advert and tracking protection, as well as cool tab-suspend features sold me.

It tends to be on a newer version of WebKit then then Safari as well.

Oh, and did I mention it can use both Chrome and Firefox extensions?

I think Google peaked about 6-8 years ago now and then started slipping at an ever accelerating rate.

It’s almost useless for me when searching anything remotely technical or otherwise niche.

I almost consistently need to go to the second page of results now, something I don’t remember doing since like 2009.

I find Bing acceptable. Brave search works well. But I’m actually using Kagi now since I’m hoping their paid model will actually mean I’m not the product.

Via the ActivityPub protocol that fediverse software uses :)

Pretty cool stuff!

Kbin can also directly interact with Mastodon users and toots because of this. Kbin magazines can natively contain both “threads” from Kbin and Lemmy, and microblog “posts” from Kbin and Mastodon. (And other software depending how they map these features.)

You bet! The fediverse is definitely a confusing concept to wrap your head around the first time. And it doesn’t help that different software server instances don’t need to use a site name that specifies which software they are (like Beehaw, for example).

I think the “dynamic updates” behaviour is tied to Lemmy’s use of websockets instead of http. Kbin uses http. The Lemmy devs have stated they’re going to move off of websockets in the future as they present scaling issues with the way the software is written.

The websocket protocol allows bi-directional push communication regardless of the previous request which means that new posts are constantly triggering server side updates which then appear like a page “refresh” on clients.

Arguably, while websockets have very cool realtime features compared to http, for a Reddit-like content aggregate their use can quickly overwhelm usability without significant retooling.

It depends on what you mean by other servers…Lemmy instances? I haven’t seen any differences between kbin instances.

Kbin is entirely different software from Lemmy; it’s a completely different backend.

So that would be why it’s “better” in that regard than Lemmy instances. My understanding is that it’s a bug in Lemmy that will be fixed soon.

The “popping” of the feed in Lemmy is tied to their use of websockets instead of http. I believe the devs stated they’ll be moving off of websockets in the future.

That might be true, I’m not a mechanical engineer but despite that, my understanding is that within the engine block itself, cylinders are primarily lubricated via the system holding pressure. This pressure starts to drop the second the engine ceases.

You can notice the effect on cars that have realtime oil temp monitors. Mine does, and it’s digital. My stable oil temp is around 216 degrees Fahrenheit. After a start-stop cycle, even for only 5-10 seconds or so, the temp drops about 5-8 degrees. After a minute, the temp is down 25 degrees. That’s significant. Essentially the engine is no longer “at temp” for the first 30 seconds or so after it resumes. That’s 30 seconds of additional semi-cold, under pressure wear each cycle.

What about the fact that the oil drains to the pan in those few seconds that the engine is stopped?

This is my real concern. Sure you can upgrade starter motors and batteries to handle the extra cycles, but you can’t do anything about increased scoring and wear on cylinders in the milliseconds before the fluids start to circulate again.