I have a theory: Japanese car's have excellent reliability, their interiors and design are lacking. If every car in the world is an EV, which due to their relative simplicity tend to be reliable, what remaining unique selling points does eg a toyota have?
Layman, so bear with me. I'm wondering where they got the amino acids and proteins from? I was under the impressino that cells needed them to be "homochiral" to function, and the artificial 'built from scratch' amino acids are 50:50 of each chirality.
In my reading of the NYTimes simplification of this story they mention that the genes were "borrowed from a virus and the ubiquitous microbe Escherichia coli".
Mainly just curious how far they managed to get to the 'from scratch' goal.
Or is what they've done a bit more of an assembly of bits and pieces? Cheers all.
Oh good point, I didn't think of transitive dependencies. A lot of languages i've worked with unfortunately have a 'do not check in the lockfile' culture, and a common 'blow away the lockfile when the package manager gets stuck' workflow, so that does concern me. Perhaps Cargo is better than average though, and the lockfile never needs nuking, providing this safety. This sounds like a good reason to check in the lockfile! Thanks for the response.
I recently ported an old brickout clone I made to Sokol (a C header-based game library). The whole executable is 500kb (macos), surely could be smaller with eg symbols stripped, and it has a whole 3d engine (not that i'm using much more than one custom shader to blit the screen, but it is using 3d engine infrastructure nonetheless). I was impressed that in this day and age such efficiency is still fashionable in some corners. The whole game is about 2mb zipped. Are shameless plugs allowed? If you're curious have a peek! github.com/chrishulbert/brickwarrior
To mitigate supply chain attacks like this, I've taken to specifying exact versions in my Rust cargo.toml, and when importing new crates, select the previous-to-latest version. Is this a reasonable mitigation? It bugs me that Swift deprecates the concept of specifying exact versions, it actively pushes you towards semver which leaves the door open to this.
"All I could think about was how bored I would eventually get" I used to wonder this. I read the religious answer to this relies on the concept of infinitude: what if an infinite god can invent an infinite number of exciting new... things to do?
The traditional concept of an 'embodied' resurrection (as opposed to ghosts playing harps) makes me lean towards: yes (eg the gut is part of the body). Who knows though, it's a fun question!
I don't understand: Who's lending the $2B in situations like this? Wouldn't they be worried that the above situation (company gutted, then going down the drain) is going to play out and they won't get their $2B back? Or is that the root problem with this whole YC submission: banks are being hit by defaults because of this exact problem?
BMW resale values make it very clear: these cars are actively hostile (in many many ways) to their owners the second they go out of warranty. Pity, their interiors are lovely. In the long term, is this strategy going to work out for them? I won't buy another one. I know... anecdata :)
I believe this is already what happens with Volkswagen - recently I had my brakes replaced by an independent mechanic, and they had to charge me $50ish for some software lock as part of the process.
Is it worth mentioning that there are almost countless Chinese EV brands nowadays? I wonder if Apple was really trying. I’m sure it’s difficult, of course, but it seems like every week there’s a new car manufacturer. To quote Clarkson ‘how hard could it be’ ;)
Anyone know if this or similar devices can display information sent from some code I write in, say, rust without drivers or libraries (eg should not be too complicated to write to) on macOS? Could be a lot of fun to be had!
I largely agree with you. I used to work at Cochlear (hearing aid implants) - their "headphone" equivalents actually had neatly replaceable batteries 10 years ago, it's doable! Larger than airpods, to be sure, however i'm sure Apple could shrink them nicely. But... would anyone want the ability to replace batteries? I wouldn't know. I suspect most people misplace them before the batteries go bad.
I have a bee in my bonnet about this software complexity issue. Perhaps it takes large amounts of humility to accept that your job is fairly mundane, and only needs simple code to get the job done? I mean: who wants to turn spanners on a Toyota when you can imagine you're working for NASA, and introduce fascinating new paradigms to your work, that ultimately add complexity. I suspect that's why i've joined so many teams that have tied themselves up in knots of un-grok-able indirection. Another theory I have is that people encounter bad code, and misdiagnose it, identifying the (wrong) solution as needing a big complex architecture.
This is really disappointing. I used to have a fertility tracking app on the iOS App Store, zero data sharing, all local thus private. But, people don’t want to pay $1 for an app, and I can’t afford the marketing drive that an investor-backed company such as this has… and so we end up with situations like this. Pity :(
You say that hamas is no "credible military threat" - may I beg you please reconsider this in light of the 1195 killed when they attacked on October 7? They're no world-class army, to be sure, but it's not like they have no teeth whatsoever...
Anecdata: Recently spoke with a friend's son who graduated compsci a year-ish ago, he reckons none of his year got jobs, now working in a kitchen. (in australia for context). Very sad. For comparison, I graduated just after the dot-com crash, and our year mostly found jobs, just not very good ones, so maybe they're doing worse than we did. Good luck convincing anyone to study compsci any more.
I printed a few for a friend. They seem to work just fine, but if you look close you can see the ‘terraced’ steps in the printing. Probably feels a bit rough. I guess you could smooth that with acetone vapour and ABS filament if so inclined.
The article does talk of it being a relatively simple proposition to embiggen the range with an bigger battery kit if that helps. But yeah, it's not a ton of range.
I'm very positive, however note that when they mention "injection molded polypropylene composite material" - this (i think) is the same material used for Seadoo Spark jetskis. I owned one and had a minor crash, and because this material cannot be repaired, the entire hull needed replacing, it was an insurance write-off. I hope they've thought about how to make this car repairable and not 'disposable' after the first inevitable minor crash. Of course this may not be a fair comparison because jetski hulls are exposed, whereas car chassis' have panels and bumpers.
Speculation: Perhaps Google accelerated the Manifest V3 change to get anti-adblocking 'baked in' and benefitting their interests, before they're forced to sell off Chrome?
As a developer I always found these maths-first approaches to Kalman filters impenetrable (I guess that betrays my lack of knowledge, I dare cast no aspersions on the quality of these explanations!). However, if like me, it helps with the learning curve to implement it first, here's a 1-dimensional version simplified from my blog:
function transpose(a) { return a } // 1x1 matrix eg a single value.
function invert(a) { return 1/a }
const qExternalNoiseVariance = 0.1
const rMeasurementNoiseVariance = 0.1
const fStateTransition = 1
let pStateError = 1
let xCurrentState = rawDataArray[0]
for (const zMeasurement in rawDataArray) {
const xPredicted = fStateTransition * xCurrentState
const pPredicted = fStateTransition * pStateError * transpose(fStateTransition) + qExternalNoiseVariance
const kKalmanGain = pPredicted * invert(pPredicted + rMeasurementNoiseVariance)
pStateError = pPredicted - kKalmanGain * pPredicted
xCurrentState = xPredicted + kKalmanGain * (zMeasurement - xPredicted) // Output!
}