Anyone else remember the game Messiah? I'm probably wrong, but it still feels to me like that was a much earlier version of "nanite"/dynamic LOD building. No pre-built LODs, but automatically changed the number of polygons on anything based. Didn't work very well, everything in game looked kinda "blobby". But if we're gonna call Nvidia's library an alternative Nanite, I wanna call Nanite a Messiah alternative.
FWIW, the javascript side of Rails is historically the least settled-upon part of the framework. I'm curious how many current Rails projects use React as an alternative over the current "convention" of Turbo. Or Hotwire. Or even UJS for legacy projects.
In our current project it's Stimulus/Turbo on the admin side (maintained by the backend devs), React on the end-user side (maintained by the front-end devs). I haven't met a single front-end dev who prefers the Rails approach. Even after trying to do some light convincing and demoing. They seem to be too committed to the React ecosystem in my experience. I can respect that, too much has been built for it already, and it's generally in high demand.
Plus, Rails story has no clear JSON boundary between back and front, which creates some discomfort (i.e. learning erb) as well. As a backend dev, I'm all-in on Rails in solo projects.
Hard disagree. "More discussions once more opinionated developers join" is universally true regardless of which frameworks/philosophies you start with. The point of convention being more important than configuration is that it reduces those conversations, because you can rely on the conventions as a default.
If an opinionated developer thinks a different configuration is better, then that helps form the conversation immediately. Everyone is already familiar with the convention, so the discussion only needs to inform everyone about the pros/cons of the alternative.
This is my #1 complaint with our new Model Y. The "Auto" setting is completely worthless. It almost never turns on when it's raining. When it does turn on, it's either too fast or too slow. It'll turn on randomly when there's no rain.
But it's not just the sensor, which would be inconvenient. The lack of control makes it *dangerous*. You have to push the button in _slightly_ on the left stalk, which makes the wipers go once. And then you have to push the left scrollwheel left or right (but not up or down!) to turn the setting up or down, while staring at the bottom left part of the screen to figure out what setting you're on. All of this takes your eyes much further away from the road, while driving in more dangerous conditions with reduced visibility.
If any hardware manufacturers are listening, I'd gladly pay $200 for an aftermarket part that lets me control my goddamn wipers.
But I suspect some company cultures are fundamentally broken. Apple started with a one-button mouse, and will probably never make a good mouse. I think tesla has adopted their broken mindset and I think the tesla culture will never make any of us happy.
Personally if the old tesla cars with the wiper control on the turn-signal stalk could just change the two useless auto settings to slow and fast intermittent... that would be SO wonderful.
Great video. Tesla cars would just be so much better with these, it's kind of infuriating.
(Also the rear cross alert pings from my old (MT Sedan) Mazda 3 Astina '14 is something I miss greatly.)
Having said that, the wipers in my LR3'22 work pretty well and I am not really giving it that much thought.
I keep the area clean and wipe the blades down regularly. I do like how easy it is to engage the wiper service mode to be able to lift the blades; no manual required.
There was a time when perhaps I didn't keep the area that clean and found I couldn't really use cruise control on a highway drive without the wipers going nuts in the dry, fortunately it's been a while since I've experienced that - upgraded behaviour, perhaps.
It would seem like you could sense rain hitting the roof through its acoustic signature using a contact piezo mic. That'd probably have a much larger effective sensing area than the IR sensor.
You don't need a large sensor area or complex audio analysis. A spot with a few IR diodes on the windshield is going to get wet if it's raining hard enough to need wipers.
Meanwhile 7? years ago I drove a company Volkswagen Touareg on a ca. 5 hour drive with constantly varying rain conditions the entire time and did not touch the wiper controls beyond initially setting them to Automatic. This is a solved problem.
I can't wait to try this out. I have a plugin installed now but table editing is still clunky. Decent first-party support of md tables is huge (for me) if true.
There are a number of Obsidian plugins that will automatically convert your notes into an actual website. I don't use any but I know they exist. (I don't use them _yet_, I have a future plan to completely remake my website and Obsidian is part of it). Does that fit the bill? Or do you want something more native-feeling?
> Just one year ago, Tim Cook had this to say about RCS: "I don't hear our users asking that we put a lot of energy in on that at this point. […] Buy your mom an iPhone.”
> Long story short, I will believe it when I see it. Apple has a long history of claiming they will support an open standard, then failing to add support. In 2010, Steve Jobs promised that Apple ‘would make FaceTime an open industry standard’. That never happened. More recently, in 2021, Apple promised to open their Find My network to competitors like Tile. Instead, they’ve penalized Tile by additional warnings in front of their app.
Some smoothly disingenuous rhetoric going on there.
WRT FaceTime - turns out video calling had patent encumbrances. Apple was sued for massive amounts as soon as they rolled out FaceTime on their own devices. The VirNetX saga just wrapped up earlier this year. [0]
And Apple has opened up their Find My Network. [1] Other trackers, such as Chipolo, are making use of it. [2] Also, Apple and Google just today published the latest revision of a cross-platform spec to detect unwanted location trackers regardless of which network you’re using. [3]
Personal experience: Bun has been a flawless drop-in replacement for both NodeJS and npm/yarn since I started using it around v0.4. Not only have I had zero issues running it, but it's been WAY faster. No benchmarks, but very noticeable, from "let's start a new build and go grab a coffee while waiting for it" on NodeJS, to "hit run aaaaand it's done."
I haven't thought twice about it. Frankly, I forgot that bun has been happily running behind the scenes for me. I highly recommend anyone using NodeJS to give it a go.
I've worked on several large node.js codebases and builds never took more than a few seconds, def. not "go grab coffee" time, so maybe something else was going on.
I wasn't familiar with BQN. Clicked through, reminded me of APL. "OH", I thought, "I see how you came up with the name." There was a (disproven) urban legend about Arthur C. Clarke's 2001, where "HAL" was secretly a reference to "IBM", where you transpose each letter by one.
H + 1 = I
A + 1 = B
L + 1 = M
Man, BQN is a clever name. Because,
A + 1 = B
P + 1 = Q
L + 1 = M...
...well crap. That theory didn't pan out at all. Needlessly disappointed myself upon hearing that it's short for "Big Questions Notation".
